Privacy

Every conversion runs locally. When you add a file, it is read into memory and processed by the ffmpeg WebAssembly engine inside your browser tab. The input, the output, and everything in between stay on your machine. Nothing is sent to a server, because there is no server doing the work.

There is no upload step to opt out of, no temporary copy held remotely, and no account that could tie a file to you. Closing the tab discards everything.

Transcodr keeps a small set of preferences in your browser's localStorage, purely so the interface remembers how you like it:

• transcodr.theme — dark or light appearance.
• transcodr.density — roomy or compact spacing.
• transcodr.autoConvert — whether to start encoding on drop.

That is the entire list. No file contents, no filenames, and no conversion history are written to storage. The session's history table lives in memory only and is gone when you reload. You can clear these preferences any time through your browser's site-data controls.

There are no analytics scripts, no tracking pixels, and no advertising. Transcodr sets no cookies and builds no profile of you. Fonts are served from this domain, so rendering the page does not call out to a third-party font host.

Two things involve a network, and neither carries your media:

• The ffmpeg engine. The first time you convert, the ffmpeg core (around 32 MB of WebAssembly, worker, and JavaScript) is downloaded from the jsdelivr.net public CDN, then cached. Like any download, that request tells the CDN your IP address and that you fetched the ffmpeg core. It never includes your files or any conversion data.
• Hosting. This site is served as static files through Cloudflare. As the host, Cloudflare may process standard request logs (such as IP address and page requested) to deliver the page and protect the service. Because conversion happens in your browser, no file ever reaches the host.

If this policy changes, the date above is updated. Material changes will be noted on the changelog.