ByHeartAI
Intermediate8 min read

Vision-Language Models

A vision-language model (VLM) is a language model that can take pictures as input: the image is turned into visual tokens that sit in the same context window as your words.

Explain like I'm new to AI

A normal LLM only reads text tokens. A vision-language model also reads pictures. You paste a screenshot and ask "why is this button disabled?" — the model answers from the pixels, not from a caption someone typed.

It does not have eyeballs. A vision encoder (or native early-fusion training) turns the image into a sequence of visual tokens. Those tokens enter the transformer next to "what's wrong here?"

A vision-language model doesn't "see" like we do — it reads an image as a sequence of visual tokens next to your question.

That is why a huge screenshot can blow the context budget — hundreds of visual tokens before you've asked anything.

Mental model

Show a friend a photo and ask a question. They look and talk. A VLM is that, implemented as: photo → numbers → same attention machinery that reads sentences.

How it works

Two common designs:

  1. Encoder + projector + LLM (classic LLaVA-style): a frozen or lightly tuned vision encoder (often CLIP-like) maps the image to vectors; a small projector aligns them to the LLM's embedding space; the LLM generates text.
  2. Native multimodal / omni models: trained from the start on mixed text, image, audio, video so fusion happens earlier — one stack, many input types.

Either way, generation of new pixels is a different family of models (next lessons). A VLM that describes a cat is not the same as a model that paints a cat.

Real-world example

You photograph a restaurant menu in another language. The VLM can translate dishes and flag allergens. For the exact price on the last line, you still want OCR (next lesson) — VLMs paraphrase and sometimes invent a digit.

Technical explanation

Visual tokens are usually patches (or learned queries over a feature map). Higher resolution → more tokens → more prefill cost and more lost-in-the-middle risk if you dump 20 photos. Production tips:

  • Resize / crop to the region that matters (the error dialog, not the whole desktop).
  • Count visual tokens in your context budget.
  • Don't assume the model "saw" small text — if the number must be right, extract it.
  • Images can carry prompt injection (text in the screenshot that says "ignore the user"). Treat pixels as untrusted, like tool output.

Common mistakes

Common mistake

Sending a 4K screenshot of an entire app and expecting the model to notice a 12px error in the corner. Crop. Visual tokens are expensive and attention is finite.

  • Using a VLM as a calculator for numbers printed in a table.
  • Confusing "the model can see" with "the model generated this image."

When to use it

  • Questions about photos, UIs, charts, diagrams — where language alone is missing the scene.

When NOT to use it

  • Pure text tasks; or when you only need the literal characters (use OCR).

Alternatives

  • Caption the image with a smaller model, then a text LLM (lossy cascade); multimodal RAG if the picture lives in a large corpus.

Quick quiz

Question 1 of 3

How does a VLM read a picture?

Question 2 of 3

Why crop a screenshot before sending it to a VLM?

Question 3 of 3

True or false: a model that describes an image is the same as a model that generates one.

Related concepts

  • What is a Context Window?The context window is the maximum number of tokens an LLM can consider at once — its working memory for a single request.
  • What are Embeddings?Embeddings turn information into numerical vectors where similar meanings sit close together, so software can compare meaning with math.

Further reading

NextImage Understanding & OCR

Last reviewed: 2026-09-04 · Written by ByHeart AI · Reviewed by ByHeart AI