Which best explains why a strong VLM miscounts objects and confuses left from right?
A VLM miscounts and confuses left/right because a fixed patch-token budget blurs detail and position, and the training objective rewarded the gist of a scene rather than an exact tally — two causes that compound.
Imagine describing a crowded photo to a friend over a bad phone line. You only get a few seconds, so you say the gist — a busy street, lots of people, some cars. You do not stop to count every person or say exactly who is to the left of whom, because that is not what the conversation rewarded. Now add that the photo arrived blurry, squished into a small thumbnail. Even if you wanted to count, the people near each other smear together and you cannot tell apart five from six. That is a vision-language model. It squeezes the picture into a small fixed set of tiles, which blurs fine detail, and it was trained to capture the overall scene, not to tally. So it confidently says the gist and quietly gets the exact count and the precise positions wrong.
Detailed answer & concept explanation~6 min readEverything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example.
Everything important, quickly.
Frame it as a diagnosis: locate where the information was lost. Walk through the patch-embedding budget as an information ceiling that blurs detail and position when objects crowd. Then layer in the training objective, which rewarded the gist of a scene rather than an exact tally. Use the text-counting test to rule out the language model. Explain why the failure is systematic across vendors, then close with mitigations that target the real cause: higher resolution or tiling, point then count prompting, and offloading exact counts to a specialist detector.
Real products, models, and research that use this idea.
- Gemini 3.1 Pro and GPT-5.5 still miscount objects in cluttered photos and flip left/right on diagrams, despite strong overall scene understanding.
- Document and chart VLMs gain measurable counting accuracy from AnyRes tiling, which spends more patches on dense regions.
- Pixtral and Llama vision models show the same systematic counting gap, confirming it is architectural rather than vendor-specific.
- Production pipelines route exact counts to a dedicated detector (e.g. a YOLO-style model) and let the VLM narrate, rather than trusting its raw tally.
What an interviewer would ask next. Try answering before peeking at the approach.
QWhy does raising resolution or tiling improve counting, and where does that approach stop helping?
Don't say thisRed flags and common mistakes that signal junior thinking. Click to expand.
Red flags and common mistakes that signal junior thinking. Click to expand.
Blaming the language model's math ability. The LLM counts perfectly over text — the loss happens in the vision pathway, where a bounded patch budget blurs detail before the model ever reasons.
The night-before-the-interview bullets. Scan these on the way to the call.
Primary sources. Skim if you want the original framing.
Same topic, related formats. Practice these next.