If you’ve compared AI assistants lately, you’ve seen the context window numbers: 128k tokens, 200k tokens, even a million. The assumption is simple: bigger number means more text. But tokens aren’t words, and the difference costs you planning time, wasted prompts, and truncated outputs when you hit limits mid-task.
Here’s the operator math you actually need, and when context size stops mattering.
What a token actually represents
A token is the smallest unit an AI model processes. In English, one token averages about 0.75 words—or four characters including spaces. That’s a rough average; actual token counts vary by language, punctuation density, and formatting.
A 200,000-token context window holds approximately 150,000 words of plain English prose. If you’re pasting code, JSON, or heavily formatted text, that number drops. A 10,000-word article with embedded HTML might consume 15,000 tokens.
Most AI platforms show token counts in their UI. Claude displays input and output token usage in the bottom-right of each conversation. ChatGPT Enterprise and API users see similar breakdowns. If you’re on a free or standard plan without token visibility, assume 1.3–1.5 tokens per word for mixed-format content.
When context size actually matters
You’ll hit context limits in three scenarios: long-document analysis, multi-file projects, and iterative editing.
Long-document analysis is straightforward. If you’re summarising a 40,000-word research report, you need at least 53,000 tokens just for input—plus headroom for your prompt and the model’s response. A 128k-token window gives you margin; a 32k window forces you to split the document and lose cross-section coherence.
Multi-file projects stack quickly. Pasting three blog drafts (3,000 words each), a style guide (2,000 words), and a content brief (1,500 words) consumes roughly 13,000 tokens before you’ve written a single instruction. If you’re working in Claude Projects or OpenAI’s persistent threads, every message you add stays in context until you hit the ceiling.
Iterative editing is the silent token drain. Each reply—yours and the model’s—adds to the running total. A 10-turn conversation about rewriting a landing page can burn 30,000 tokens even if the page itself is only 800 words. When you hit the limit, the model drops the earliest messages to make room. If those early messages contained key instructions or reference material, the model’s output quality degrades without warning.
The non-obvious cost of going wide
Larger context windows let you load more material, but they don’t guarantee better output. Models perform best when the input is relevant and structured. Dumping six unrelated PDFs into a 200k-token window often produces worse results than curating two directly applicable documents in a 32k window.
Context size also correlates with cost. Claude’s API charges $3 per million input tokens for Sonnet 3.5 and $15 per million for Opus. A single 150,000-token conversation costs $0.45 in input alone on Sonnet—or $2.25 on Opus. If you’re running dozens of long-context sessions per week, the bill adds up faster than most solo operators expect.
There’s a practical ceiling, too. Reading and synthesising 150,000 words takes a human hours. If you can’t review the source material yourself, you’re trusting the model’s interpretation without verification. That’s fine for low-stakes summaries; it’s risky for client work, legal documents, or anything you’re publishing under your name.
How to manage context in real projects
Start with the smallest viable input. If you’re editing a blog post, paste the post and your edit brief—not your entire content archive. If the model needs more context, you can add it in follow-up messages.
Use reference documents strategically. Instead of pasting a 50-page brand guide, extract the three sections relevant to your current task: voice, formatting, and example snippets. Reattach the full guide only if the model’s output misses the mark.
For multi-document work, create a structured index. If you’re analysing five competitor landing pages, paste each page with a clear heading: “Competitor A – Landing Page.” Then ask the model to compare specific elements—headlines, CTAs, pricing tables—rather than requesting a general summary. Narrow questions produce tighter answers and burn fewer tokens per insight.
In long conversations, periodically summarise and restart. After 15–20 turns, ask the model to summarise decisions and next steps, copy that summary into a new conversation, and continue from there. You’ll lose some nuance, but you’ll avoid the drift that happens when early context gets pushed out of the window.
When to ignore context size entirely
If your typical AI tasks are under 5,000 words of input—drafting emails, rewriting headlines, generating social captions—context window size is irrelevant. A 32k-token window gives you 24,000 words of headroom. You’ll never hit it.
Same goes for structured workflows. If you’re using AI to generate product descriptions from a CSV template, each task is isolated. A 4k-token window is plenty.
Context windows matter most for operators doing research synthesis, long-form editing, or multi-session projects. If that’s not your work, optimize for model quality and cost instead.
Want breakdowns like this in your inbox? Subscribe to One Two Three Send for weekly deep-dives on the tools and workflows that actually move online businesses forward.
Heads up — some links in this article are affiliate links. If you sign up through them, we may earn a small commission at no extra cost to you. We only recommend tools we use ourselves.