Trimming uniform or independent margins in millimetres
Removing wide scanner borders, printer crop marks, or uneven letterheads requires precise measurements rather than guesswork. Every margin entered in millimetres converts to PDF points using the exact 72 pt per 25.4 mm ratio documented in the MDN Web Docs CSS Length Units Reference, running locally with 0 bytes uploaded.
Using the live first-page preview overlay before saving
When you load a document, the interface renders a 240 px thumbnail of page 1 using a local in-memory blob URL and overlays a darkened mask around the kept area. Leaving Same on all sides checked defaults to 10 mm on every edge, or you can uncheck it to dial in Top, Bottom, Left, and Right independently.
Watching the highlighted boundary shrink in real time prevents clipping running headers or page numbers by accident. Because the thumbnail updates on every keystroke, you can test asymmetric trims on scanned receipts or journal articles before touching the underlying file.
If you want to standardize mixed page dimensions onto A4 or US Letter sheets after trimming excess whitespace, you can scale pages to standard A4 or US Letter sizes in the next step.
Targeting specific page ranges instead of the whole document
Typing a range such as 2-5 into Pages restricts trimming to those leaves while leaving cover sheets or full-bleed figures untouched. Leaving Pages empty applies the exact millimetre trim to every page in the PDF.
Selective cropping is especially helpful when an appendix contains wide landscape charts while the main body carries oversized scanner margins. You can trim the noisy borders on pages 2 through 14 without clipping edge-to-edge diagrams on page 1.
Is cropped content permanently deleted from a PDF?
Cropping a PDF hides everything outside the new visible boundary without erasing underlying text, paths, or images from the file. Viewers clip the display and print output to the updated bounding box, but text located in the trimmed margin can still be copied or found by search tools.
As documented in the Library of Congress PDF Format Description, page boxes act as display viewports over the underlying content stream. If you scanned a two-page book spread and need to separate two-page book scans into individual leaves cleanly, use a dedicated half-page splitter rather than cropping twice.
| Action | Visual appearance | Underlying text searchable? | Suitable for redacting secrets? |
|---|---|---|---|
| Bounding-box PDF crop | Margin hidden on screen and print | Yes, text remains in stream | No, never use for redaction |
| Page rotation | Orientation changes by 90 degrees | Yes, text stays intact | No |
| Explicit page deletion | Entire page removed from catalog | No, page objects pruned | Yes, for whole-page removal |
| Rasterization or redaction | Pixels blacked out or flattened | Removed in redacted zone | Yes, when content is purged |
| Page scaling or resize | Content scaled onto new sheet size | Yes, vector text preserved | No |
How MediaBox, CropBox, TrimBox, and BleedBox interact
PDF geometry relies on nested rectangular coordinate arrays defined in the PDF Association ISO 32000-2 Specification. Understanding how these five page boundaries interact explains why some crop tools produce inconsistent results across desktop viewers, browser tabs, and commercial print RIPs.
Why cropping updates MediaBox and CropBox together
Some editors only shrink CropBox while leaving MediaBox at the original sheet size, causing imposition tools and certain mobile viewers to still report old dimensions. Updating both MediaBox and CropBox to the exact cropped coordinates guarantees uniform page sizes everywhere, and pairs cleanly with Rotate PDF if pages also need orientation fixes.
Updating both boxes also preserves clean thumbnails in operating-system file managers. Downstream layout tools read the new page width and height directly without falling back to oversized white margins.
Why TrimBox, BleedBox, and ArtBox are cleared on save
Because TrimBox, BleedBox, and ArtBox must sit inside MediaBox under PDF geometry rules, leaving old prepress coordinates behind can break downstream validation. Deleting those three optional boxes on cropped pages keeps every page dictionary compliant across print and archival tools.
Handling rotated pages and minimum 28-point safety limits
Scanned batches often mix portrait pages with rotated landscape exhibits, which can invert margins if coordinates are applied naively. Inspecting each page’s rotation flag avoids trimming the wrong side on mixed-orientation packets.
Mapping visual edges accurately on 90, 180, and 270 degree scans
Before subtracting margins, the geometry helper inspects each page’s /Rotate angle and maps your visual Top, Right, Bottom, and Left values into the page’s internal coordinate frame. Trimming 15 mm from the visual top always removes the top edge you see in the preview, powered locally via MDN Web Docs URL.createObjectURL() API.
When preparing trimmed handouts for compact printing, you can also arrange them into multi-page N-up sheet layouts.
Avoiding the 28-point minimum remaining dimension error
To prevent pages from collapsing into invisible zero-width strips, the cropper enforces a 28-point minimum remaining width and height. Whenever negative numbers or all-zero margins are entered, validation catches the mistake before rewriting the file.
Tip: Remember that 10 mm equals roughly 28.35 pt. If you see a minimum-size error on a narrow receipt or ticket, reduce opposite margins so at least 10 mm of content remains on both axes.