Handle Sensitive Documents Without Uploading Them

ID scans, medical results, contracts: how FileForge's local-first design keeps sensitive files on your device — and how to verify it yourself in DevTools.

Runs entirely in your browser — no uploads

The threat model, plainly

When you use an upload-based converter, copies of your file exist on: your device, the service's servers (at least transiently), possibly their CDN and backups, and whatever logs they keep. With FileForge, copies exist on: your device. That's the whole list.

This matters most for the documents people are told to protect: passports and ID scans, medical results, tenancy agreements, court paperwork, salary slips. Uploading them to a random free converter is exactly the habit security guidance warns about.

How FileForge enforces this technically

There is no upload endpoint. Tools read your file with the browser's own File API into memory, process it with JavaScript/WASM libraries such as pdf-lib and pdf.js, and hand you back a download via a local blob URL. You can confirm this on any tool page: open DevTools → Network, run an operation, and observe that no request carries your file.

A private workflow for sensitive documents

  1. Merge or split first. Merge PDF and Split PDF rearrange documents without any network involvement.
  2. Fix orientation and order. PDF Page Organizer rotates, deletes, duplicates and reorders pages visually — useful when a scanner produced sideways or duplicated pages of a signed contract.
  3. Shrink before emailing. Compress PDF reduces size locally. Honest caveat: it re-renders pages as images, so text becomes non-selectable — fine for reading copies, less ideal for archival masters.
  4. Inspect unknown files safely. File Inspector shows type and metadata without executing anything, and Image Metadata Viewer reveals GPS coordinates and device info embedded in photos — handy before you share a photo publicly.

What FileForge does not do

  • No accounts, so there is no profile to breach.
  • No file retention, because no file is received.
  • No OCR — scanned pages can't be converted to searchable text; that requires different tooling.

Practical rule of thumb

If a document would embarrass you or harm someone if leaked, process it with tools that can't leak it. Local-first utilities like FileForge make that the default instead of an extra precaution.

Try it now