Open DevTools.
Rescale every page to A4, Letter, or a percentage.
Watch nothing get sent anywhere.
Pick a target paper size or a percentage and every page — plus everything drawn on it — scales proportionally to fit. All inside this tab. Zero network requests after the page loads, same rule as every other tool here. Check the Network tab yourself.
Drop one PDF here or click to browse
One file at a time · stays on this device
Honest note: "Fit to size" scales each page uniformly (same factor on both axes, no stretching) so its content keeps its proportions inside the target dimensions — the result page won't always exactly match the target's aspect ratio if the source page's proportions differ. This changes page and content dimensions together; use Crop instead if you want to trim margins without rescaling anything.
Why trust this tool
No accounts
No signup, no email, no watermark. Use it and close the tab.
No limits (for now)
Resize as many pages as your device's memory allows. No artificial caps.
Cropping margins or splitting a PDF too? Both live too.
Trim margins without rescaling content, extract a range or split every page into its own file, or fix pages scanned sideways — same rule: everything stays local. Leave your email and we'll let you know about a Pro batch mode.
Thanks — saved locally for now, we'll be in touch once signups are live.
Rescaling the page itself, not just the view
Resize Pages changes a page's actual MediaBox and CropBox dimensions and its content transformation matrix together, via pdf-lib's page.scale() — so the content genuinely gets bigger or smaller, unlike zooming in a viewer. Pick a standard target (A4, Letter, Legal, A3, A5) or a raw percentage; "fit to size" mode scales uniformly using the smaller of the two axis ratios, so content never distorts even when the source and target aspect ratios don't match.
This is a different operation from Crop, which only changes what's visible without touching page dimensions or scale. Rescaling every page of a long or image-heavy PDF at once is one of the more memory-intensive operations here, since each page's content has to be recomputed — if a big file stalls mid-resize, here's why.