Describe why counting and precise spatial relations remain weak spots for capable VLMs
Even strong 2026 VLMs miscount objects and get left/right or above/below relations wrong on cluttered images. Explain the architectural and training reasons behind this, and name one practical mitigation.
Counting and exact spatial relations stay weak because a bounded patch budget blurs detail, and captioning-style training rewarded the scene's gist, not an exact tally — so the skill was never represented or rewarded.
Imagine you are handed a mosaic made of a few hundred tiles and asked how many marbles are in the picture. Each tile averages whatever sits inside it, so when marbles cluster, a tile just shows a vague marble-ish smear and you cannot count them apart. Now imagine that whenever you practiced describing mosaics, you were only ever graded on saying the theme — a bowl of marbles, a sunny garden — never on the exact number. You would get very good at themes and never learn to count, because counting was never what earned you marks. That is a vision-language model. It compresses the picture into a fixed set of tiles, which loses the detail needed to count, and it was trained to nail the theme, not the tally. So it sounds confident and gets the number a little 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.
Separate the two causes cleanly. Walk the representation problem: a bounded patch budget that blurs detail and quantizes position, so crowded objects merge and exact counts and relations are lost before reasoning. Then the training problem: captioning and contrastive objectives reward the gist, never an exact tally, so the skill was never developed. Argue the failure is systematic, not noise. Close with a mitigation ladder from cheapest to most robust: point then count prompting, higher resolution or tiling, and offloading the exact count to a specialist detector while the VLM orchestrates.
Real products, models, and research that use this idea.
- Gemini 3.1 Pro and GPT-5.5 reliably describe a crowded scene yet miscount the objects in it, showing the gap is about counting, not understanding.
- Chart and document VLMs improve markedly with AnyRes tiling, which spends extra patches on dense regions to resolve fine detail.
- Robotics and AR perception stacks pair a VLM for scene understanding with a dedicated detector for exact counts and precise grounding.
- Pixtral and Llama vision models exhibit the same counting and left/right weaknesses, confirming the cause is architectural, not a single vendor's bug.
What an interviewer would ask next. Try answering before peeking at the approach.
QWhy does point then count prompting help even without changing resolution or the model?
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.
Naming only the patch budget and stopping there. The architecture is half the story — the training objective never rewarded an exact tally, so even with detail the model wasn't taught to count.
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.