Processed on your device

No server copy

No server upload

104 file formats

Free tools

2026-09-08

How Local File Conversion Works in the Browser

From dropzone to download: encoding, decoding, and what still comes from the network — without uploading your file contents.

ConversionFile handling

The conversion path

You choose a file, JavaScript reads it into memory, client-side codecs decode and re-encode (or remux) the bytes, and a Blob URL lets you download the result. Refreshing clears in-memory copies.

Encoding vs container changes

Some conversions change the codec (WAV→MP3, PNG→JPG). Others mainly change the container (MKV→MP4 remux). Quality impact depends on whether a lossy encode happens — see our quality guides.

What still comes from the network

The app shell and WASM codecs may download like any website. Your document contents are not posted to a remote conversion endpoint.

Keep exploring this topic

Follow the format knowledge graph — hubs, comparisons, converters, and quality guides — not a bounce to the homepage.

← All posts