PDF & Documents100% Free for AllClient-Side PrivateAuto-saved (3 days)

PDF Page Counter & Compressor Info

Analyze PDF documents, verify page dimensions, check encryption status, and optimize document structure client-side.

Upload PDF to inspect & optimize

Fast client-side inspection. Check page count, size, and metadata.

This tool inspects a PDF rather than re-compressing it: it reports the page count, file size, title, and author so you can see what you are dealing with before deciding how to shrink it. It does not re-encode the images inside the file, because doing that properly needs image codecs that pdf-lib does not provide. What follows is the approach that actually works, using the tools available here.

How to inspect a PDF and reduce its size

Upload the PDF to see its page count, size, and metadata.
Work out where the weight is: if the page count is low but the file is large, the pages are scans or contain high-resolution images.
Remove what you do not need. Use the Split PDF tool to extract only the pages you actually have to submit — this is usually the single biggest reduction available.
If the file is a scan and still too large, rescan the original at 150–200 DPI rather than 600. Reducing the source resolution beats any post-processing.
For a document you generated yourself, re-export it from the original application with image quality set lower.

The PDF Page Counter & Compressor Info runs entirely in your browser — nothing you enter is uploaded, stored, or logged.

When to use this tool

Diagnosing an oversized PDF before you act

A 30MB three-page PDF and a 30MB 200-page PDF need completely different fixes. Checking the page count first tells you which problem you have.

Trimming a document to a submission limit

When a form asks for one page of a statement, extracting that page removes far more weight than any compression setting would.

Checking document metadata before sharing

PDFs carry the title and author from whatever produced them, which sometimes reveals an internal filename or a colleague's name you would rather not send out.

Things worth knowing

Page count against file size is the fastest diagnostic: more than about 1MB per page means the pages are images, not text.
Text-based PDFs exported from Word are already compact. If yours is large and text-only, the cause is usually embedded fonts or an oversized logo.
Rescanning at a lower DPI is more effective than any amount of post-processing, and it does not stack compression artefacts.
Splitting out the pages you need is lossless, unlike image re-compression.

Frequently Asked Questions

How are files processed?

Files are parsed directly in browser memory.

Does this tool actually compress the PDF?

No, and it is worth being clear about that. It inspects the document and reports what is inside it. True PDF compression means decoding every embedded image, re-encoding it at lower quality, and rebuilding the file — which needs image codecs this browser-side library does not include. Anything claiming to do that purely with pdf-lib is re-saving your file and reporting the small difference as a saving.

Then how do I actually make my PDF smaller?

In order of effectiveness: remove pages you do not need with the Split PDF tool, rescan the source at 150–200 DPI instead of 600, or re-export from the original application at lower image quality. For a scan that must keep every page at full fidelity, a desktop tool such as Ghostscript will do genuine image re-encoding.

Why is my PDF so large in the first place?

Almost always embedded images. A page scanned at 600 DPI is roughly sixteen times the data of the same page at 150 DPI, with no visible benefit on screen or in ordinary print.