Why can a single high-res image cost more input tokens than a multi-paragraph prompt?

When you send an image to a vision-language model, the model does not look at raw pixels. There is a small image encoder in front of the language model that turns the image into a sequence of tokens, just like a tokenizer turns text into tokens. The language model then reads those image tokens the same way it reads word tokens. The encoder tiles the image. It splits the picture into fixed-size squares, often 512 by 512 pixels, and produces a fixed number of tokens per square. Each square becomes something like 100 to 300 tokens depending on the model. A small picture is one or two squares; a high-resolution photo is many squares; a 4K screenshot can be dozens of squares. The bill follows directly from this. Every image token counts as an ordinary input token at the standard per-token rate. So a single high-resolution image often costs 1000 to 3000 tokens, more than a multi-paragraph prompt. People sending a 4K photo and a one-line question are paying mostly for the image. Providers give you a knob. Most APIs expose a detail parameter, sometimes called resolution or fidelity, that forces the image to be processed at low resolution. In low-detail mode the encoder uses one shrunken tile and emits a few hundred tokens regardless of the source size. That is a big cost cut when you only need the rough scene. For fine-grained tasks like reading text in an image, you need high detail and the higher bill.

Image input to a vision-language model is not free and not flat-priced. The model has an image encoder, typically a CLIP-style or SigLIP-style vision transformer, that processes the image as a sequence of patches and emits an embedding sequence the language model attends to. That sequence is what the API calls image tokens, and every image token is billed at the model's standard input rate. The encoder tiles the image at a fixed resolution per tile, typically 512x512 pixels. A small image fits in one tile. A larger image is split into a grid of tiles, and the encoder also typically adds one low-resolution overview tile so the model sees the whole image at once before attending to the high-resolution detail. Each tile produces a fixed number of tokens, often somewhere between 100 and 300 depending on the model's patch size and any compression in the projector. A 1024x1024 image therefore produces about 4 high-detail tiles plus 1 overview, landing around 1000-1500 tokens. A 4K image produces dozens of tiles and can exceed 5000 tokens. Comparable text would need to be 7500+ words. This matters because input pricing is structured around tokens, not images. A short user question with a 4K photo can cost more than the same model reading the entire text of a long article. Real applications discover this the hard way when they ship a feature that uploads phone-camera photos at native resolution and watch the API bill jump 5-10x. The mitigation lever is the detail or resolution parameter. OpenAI's vision API exposes detail set to low, high, or auto; Anthropic's API distinguishes hi-res from a single small tile internally. In low-detail mode the encoder uses a single down-scaled tile (typically 85 tokens for OpenAI), an order of magnitude smaller than the high-detail path. The right discipline is to choose detail per task: low detail for scene description or rough classification, high detail for OCR, chart reading, or any task where small visual structures carry