How Do I Check What's Taking Up the Most Space Inside a PDF?
Direct answer
Use a PDF space-audit or inspection tool to break the file into its components — images, fonts, embedded files, structure overhead — before compressing. BytesPDF's local checker estimates those stored-byte buckets; desktop tools like Acrobat's Audit Space Usage, or free local utilities such as pdffonts and qpdf, offer deeper inspection when needed.
See estimated stored bytes for images, embedded fonts, attachments, metadata and remaining document structure before changing a copy. Run the local PDF space audit
Why this happens
The most direct method is a space audit: Adobe Acrobat's 'Audit Space Usage' report (Save as Other > Optimized PDF) lists the percentage of bytes held by images, fonts, content streams, and document overhead. Seeing 95% images versus 40% fonts leads to completely different fixes.
Free local utilities answer narrower questions without uploading anything: pdffonts (from Poppler) lists every embedded font and whether it is subsetted; qpdf or mutool can expand a PDF's object structure so you can see image streams and their encodings; a hex-level look is rarely necessary for a practical decision.
Be cautious with 'analyze my PDF online' services: uploading a bank statement, medical record, or contract to see its breakdown moves the whole document to a third party. Prefer browser-local or installed tools for sensitive files, and audit a copy rather than the only original.
What each finding usually means
- Images dominate → downsampling and image recompression will help most.
- Fonts dominate → the file was likely edited or merged often; font subsetting/dedup tools apply.
- Attachments dominate → remove or extract embedded files rather than recompressing pages.
- Structure overhead dominates → a clean rewrite (object streams, no incremental history) helps.
- Nothing dominates → the file may already be efficient; strong compression could only add artifacts.
What BytesPDF does
BytesPDF's pre-send checker estimates raw stored bytes for image streams, embedded font programs, embedded-file attachments, metadata streams, other streams, and remaining document structure. The read-only audit runs in browser memory and does not promise that every identified component can be removed safely.
Audit results describe the current file only. After any fix, re-check the output copy: re-encoding can occasionally make an already-efficient component larger.
Related answers and guides
Related privacy-sensitive scenarios
Scenario guides with destination checks for the document you are preparing.
Test your PDF locally
PDF content stays in the browser tab and is not uploaded to BytesPDF servers.