Why a PDF Grows After You Edit It
You removed two pages and the file got larger. That is normal, it has a cause you can name, and there is a way to get the space back.
Written against the Aug 8, 2026 release·what has changed since
You opened a twelve page document, deleted two pages, saved it, and the file is bigger than it was. Nothing is broken. This is a normal consequence of how PDFs are written, and once you know the cause the fix is obvious.
Most editors append rather than rewrite
A PDF can be saved incrementally. Rather than rebuilding the file, the editor writes the changes onto the end and adds a new index saying which version of each object is current. The old objects are still in there. They are simply no longer pointed at.
This is a genuinely good design for its purpose: an incremental save is fast, and it means a signature applied earlier can still be verified against the bytes it signed. It also means that deleting a page adds bytes rather than removing them.
Getting the space back
A full save rewrites the document from the objects that are actually reachable, and everything orphaned is left behind. That is what lossless compression does here: no image is touched and no text is re-rendered, the file is simply rebuilt without the parts nothing refers to.
Rebuild a document losslessly
Choose lossless cleanup or smaller raster pages with an explicit quality trade-off.
If that barely changes the size, the file was already compact and the weight is real content rather than history. At that point the only lever left is rasterising, which trades selectable text for a smaller file and is a decision rather than a cleanup.
- Incremental saves append changes and leave the old objects in place.
- So a file can grow when you remove something from it.
- Removed pages remain in the bytes until the document is rewritten in full.
- A lossless rebuild reclaims the space without touching any content.
Was this article helpful?
Your answer stays in this browser. Nothing is sent to us. See how it works.
Keep reading
Reviewed and maintained by
Novus Stream Solutions Editorial Team
The Novus Stream Solutions Editorial Team maintains Novus PDF Studio's product documentation, tutorials and PDF explainers. The team checks product claims against the current browser-local implementation and tests, prefers primary specifications and vendor documentation, and corrects material errors openly. The byline identifies the responsible organization; it does not imply a named expert or professional adviser.
Privacy note: every tool mentioned in this article runs entirely in your browser. Nothing is uploaded or queued on a server. A PDF stays in the tab unless you explicitly use Save on this device, which stores that session in this browser without storing passwords. More on the how it works page.