Guides · updated October 22, 2026

Online vs local conversion

What an upload converter does with your video, what a local converter does instead, and how to verify the difference in your browser.

Tested: 22 October 2026 · Chrome 156 · DevTools Network check on the browser converter

Short answer

An online converter uploads the file to a server, converts it there, and usually deletes it later. A local converter reads the file in your browser and writes the output in the tab; no request carries the file. Uploading is not automatically unsafe, but it creates a copy you cannot audit.

What “upload” means

When a converter uploads a file, the browser sends the bytes to an HTTP endpoint. The server writes them to storage, runs a converter, stores the result, and gives you a download link. The file exists in at least three places during the job: your disk, the server’s temporary storage, and the response.

Encryption in transit protects the bytes while they travel. It does not change the fact that the server has a copy. Retention policies decide how long that copy lives: some services delete after an hour, some after a day, some keep it until you delete it manually. Subprocessors and backups can extend the window.

None of this makes every server converter malicious. It makes the copy real. For a public trailer, that may be fine. For a client interview, a medical recording or an unreleased song, it is a decision worth making deliberately.

What a local converter does instead

A local converter uses the browser’s File API to read the file you chose. It decodes the audio with WebCodecs, encodes it with a WASM encoder, and writes the result as a Blob. The Blob is downloaded through a blob: URL, which points at memory in your tab, not at a remote server.

There is still a server involved in serving the page: the HTML, CSS, JavaScript and fonts arrive over HTTP. The analytics script sends a page view. But the media file is not part of those requests.

How to verify it yourself

Open the converter in Chrome or Edge.
Open DevTools → Network, and clear the list.
Drop a file into the converter.
Filter by Fetch/XHR.
Convert.

You will see the page’s own assets and, depending on the site, an analytics request. You will not see a request whose body is your video. The file read happens through the File API and does not appear as a network transfer.

A second check: load the page, disconnect the network, and convert. A local tool still works because the code is already in the tab. A server tool fails at the upload step.

The honest trade-offs

Property	Local	Server
Upload wait	None	The whole file must arrive first
File copy	None	At least one server-side copy
Codec coverage	Browser decoders only	Whatever the server installs
Memory ceiling	Your device	The server’s plan
Works offline after load	Yes	No
Audit surface	The page’s code and network log	The page, the API and the retention policy
Cost	Your CPU and battery	Someone else’s CPU, often ads or a quota

When a server is the right call

A multi-gigabyte file on a phone with little free memory.
A codec the browser cannot decode, such as AC-3 or DTS.
A batch that must run unattended.
An integration that needs an API, not a web page.

A local tool should not pretend to cover those cases. This one refuses unsupported codecs and says why. That is a feature, not a limitation to hide.

The “safe converter” question

There is no universal safe/unsafe label. Ask three questions instead:

Does the file leave the device? If yes, where does it go?
How long is it kept? “Deleted after 24 hours” is still 24 hours.
Can you verify the claim? A network log is better than a badge.

If the answer to the first question is “no”, the other two are much less interesting. That is the only real advantage of a local converter, and it is enough.

FAQ

Is it safe to upload an MP4 to an online converter?

It depends on the site. A server converter receives a copy, may keep it for minutes or hours, and may use subprocessors. Check the retention policy and whether the file is encrypted at rest. If the recording is private, a local converter avoids the copy entirely.

How can I tell whether a converter really processes locally?

Open DevTools → Network, clear the list, and convert a file. If the file is uploaded, a request with a large body appears. A local converter reads the file through the File API, which does not create a network request. You can also disconnect the network after the page loads and convert; a local tool still works.

Is a local converter faster?

There is no upload wait, so a large file starts immediately. The encoding speed depends on your device. A server with a fast CPU can beat a phone, but it first has to receive the whole file.

Can a local converter still see my file?

The page can read the file you choose; that is how it converts. The question is whether the code sends it anywhere. Use a page you trust, keep the browser updated, and verify the network behaviour if the file is sensitive.

When is a server converter the better choice?

Very large files on a low-memory device, codecs the browser cannot decode, or automation that needs an API. A server has more CPU and memory; a local tool has a smaller trust surface. Pick based on the file, not on a slogan.