Written by Sam Taylor — Full-Stack Developer. building web tools for years. Built Formly to replace 15 bookmarked converter sites with one URL. More about me →
When you use a traditional online converter, your file gets uploaded to a remote server, processed there, and downloaded back. But browser-based converters are different — they process everything locally on your device. Here's how that works, and why it matters for your privacy.
Most "free online converters" follow the same pattern: upload → server processes → download. This means your files — including sensitive photos, private documents, and confidential data — travel to a third-party server. The converter site now has a copy of your file. What happens to it afterward? Most privacy policies are vague, and practices vary widely.
Common risks include: files stored on servers for days (or indefinitely), metadata extraction and sale, files used to train AI models without consent, and data breaches exposing uploaded files.
Modern browsers expose powerful APIs that make local file processing possible:
The FileReader API reads the raw bytes of a file you select (via drag-and-drop or file picker). The file data stays in memory and is never sent anywhere. This is the entry point for all local processing.
The Canvas API can decode and encode images. When you load an image onto a canvas (via drawImage), the browser decodes the input format (WebP, PNG, JPEG, HEIC via decoder libraries). You can then export the canvas as a different format using toBlob() or toDataURL(). This is how format conversion works — no server needed.
For formats that browsers don't natively support (like HEIC or specialized compression), converters use WebAssembly — compiled C/C++ libraries running in the browser at near-native speed. WASM enables complex operations like HEIC decoding or PDF rendering without server-side processing.
To keep the UI responsive during heavy processing, browser converters use Web Workers — background threads that handle decoding and encoding without freezing the page. This is what enables batch processing of large files.
| Feature | Server-Based | Browser-Based |
|---|---|---|
| Privacy | Files leave your device | Files stay local |
| Speed | Upload + process + download | Instant, no upload time |
| File size limits | Often capped | Limited by browser memory |
| Works offline | No | Yes (after page load) |
| Format support | Unlimited | Limited by browser APIs |
Three trends are converging to make browser-based tools the default: privacy regulations (GDPR, CCPA) are making server-based file processing more legally complex; browsers are gaining more APIs (WebCodecs, File System Access); and WebAssembly performance is approaching native speeds for image/video processing.
Formly and similar tools represent a shift toward local-first computing — where your data stays on your device, and the web provides the processing logic without the data transfer.
Written by Sam Taylor — Full-Stack Developer. building web tools for years. Built Formly to replace 15 bookmarked converter sites with one URL. More about me →