Free AI Token Counter: Paste, Count, and Price Your Prompt
Estimated at four characters per token, the same rule the calculator and the optimizer use. Exact counts vary by a few percent between tokenizers. Counted in your browser; nothing is uploaded.
A token counter tells you how many billable units your text will consume before you send it to an API. The counter above is free and private: paste any prompt, document, or code file and the count updates live as you type. There is no signup and no upload. It runs entirely in your browser, so proprietary prompts and confidential documents never leave your machine.
Why two counters disagree
Exact counts vary slightly by model because each provider uses its own tokenizer: OpenAI's GPT models, Anthropic's Claude, and Google's Gemini all split text a little differently. For English prose, the 4 characters per token rule used here lands within roughly 10 to 15% of the true count, which is plenty for budgeting. Code, JSON, and non-English text tokenize less efficiently, so expect real counts to run higher there.
Counting is the diagnosis, not the cure
What separates this from a plain token counter is what happens next. The same count drives the cost calculator, which prices your prompt across every major model at your chosen scale, and the prompt optimizer, which shows how many of those tokens you can delete without changing what the model does. Counting tokens tells you the size of the bill; cutting them is how you lower it.