The quiet default of web tools
Almost every "free online converter" works the same way: your file travels to their server, gets processed by their code, and a result travels back. It feels instant, so it's easy to forget that a copy of your file crossed the internet, sat in someone's queue, and entered their infrastructure — logs, caches, backups and all.
Local-first flips that model. The program comes to you; your data stays put.
What "local-first" means in practice on FileForge
Each FileForge tool is a plain web page plus JavaScript. When you pick a file, the browser's File API hands the page a reference to the file on your disk. Processing libraries like pdf-lib (writing PDFs) and pdf.js (reading them) operate on that in-memory copy. When the work is done, the result becomes a Blob — a local object — and your browser saves it straight to your downloads folder.
At no point is there a server URL to send the file to. Not "we promise not to look" — the pathway simply doesn't exist.
Verify it yourself in thirty seconds
- Open any tool — say, Merge PDF.
- Press F12 and switch to the Network tab.
- Add files and click merge.
- Watch the request log: no requests carry your file. The only network activity is loading the page itself.
We encourage this check. Trust is cheaper when it's verifiable.
What you gain beyond privacy
- Speed. No upload wait, no queue position, no "processing…" spinner tied to someone else's capacity. Your CPU does the work at full speed.
- No artificial limits. Free tiers elsewhere meter usage because servers cost money. Local processing costs us nothing per job, so FileForge has no task caps, watermarks or size paywalls — the ceiling is your device's memory.
- Confidentiality by default. Contracts, medical letters, IDs and payroll files never become someone else's data, so there's no retention policy to read and no breach notification to await.
Honest trade-offs
Local-first isn't magic. Heavy operations use your hardware, so a huge PDF merges at your machine's pace, not a datacenter's. And some features — OCR on scanned pages, keeping text selectable while aggressively compressing — genuinely need engines we haven't built. Where a tool has a limitation, we say so on the tool page itself rather than pretend otherwise.
Why we think this is the future of small file tasks
Browsers have quietly become the most capable runtime on earth: they ship cryptographic hashing, image codecs, PDF parsing and ZIP compression as standard. Once you notice that, the old upload-the-file-to-a-server dance looks like a relic. FileForge is our bet that most everyday file tasks belong where the files already are — on your device.