Contrastive Language-Image Pre-Training for zero-shot visual understanding
- Framework
- HF
- Downloads
- 6.3M
- Benchmarks
- 3
19,428 models
19,428 models
Contrastive Language-Image Pre-Training for zero-shot visual understanding
Sigmoid Loss for Language Image Pre-Training, efficient contrastive learning
Multilingual vision-language encoder with dense features and localization
Self-supervised vision foundation model producing all-purpose visual features
Next-generation self-supervised vision model with Gram anchoring and 6.7B scaling
Open-source CLIP trained on 2B image-text pairs at giant scale
Nine, and they are not the same thing as the catalog. The managed extractors run intfloat/multilingual-e5-large-instruct for text (1024-d), google/siglip-base-patch16-224 for images (768-d), google/vertex-multimodal (1408-d) and google/gemini-embedding-2 (3072-d) for unified multimodal, insightface ArcFace for faces (512-d), CLAP for audio fingerprints (512-d), facebook/dinov2-base for visual similarity and jinaai/jina-embeddings-v2-base-code for code (both 768-d, inside the web scraper). The rerank retriever stage runs BAAI/bge-reranker-v2-m3. Everything else in this catalog is documented here, not hosted here.
Not by naming it. No extractor takes a Hugging Face model id as a parameter, so there is no field to put one in. Three paths do work. Use a managed extractor and get the model it runs. Run the model on your own hardware and upsert the vectors through POST /v1/namespaces/{namespace_id}/documents/upsert, which stores them beside everything else. Or on Enterprise, upload the weights through POST /v1/namespaces/{namespace_id}/models, which accepts the huggingface format, and load them from a custom plugin.
Ask whether a text query has to reach a non-text asset directly. If your video is searchable through its transcript and your images through their captions, a text model over that generated text is cheaper and usually more accurate, because retrieval quality on words is a solved problem and cross-modal alignment is not. If the query is 'find the shot that looks like this' or the visual content carries meaning no caption records, you need a shared space and a multimodal model. Most production systems run both indexes rather than choosing.
A float32 vector is 4 bytes per dimension, so a million items costs 4 GB at 1024 dimensions, 3 GB at 768, and 12 GB at 3072. That is before any quantization and before payload. Models trained with Matryoshka representation learning, such as Gemini Embedding 2, let you truncate to a shorter prefix without re-encoding, so the width becomes an index-time decision rather than a model-selection one. Dimensions are fixed at namespace creation in Mixpeek, so changing a width later means re-indexing.
It is the monthly figure from the HuggingFace API at the time of the last sync, not a live read, so it lags. The sync date is on each model page. Download count is a popularity signal and a poor quality signal: the most-downloaded model in a category is frequently an older checkpoint that a tutorial pinned years ago.
Every model page in one place, 444 in total.