How PDFNipper Works

Most "free" PDF tools on the internet work by uploading your file to a remote server, processing it there, and sending the result back to you. That means your documents — bank statements, contracts, medical records, tax forms — pass through someone else's computer. Some services retain those files for hours or days. Others don't clearly disclose what happens to your data at all.

PDFNipper works differently. Every PDF operation happens entirely inside your web browser, on your own device. Your files are never transmitted over the internet.

The Technical Architecture

When you upload a PDF to PDFNipper, here's what actually happens:

  1. File reading: Your browser's built-in File API reads the PDF from your device into local memory. This is the same mechanism your browser uses when you attach a file to an email — the file is read locally, not uploaded anywhere yet.
  2. Thumbnail rendering: A JavaScript library called PDF.js (originally developed by Mozilla for Firefox's built-in PDF viewer) renders each page of your PDF as a small thumbnail image. This happens entirely in your browser's memory using a <canvas> element.
  3. Page selection: When you click pages to mark them for removal, that selection state is stored in your browser's memory as a simple list of page numbers. No data is sent anywhere.
  4. PDF reconstruction: When you click "Remove Pages," a JavaScript library called pdf-lib creates a new PDF document containing only the pages you chose to keep. This happens entirely in memory — no server involved.
  5. Download: The new PDF is offered to you as a download using a Blob URL — a temporary link that points to data in your browser's memory. When you close the tab, this data is released.

At no point in this process does your file leave your device. There is no upload step, no server processing, and no temporary storage on our end.

The Libraries We Use

PDFNipper relies on two well-established, open-source JavaScript libraries:

  • pdf-lib — A pure JavaScript library for creating and modifying PDF documents. It can remove pages, merge files, split documents, rotate pages, and more — all without a server. It's actively maintained and widely used.
  • PDF.js — Mozilla's open-source PDF rendering library, the same technology that powers Firefox's built-in PDF viewer. We use it to generate the page thumbnail previews you see in the tool.

Both libraries are loaded only when you actually upload a file, so the initial page load stays fast.

How to Verify This Yourself

You don't have to take our word for it. Here's how to confirm that your files stay private:

  1. Open PDFNipper in your browser.
  2. Press F12 (or right-click and select "Inspect") to open your browser's developer tools.
  3. Click the Network tab. This shows every request your browser makes to the internet.
  4. Upload a PDF and use the tool normally — select pages, remove them, download the result.
  5. Look at the Network tab. You'll see requests for the webpage itself, fonts, and scripts, but you will not see any request that uploads your PDF file.

For an even stronger test: upload a PDF, then disconnect your computer from the internet (turn off Wi-Fi or unplug Ethernet). The tool will continue to work normally, because it doesn't need an internet connection to process your file.

Why This Matters

Privacy isn't just a feature checkbox — it's an architectural decision. When a tool processes files on a server, there are real risks:

  • The server could be breached, exposing your documents.
  • The service could retain copies of your files longer than disclosed.
  • Employees of the service could potentially access your documents.
  • Government agencies could subpoena files stored on the server.
  • The service's privacy policy could change at any time.

With client-side processing, none of these risks apply. Your files exist only in your browser's memory for the duration of your session. There's nothing for us to breach, retain, or hand over, because we never had your files in the first place.

Performance Considerations

Because everything runs in your browser, performance depends on your device:

  • Modern desktop computers handle PDFs up to about 100 MB without issues.
  • Laptops work well for most typical documents (under 50 MB).
  • Mobile devices can process smaller PDFs, but may struggle with very large files due to limited memory.

If you encounter a "file too large" error, it means your browser ran out of available memory. Try using a desktop computer with more RAM, or split the file into smaller sections first.

Questions?

If you have questions about how PDFNipper works or want to report an issue, please visit our contact page. You can also learn more about the project on our about page.