A few months ago I started building something simple: free online tools that do their entire job inside your browser. Today the collection — Napizo — has 15 tools: PDF to JPG, JPG to PDF, PDF merger, PDF compressor, image compressor, image resizer, background remover, QR code generator, word counter, an AI caption generator, an InPage Urdu-to-Unicode converter, an EPUB splitter, and a few more.
The unusual part isn't the tool list. It's the architecture: your files never leave your device. No uploads, no sign-up, no server processing your documents. Here's what I learned building it that way.
Most free tool sites work like this: you upload your file, their server processes it, you download the result. That model has real costs — bandwidth, compute, storage — which is exactly why those sites are covered in ads and paywalls.
Running everything in the browser flips the economics: the user's device does the work, so there is no per-file server cost at all. It also kills the biggest trust question for a tools site — "where did my file go?" — because the answer is verifiable: nowhere.
There's no backend framework. The stack is HTML/CSS/JavaScript plus battle-tested client-side libraries: PDF work runs on pdf.js and pdf-lib entirely in memory; image work uses the Canvas API and Web Workers; OCR for the PSD converter uses Tesseract.js rebuilt into layered files via ag-psd.
"Boring" matters here: fewer moving parts means the tools keep working even on a plain static host, and every tool is auditable by anyone who opens dev tools.
1. Memory on mobile. A phone browser will kill your tab if you load a 100-page PDF into RAM carelessly. The fix: process pages in chunks, release object URLs promptly, and never keep the full decoded document in memory longer than necessary.
2. Trust signals. A free tools site with no company behind it has to earn trust differently: clear privacy copy ("files stay in your browser"), an honest limitations page, and About/Contact/Privacy/Terms pages that read like a real site. We published all of them before caring about SEO at all.
3. Saying what tools CAN'T do. The PSD converter's "editable text layers" are AI-reconstructed via OCR — fonts won't match the original. We say that on the tool page itself. Short-term it costs conversions; long-term it's the only way people come back.
Ship the tool that solves one person's Tuesday-morning problem — compressing a PDF for an email attachment, resizing a photo for a form upload. Boring problems, done instantly, with zero friction. Then make the privacy story the headline, not a footnote.
The full collection is live here if you want to try the tools: https://napizo.netlify.app