Why I built 43+ PDF tools to process files locally in the browser

Aniket Gawande — Sun, 20 Sep 2026 10:34:01 +0000

Most online PDF tools follow the same pattern:

Upload your file → wait for it to process → download it again.

That works, but it also means sensitive documents may leave your device.

I wanted to build the opposite.

Your files. Your device.

1into1 PDF is a privacy-first, local-first suite with 43+ PDF and document tools.

Core workflows process files directly in the browser instead of uploading them to a processing server.

That means users can work with PDFs while keeping their documents on their own device.

Why local processing matters

PDFs often contain sensitive information:

contracts
bank statements
IDs
invoices
legal documents
financial records
confidential business files

For these files, privacy should not depend on trusting another processing server.

Local browser processing changes that model.

Instead of sending the document somewhere else, the browser does the work.

What I wanted 1into1 PDF to offer

Privacy-first processing

Core workflows run locally, so the files stay on the user's device.

No signup required

Users can start using the core tools without creating an account.

No desktop software installation

The suite runs in the browser and can also be installed as a PWA.

Offline-capable workflows

After the application and required resources are loaded, many core tools can continue working without an active internet connection.

Fast local processing

Removing the traditional upload → server processing → download cycle can make many workflows feel much faster.

More than basic PDF tools

The suite currently includes 43+ tools, including:

PDF compression
exact target-size compression
merge and split
OCR
permanent redaction
PII and secrets detection
Bates numbering
PDF sanitization
bank-statement extraction
PDF to Markdown for AI/LLM workflows
PDF to image
image conversion
N-Up
booklet creation
signing
editing
and more
Handling larger files

One challenge with local processing is that every user's device has different hardware and browser resources.

So instead of pretending there is one universal desktop limit, 1into1 PDF uses device-aware capacity guidance.

Pro supports up to 150 MB on mobile and tablet, while desktop can process files beyond 150 MB based on the user's device capacity and the selected workflow.

The main idea

The positioning became very simple:

Most online PDF tools are upload-first.
1into1 PDF is device-first.

The goal is not only to provide lots of PDF tools.

It is to make privacy, speed and low friction part of the architecture itself.

43+ tools. No signup to start. No installation. Local-first. Offline-capable.

You can try it here:

https://www.1into1.com/

I’d be interested to hear how other developers approach local browser processing, especially for large files and memory-heavy document workflows.

DEV Community: Aniket Gawande

Why I built 43+ PDF tools to process files locally in the browser