Runs in your browser

Merge, split and fix PDFs without uploading them

PDFNest reads your files with JavaScript inside this tab. There is no upload step, no account, no queue and no watermark. Close the tab and nothing is left behind.

Start here: check a file

Drop one PDF to see its page count, page size, rotation and whether it is encrypted. This is the same engine the tools use, so if the inspector can read the file, the tools can too.

The four tools

Each one downloads a new file; your original is untouched.

M

Merge PDFs

Add as many files as you need, drag their order with the arrows, and read the page count before you commit. The output keeps the original page content and text layers.

Open the merge tool →
S

Split a PDF

Three modes: one file per page, custom ranges like 1-3,5,7-9, or a fixed number of pages per file. Every part downloads on its own.

Open the split tool →
R

Rotate pages

Fix a sideways scan in one click. Rotate every page or only the ones you name, by 90, 180 or 270 degrees, without re-rendering anything.

Open the rotate tool →
#

Add page numbers

Choose the corner, the first number, the font size and a format such as 4 / 12 or Page 4 of 12. Cover pages can be left unnumbered.

Open the numbering tool →

How a job runs

  1. You pick or drop a file. The browser reads the bytes into memory - the same memory the page is already using.
  2. The PDF engine parses the document, copies the pages you asked for and writes a new file structure.
  3. You download the result from a local blob URL. The file is created on your disk by your own browser.

There is no server component to fail, which also means there is nothing to wait in line for. Very large documents are limited by your device's memory rather than by an upload quota.

Guides

Written from real document work, not from a keyword list.

Page order and bookmarks when merging

Why the order you pick matters more than the tool you pick, and which parts of a PDF survive a merge.

Read the guide →

Splitting: pages, ranges, chunks

How to choose between one file per page, a list of ranges and fixed-size batches, with naming that stays sortable.

Read the guide →

Online password removal, carefully

What a password-protected PDF really stores, why upload-based unlockers are risky, and what to do instead.

Read the guide →

Page number typography

Margins, font size and odd/even placement, plus what happens when a document already has numbers.

Read the guide →

Shrinking a scanned PDF

Which levers actually reduce scan size, in the order worth trying, and when the answer is "don't".

Read the guide →

Naming and merging an archive

A simple convention for contracts and invoices that survives a merge and still sorts correctly five years later.

Read the guide →

Questions people ask before using it

Are my files really not uploaded?

Correct. The page never calls a server for your document. You can confirm it: open your browser's network panel, run a merge, and watch that the only requests are for the page's own CSS, JavaScript and any ads that load. The processing happens in the tab and the result is assembled as a blob on your machine.

Why does a merged PDF lose its bookmarks?

Bookmarks live in the document outline, which points at named destinations inside one file. When pages are copied into a new document those destination names have no meaning, so the outline is dropped instead of being left pointing at nothing. Page content, text, images and form fields are carried over.

What happens with a password-protected file?

The engine will usually open files that only carry an owner password, and it will warn you that the output may be wrong. Files that need a password to open cannot be decrypted without the password, and PDFNest will not pretend otherwise. Remove the password in your PDF reader, then come back.

Is there a file size limit?

No fixed limit - the practical limit is your device's memory, because the whole document is held in the tab while it is processed. A 300-page scan of 200 MB can work on a desktop with enough RAM and will struggle on a phone. If a job stalls, close other tabs and try again, or split the work into smaller batches.

Does it work offline?

Once the page and its scripts are cached, yes - there are no runtime network calls. Load the page while online, then the tools keep working if the connection drops.