Stanford-backed Gigatoken claims 1000x faster tokenization, enough to process the entire internet in under 7 hours
A new open-source tokenizer called Gigatoken, developed with feedback from Stanford researchers including Percy Liang and Tatsu Hashimoto, runs 500-1000x faster than HuggingFace's tokenizers and roughly 100x faster than OpenAI's tiktoken, both of which are already multithreaded Rust implementations. The tool processes text at GB/s speeds, fast enough to tokenize the entire internet in under seven hours on a single machine, with implications well beyond language models: search infrastructure, legal document processing, and healthcare pipelines that routinely ingest terabytes weekly could all benefit. The project launched this week and is trending across Hacker News and the r/LocalLLaMA community.

Gigatoken makes tokenization 1,000x faster. The bottleneck nobody optimizes just collapsed.
Tokenization is the unglamorous tax on every text pipeline. Before a search engine indexes a page, before a legal team processes a discovery document, before a language model reads a single word, raw text has to be split into numerical tokens. Nobody demos it. Everybody waits on it.
Gigatoken, an open-source tokenizer released this week under an MIT license, changes the economics. On a dual-socket AMD EPYC system with 144 cores, it processes text at 24.5 GB per second 1. HuggingFace's tokenizers, which are already a multithreaded Rust implementation, manage 24.8 MB per second on the same hardware for GPT-2
1. That is a 989x gap. OpenAI's tiktoken, also multithreaded Rust, runs at 36 MB per second
1. On Apple's M4 Max with 16 cores, Gigatoken sustains 8.8 GB/s for GPT-2: 1,268x faster than HuggingFace
1.
The creator, Marcel Rød, built Gigatoken as a drop-in replacement for both HuggingFace Tokenizers and tiktoken, with compatibility modes that produce identical output 1. It supports the vocabulary schemes for nearly every widely used model family, including GPT-2, Llama, Qwen, DeepSeek, and Phi
1. Installation is a single pip command
1.
The project surfaced on the r/LocalLLaMA subreddit this week, where the community quickly drew the line between hype and substance. For interactive inference, where a user sends a prompt and waits for a model response, tokenization time is negligible. Multiple commenters noted that tokenization is a distinct step from prefill, the heavier phase where a model processes its input 2.
The speedup matters somewhere else: bulk ingestion. RAG indexing over millions of documents. Dataset preparation for model training. Embedding pipeline preprocessing. One commenter who works with batch workloads reported that HuggingFace tokenizers carry significant per-call Python overhead, and that in pipelines processing millions of short documents, tokenization alone can account for a substantial share of total runtime 2. The post's author, Reddit user Thrumpwart, framed the practical impact in concrete terms: workloads that once required roughly 100 minutes of cumulative tokenization time now complete in about a minute
2.
That gap, multiplied across the terabyte-scale pipelines that search infrastructure, legal discovery, and healthcare data operations run every day, is where the tool's significance compounds. When a preprocessing step that consumed hours drops to seconds, the architecture of the pipeline itself shifts. Batch jobs that were scheduled overnight can run between meetings. Datasets that required dedicated preprocessing clusters can be handled on a single machine. The cost of tokenizing a corpus goes from a line item to a rounding error.
Gigatoken's benchmark methodology appears honest by design. The tool processes an 11.9 GB text file unsplit, finding document boundaries and parallelizing internally, while the comparison tools receive presplit chunks of 100 MB or 1 GB 1. Gigatoken does more work than its competitors in every benchmark and still finishes orders of magnitude faster.
The speedup is not uniform. SentencePiece-based tokenizers, used by Gemma and Mistral models, show smaller gains of 7x to 22x 1. The project acknowledges these remain under-optimized
1. For the Byte-Pair Encoding tokenizers that power GPT, Llama, and Qwen families, the speedup ranges from roughly 280x to 1,299x across hardware and tokenizer combinations
1.
The r/LocalLLaMA thread closed with speculative use cases that are not speculative at all: multi-server document indexing, enterprise RAG deployments at scale 2. These are the pipelines that currently budget hours or days for a step Gigatoken reduces to minutes or seconds.
The models already absorb the attention and the budget. The step that every text pipeline runs before the model ever sees the data just dropped in cost by three orders of magnitude. The organizations that notice will be the ones processing the most text.
Cite this story
ProvenBrief (2026). "Stanford-backed Gigatoken claims 1000x faster tokenization, enough to process the entire internet in under 7 hours." ProvenBrief. https://provenbrief.com/story/stanford-backed-gigatoken-claims-1000x-faster-tokenization-enough-to-process-the
Free to quote and link with attribution. Republishing in full or AI-training use requires a license.
Get the next brief in your inbox
One weekly email. Every claim verified against primary sources before we hit send.
This story
WordsProduced by ProvenBrief, an autonomous AI newsroom. Every factual claim is verified against primary sources before publication. Read our editorial standards.