Multiple Pages Per Sheet — N-Up PDF
Arrange 2, 4, 6, 9, or 16 PDF pages on a single sheet for compact printing.
Drop your PDF file hereTap to select a file
Supports PDF, up to 200MB
What to do next
Related tools
Create Booklet
Generate a booklet imposition layout from your PDF for saddle-stitch or signature-fold printing.
pdfResize PDF
Resize all pages in a PDF to a target paper size with fit, fill, or stretch content scaling.
pdfAdd Blank Page
Insert blank pages into a PDF at the start, end, after a specific page, or at regular intervals.
pdfChange Page Dimensions
Change the canvas dimensions of PDF pages with precise control over content anchoring and page selection.
pdfAbout Multiple Pages Per Sheet
Multiple Pages Per Sheet runs the PDF document workflow job locally inside your browser. Arrange 2, 4, 6, 9, or 16 PDF pages on a single sheet for compact printing. The work happens on your machine, the result is generated on your machine, and the page exposes the controls you need to drive it without burying them in menus.
Reach for Multiple Pages Per Sheet when you need a predictable result on a single file. The page works on the first visit, the controls are visible without a menu, and the output is delivered the moment the engine finishes.
Multiple Pages Per Sheet runs the entire transformation inside your browser. The file is read by JavaScript running in the page, processed in-memory by the open-source pdf-lib JavaScript library, and written back as a download. The browser is the runtime; the page is the interface. You can confirm what the tool does by opening the developer-tools Network tab during a run — the only requests are for the page's own static assets.
Multiple Pages Per Sheet is implemented on top of the open-source pdf-lib JavaScript library. The accepted input formats are PDF, decoded in the browser, processed, and re-encoded into the output format. Files up to 200 MB are well within the comfort zone of any modern browser.
On limits: 200 MB per file is the ceiling. Output formats and quality settings are listed in the controls panel above, and they apply to every run.
Anyone who works with PDF document workflow on a casual basis — researchers archiving reference papers, legal teams preparing exhibit bundles, HR teams handling onboarding documents — finds Multiple Pages Per Sheet a quick way to get the result. The page loads in under a second, the controls are visible from a single screen, and the result downloads or copies in one click.
The output handed back by Multiple Pages Per Sheet is `{name}-nup.pdf`. If you would prefer to keep the result in the browser instead of downloading it, you can copy it from the result panel and paste it directly into another tab — useful when the next tool in your workflow expects pasted text rather than a file.
Multiple Pages Per Sheet is intentionally narrow in what it does, which makes it easy to slot into a longer workflow. Take its output, hand it to whichever next tool fits the job, and Multiple Pages Per Sheet stays out of your way until the next time you need it.
Multiple Pages Per Sheet is built around steady iteration on a small set of options rather than feature creep. Every additional setting attracts a slightly different audience, but a long settings panel makes the common case slower for everyone. The current controls reflect what users of the tool actually use.
A short note on how Multiple Pages Per Sheet came to look the way it does: every iteration started by watching how someone unfamiliar with the tool actually used it, then removing whatever got in their way. That is why the upload area dominates the screen, the run button is bigger than the secondary controls, and the result panel is unmissable when the job finishes.
If you also use a command-line tool for multiple pages per sheet, Multiple Pages Per Sheet is a convenient alternative for the times you are on a different machine or helping someone who is not comfortable in a terminal. The output is a standard file in the format documented above.
A few practical tips that experienced users of Multiple Pages Per Sheet pick up over time. First, keep your default browser updated — the engine relies on standard web APIs and newer browser versions are noticeably faster than ones from a few years ago. Second, close other heavy tabs before processing a large input; the engine shares CPU and memory with whatever else is open. Third, if you re-run the same kind of job often, your last-used settings are remembered for the rest of the tab session, so subsequent runs are essentially one click.
Common gotchas worth flagging: Multiple Pages Per Sheet only accepts PDF, so if your file is in another format you will need to convert it first. The 200 MB ceiling is per-file, not per-session; you can run as many separate jobs as you like, but a single oversized input will be rejected on load.
Open the workspace above to start using Multiple Pages Per Sheet. The engine loads on the first interaction so the page itself stays light, and once the tool is warm it processes subsequent jobs quickly. The moment the page is interactive, the tool is ready to do real work on your file.
How it works
- 1Open the Multiple Pages Per Sheet workspace above. The interface is a single page, so there is nothing to navigate.
- 2Select the PDF file you want to process — drag-and-drop and the file picker both work.
- 3Adjust the options to match what you need. Sensible defaults cover the most common case, so you can usually skip this step.
- 4Click to start the job. The engine (the open-source pdf-lib JavaScript library) processes the input in the page; you can watch the progress indicator until it completes.
- 5Grab the output named `{name}-nup.pdf` as soon as the run completes. You can also copy the result instead of downloading if the next tool in your workflow accepts pasted input.
- 6Run additional jobs as needed. The same controls and defaults apply on every run.
Common use cases
- Add page numbers to a draft report before circulating it for review using Multiple Pages Per Sheet.
- Split a 200-page exhibit bundle into one PDF per exhibit.
- Extract a specific signed page from a long contract bundle.
- Strip blank or test pages from a scanned document.
- Combine a set of references into a single application packet.
- Shrink a scanned invoice so it fits past an email gateway.
- Convert a bundle of flyers into a single archival PDF.
- Compress a marketing deck so the email send-out finishes in seconds.
- Lock a confidential document with a password before sharing externally.
- Rotate scanned pages that came in upside-down from the office scanner.
FAQ
Which layouts are available?
2-up (1×2), 4-up (2×2), 6-up (2×3), 9-up (3×3), and 16-up (4×4) layouts.
Can I add borders?
Yes — toggle page borders on or off to visually separate pages on the sheet.
Page ordering?
Choose left-to-right, top-to-bottom, or column-first ordering for page placement.
Private?
Yes — all layout runs locally.
Output quality?
Content is scaled to fit each cell without quality loss; vector content remains sharp.
Mixed orientations?
Pages are scaled individually to fit their cell regardless of orientation.
Do I need to install anything to use Multiple Pages Per Sheet?
No installation is needed. Multiple Pages Per Sheet runs as a normal web page, with no browser extension, no native helper, and no separate desktop client to download. That is partly a privacy choice — extensions can request broad permissions, while a regular page is sandboxed by default — and partly a convenience one: you can use Multiple Pages Per Sheet on any computer you have temporary access to without leaving anything installed on it.
Can Multiple Pages Per Sheet run inside a corporate firewall?
Multiple Pages Per Sheet is a static page running an open-source engine in your browser, so a typical corporate firewall does not get in the way as long as it allows JavaScript to load from Favtoo. For teams that need to host it themselves on an internal network, the underlying engine (the open-source pdf-lib JavaScript library) is open-source and can be packaged into a private build with the same behaviour. Reach out via the Contact page if that is something you are exploring.
Does Multiple Pages Per Sheet upload my file to a server?
Your file is processed inside your browser by the open-source pdf-lib JavaScript library. The engine reads the file's bytes from your tab's memory, computes the result, and writes the result back into the tab. You can confirm what the page does by opening developer tools and watching the Network tab during a run — the requests you see are for the tool's static assets only.
How fast is Multiple Pages Per Sheet?
Most jobs finish in seconds. Speed scales with input size and with how many CPU cycles your browser tab has available — the engine runs in your browser, so it shares resources with whatever else you have open. For inputs near the 200 MB ceiling, expect anywhere from a few seconds to roughly a minute on a typical laptop. Closing other heavy tabs noticeably speeds things up.
Does Favtoo keep a copy of files I process with Multiple Pages Per Sheet?
Favtoo keeps no copy of your file because Favtoo never receives your file. Multiple Pages Per Sheet runs entirely in your browser, the input is held only in your tab's memory, and closing the tab discards it. There is no opt-in cloud history, no "recent jobs" panel synced to an account, and no server-side retention to configure — the architecture simply has nowhere for your file to be stored.
What does the error message in Multiple Pages Per Sheet mean?
Failures usually fall into one of three buckets: the input is in an unsupported format, the input is over the size cap, or the input is structurally malformed (a truncated download, a partial export, or a stream the engine does not recognise). The first two are easy to confirm — check that your file is one of PDF and that it is below 200 MB. For the third, opening the file in its native viewer first is the fastest way to confirm the source is intact.
Can I trust the output of Multiple Pages Per Sheet for important work?
Multiple Pages Per Sheet is built on the open-source pdf-lib JavaScript library, which is the same class of engine used by professional PDF document workflow pipelines. For deterministic operations, the output is byte-identical to what an equivalent CLI run would produce; for operations involving a codec or a model, the result is well within the range of what comparable tools generate. If you have a specific reference output you need to match, run a small test job first to confirm the configuration produces what you expect.
Which file formats does Multiple Pages Per Sheet accept?
Multiple Pages Per Sheet accepts PDF. If your input is in a format that is not directly supported, convert it first using one of Favtoo's converter tools — every Favtoo converter outputs a file that is a clean input to the next tool in the chain.
Can I call Multiple Pages Per Sheet from a script?
Multiple Pages Per Sheet is a browser-only tool by design and does not expose a hosted API. The reason is the same as the privacy story: there is no Favtoo backend doing the work, so there is no service to call. If you need to script the same transformation, the underlying engine (the open-source pdf-lib JavaScript library) is open-source and can be used directly from your own code.