Model reference · open weights

blip2-opt-coco

LLMs Salesforce Image→text 1 build Open weights 3k dl/mo

blip2-opt-coco is an open-weight language model from Salesforce. blip2-opt-2.7b-coco (FP32) weighs 7.7 GB; the smallest configuration that runs it is RTX 3060 12 GB.

  • BLIP-2 is an image-to-text model developed by Salesforce that uses a frozen OPT-2.7b language model and a CLIP-like image encoder connected by a Querying Transformer.
  • The model has 3.9 billion parameters and supports English for tasks such as image captioning and visual question answering.
  • It is released under the MIT license.

Summary of the Salesforce/blip2-opt-2.7b-coco model card, 2026-10-01

What it is

Released bySalesforce
Released2023-02-07
Parameters3.9B
VRAM7.7 GB for the weights

What it runs on

Memory and cards for blip2-opt-2.7b-coco (FP32)

7.7 GBweights, file size
328 MBcache per 1K tokens
1.9 GBruntime overhead, at least
2,048 tokenscontext max
CardRequests at onceContext maxMemory
2K each
RTX 3060 12 GB2all 2K11.6 GB
RTX 4060 Ti 16 GB8all 2K15.4 GB
RTX 3090 24 GB20all 2K23.4 GB
RTX 4090 24 GB20all 2K23.4 GB
RTX 5090 32 GB31all 2K31.0 GB
L40S 48 GB51all 2K44.0 GB
A100 80 GB102all 2K78.2 GB
H100 80 GB97all 2K78.1 GB
RTX PRO 6000 Blackwell 96 GB120all 2K93.8 GB
DGX Spark (GB10) 128 GB unified141all 2K107 GB
H200 141 GB186all 2K138 GB
B200 180 GB242all 2K176 GB
2× RTX 3060 12 GB
tensor parallel
17all 2K11.6 GB a card
Memory needed at each load
Requests at once2K tokens each
110.3 GB
513.0 GB
815.0 GB
1620.4 GB
3231.1 GB
6452.6 GB

One card, with vLLM's small-card settings.

From the model card

What Salesforce says about blip2-opt-coco

Read the model card

BLIP-2 model, leveraging OPT-2.7b (a large language model with 2.7 billion parameters). It was introduced in the paper BLIP-2: Bootstrapping Language-Image Pre-training with Frozen Image Encoders and Large Language Models by Li et al. and first released in this repository.

Disclaimer: The team releasing BLIP-2 did not write a model card for this model so this model card has been written by the Hugging Face team.

Model description

BLIP-2 consists of 3 models: a CLIP-like image encoder, a Querying Transformer (Q-Former) and a large language model.

The authors initialize the weights of the image encoder and large language model from pre-trained checkpoints and keep them frozen while training the Querying Transformer, which is a BERT-like Transformer encoder that maps a set of "query tokens" to query embeddings, which bridge the gap between the embedding space of the image encoder and the large language model.

The goal for the model is simply to predict the next text token, giving the query embeddings and the previous text.

alt="drawing" width="600"/>

This allows the model to be used for tasks like:

  • image captioning
  • visual question answering (VQA)
  • chat-like conversations by feeding the image and the previous conversation as prompt to the model

Direct Use and Downstream Use

You can use the raw model for conditional text generation given an image and optional text. See the model hub to look for fine-tuned versions on a task that interests you.

Bias, Risks, Limitations, and Ethical Considerations

BLIP2-OPT uses off-the-shelf OPT as the language model. It inherits the same risks and limitations as mentioned in Meta's model card.

Like other large language models for which the diversity (or lack thereof) of training data induces downstream impact on the quality of our model, OPT-175B has limitations in terms of bias and safety. OPT-175B can also have quality issues in terms of generation diversity and hallucination. In general, OPT-175B is not immune from the plethora of issues that plague modern large language models.

BLIP2 is fine-tuned on image-text datasets (e.g. LAION ) collected from the internet. As a result the model itself is potentially vulnerable to generating equivalently inappropriate content or replicating inherent biases in the underlying data.

BLIP2 has not been tested in real world applications. It should not be directly deployed in any applications. Researchers should first carefully assess the safety and fairness of the model in relation to the specific context they’re being deployed within.

Ethical Considerations

This release is for research purposes only in support of an academic paper. Our models, datasets, and code are not specifically designed or evaluated for all downstream purposes. We strongly recommend users evaluate and address potential concerns related to accuracy, safety, and fairness before deploying this model. We encourage users to consider the common limitations of AI, comply with applicable laws, and leverage best practices when selecting use cases, particularly for high-risk scenarios where errors or misuse could significantly impact people’s lives, rights, or safety. For further guidance on use cases, refer to our AUP and AI AUP.

How to use

For code examples, we refer to the documentation.

Quoted from the model card on Hugging Face. The full card is behind the Hugging Face link above.

© 2026 AxForge · EU-hosted AI infrastructure Pricing Docs Trust Privacy Terms