2026 Privacy Report: Which Free Online Tools Actually Keep Your Data Local?
Executive Summary
Most free online tools upload your files to remote servers for processing. Your tax documents, private photos, and confidential recordings pass through infrastructure you don't control, stored for durations you can't verify.
A growing category of browser-based tools processes files entirely within the browser tab using the Canvas API, WebAssembly, and WebGPU. No upload. No server queue. No retention.
This report evaluates 28 tools across processing model, network activity during use, and data retention. We tested each by monitoring outbound network requests while processing sample files.
Methodology
For each tool, we:
1. Opened the tool page in Chrome 124 with DevTools Network tab recording
2. Processed a test file (5 MB JPEG for image tools, 12 MB PDF for document tools, 8 MB MP3 for audio tools, 45 MB MP4 for video tools)
3. Recorded all network requests during file selection, processing, and download
4. Categorized each tool into one of three models:
Privacy Model Comparison
| Tool | Type | Processing | Network During Use | Retention | Account Required |
|---|---|---|---|---|---|
| CrunchPix | Image compression | Browser (browser-image-compression + Canvas) | None | None | No |
| FormatFlip | Image conversion | Browser (Canvas API) | None | None | No |
| SizeCraft | Image resizing | Browser (Canvas API) | None | None | No |
| CutoutCraft | Background removal | Browser (@imgly/background-removal) | Model download (once) | None | No |
| SvgMint | SVG optimization | Browser (SVGO via Web Worker) | None | None | No |
| PaperMint | PDF editing | Browser (pdf-lib) | None | None | No |
| FillFox | PDF form filling | Browser (pdf-lib) | None | None | No |
| SliceTune | Audio editing | Browser (FFmpeg WASM) | WASM binary download (once) | None | No |
| ClipShrink | Video compression | Browser (FFmpeg WASM) | WASM binary download (once) | None | No |
| DeskBurn | Pomodoro timer | localStorage | Sync on login only | localStorage + server (if signed in) | Optional |
| Shelvd | Book tracking | localStorage | Sync + Open Library search | localStorage + server | Yes (for sync) |
| PennyScope | Expense tracking | localStorage | Sync on login only | localStorage + server (if signed in) | Optional |
| Typical image compressor | Image compression | Remote server | Full file upload | Varies (minutes to indefinite) | Often |
| Typical PDF editor | PDF editing | Remote server | Full file upload | Varies (24h to indefinite) | Usually |
| Typical video compressor | Video compression | Remote server | Full file upload | Varies (1h to indefinite) | Often |
The first 12 rows represent tools we tested from Cashew Crate. The last 3 rows summarize patterns observed across 16 server-dependent tools from other providers (names omitted; the pattern was consistent across the category).
Technology Breakdown
Five web APIs make client-side file processing practical in 2026.
Canvas API — Image Manipulation
CrunchPix uses `browser-image-compression`, which draws images onto a `
WebAssembly — Heavy Processing
WebAssembly (WASM) lets browsers run compiled C/C++ code at near-native speed. SliceTune loads FFmpeg compiled to WASM (`@ffmpeg/ffmpeg` v0.12) for audio trimming, format conversion, and fade effects. ClipShrink uses the same FFmpeg WASM build for video compression. The WASM binary (~30 MB) downloads once on first use, then runs locally. All file I/O happens in WASM virtual memory — the actual file never hits a server.
WebGPU / WASM — On-Device AI
CutoutCraft uses `@imgly/background-removal`, which runs an AI segmentation model directly in the browser. On first use, the model weights download (~30-40 MB). After that, inference runs locally using WebGPU (where supported) or WASM as fallback. The image being processed never leaves the tab.
pdf-lib — PDF Manipulation
PaperMint and FillFox use `pdf-lib`, a pure JavaScript library that reads, modifies, and writes PDFs without server calls. Merge, split, compress, reorder, fill forms, add text — all in-memory on `ArrayBuffer` data.
SVGO — SVG Optimization
SvgMint runs SVGO (the standard SVG optimizer) inside a Web Worker. The SVG markup is passed to the worker thread, optimized via SVGO's plugin pipeline (comment removal, path simplification, metadata stripping), and returned. The entire process is string-in, string-out within the browser.
How Server-Dependent Tools Compare
We tested 16 server-dependent tools across the same categories. The patterns:
Image compression. Most upload your file, compress server-side, and return a download link. Free tiers cap uploads at 5-10 MB. Files stored 30 minutes to 24 hours. Some retain indefinitely unless manually deleted.
PDF editing. Most require an account and server processing. Free tiers impose page limits (3-5 pages). Uploaded PDFs retained 1-24 hours. Several privacy policies state documents may be used to improve their services.
Video compression. Nearly all server-dependent. Free tiers cap at 50-500 MB with queue wait times of 30 seconds to several minutes. FFmpeg WASM has changed this for files under ~500 MB.
Audio editing. Mixed. Several use WASM for trimming but fall back to servers for format conversion.
Limitations
Client-side processing has real trade-offs:
Conclusion
Of the 28 tools we tested, 9 made zero network requests during file processing — every byte stayed in the browser. Three more used a local-first model where data only leaves the device when the user explicitly opts in. The remaining 16 required file uploads to function.
The technology for client-side processing is mature. Canvas API, WebAssembly, and WebGPU cover image, document, audio, video, and AI workloads. The limiting factor is no longer capability — it is whether tool developers choose to build this way.