How in-browser file conversion works

Almost every "free file converter" on the web works the same way: you upload your file to a stranger's server, it gets converted there, and you download the result. Morphr does the opposite — every conversion runs inside your own browser, and your file never leaves your device. This page walks through how that works, and where it has limits.

Your file never gets uploaded

When you drop a file onto Morphr, the bytes are read directly from your disk into a sandbox inside the browser tab — the same sandbox that runs any web page. The conversion happens there, in memory, and the finished file is handed straight back to you as a download. No copy is ever sent across the network. You can prove it: open your browser's developer tools, switch to the Network tab, and convert a file. You'll see the page and its code load, but not a single byte of your document going out.

That design has real consequences. There's no upload wait, so a 50 MB image converts as fast as your device can crunch it, and no server-imposed size cap — the only ceiling is your available memory. Because the file stays local, you can convert a confidential contract or a medical scan without handing it to anyone. There's nothing to leak when nothing was sent.

Three engines, picked automatically

"In the browser" doesn't mean one trick. Modern browsers are capable computers, and Morphr routes each job to whichever of three engines does it best — you never have to choose:

• The browser's own image pipeline. For common photo formats — JPEG, PNG, WebP, and decoding HEIC and AVIF — the browser already has fast, hardware-accelerated decoders and encoders built in. Morphr uses them directly, which keeps these conversions tiny and instant.
• A Rust engine compiled to WebAssembly. For everything the browser can't do natively — TIFF, BMP, GIF and other rasters, camera RAW previews, document and data formats, lossless metadata stripping — Morphr ships a compiled Rust engine that runs at near-native speed inside the page. It's downloaded only the first time you need it, so simple image conversions never pay for it.
• A full transcoder for audio and video. Re-encoding video or audio is heavy work, so those jobs use a self-contained build of FFmpeg, also compiled to run in the browser. It's a larger download, so it loads only if you actually transcode something.

All of this runs in a background worker thread, so the page stays responsive and you get a real progress bar while it works.

Lossy vs. lossless: what you keep

The most useful thing to understand about any conversion is whether it's lossless or lossy. A lossless conversion preserves the original data exactly: convert a PNG to BMP and back and you get identical pixels; convert CSV to JSON and every value is carried across untouched. A lossy conversion deliberately discards some detail to save space — that's how JPEG, MP3 and most video formats achieve their small sizes.

Two things follow from that. When a conversion is lossy, Morphr gives you a quality slider so you pick the size-versus-fidelity trade-off yourself. And quality that's already been discarded can't come back: converting a JPEG to PNG makes a perfect copy of the JPEG, but it won't restore the detail JPEG threw away, and going from one lossy format to another (say MP3 to M4A) just compounds the loss. When in doubt, keep an original.

Metadata, and why re-encoding cleans it

Photos carry more than pixels. Most images embed EXIF metadata — the camera and lens, the exact time, and often the GPS coordinates where the shot was taken. When Morphr re-encodes an image to a new format, that hidden metadata is left behind, so the file you download won't quietly reveal where you live or when you were somewhere. If you'd rather keep a file in its original format but still scrub its metadata, the Inspect tool shows you exactly what's hidden inside a file and strips it in place.

What it can't do (on purpose)

Running locally has limits worth being upfront about. Camera RAW files are converted by extracting the full-size preview the camera embedded, not by developing the raw sensor data — perfect for sharing a shot quickly, but not a replacement for a raw editor. Converting a PDF to an editable document pulls out its text and reading order, but can't rebuild the original page layout, fonts and images, and a scanned image-only PDF has no text to extract at all. And because the work happens on your device, a very large video transcode is bounded by your machine's memory and speed rather than a server farm's. These are the trade-offs that come with keeping your files on your own machine.

Try a conversion

Every conversion below runs entirely in your browser, free and without a sign-up:

Want the deeper technical story — the exact engines and how each conversion is routed? See the about page.