Uncategorized

Post5

Gemma 3n model card

Model PageGemma 3n

Resources and Technical Documentation:

Terms of UseTerms
Authors: Google DeepMind

Model Information

Summary description and brief definition of inputs and outputs.

Description

Gemma is a family of lightweight, state-of-the-art open models from Google, built from the same research and technology used to create the Gemini models. Gemma models are well-suited for a variety of content understanding tasks, including question answering, summarization, and reasoning. Their relatively small size makes it possible to deploy them in environments with limited resources such as laptops, desktops or your own cloud infrastructure, democratizing access to state of the art AI models and helping foster innovation for everyone.

Gemma 3n models are designed for efficient execution on low-resource devices. They are capable of multimodal input, handling text, image, video, and audio input, and generating text outputs, with open weights for instruction-tuned variants. These models were trained with data in over 140 spoken languages.

Gemma 3n models use selective parameter activation technology to reduce resource requirements. This technique allows the models to operate at an effective size of 2B and 4B parameters, which is lower than the total number of parameters they contain. For more information on Gemma 3n’s efficient parameter management technology, see the Gemma 3n page.

Inputs and outputs

  • Input:
    • Text string, such as a question, a prompt, or a document to be summarized
    • Images, normalized to 256×256, 512×512, or 768×768 resolution and encoded to 256 tokens each
    • Audio data encoded to 6.25 tokens per second from a single channel
    • Total input context of 32K tokens
  • Output:
    • Generated text in response to the input, such as an answer to a question, analysis of image content, or a summary of a document
    • Total output length up to 32K tokens, subtracting the request input tokens

Citation

