Consistent physical pages
Make mixed PDF pages use one paper size
Page-size normalization changes the physical page boundary, not the document order. Choose A4, US Letter, Legal, A3, or a custom size. Each accepted source page is embedded structurally, scaled proportionally with Fit, and centered on a new target page. The full page remains visible, although margins can appear when aspect ratios differ.
How the Fit workflow behaves
- STEP 1
Inspect one PDF
The browser checks page count, size groups, orientation, encryption, signatures, and unsupported interactive structures.
- STEP 2
Choose a base size
Select a preset or enter custom millimetres or inches. Landscape sources automatically use the swapped target dimensions.
- STEP 3
Review the rewrite
Download only after checking page totals, target, orientation breakdown, output name, and actual file-size change.
What accepted content keeps
Selectable text, vector drawings, and raster images remain structural page content rather than becoming one rendered page image. This is not OCR and does not add searchable words to scans.
New page boxes
The new MediaBox is the selected target boundary. Original CropBox, BleedBox, TrimBox, and ArtBox values are not copied; the new page boundary becomes the effective output geometry.
Documents V1 rejects
Encrypted or password-protected PDFs, signed PDFs, forms, links, comments and other annotations, bookmarks, and tagged accessibility structures are blocked before normalization rather than silently stripped.
Limits and privacy
One PDF can be up to 100 MiB and 80 pages. Processing uses local browser bytes and does not upload the PDF to FiloTool for page-size processing. Complex files can still exceed available device memory.
Normalization is not compression
Embedding each page into a new page can increase the PDF's byte size. Use PDF Compressor only when reducing bytes is a separate goal. Merge PDF combines documents without standardizing their page dimensions, while Rotate PDF changes viewing orientation rather than physical paper size.
PDF page-size questions
What does PDF page-size normalization change?
It places each existing page onto a new page with the selected physical dimensions. Fit mode scales the full source page proportionally and centers it, so differing aspect ratios can leave margins. Page order and count remain unchanged.
Are portrait and landscape pages kept?
Yes. The selected size is the portrait/base target. Portrait source pages use it directly, while landscape source pages automatically swap the target width and height. The tool does not force all content into portrait orientation.
Which page sizes are supported?
The presets are A4, US Letter, Legal, and A3. Custom width and height can be entered in millimetres or inches; each dimension must be between 1 and 200 inches, or the equivalent 25.4 to 5,080 millimetres.
Why are interactive or signed PDFs rejected?
Embedding a source page preserves its visible structural content but does not reliably preserve links, comments, form fields, bookmarks, accessibility structure, or signatures. Rejecting those PDFs prevents the tool from silently removing important behavior. Geometry changes would also invalidate existing digital signatures.
Can an encrypted PDF be normalized?
No. V1 does not request a password or create an unencrypted replacement. Encrypted and password-protected PDFs are rejected because this workflow cannot safely preserve the source encryption.
Can normalization make a PDF larger?
Yes. Every accepted source page is embedded into a new target-sized page, which adds PDF objects and can increase output size. The result reports original bytes, output bytes, and the measured percentage change without treating growth as compression failure.