Skip to content

Convert Files in Your Browser

Files are processed on your own device. Nothing is uploaded, because there is no server to upload to.

Drop any file to get started

100% In-Browser Processing

Your files are processed strictly in local device memory. Nothing is uploaded. See how, and check for yourself.

How It Works

How it works

The site is a static export — HTML, JavaScript and WebAssembly on a CDN, with no backend behind it. When you drop a file in, the page reads it into memory and runs the conversion in a Web Worker on your own CPU. The output is handed back as a blob URL for you to save. At no point is there a request carrying your data, because there is no endpoint that would accept one.

The heavy lifting is done by the same libraries a desktop tool would use, compiled to WebAssembly: ffmpeg for video and audio, libheif for HEIC, Tesseract for OCR, qpdf and pdf-lib for PDFs, libarchive for 7z and tar. Simpler jobs — resizing an image, reformatting JSON — use browser APIs directly and need no download at all.

The trade-off is honest and worth stating: your device does the work, so a long video takes longer on a phone than on a workstation, and a file large enough to exhaust available memory will fail rather than queue. In exchange, the file never leaves the machine it started on.

Nothing is uploaded

Not the file, not its name, not the settings you chose. This is a property of the architecture rather than a policy: there is no server that could receive them. Open your browser's network panel during a conversion and you will see it.

No round trip

A 200 MB video is not sent anywhere and not fetched back, so the upload and download disappear from the total. Whether that is faster overall depends on your CPU against theirs — on a slow connection it usually is, and there is never a queue.

Runs without a connection

A service worker caches the pages and worker bundles after the first visit, so the converters keep working offline. Tools whose codec or model you have not downloaded yet are the exception — there is nothing cached for them to run.

What is actually supported

Images convert between HEIC, AVIF, WebP, PNG, JPG, GIF and SVG. Video and audio go through ffmpeg, which covers MP4, MKV, MOV, WebM, MP3, WAV, FLAC, AAC and Opus, plus the operations around them — trimming, cropping, rotating, muting, changing speed, burning in subtitles. PDFs can be merged, split, rotated, compressed, unlocked, watermarked, numbered, and converted to and from images. CSV, JSON, YAML, XML and Markdown convert between each other. ZIP, RAR, 7z and tar.gz archives can be extracted.

The supported formats page lists every pair that is wired up. A build check enforces that each input format has a real sample file committed to the test suite and is actually accepted by the tool that claims it, so the list cannot drift ahead of what the code does. Pairs that are not on it are not supported, rather than supported badly.

Frequently Asked Questions

Where do my files go?

Nowhere. The file is read into memory by the page you already have open and processed there, by JavaScript and by codecs compiled to WebAssembly. There is no upload step because there is no server to upload to: the site is a set of static files. You can verify this yourself by opening your browser's network panel during a conversion, or by disconnecting from the network first.

How is this paid for?

Advertising. The site carries Google AdSense, and Cloudflare Web Analytics for cookieless page-view counts. Those are the only two third parties, and neither one receives your files, filenames, or conversion settings, because that data never leaves the page. There are no accounts and nothing to subscribe to.

What are the limits?

Your device's memory, mainly. A conversion holds the input and the output in RAM at the same time, so a large video can fail on a phone where it would succeed on a laptop. There is no imposed file size cap, but there is a real one, and the tools warn you when a file is large enough to be at risk. Speed depends on your CPU rather than on a queue.

Does anything need installing?

No. It runs in current versions of Chrome, Firefox, Safari and Edge, on desktop and mobile. Some tools do download a codec or a model the first time you use them — the ffmpeg build is about 10 MB compressed, the face detector about 12 MB — and it is cached from then on. The simpler tools need nothing beyond the page itself.

Does it work offline?

After the first visit, mostly. A service worker caches the pages and the worker bundles, so the core converters keep working with no connection. Tools whose model or codec you have not downloaded yet will not, since there is nothing cached to run.

What can it convert?

Images (HEIC, AVIF, WebP, PNG, JPG, SVG), video and audio via ffmpeg, PDFs, archives, and text data formats such as CSV, JSON, YAML and XML. The supported formats page lists every extension and every pair that is actually wired up.