Token savings leaderboard
Not all prompt compression is equal. Stripping whitespace might save two percent while removing a redundant few-shot block saves forty. This tool applies each common technique to your actual prompt, measures the tokens it saves, and ranks them — so you spend your effort on the change that moves the bill, not the one that feels tidy.
How it works
The tool tokenizes your original prompt, then applies each technique independently: trimming few-shot examples, shortening verbose instructions to concise equivalents, collapsing whitespace and formatting, minifying embedded structured data, and removing filler phrases. It measures the token reduction from each, ranks them highest-first, and shows the combined result when you stack the ones you enable. Everything runs locally.
Tips and notes
Start at the top of the leaderboard — the biggest single saving is usually few-shot reduction or cutting a redundant instruction block, not micro-edits. But the highest-saving techniques are also the riskiest for quality, so apply them and re-run your evaluation set before shipping. Whitespace and structured-data compaction are nearly always safe and free wins. If your prompt is mostly a fixed system message, also check whether prompt caching makes the whole question moot for the repeated portion. Treat the savings as close estimates and verify behavior, not just token count.