How to Remove White Margins from a PDF (No Upload) [2026]
White margins on scanned PDFs waste screen space on e-readers and tablets β and make reading unnecessarily difficult. SammaPix PDF Crop removes those margins entirely in your browser using pdf-lib setCropBox, with a live pdf.js preview and per-side control. No upload required. Here is how to do it and what values to use.

Table of Contents
Why white margins on PDFs are a bigger problem than they look
On a 24-inch monitor, a PDF with 15mm white margins on each side looks fine. The screen is large enough that the whitespace around the content does not feel intrusive. But the same PDF on a 6-inch Kindle screen or a 9-inch tablet tells a different story.
PDF viewers on e-readers and tablets display the entire page as defined, including all margins. On a Kindle Paperwhite (1236 x 1648 pixels, 227 ppi), a scanned A4 document with 20mm margins on each side loses roughly 30% of the screen area to whitespace. The remaining 70% renders the content, which means the text is displayed at 70% of what it could be if the margins were removed.
The fix is simple: remove the white margins. I built SammaPix PDF Crop to do exactly this β entirely in your browser, without uploading your document to any server, using pdf-lib's setCropBox and a live pdf.js preview.
Where white margins come from: scanners, apps, and exports
White margins in PDFs originate from three main sources, each with slightly different characteristics:
Flatbed scanner borders
Flatbed scanners capture a fixed area defined by the scan glass. When you place an A4 document on a scanner with a Letter-sized scan area, the scanner captures the full Letter area β including the empty zones around the A4 sheet. These appear as white or light-gray borders in the output PDF. The width of these borders depends on how precisely you positioned the document on the glass.
Phone scanning apps
Apps like Adobe Scan, Microsoft Lens, Google Drive Scan, and Apple Continuity Camera use perspective correction and document detection to automatically crop the captured image to the document boundary. However, they typically add a small padding around the detected edge β a few millimetres β to avoid accidentally clipping content. This padding appears as thin white borders in the exported PDF.
Print-formatted document exports
Academic papers, textbooks, and reports exported from Word, LaTeX, LibreOffice, or InDesign are formatted for print with standard page margins (typically 20 to 30mm on each side). These margins are intentional for the printed page β they improve readability and leave room for binding. On a screen, especially a small one, they serve no purpose and waste space. Cropping them produces a screen-optimized version of the document that the reader can load on their e-reader or tablet.
The e-reader and tablet impact: why margin removal matters there most
PDF viewers on e-readers and tablets differ from desktop viewers in one critical way: they do not automatically reflow text. They display the PDF as-is, at the page dimensions defined in the file. This means white margins are always visible and cannot be hidden by zooming to a column.
Kindle and e-ink devices
Kindles have a built-in margin trimmer for e-books, but for PDFs it does not work reliably β and on the basic Kindle models, it is not available at all. The correct approach is to remove the margins before transferring the PDF. A scanned A4 document with 25mm margins cropped to nearly content-only on a Kindle Paperwhite screen renders the text about 35% larger, making it genuinely readable without zooming or horizontal scrolling.
iPad and Android tablets
On an iPad Pro (11 or 13 inch), the margin waste is less severe β the screen is large enough to absorb 20mm margins without destroying readability. But on a standard iPad or an Android tablet in the 8 to 10 inch range, margin removal still provides a meaningful improvement. More importantly, it eliminates the need to pinch-and-zoom to read content β a friction point that adds up over long reading sessions.
Two-column academic papers: the extreme case
The most dramatic improvement from margin cropping applies to two-column academic papers in PDF format (IEEE, Elsevier, ACM, and similar journal styles). These papers have wide left and right outer margins β often 20 to 25mm β plus the gutter between the two columns. On a tablet, the text in each column is tiny. Cropping the outer margins aggressively (while leaving the center gutter) makes each column significantly more readable without horizontal scrolling.
Remove white margins from your PDF, no upload
Per-side margin control. Live preview updates as you type. Text stays selectable. Works on scanned documents, academic papers, and phone scan exports. Free, no signup.
Open PDF Crop, FreeHow CropBox removes margins without deleting content
The PDF specification defines a set of page boundary boxes. When SammaPix PDF Crop applies your margin values, it uses pdf-lib to set the CropBox on each page. Here is what that means:
- MediaBox β the full physical page size. Unchanged by cropping. For a scanned A4 page, this is 595 x 842 points.
- CropBox β the region of the page that PDF viewers display. When you crop 40 points from each side of an A4 page, the CropBox becomes
[40, 40, 555, 802]β inset from each edge by 40 points. Viewers display only this rectangle.
The white margin areas are hidden, not deleted. The original scanned image is still present in full behind the CropBox boundary. This has two practical implications:
- The operation is reversible. You can always set a new CropBox (or remove it entirely) to restore the original margins. The underlying scan is never changed.
- The file size does not decrease. The margin image data is still present. To reduce the file size of a scanned PDF, run it through PDF Compress after cropping.
Because no content is re-encoded, the operation is instantaneous regardless of page count, and text (including OCR text layers from scanning apps) remains selectable in the output.
How to measure the right crop values
The live preview in SammaPix PDF Crop is your primary tool for finding the right values. But having a starting point helps. Here are reference values for the most common scenarios:
| Source | Typical margin width | Starting crop value (points) |
|---|---|---|
| Flatbed scanner border | 3 to 8mm | 8 to 23 pt per affected side |
| Phone scanning app padding | 2 to 5mm | 6 to 14 pt per side |
| Academic paper (Word/LaTeX) | 20 to 30mm | 57 to 85 pt per side |
| Book chapter (print layout) | 15 to 25mm | 43 to 71 pt per side |
| Presentation export (slide whitespace) | 10 to 20mm | 28 to 57 pt per side |
To convert millimetres to points: multiply by 2.835. A 20mm margin is 57 points. A 25mm margin is 71 points. Leave 5 to 10 points of whitespace on each side as a safety margin β this prevents edge content from being clipped if the document has any slight variation in margins across pages.
How to remove white margins from a PDF, step by step
The full process takes under two minutes for most documents:
- Go to sammapix.com/tools/crop-pdf in Chrome, Safari, Firefox, or Edge. No account required.
- Drop your PDF onto the dropzone. pdf.js renders a live preview of the first page. You can immediately see the white margins and estimate their width relative to the content area.
- Enter starting crop values. Using the reference table above as a starting point, type values for top, right, bottom, and left. For a scanned document with uniform borders, try 30 to 50 on each side first and adjust from there.
- Watch the preview update. As you type, the live preview shows you exactly where the CropBox boundary falls. Adjust each side independently until the visible area starts close to the content with a few points of breathing room.
- Confirm no content is cut off. Scroll through the preview to check different representative pages β the first page, a body page, and the last page β to make sure the margins are consistent and nothing is clipped.
- Click Crop PDF and download. pdf-lib applies the CropBox to all pages. The output is served from browser memory as a Blob. No network request occurs. Transfer the downloaded PDF to your Kindle, tablet, or e-reader app.
Optimizing academic papers for tablet reading
Academic papers are the use case where PDF margin removal has the most impact. Most papers follow a two-column layout (IEEE, ACM, Elsevier, Springer) with wide outer margins β designed for A4 or Letter print with generous whitespace. On a 10-inch tablet, these papers are borderline unreadable without zooming.
Recommended crop values for two-column papers
For standard IEEE or ACM two-column A4 papers (595 x 842 pt page), start with these values and adjust using the preview:
- Top: 50 to 60 pt (removes the running header and most of the top margin)
- Bottom: 50 to 60 pt (removes the running footer with page number and bottom margin)
- Left: 40 to 55 pt (trims the left outer margin)
- Right: 40 to 55 pt (trims the right outer margin)
Be careful not to crop the running headers or footers on the first page β title, authors, and abstract are often formatted differently and extend closer to the edges than the body pages. Check the first and last page in the preview before downloading.
The result
With 50 pt cropped from each side of a standard A4 paper, the visible area increases from 595 x 842 to 495 x 742 points β the content fills about 22% more of each dimension. On a 10-inch tablet at 100% zoom, the text renders noticeably larger. On a 6-inch e-ink device, the improvement is even more pronounced. The paper is still displayed as a two-column layout (cropping does not reflow text), but the text size makes it genuinely comfortable to read without pinching.
Your PDF stays on your device
Per-side margin control. Live preview. No upload, no account, no server. Text stays selectable. Ideal for scanned documents and academic papers optimized for e-readers. Free.
Browser-based vs upload-based margin removal: honest comparison
Here is an objective comparison across the dimensions that matter for this specific use case:
| Dimension | Upload-based (iLovePDF, Smallpdf, Adobe Online) | Browser-based (SammaPix) |
|---|---|---|
| Privacy | Full document uploaded to a remote server before cropping. | File never leaves your device. Verifiable via Network inspector. |
| Live preview | Usually requires uploading first. Preview is server-rendered. | Instant local preview via pdf.js. Updates as you type values. |
| Per-side control | Many tools offer only symmetric margins. Some have per-side on paid plans. | Always per-side β top, right, bottom, left independently. |
| OCR text layer preservation | Depends. Some tools rasterize during crop, destroying the OCR layer. | Always preserved. CropBox does not touch the content stream. |
| File size limits | Free plans cap at 5 to 25 MB. Larger files need a subscription. | Limited only by device memory. No artificial cap. |
| Works offline after page load | No. Requires upload and server processing. | Yes. Cropping works without an internet connection once the page is loaded. |
Other PDF tools that run in your browser
SammaPix offers a full suite of browser-based PDF tools. All of them run locally with no upload and no server processing:
- PDF Crop: set CropBox margins per side β top, right, bottom, left. Live preview. Text stays selectable. No upload. See also the full guide at Crop a PDF Online Free (Trim Margins).
- PDF Compress: after cropping, reduce the file size of your scanned PDF by rasterizing and re-encoding page images at a lower quality. Read the full guide at Compress a PDF online without uploading it.
- PDF Rotate: fix sideways pages before cropping. Rotation is written permanently into the page Rotate property. Read the full guide at Rotate a PDF online without uploading it.
- Remove PDF Pages: delete blank scanner pages or unwanted sections from your scanned document before sending. Thumbnail grid and range input. Read the full guide at Delete pages from a PDF online free.
- PDF Split: extract specific pages or sections from a longer document before cropping. Useful for academic papers where you want to crop and transfer only a specific section.
All your PDF needs, all in-browser
Crop margins, compress, rotate, remove pages, and split PDFs without uploading them anywhere. All tools run locally in your browser via pdf.js and pdf-lib. No server. No signup. No watermark.
FAQ
Why do scanned PDFs have white margins?
Flatbed scanners capture the entire scan bed area, which is always slightly larger than the document being scanned. The area around the document β where the scan bed is empty β appears as white (or occasionally black) borders in the output PDF. These borders are not part of the original document. They are an artifact of how flatbed scanners work: the scan area is fixed, and the document inside it is smaller than the maximum scan dimensions. Removing them is pure cleanup, not content loss.
Why does removing white margins matter for e-readers and tablets?
PDF viewers on Kindle, iPad, and Android tablets display the full page including all white margins. On a 6-inch Kindle screen, a scanned A4 document with 15mm margins on each side loses roughly 25% of the available screen width to whitespace. The text renders smaller to fit the full page. Cropping those margins away forces the viewer to fill the screen with actual content, which increases the effective text size by 20 to 40% without changing the document. For academic papers on two-column layouts with wide outer margins, the improvement is dramatic.
How do I figure out how many points to crop from each side?
Start with the live preview in the SammaPix PDF Crop tool as your guide. A standard white margin on a scanned A4 document is typically between 20 and 50 points wide (1 point equals 1/72 of an inch, so 72 points equals one inch). For a document with visibly thick margins, start with 40 to 50 on each affected side. For thin scanner borders, 10 to 20 is usually enough. Type a value, watch the preview update, and adjust until the visible boundary sits close to the content β leaving 5 to 10 points of safe whitespace is a good practice to avoid clipping.
Will removing white margins reduce the file size?
No. Setting the CropBox via pdf-lib only changes a small dictionary entry in each page object β it does not remove any image data from the file. The full scanned image (including the white margin areas) is still present in the file. The CropBox simply tells viewers to display only the inner rectangle. If you want to also reduce the file size of the scanned PDF, run it through the SammaPix PDF Compress tool after cropping.
Can I remove margins from just some pages, or does it apply to all pages?
SammaPix PDF Crop applies the same margin values to all pages in the document. This is the right behavior for scanned documents where the same scanner border appears on every page. If you need different crops on different pages β for example, a document with both portrait and landscape pages β the current version does not support per-page crop values. For that workflow, consider splitting the document first with PDF Split, cropping each section separately, then merging the results back with PDF Merge.
Does cropping white margins affect the text I can search or select?
No. SammaPix PDF Crop uses pdf-lib setCropBox β it does not rasterize or re-render the page. For scanned PDFs that already consist of images (and whose text was made searchable by OCR), the OCR text layer is preserved exactly as-is. For text-based PDFs, all text remains selectable and searchable. The CropBox only changes what is displayed β the underlying page content stream is completely untouched.
Does this work on PDFs from a phone scanner app like Adobe Scan or Microsoft Lens?
Yes. PDFs exported from Adobe Scan, Microsoft Lens, Google PhotoScan, or any other phone scanning app work the same way. These apps sometimes add thin white borders around the cropped page area, or include slight padding around the detected document boundaries. SammaPix PDF Crop handles these exactly like flatbed scanner borders: drop the PDF, set your margin values in the live preview, and download the tightly cropped version.
How is this different from cropping an image in an image editor?
Image editor cropping permanently removes pixels outside the crop boundary β the content is gone, and the file size typically decreases. PDF CropBox cropping hides content outside the boundary but keeps it in the file β no pixels are removed, and the file size is essentially unchanged. For margin removal from scanned documents, both achieve the same visual result. The PDF approach has the advantage of being completely reversible: you can always set a new CropBox to reveal more or less of the page later. The image approach is destructive and irreversible.