Gemma 4 E 2B It, built by Google, excels at tasks such as text generation, coding, and reasoning, thanks to its Dense and Mixture-of-Experts architectures. Notably, it features an extensive context window of up to 131,072 tokens, allowing it to process and understand large amounts of text.
Input
Output
Context
131K
Max Output
8K
Parameters
5.1B
Input Modalities
Output Modalities
Loading capabilities…
Estimates based on INT8 quantization at up to 32K context. A count above one assumes tensor parallelism across the cards. Actual requirements vary by framework and configuration.
The creator's other models in the catalog, with their context, size and license where published.
Put this model beside its alternatives on the same evidence, or go back to the full catalog.
Answered from the entry's own fields: context, license, modalities, evidence, serving and the memory to self-host.
Gemma 4 E2B IT advertises a context window of 131,072 tokens, with a maximum output of 8,192 tokens in a single response. The figure is the creator's published maximum; a given provider may serve less, and the gateway routes on what each provider actually serves.
Yes. Gemma 4 E2B IT is an open-weight model released under the Apache 2.0 license, so the weights can be downloaded and self-hosted within that license's terms.
Gemma 4 E2B IT accepts Text, Image and Audio and produces Text, Image and Audio. The capabilities card on this page lists which API features each deployment honours, such as function calling and structured output, with the source each was checked against.
Gemma 4 E2B IT has published results from Artificial Analysis, shown by suite in the benchmarks card above exactly as the publisher reported them. Scores are not combined across suites, and a suite that has not measured Gemma 4 E2B IT is shown as not available rather than estimated.
Not on the managed pool today; Gemma 4 E2B IT is listed for reference and comparison. Connect your own provider key or endpoint that serves it and the gateway runs it on your account, with routing decisions recorded the same way.
About 5.4 GB at INT8 for the weights and a default context, from the catalog's 5.1B parameter count; FP16 needs roughly twice that, and long contexts or many concurrent requests add KV cache on top. The GPU section on this page lists cards that hold it, and the capacity planner sizes it for your context length and traffic.
Fields collected from public registries, provider APIs and benchmark publishers, each tagged with its source.
Last updated: Nov 6, 2026
One gateway in front of every model, with your policies applied and every decision on record. Start on the free plan with 5,000 requests a month, no card required.