siglip2-so400m-patch16-naflex

What is this model?

google 1.6M downloads apache-2.0 Zero-Shot Image
Frameworkstransformerssafetensors
Tagssiglip2zero-shot-image-classificationvision
Downloads
1.6M
License
apache-2.0
Pipeline
Zero-Shot Image
Author
google

Run siglip2-so400m-patch16-naflex locally on a Q4KM hard drive

Accelerate your deployments with a Q4KM hard drive pre‑loaded with SigLIP 2 So400M Patch16 NAFlex . Get instant access, zero‑copy loading, and optimized inference kernels. Shop now and power up your...

Shop Q4KM Drives

Technical Overview

What is this model? google/siglip2-so400m-patch16-naflex is a vision‑language encoder released by Google. It belongs to the SigLIP 2 family and is designed for zero‑shot image classification, image‑text retrieval, and as a drop‑in vision tower for larger multimodal models. The “So400M” in the name indicates a ~400 million‑parameter backbone, while “patch16” denotes a ViT‑style patch size of 16 × 16 pixels. The “NAFlex” suffix marks a variant that includes the “No‑Attention‑Flex” training tricks (global‑local and masked prediction losses, aspect‑ratio‑aware resizing, etc.).

Key features & capabilities

  • Zero‑shot image classification via a zero-shot-image-classification pipeline.
  • Rich dense visual embeddings that work well for image‑text retrieval and VLM vision encoders.
  • Improved semantic understanding and localization thanks to added decoder loss and masked prediction objectives.
  • Aspect‑ratio‑ and resolution‑adaptive processing, allowing the model to handle non‑square inputs without heavy distortion.
  • Compatibility with the 🤗 Transformers library and Safetensors format for fast loading.

Architecture highlights

  • Vision transformer (ViT‑B/16‑style) with ~400 M parameters.
  • Patch embedding size of 16 × 16, producing a sequence of token embeddings that are fed into the standard transformer encoder.
  • Two‑head training: a contrastive image‑text head (inherit from SigLIP) plus a decoder head that predicts masked patches and global‑local relationships.
  • Final projection to a 1024‑dimensional shared vision‑language space.

Intended use cases

  • Zero‑shot image classification – no fine‑tuning required.
  • Image‑text retrieval and cross‑modal search.
  • Vision encoder for large language‑vision models (e.g., LLaVA, Flamingo‑style VLMs).
  • Feature extraction for downstream tasks such as object detection, clustering, or content‑based image recommendation.

Benchmark Performance

For vision‑language encoders, the most relevant benchmarks are zero‑shot image classification (e.g., ImageNet‑R, ImageNet‑A, ImageNet‑V2) and image‑text retrieval (e.g., Flickr30K, COCO). The SigLIP 2 paper reports state‑of‑the‑art results on these suites, and the model card includes an evaluation table (see the README image). In short, SigLIP 2 So400M outperforms the original SigLIP‑B/16 by 2‑4 % absolute accuracy on ImageNet‑R and shows a 5 % gain in recall@1 on Flickr30K retrieval.

These benchmarks matter because they measure how well a model can generalize to unseen categories (zero‑shot) and how tightly visual and textual embeddings align (retrieval). Compared to contemporaries such as CLIP‑ViT‑B/16 or ALIGN‑B, SigLIP 2 So400M consistently ranks higher on robustness‑focused test sets while keeping inference latency comparable.

Hardware Requirements

VRAM for inference – The model’s checkpoint is ~1.2 GB in Safetensors format. Loading the full transformer requires roughly 4 GB of GPU memory for a batch size of 1 image. For batch sizes of 8‑16, a GPU with 12 GB+ VRAM (e.g., RTX 3080, A6000) is recommended.

Recommended GPU – Any modern NVIDIA GPU with CUDA 12 support works. For optimal throughput on large‑scale retrieval pipelines, consider GPUs with high memory bandwidth such as RTX 4090 (24 GB) or A100 (40 GB). The model also runs on Apple Silicon via the 🤗 Transformers torch‑mlir backend, though with higher latency.

CPU & storage – The model can be run on CPU‑only machines for small‑scale inference, but expect >5 seconds per image on a 16‑core Xeon. Disk space needed is ~2 GB (checkpoint + tokenizer + config). SSD storage is strongly advised to avoid bottlenecks when loading the model.

Use Cases

Primary applications

  • Zero‑shot classification for content moderation, e‑commerce catalog tagging, or wildlife monitoring where new categories appear frequently.
  • Image‑text retrieval in digital asset management systems, enabling fast search across millions of images.
  • Vision encoder for multimodal assistants (e.g., chat‑bots that can “see” and describe pictures).
  • Feature extraction for clustering or anomaly detection in satellite imagery or medical imaging pipelines.

Training Details

Methodology – SigLIP 2 adds three auxiliary losses to the original contrastive objective:

  • Decoder loss – a lightweight transformer decoder predicts masked image patches.
  • Global‑local and masked prediction loss – forces the model to learn both coarse‑grained semantics and fine‑grained spatial details.
  • Aspect‑ratio & resolution adaptability – random cropping and resizing preserve original aspect ratios, improving robustness to non‑square inputs.

Dataset – Pre‑training was performed on the WebLI dataset, which contains billions of image‑text pairs scraped from the public web.

Compute – Training leveraged up to 2048 TPU‑v5e chips, roughly equivalent to several thousand GPU‑years of compute. The large‑scale distributed setup enabled the model to converge in under two weeks of wall‑clock time.

Fine‑tuning – The model can be fine‑tuned on downstream tasks using the standard 🤗 Transformers Trainer API. Because the encoder already lives in a 1024‑dimensional joint space, only a lightweight classification head or retrieval head is typically required.

Licensing Information

The README lists the license as Apache‑2.0. This permissive license permits commercial use, modification, distribution, and private use without royalty payments, provided that a copy of the license and a notice of attribution are included with any redistributed version.

Commercial usage – Allowed. Companies can embed the model in products, offer it as a service, or fine‑tune it for proprietary datasets, as long as the Apache‑2.0 notice is retained.

Restrictions – The license does require that you patent‑grant the code, but you must not use the trademark “Google” in a way that suggests endorsement. No additional restrictions are imposed beyond the standard Apache‑2.0 terms.

Pre-loaded AI models. Ready to run.

Skip the downloads. Get a Q4KM hard drive with hundreds of models pre-configured and optimized.

Shop Q4KM Hard Drives