Why Hindi and Tamil cost more tokens per word than English

1 November 2026 • 6 min read

In short

  • In Sarvam's 2024 tokenizer table, GPT-4o needs 1.65 tokens per Hindi word and 3.17 per Tamil word, against 1.23 for English. Newer models may differ, so count your own text.

LLM APIs bill by the token, not by the word. A token is a piece of text that the model's tokenizer cuts out of your input. If a language is cut into more pieces for the same sentence, the same message costs more, uses up more of the context window and takes longer to process. For a product serving Hindi and Tamil users, that is a cost line worth knowing before you set a per-user budget. This page checks the claim against published measurements, shows what they say, and tells you what is out of date.

1. Does the claim hold?

Yes, with a large difference between the two languages and between tokenizers. The cleanest published numbers come from a model card by Sarvam AI, an Indian model maker, so they are a vendor's own measurement and should be read that way. The card reports "fertility", which is the average number of tokens per word, for four tokenizers.

LanguageGPT-4oGemma-2Llama-3.1Sarvam-2B
English1.231.231.241.43
Hindi1.651.962.671.4
Tamil3.174.1912.392.17

Tokens per word, from the Sarvam-2B model card (August 2024). Lower is cheaper.

Divide each Indian-language figure by the English figure for the same tokenizer and you get the extra cost of the same number of words. These ratios are our arithmetic:

  • GPT-4o: Hindi 1.34 times English, Tamil 2.58 times.
  • Gemma-2: Hindi 1.59 times, Tamil 3.41 times.
  • Llama-3.1: Hindi 2.15 times, Tamil 9.99 times.

So Hindi is a modest premium on GPT-4o's tokenizer, and Tamil is a large one. Sarvam's own model flips the picture: its Hindi figure of 1.4 is lower than its English figure of 1.43, because the tokenizer was built for Indian languages. In an earlier post on its first model, Sarvam said existing multilingual models often need 4 to 8 tokens per word for Indic scripts, against 1.4 for English. That was Sarvam's description of the models it compared against. Its own table puts Hindi on the other tokenizers between 1.65 and 2.67, below that range, though Tamil on Llama-3.1 is above it.

2. Why it happens

A tokenizer learns its vocabulary from a training text. Common character sequences in that text become single tokens; rare ones are split into smaller pieces. If the text is mostly English, English words get whole-word tokens, while Tamil words are broken into many small fragments.

A NeurIPS 2023 paper by Petrov and co-authors measured this across languages. It found that the same text translated into different languages can differ in tokenized length by up to 15 times in some cases, and that the disparity persists even for tokenizers built for multilingual use. The authors link it to the corpus: tokenizers are heavily influenced by the biases of their source text. A second 2023 paper, by Ahia and co-authors, analysed OpenAI's API on 22 languages and concluded that speakers of many languages are overcharged while getting poorer results.

Both papers used the tokenizers of their day, which are older than the models you will call in 2026, so we do not quote their language-by-language figures.

3. What it does to your bill, context and latency

Three effects, all from the same cause.

  1. Cost. Input and output are priced per token. For the same number of words, a tokenizer with a ratio of 2.58 means 2.58 times the tokens, so 2.58 times the bill on that text.
  2. Context. The context window is also counted in tokens. A Tamil conversation fills it sooner, so fewer past turns or retrieved documents fit.
  3. Latency. More tokens take longer to read and to generate. Petrov and co-authors list processing time and latency, along with cost and context, as places where the gap shows up.

The size of each effect depends on your model. Work it out from your own traffic, not from a table in a blog post.

4. Why the table may be out of date

The Sarvam card dates from August 2024 and covers four tokenizers that were current then. Vendors change tokenizers between model generations. Anthropic's token-counting guide says Claude 4.7 and later models use a newer tokenizer, and that the same input text produces about 30 percent more tokens than on earlier models. That statement is about all text, not Indian languages in particular, but it shows that counts move between generations, and that you should recount against the exact model you plan to call. We found no vendor-published Hindi or Tamil figure for the 2026 models, so the premium for those models is unmeasured here.

5. How to measure it for your product

  • Take a sample of real user messages in each language you serve, plus your system prompt.
  • Count tokens with the vendor's own counter for the exact model ID. Anthropic offers a token-counting endpoint, and says token counting is free to use, within rate limits.
  • Divide by the number of words to get tokens per word. Compare it to the same text in English.
  • Multiply by your expected messages per user per month and the model's per-token price to get a cost per user.
  • Repeat for every model you are considering. The ranking can change between languages.

6. Ways to bring the cost down

  • Choose the model with the tokenizer. If most of your users write Tamil, test an Indic-built model such as those from Sarvam against a frontier model on both quality and tokens. See our Sarvam pricing page.
  • Trim what you resend. System prompts and retrieved passages are billed on every call. Shorten them and cut duplicates. Our LLM costs at scale page covers this.
  • Cap the output. Set a maximum length for answers in the language that costs most.
  • Test the script. Whether Hindi typed in Latin letters ("Hinglish") costs more or less than Devanagari depends on the tokenizer, and none of the sources we read measured it. Test it on your model before you change your interface.

For a cross-vendor view of prices, see the LLM API comparison for India.

Questions people ask

How many more tokens does Hindi use than English?

On GPT-4o's tokenizer, per Sarvam's 2024 table, 1.65 tokens per Hindi word against 1.23 for English, about 1.34 times. Other tokenizers in the same table range up to 2.67 for Hindi.

Is Tamil more expensive than Hindi to process?

On every general-purpose tokenizer in that table, yes: Tamil is 3.17 tokens per word on GPT-4o and up to 12.39 on Llama-3.1, against 1.65 and 2.67 for Hindi.

Do newer models fix this?

We could not confirm it. The published Indian-language figures date from 2024 and earlier. Count tokens on the model you plan to use.

Does token cost mean per-word pricing?

No. Vendors price per token. The per-word figure is a way to compare languages; your invoice follows the token count.

Sources

  1. Sarvam AI, sarvam-2b-v0.5 model card (tokenizer fertility table), August 2024
  2. Sarvam AI, Sarvam-1 announcement, 24 October 2024
  3. Petrov et al., Language Model Tokenizers Introduce Unfairness Between Languages, NeurIPS 2023 (arXiv)
  4. Ahia et al., Do All Languages Cost the Same? Tokenization in the Era of Commercial Language Models, 2023 (arXiv)
  5. Anthropic, Token counting (Claude docs), read 1 November 2026

Nine stories, every morning at 09:15 IST.

Get the brief free →