The largest publicly available context window now sits at ten million tokens — enough, roughly, to fit a mid-sized company's entire codebase, or several years of a person's email, into a single prompt. It is a genuinely large number, and also, according to usage figures shared by two infrastructure providers on background, mostly theoretical for the traffic actually running through production systems today.
Median context length across one provider's enterprise traffic, per figures shared with ATOMFACE, sits under 200,000 tokens — roughly two percent of the available window. The distribution has a long tail: a small fraction of workloads, mostly in codebase-scale analysis and legal document review, regularly push into the millions. But the bulk of real usage looks nothing like the capability headlines.
Part of the gap is cost. Even with efficiency gains, processing millions of tokens per request is expensive at scale, and most applications don't need to reread an entire history to do their job well — they need the right slice of it. That has driven continued investment in retrieval and memory systems that sit alongside large context windows rather than being replaced by them: instead of stuffing everything into the prompt, a system fetches the relevant fraction and leaves the rest out.
There's a second, less discussed reason usage lags capacity: model behavior over very long contexts is still not fully trusted. Several researchers pointed to a well-documented pattern sometimes called "lost in the middle," where information placed in the interior of a very long prompt gets weighted less reliably than information near the start or end — a problem that has improved substantially with newer architectures but has not disappeared entirely. For applications where missing a buried fact is costly — contract review, medical records, compliance — teams say they still chunk documents and verify retrieval rather than relying on the model to reliably attend to everything in a single enormous pass.
"A ten-million-token window is a real capability and I don't want to undersell it," said one applied research lead at a company building document-analysis tools who spoke on condition their employer not be named. "But 'the model can technically see it' and 'the model will reliably act on it correctly' are different claims, and a lot of our engineering time goes into closing that gap rather than assuming it's already closed."
None of this means the long-context race has been pointless. The headline numbers have dragged down the cost and improved the reliability of much more modest context lengths — the 50,000-to-200,000 token range where most real workloads actually live — as a byproduct of labs competing at the extreme end. It's a familiar pattern in hardware and infrastructure: the benchmark-chasing frontier capability turns out to matter most for what it does to the median, not for how often it's used at its own extreme.