Skip to content
DontTouch My Doc.
§01 · Bulletin 100% client-side

Don't touch my doc

Your docs. Your device. No exceptions. Free PDF tools that never upload your files — merge, split and compress entirely inside your browser, while the rest of the internet helps itself to your paperwork.

Start merging How it works
no sign-up · no watermarks · no limits
0
files uploaded
0
accounts required
∞
docs processed
Jump to: Merge. Split. Organise. Compress. Redact. Strip lines.
§02 · Tools

Six tools, zero servers.

Everything below runs inside your browser tab. Close the tab and the files are gone — from us, for real, because we never had them.

Tool · 01

Merge.

Combine any number of PDFs. Drag to re-order, then download one tidy file.

Merge PDFs → Local only
Tool · 02

Split.

Pull pages out of a PDF — one by one, or by custom ranges like "1-3, 5, 8-10".

Split a PDF → Local only
Tool · 03

Organise.

Rearrange, rotate and delete pages. Drag-and-drop thumbnails, bulk-rotate a batch.

Organise pages → Local only
Tool · 04

Compress.

Shrink scanner-sized PDFs so they fit in email and upload forms. Light, medium, or ruthless.

Compress PDFs → Local only
Tool · 05

Redact.

Click-and-drag black boxes over anything sensitive. Text underneath is permanently destroyed.

Redact a PDF → Local only
Tool · 06

Strip lines.

Remove line numbers from court transcripts, legislative drafts, and annotated editions.

Remove line numbers → Local only
§03 · Why we built this

Most PDF tools quietly upload your files to their servers. We thought that was rude.

Contracts, tax returns, resumes, medical forms — people handle their most sensitive documents in the browser. So we made tools that are honest about where the processing happens.

  • 01
    No uploads

    Your files stay on your machine.

    The tool code runs entirely in your browser via WebAssembly. There is no endpoint to upload to, because we never built one.

  • 02
    No accounts

    No email, no password, no "free trial".

    You shouldn't need a login to merge two PDFs. We agree.

  • 03
    No watermarks

    Your document comes out clean.

    No logo in the corner, no "Processed by…" footer, no 2-of-5 page limit nudging you to pay.

  • 04
    No tracking

    We don't know what you're doing here.

    No analytics pixels inside the tools, no third-party scripts peeking at your files. The site is a static bundle. That's it.

§02 · Procedure

Three steps.

Three steps. None of them involve a server.

  1. Step 01 1

    Pick a file.

    Drag a PDF onto a tool, or browse from your device. Nothing is sent anywhere — the tool lives inside this tab.

  2. Step 02 2

    We process locally.

    pdf-lib and PDF.js do the work inside your browser using WebAssembly. Your document stays on your machine.

  3. Step 03 3

    Download the result.

    You get a fresh file to save. Close the tab and the traces of what you did evaporate with it.

§04 · FAQ

FAQ.

Short answers. Anything missing? Tell us.

So you really can't see my files?
Correct. The tool code runs entirely inside your browser. There is no endpoint to upload to and no server-side processing step — the site is a static bundle served from a CDN. You can verify it by opening your browser's network tab while you use a tool.

Is there a file-size limit?
Technically, no. Practically, your browser's RAM is the ceiling. Most modern browsers handle a few hundred megabytes before getting sluggish. If you're working with very large scans, start with Compress.

Why is it free?
Because a flat HTML/JS bundle on a CDN costs us almost nothing to serve, and we plan to show a couple of unobtrusive ads around the content. No paywall, no freemium trap.

Do you support password-protected PDFs?
Not yet. If a file requires a password we'll show a friendly error. Add decrypting your PDF in your native viewer first as a pre-step.

What about OCR, editing existing text, signing?
Not for now. We only ship tools that can run fully on-device: merge, split, organise, compress, redact, and strip line numbers. Editing existing PDF text reliably needs the original fonts; signing needs secure credential handling — both are on the "maybe later" list only if we can do them without a server.