How to check context window usage before you send
Every model has a fixed context window — the maximum number of tokens it handles in one request. The system prompt, the conversation history, any retrieved documents, your new message and the reply all share that one budget. When the total passes the limit, the API rejects the request or your app silently drops older history. Checking first is cheaper than debugging a truncated reply.
This visualizer does the check in your browser:
- Paste the text — a prompt, a chat transcript, a document you plan to attach. The tool estimates its tokens with a byte-pair-style heuristic and shows the count live as you type.
- Pick the model — nine real models with their published windows, or a custom window for any model not listed. The usage bar shows your text, system prompt, history and output reserve as separate segments.
- Read the verdict — the share of the window used, the tokens remaining, the estimated cost per request, and how many more turns fit. Warnings appear at 50%, 80% and 95%.
- Compare models — the table shows the same text against every listed model, so you can see at a glance which window actually fits it and what each one would cost.
Why a prompt costs more the longer you chat
Each new turn re-sends the entire conversation history as input tokens. A chat that starts at 500 input tokens can reach 5,000 after a dozen turns — and the input bill grows with it, even though you only typed a short message. Long system prompts and retrieved documents add the same way. The "turns left" figure is the practical version of this: how many more messages of a typical size fit before the window runs out.
Honest limitations
The token count is an estimate
Real token counts depend on the model's own tokenizer. This tool's heuristic lands within about 10% on plain English prose and reads a little high on code and JSON, where punctuation is dense. Use the provider's tokenizer for billing.
Prices are indicative list prices
Model prices are the providers' published list prices as of November 2026. Long-prompt surcharges are not applied — Gemini 2.5 Pro, for example, bills prompts over 200,000 tokens at a higher rate. Check the provider's pricing page before budgeting.
Model windows change
Providers raise context windows and launch new models regularly. The nine listed models were verified against published figures in November 2026; if a model you use is missing or its window has grown, use the Custom option and type the published number.
Chat apps add hidden tokens
Chat interfaces wrap your text in formatting, role markers and tool definitions that also consume tokens — typically a few hundred per turn. Treat the estimate as the floor, not the ceiling, of what a real request uses.