Tokens per page
Estimating tokens for a PDF, book, or report? Enter the page count to get tokens instantly.
Short answer
About 650 tokens per page — one page ≈ 500 words ≈ 650 tokens.
Standard estimate for a text page. Dense academic pages run higher (up to ~800); sparse pages run lower (~400).
Estimated tokens
≈ 6,500
10 pages × 650 tokens ≈ 5,000 words
| Pages | Tokens (approx.) |
|---|---|
| 1 page | 650 |
| 10 pages | 6,500 |
| 50 pages | 32,500 |
| 100 pages | 65,000 |
| 300 pages (a book) | 195,000 |
| 500 pages | 325,000 |
| 1,000 pages | 650,000 |
Assumes ~500 words per page at 1.3 tokens per word. Scanned PDFs sent as images cost 2–3× more than text extraction — extract the text first when you can.
About 650 tokens for a standard text page (~500 words). Dense pages with small type can reach ~800; sparse pages drop toward ~400.
Roughly 195,000 tokens of plain text — about 150,000 words. That fits inside a 200K context window with a little room to spare.
Yes, if the PDF is sent as images. A page rendered for vision costs roughly 1,100–1,500 tokens before any text is read — 2–3× the text-only cost. Extracting the text first is much cheaper.
About 195 pages of text (128,000 ÷ 650), minus whatever you reserve for the model's answer.
Yes. Tables, code blocks, footnotes, and heavy punctuation all tokenize less efficiently than plain paragraphs, pushing a page above the 650 average.
Copy the text into the free token calculator on the homepage for an exact count, or use the context window checker to see if it fits your model.