TokenPad
RAG

Document Token Profiler

Find which sections of a document are eating the token budget.

Your input

252 characters11 lines0 tokensor drop a file

Document ProfilerExact
0Token change
Token change0no change
Input tokens0what you pasted
Output tokens0what you would send
Token cost of this result
Output tokens0
As input$0.00
× 100K requests$0.00

Everything on this page runs in your browser. Nothing you paste is transmitted, because there is no server here to transmit it to.

Result
 

Density is the signal

Characters per token tells you what kind of content you are looking at. English prose sits near four. Below three means code, tables, identifiers or non-Latin script — content that costs two or three times more per page than the prose around it.

A document that is more expensive than its length suggests almost always has a few dense sections doing it. Finding them takes seconds here and is otherwise invisible.

What to do about a dense section

If it is a table, convert it to CSV — usually a two-thirds reduction. If it is code, consider whether the comments are needed. If it is a base64 blob or a list of identifiers, ask whether the model needs it at all.

For retrieval corpora, dense sections are also the ones most likely to chunk badly, so profiling doubles as a chunking sanity check.

Frequently asked questions

Are these counts exact?
No — they are estimated from character length so that profiling many sections stays fast. Use the token counter for an exact figure on the whole document, or on any section you decide to act on.
What section size should I profile by?
Markdown sections for documentation, paragraphs for prose, lines for structured data or logs. The right granularity is whatever unit you could actually remove or rewrite.

More rag tools