DEV Community

AI Notes
AI Notes

Posted on

Why We Built a Privacy-First Image Processing Tool (And Why You Should Too)

Most online tools upload your files to their servers. We built ToolVault to change that — processing everything locally in the browser with WebAssembly.

The Problem

When you use an online image converter or PDF tool, your files are uploaded to someone else's server. For personal photos, that's probably fine. But for client assets, contracts, or sensitive documents? That's a privacy risk.

Our Solution

ToolVault processes 32 different tools entirely in your browser:

  • Image conversion: HEIC, AVIF, WebP, JPG, PNG
  • PDF tools: Merge, compress, convert
  • QR codes: Generate, read, batch process

Everything runs on WebAssembly with no server involvement. Your files physically never leave your device.

Technical Stack

  • SvelteKit (static-first)
  • @jsquash WASM codecs
  • IndexedDB for file storage
  • Web Worker pool for concurrent processing
  • PWA installable as standalone app

Why It Matters

Privacy isn't just a feature — it's the architecture. No servers means no bandwidth costs, which means we can keep it free forever.

Try it: https://toolvault.top

webdev #javascript #privacy #opensource

Top comments (0)