I Built CrabPDF: a Privacy-First PDF Editor That Runs Locally in the Browser

Pucyta — Mon, 27 Apr 2026 17:11:28 +0000

PDF tools are everywhere, yes.

This is what I believed. But every time I needed to edit quickly a PDF from another computer, I found always the same problems: upload your file, create account, download some software on desktop, pay before to do the useful part, or accept that your document go through a server somewhere.

This felt wrong, especially for documents that maybe contain personal informations, legal things, financial papers, or work files.

So I decided: build CrabPDF.

Why I Built It

Do not think I built CrabPDF because internet needs another PDF tool.

There are already many tools. Use them to merge PDFs, split pages, rotate documents, convert files. Okay, fine.

But the problem is that most of them stop to be simple when you need something more serious. Edit text inside PDF, run OCR, compress the document, apply real redaction... try to do this. You will see.

And privacy? Often is not clear.

Many online PDF editors say "secure" or "privacy-friendly" but still the user must upload the document to a server. For some documents, this is simply not acceptable. Do not do this.

I wanted something different. Open the website. Load a PDF locally. Edit it in the browser. Install it as a PWA. Disconnect from internet. Keep working offline.

This became the core idea.

What Makes CrabPDF Different

Do not upload your file. This is the main point.

CrabPDF process the PDF inside the browser. The core editing workflow does not require to upload the document to a backend server.

This matter because PDFs often contain sensitive data. Contracts, invoices, medical documents, identity documents, work files, these are not files that people should upload casually to a random website. Please, think about this.

With CrabPDF, your file stay on your machine.

The browser load the app, but the document itself is handled locally. This means also you can install CrabPDF as Progressive Web App. Once installed and cached, open it and continue to work even without active network connection.

For me, this is the real privacy angle. Not just "we promise we delete your file later." More like: your file does not need to leave your computer in first place.

Why Browser-Based PDF Editing Is Hard

Do not think PDF editing is simple. It is not.

When you see a paragraph in a PDF, internally maybe it is not stored as paragraph at all. It can be a collection of positioned text fragments, each with own coordinates, font references, transformations, encoding details.

So the editor must handle: detect text positions, map rendered text back to PDF objects, handle embedded fonts, preserve layout, deal with scanned documents, support different PDF producers, avoid broken output files — and make all of this work inside the browser.

Then there is performance. Be careful with this. PDF processing can be heavy.

Final Thoughts

I would not have built CrabPDF if I found quickly a tool that did what I needed.

I wanted a PDF editor that run locally in browser, let me edit real PDF text, support OCR, compress documents, perform true redaction, and work without force me to upload sensitive files or create an account.

This combination was harder to find than I expected.

So I built it. Try it, use it, and send me feedback.

https://crabpdf.com

Do not be shy.

DEV Community: Pucyta

I Built CrabPDF: a Privacy-First PDF Editor That Runs Locally in the Browser

Why I Built It

What Makes CrabPDF Different

Why Browser-Based PDF Editing Is Hard

Final Thoughts