Why private conversion matters
Most converters upload your files to a server. Learn why browser-only conversion with ffmpeg.wasm is safer for personal and business videos.
Most online converters work the same way: you upload your video, it sits on someone else's server, gets converted, you download it, and you hope they delete it. That hope is not a privacy policy.
The real risk of server-side converters
When you upload a video or audio file, you are handing over content that may contain faces, voices, location data, financial discussions, or unreleased work. That file passes through:
- Upload logs and temporary storage
- Third-party cloud providers
- Analytics and ad trackers that log your IP and file name
- Backups that may persist longer than the "we delete after 1 hour" promise
Even if the service is honest, a breach, misconfigured bucket, or subpoena can expose your files. For creators handling client footage, lawyers handling depositions, or families sharing home videos, that risk is unacceptable.
How browser-only conversion works
JSM-Video.com does not have an upload endpoint. There is no server to receive your file. Instead, it loads ffmpeg.wasm - a WebAssembly port of FFmpeg - directly into your browser tab. Your file stays in your device memory, is written to the in-memory virtual file system of FFmpeg, converted, and offered back as a Blob for download.
We verify this with two technical choices:
- All conversion code runs in a Web Worker (
/ffmpeg/worker.js) isolated from the main thread. - Network inspector shows zero POST requests with your file. Only the engine (~30MB, cached after first use) is downloaded from a CDN.
When private conversion is essential
- Client work: Wedding videographers, YouTubers, agencies - you are under NDA. Local conversion keeps you compliant.
- Business recordings: Team meetings, interviews, HR recordings contain PII.
- Personal memories: Kids, home, travel. You don't want them on a random server.
Does private mean slower?
First load takes a moment because the engine downloads. After that, conversions run at near-native speed, and if your browser supports crossOriginIsolated, we enable multi-threaded mode that uses multiple CPU cores. For simple tasks like WAV export or MP4 to WebM via MediaRecorder, we even bypass FFmpeg entirely and use your GPU hardware acceleration for instant results.
How to stay private
- Check that the site says "No upload" and your DevTools Network tab shows no file upload.
- Prefer tools that are open about using ffmpeg.wasm or Canvas/WebCodecs locally.
- Close the tab after downloading - the virtual file system is wiped from RAM.
Private conversion is not a marketing badge. It is an architecture choice: no upload endpoint exists. That's how JSM-Video.com is built.
What server-side converters actually do with your file
The typical flow: your browser POSTs the file to an API endpoint, the server writes it to disk (often on object storage like S3), a worker process converts it, the result is served back for download, and a cleanup job deletes the originals "within 24 hours" or "immediately." Every one of those stages is a privacy surface:
- Upload logs: Web servers log filenames, sizes, timestamps, and your IP by default. Those logs get backed up.
- Object storage: "Deleted" files on cloud storage often persist in version history or backups the provider controls, not the converter site.
- Analytics and ads: Most free converters run ad networks and analytics that fingerprint your browser and log what you converted.
- Employee access: Someone at the company can open your file. There is no technical barrier — only policy.
- Legal compulsion: Stored files can be subpoenaed. Files that never left your device cannot.
GDPR and professional obligations
If you handle other people's data, uploading it to a random converter may breach your obligations. Under GDPR, sending personal data (faces and voices count) to a third-party processor requires a data processing agreement — which no free converter offers. Lawyers, healthcare workers, HR departments, and videographers under NDA all have professional duties that server-side conversion quietly violates. Browser-local conversion sidesteps the entire question: no transfer, no processor, no breach.
How to verify a tool is truly private
Don't take marketing copy at face value. Verify in 30 seconds:
- Open your browser's DevTools (F12) → Network tab.
- Drop a video into the converter and run a conversion.
- Watch for POST or PUT requests carrying megabytes. A truly local tool shows only the initial engine download (~30MB, once, cached) and zero upload traffic.
- Bonus: disconnect from Wi-Fi mid-conversion. If it keeps working, nothing was ever leaving your device.
JSM-Video.com passes all of these by construction — there is literally no upload endpoint in the codebase to send your file to.
The performance myth
"But servers are faster, right?" Sometimes — a 64-core cloud machine beats a laptop. But you're forgetting the upload: pushing a 500MB file up a 10 Mbps home connection takes nearly 7 minutes before conversion even starts. Local conversion starts instantly. For files under a few hundred megabytes, local usually wins on total wall-clock time. And for the WebM/GPU path, your graphics chip is genuinely faster than most server CPUs anyway.
What private conversion can't protect against
Honesty matters: local conversion protects your file in transit and at rest on someone else's infrastructure. It doesn't protect against malware already on your device, a compromised browser extension reading your downloads, or someone looking over your shoulder. Privacy is layers — local conversion removes the biggest, most unnecessary layer of exposure (uploading to strangers), but keep your device itself secure too.
Frequently asked questions
Do you store my files?
No. There is no server storage because there is no upload. Your file lives in your browser tab's memory and is gone when you close the tab.
Can you see what I convert?
No. Conversions happen in your browser; our servers never receive your file, its name, or its metadata. We can't see what we never receive.
What about the 30MB engine download?
That's ffmpeg.wasm (the conversion engine) fetched once from a CDN and cached by your browser — the same way any website loads a JavaScript library. It contains code, not your data, and it runs locally.
Is browser conversion safe for client work under NDA?
It's the safest practical option short of air-gapped desktop software. No third party ever holds the file, which is exactly what most NDAs require. When in doubt, check with your client's security policy — but "never uploaded anywhere" is usually the easiest answer to defend.
Why do other converters offer accounts and history?
Because their business model needs your files on their servers — conversion history, re-downloads, and "cloud storage" are features built on keeping your data. A local tool has nothing to store, so there's nothing to make an account for.
Does private mode work offline?
After the first visit (which caches the engine), yes. Drop a file with no connection and conversion proceeds normally — the ultimate proof nothing uploads.