@article{gemma_3n_2025,
    title={Gemma 3n},
    url={https://ai.google.dev/gemma/docs/gemma-3n},
    publisher={Google DeepMind},
    author={Gemma Team},
    year={2025}
}

Model Data

Data used for model training and how the data was processed.

Training Dataset

These models were trained on a dataset that includes a wide variety of sources totalling approximately 11 trillion tokens. The knowledge cutoff date for the training data was June 2024. Here are the key components:

  • Web Documents: A diverse collection of web text ensures the model is exposed to a broad range of linguistic styles, topics, and vocabulary. The training dataset includes content in over 140 languages.
  • Code: Exposing the model to code helps it to learn the syntax and patterns of programming languages, which improves its ability to generate code and understand code-related questions.
  • Mathematics: Training on mathematical text helps the model learn logical reasoning, symbolic representation, and to address mathematical queries.
  • Images: A wide range of images enables the model to perform image analysis and visual data extraction tasks.
  • Audio: A diverse set of sound samples enables the model to recognize speech, transcribe text from recordings, and identify information in audio data.

The combination of these diverse data sources is crucial for training a powerful multimodal model that can handle a wide variety of different tasks and data formats.

Data Preprocessing

Here are the key data cleaning and filtering methods applied to the training data:

  • CSAM Filtering: Rigorous CSAM (Child Sexual Abuse Material) filtering was applied at multiple stages in the data preparation process to ensure the exclusion of harmful and illegal content.
  • Sensitive Data Filtering: As part of making Gemma pre-trained models safe and reliable, automated techniques were used to filter out certain personal information and other sensitive data from training sets.
  • Additional methods: Filtering based on content quality and safety in line with our policies.

Implementation Information

Details about the model internals.

Hardware

Gemma was trained using Tensor Processing Unit (TPU) hardware (TPUv4p, TPUv5p and TPUv5e). Training generative models requires significant computational power. TPUs, designed specifically for matrix operations common in machine learning, offer several advantages in this domain:

  • Performance: TPUs are specifically designed to handle the massive computations involved in training generative models. They can speed up training considerably compared to CPUs.
  • Memory: TPUs often come with large amounts of high-bandwidth memory, allowing for the handling of large models and batch sizes during training. This can lead to better model quality.
  • Scalability: TPU Pods (large clusters of TPUs) provide a scalable solution for handling the growing complexity of large foundation models. You can distribute training across multiple TPU devices for faster and more efficient processing.
  • Cost-effectiveness: In many scenarios, TPUs can provide a more cost-effective solution for training large models compared to CPU-based infrastructure, especially when considering the time and resources saved due to faster training.

These advantages are aligned with Google’s commitments to operate sustainably.

Software

Training was done using JAX and ML Pathways. JAX allows researchers to take advantage of the latest generation of hardware, including TPUs, for faster and more efficient training of large models. ML Pathways is Google’s latest effort to build artificially intelligent systems capable of generalizing across multiple tasks. This is specially suitable for foundation models, including large language models like these ones.

Together, JAX and ML Pathways are used as described in the paper about the Gemini family of models“the ‘single controller’ programming model of Jax and Pathways allows a single Python process to orchestrate the entire training run, dramatically simplifying the development workflow.”

Evaluation

Model evaluation metrics and results.

Benchmark Results

These models were evaluated at full precision (float32) against a large collection of different datasets and metrics to cover different aspects of content generation. Evaluation results marked with IT are for instruction-tuned models. Evaluation results marked with PT are for pre-trained models.

Reasoning and factuality

BenchmarkMetricn-shotE2B PTE4B PT
HellaSwagAccuracy10-shot72.278.6
BoolQAccuracy0-shot76.481.6
PIQAAccuracy0-shot78.981.0
SocialIQAAccuracy0-shot48.850.0
TriviaQAAccuracy5-shot60.870.2
Natural QuestionsAccuracy5-shot15.520.9
ARC-cAccuracy25-shot51.761.6
ARC-eAccuracy0-shot75.881.6
WinoGrandeAccuracy5-shot66.871.7
BIG-Bench HardAccuracyfew-shot44.352.9
DROPToken F1 score1-shot53.960.8

Multilingual

BenchmarkMetricn-shotE2B ITE4B IT
MGSMAccuracy0-shot53.160.7
WMT24++ (ChrF)Character-level F-score0-shot42.750.1
IncludeAccuracy0-shot38.657.2
MMLU (ProX)Accuracy0-shot8.119.9
OpenAI MMLUAccuracy0-shot22.335.6
Global-MMLUAccuracy0-shot55.160.3
ECLeKTicECLeKTic score0-shot2.51.9

STEM and code

BenchmarkMetricn-shotE2B ITE4B IT
GPQA DiamondRelaxedAccuracy/accuracy0-shot24.823.7
LiveCodeBench v5pass@10-shot18.625.7
Codegolf v2.2pass@10-shot11.016.8
AIME 2025Accuracy0-shot6.711.6

Additional benchmarks

BenchmarkMetricn-shotE2B ITE4B IT
MMLUAccuracy0-shot60.164.9
MBPPpass@13-shot56.663.6
HumanEvalpass@10-shot66.575.0
LiveCodeBenchpass@10-shot13.213.2
HiddenMathAccuracy0-shot27.737.7
Global-MMLU-LiteAccuracy0-shot59.064.5
MMLU (Pro)Accuracy0-shot40.550.6

Android Performance Benchmarks with Google AI Edge

Note that all benchmark stats are from a Samsung S25 Ultra with 4096 KV cache size, 1024 tokens prefill, 256 tokens decode.

These numbers will continue to improve while Gemma 3n is in preview.

Weight QuantizationBackendPrefill (tokens/sec)Decode (tokens/sec)Time to first token (sec)Model size (MB)Peak RSS Memory (MB)GPU Memory (MB)
dynamic_int4CPU11812.89.242013924193
dynamic_int4GPU44616.115.1420155043048
  • Model size: measured by the size of the .tflite flatbuffer (serialization format for LiteRT models)
  • The inference on CPU is accelerated via the LiteRT XNNPACK delegate with 4 threads
  • Benchmark on CPU is done assuming XNNPACK cache is enabled
  • Benchmark on GPU is done assuming model is cached
  • Vision encoder is always run on GPU with 512×512 resolution
  • Cpufreq governor is set to performance during benchmark. Observed performance may vary depending on your phone’s hardware and current activity level.
  • dynamic_int4: quantized model with int4 weights and float activations.

 

Author


Avatar