Language Economy · standard corpus · reproducible

The LLM Token Tax: the same sentence, 2–10× the tokens.

Every model splits text into tokens differently. For the same meaning, a German sentence, an Arabic sentence, a Hindi sentence cost far more tokens on some models than others — and tokens are the unit you pay for: API price, GPU time, and the real size of your context window. We measured 9 open tokenizers across 204 languages on 997 parallel sentences (FLORES-200) — including the just-released Kimi K2. This is an efficiency measurement, not a quality one.

204languages measured, one parallel corpus
9open-model tokenizers
10.4×worst-case token tax vs English
$0to reproduce — tokenizer only, no GPU

Leaderboard — average token tax across 204 languages

Mean tokens-per-sentence relative to English, averaged over every language. Lower is better. Big-vocabulary, multilingual-first tokenizers win; 32k-vocab models are the most expensive off English.

Gemma-2256k vocab2.09×
BLOOM250k vocab2.29×
DeepSeek-V3128k vocab2.49×
Kimi-K2163k vocab · new →2.52×
Qwen2.5151k vocab2.75×
Llama-3.1128k vocab3.00×
Llama-232k vocab3.11×
Phi-3.532k vocab3.11×
Mistral-v0.332k vocab3.11×

The full table — token tax by language × model

Each cell = tokens for that language ÷ tokens for the same English sentences. 1.00× = English baseline; 2.00× = twice the cost for the same meaning. Hover a cell for detail.

Qwen2.5Llama-3.1Llama-2Mistral-v0.3Gemma-2DeepSeek-V3BLOOMPhi-3.5
English1.001.001.001.001.001.001.001.00
Chinese1.021.302.021.641.090.960.942.02
Spanish1.521.551.461.581.261.501.211.46
Arabic1.631.663.433.481.501.621.163.43
Hindi4.452.544.624.581.862.821.304.62
Portuguese1.461.481.431.551.231.431.121.43
Russian1.771.641.661.891.401.612.501.66
Japanese1.411.522.242.151.171.431.792.24
German1.551.571.411.571.251.511.681.41
French1.561.581.461.591.341.531.191.46
Korean1.641.493.202.471.641.662.783.20
Italian1.621.631.461.601.331.541.611.46
Turkish1.611.402.082.201.392.021.962.08
Vietnamese1.431.382.932.921.362.111.272.93
Polish1.771.891.711.901.461.692.141.71
Ukrainian2.521.661.731.951.672.182.751.73
Thai2.562.214.374.221.831.784.594.37
Greek4.902.255.015.252.292.703.795.01
Bengali5.055.795.404.932.692.021.185.40
Swahili1.931.931.861.941.601.941.241.86
efficient expensive

The just-released Kimi K2 is in the leaderboard above (4th of 9) and gets its own head-to-head write-up — what a 1-trillion-parameter model's tokenizer actually costs → The heatmap keeps the original eight for readability.

Why this is money, not trivia. Token count is the billing unit and the compute unit. A model with a 1.55× German tax means: German users pay ~55% more per API call for the same content; self-hosting burns ~55% more GPU time and KV-cache per request; and a “128k context window” holds ~55% less German than English. Per-token pricing is, in effect, a hidden surcharge on every non-English language — and this table shows exactly how big it is, per model, on a standard corpus anyone can re-run.

What we are — and are not — claiming

This is efficiency, not quality. A high token tax does not mean a model is “bad” at that language — it means its tokenizer is inefficient there, so that language costs more and fits less context. A model can be excellent at Hindi and still be token-expensive at it; the two are separate measurements and we do not conflate them.

This is a tokenizer measurement, not our internal X-Ray scan. It needs no weights and no GPU — just each model’s public tokenizer — which is exactly why we can run it for every open model, in the open, and why you can reproduce it yourself. Our layer-level X-Ray is a different, deeper instrument; this table is its lightweight companion.

Method (reproducible)

Corpus: FLORES-200 dev — 997 sentences, professionally translated into every language, so each column measures the same meaning. Metric: total tokens per language ÷ total tokens for the identical English sentences, per tokenizer (add_special_tokens=False). Tokenizers: Qwen2.5, Llama-3.1, Llama-2, Mistral-v0.3, Gemma-2, DeepSeek-V3, BLOOM, Phi-3.5 (public, unmodified). One caveat on the corpus: FLORES is news/encyclopedic prose; code, chat and domain text will differ. Token count is a property of the tokenizer, so it is identical across model sizes within a family — a 0.5B and a 32B of the same family tokenize a sentence the same way.

Scan your model → building a multilingual model? See your own language economy before and after you extend the vocab.

← X-Ray for LLMsAll research notes

— Tetracta AI Teams · for humans, like humans.