Is It Safe to Use Online Converters? Upload-Based vs In-Browser Processing
Updated
Online converters are convenient: no installation, no settings to learn, and they work on any computer. But most of them work by uploading your file to someone else's server, converting it there and letting you download the result. For a meme that is fine. For a video of your children, a recorded business meeting or a confidential interview, it is worth knowing where the file goes.
There is another way to build a converter, where the processing happens inside your own browser and the file never leaves your device. This guide explains the difference, the real risks of each, and how to check what a tool is actually doing.
How upload-based converters work
A traditional online converter sends your file over the internet to its servers, runs conversion software such as ffmpeg there, stores the output, and gives you a download link. The service therefore holds a copy of your original and the converted file, at least for a while.
That is not automatically dangerous. Reputable services use encrypted connections and delete files after a stated period. The risk is that you are relying entirely on their policy and their security, and you usually cannot verify either.
- Retention: files may be kept longer than you expect, in backups or logs, or reused in ways described deep in the terms of service.
- Access and breaches: anyone with access to the servers, or anyone who breaches them, could see your files.
- Jurisdiction: the servers may be in a country with different privacy laws from yours.
- Practical limits: large files take a long time to upload and download, and many services cap file size or daily conversions on free plans.
The bigger danger: shady converter sites
Most real harm from converters does not come from reputable services quietly reading files. It comes from sites designed to make money from confused visitors: fake download buttons in ads, pages that push you to install a desktop app or browser extension, notification prompts that later spam you, and downloads that arrive as an executable instead of a video.
A few rules avoid nearly all of it. A video or audio conversion should give you a video or audio file, never a .exe, .dmg, .apk or installer. You should not need to install an extension or allow notifications. And if a page is covered in flashing download buttons, the real one is usually the least prominent.
How in-browser processing works
Modern browsers can run serious media software locally. WebAssembly lets a site run compiled code such as ffmpeg inside the browser at close to native speed, and the WebCodecs API gives web pages direct access to the same hardware video encoders and decoders your operating system uses. A converter built on these technologies downloads the processing engine to your browser, and your file is read, converted and saved entirely on your own device.
The privacy benefit is structural rather than a promise: a file that is never uploaded cannot be retained, leaked from a server or read by the operator. There are practical benefits too. There is no upload wait, so large files often finish sooner, and there is no server-side file size cap. The trade-offs are that speed depends on your own computer, very large files are limited by the memory available to the browser, and phones are slower than desktops.
What MediaConverter.io processes locally, and what it does not
Our core tools run entirely in your browser using WebCodecs and WebAssembly: the Video Converter, Audio Converter, Video Compressor, Video Cutter, Video Splitter and Video Rotator, along with the one-click conversion pages such as MOV to MP4. Your media is not uploaded when you use them.
A few features in the Video Editor and our AI Studio need server-side models that are too large to run in a browser: AI noise reduction, automatic subtitles (transcription) and, in the AI Studio, vocal and music separation. For these, only the audio track is extracted on your device and sent to our processing server; the video itself stays local. The AI Studio asks for your consent before sending audio. If you prefer that nothing leaves your device, simply do not use those features; everything else keeps working.
The optional chat assistant receives information about the file you are working on, such as its name and duration, so it can help with settings, but not the media file itself. Like most websites, we use analytics to understand how the site is used; our privacy policy has the details.
How to check any converter yourself
You do not have to take any site's word for where your file goes. These checks work on any converter:
- Watch the network: open your browser's developer tools (F12 or Cmd+Option+I), go to the Network tab and start a conversion. An upload-based tool shows a large outgoing request roughly the size of your file; a local tool does not.
- Look for an upload step: an upload-based tool shows an upload progress bar before conversion starts, and slows down on a slow connection; a local tool starts working on a large file immediately and is limited by your computer instead.
- Read the privacy policy for concrete statements about where files are processed and how long they are kept, not just general reassurance.
- Check what you download: the output should be the media format you asked for, and nothing else.
Choosing the right tool for sensitive files
For anything personal, confidential or covered by an agreement with a client or employer, prefer tools that process locally: in-browser converters, or desktop apps from well-known sources. Keep upload-based services for files you would be comfortable posting publicly. For company material, also check your organisation's policy, which may restrict third-party services regardless of how they work.
If a file is too big to send once converted, our guide on sending large videos shows how to shrink it locally before it goes anywhere.
Tools used in this guide
Frequently Asked Questions
01
02
03