{ "@context": "https://schema.org", "@type": "WebPage", "@id": "https://www.initiumstrategies.com/glossary/token#webpage", "name": "Token", "description": " A small chunk of text models read and write; length limits and cost are usually counted in tokens.", "url": "https://www.initiumstrategies.com/glossary/token", "inLanguage": "en", "dateModified": "2026-09-18T14:13:00.398Z", "datePublished": "2026-09-18T14:13:00.398Z", "isPartOf": { "@id": "https://www.initiumstrategies.com/#website" }, "publisher": { "@id": "https://www.initiumstrategies.com/#organization" }, "mainEntity": { "@type": "DefinedTerm", "@id": "https://www.initiumstrategies.com/glossary/token#term", "name": "Token", "description": " A small chunk of text models read and write; length limits and cost are usually counted in tokens.", "url": "https://www.initiumstrategies.com/glossary/token", "inDefinedTermSet": { "@id": "https://www.initiumstrategies.com/glossary#termset" } } }
A token is a piece of text — often a word fragment — that language models use as their basic unit of input and output. It is useful for understanding context window limits, pricing, and why long documents must be split or summarized.
Whilst “word count” feels intuitive, in practice token counts diverge from words and blow up with code or odd formatting. For example, a short-looking PDF paste still overflows the context window. We often recommend designing chunk sizes and prompts against token budgets, and watching Time to First Token when streaming latency matters.