Rasp

Privacy

How to convert files without uploading them

Three approaches that keep the file on your machine — and a thirty-second test that tells you which one you are actually using.

How can I convert a file without uploading it?

Three ways. Use desktop software, which never touches a network. Use a command-line tool such as ImageMagick or Ghostscript. Or use a browser-based converter that runs the codecs locally in WebAssembly, so the file is read from disk into memory and handed straight back without becoming a network request.

How to do it

  1. Decide how often you will need it. A one-off conversion rarely justifies installing software. A recurring task usually does, because desktop tools are faster and work with no connection at all.
  2. Pick the approach that fits. Desktop software for repeated or bulk work. A command-line tool if you are comfortable in a terminal and want scripting. A browser-based local converter for a one-off, with nothing to install.
  3. Verify before you trust. Open developer tools, watch the Network tab, and convert something. A request the size of your file means it was uploaded. Nothing of that size means it was not.
  4. Keep the original. Whatever route you take, conversion is usually one-way. Keep the source file until you have confirmed the result is what you needed.

Why most converters upload in the first place

It is worth knowing that this is a historical accident rather than a necessity.

Until fairly recently, a browser genuinely could not decode a HEIC or assemble a PDF. The libraries that do that work are written in C and C++, and there was no way to run them in a web page. A server was the only option.

WebAssembly changed that. It lets compiled C and Rust libraries — the same ones a server would use — run inside a browser at close to native speed. The technical reason to upload disappeared.

The commercial reason did not. Uploading creates a funnel: accounts, file size limits, queue times, premium tiers. A tool that runs on your machine can charge for none of those.

The three approaches

Desktop software

The strongest option, and the right one for recurring work.

ImageMagick converts essentially any image format from the command line. ffmpeg does the same for video and audio. Ghostscript handles PDFs, including compression, which browser tools generally cannot. On a graphical desktop, GIMP, IrfanView on Windows and Preview on macOS all convert common formats without ceremony.

The cost is installation, and a learning curve on the command-line tools. The benefit is that they work with no connection at all, handle enormous files, and can be scripted over thousands of files at once.

Command line, for scripted work

If you are converting one file, this is overkill. If you are converting four thousand, nothing else comes close:

magick mogrify -format jpg *.heic

That is the entire job. No tool with a web interface will beat it.

A browser-based local converter

For a one-off, this is usually the right trade. Nothing to install, nothing to learn, and — if the tool genuinely runs locally — the file never leaves your machine.

The catch is that “runs locally” is a claim, and claims are cheap. Which brings us to the only part of this page that really matters.

Verify, do not trust

Any site can write “your files are never uploaded” on a page. Very few make it checkable.

The test takes thirty seconds and works anywhere:

  1. Open developer tools — F12, or ⌥⌘I on a Mac
  2. Select the Network tab
  3. Convert a file
  4. Look for a request roughly the size of your file

A 4 MB photo being uploaded produces a 4 MB request. It is unmistakable. If nothing of that size leaves, the conversion happened on your machine.

Do this once per tool you rely on. It converts a marketing claim into an observation.

What this site does

Every tool here runs its codecs in your browser through WebAssembly, in a Web Worker so the interface stays responsive. Images go through codecs derived from Google’s Squoosh; HEIC through libheif; PDFs through pdf-lib and PDF.js.

Each tool page also carries an Uploaded readout wired directly to the page’s own outbound network requests. It is a measurement, not a reassurance — on a successful conversion it reads 0 B, and you can confirm that against the Network tab.

One honest limitation: there is no service worker, so offline operation is not guaranteed. The page and codecs are usually cached after first use, but that is a convenience rather than a promise, and this site will not claim otherwise.

If you want the fuller picture of what uploading actually risks, is it safe to convert files online works through it.

Questions

Do browser-based converters really work without uploading?
Some do and some do not, and the label on the page is not evidence. A genuine one runs the codecs in your browser through WebAssembly; a fake one has an upload endpoint and a reassuring paragraph. The Network tab distinguishes them in thirty seconds.
Is a browser tool as safe as desktop software?
For a single conversion, effectively yes — the file does not leave your machine in either case. Desktop software is stronger on one point: it works with no connection at all, so there is no page to be changed underneath you between visits.
What desktop software should I use?
ImageMagick and ffmpeg cover almost every image and video conversion from the command line. Ghostscript handles PDFs. On a graphical desktop, GIMP, IrfanView on Windows and Preview on macOS all convert common formats.
Does a browser-based converter work offline?
Often, but rarely with a guarantee. The page and its codecs are cached after first use, so a later conversion may work with no connection — but unless the site ships a service worker, that is a convenience rather than a promise. This site does not, and says so.
Why do most online converters upload?
History and economics. Until WebAssembly matured, browsers genuinely could not run the necessary codecs, so a server was the only option. Uploading also creates a funnel — accounts, file size limits, premium tiers — that a local tool cannot.
Is there a size limit on local conversion?
Only your device's memory. Upload limits exist because bandwidth and storage cost the operator money, and neither applies when the work happens on your own machine.
Can I convert a file on my phone without uploading?
Yes. A browser-based converter that runs locally works the same way on a phone, subject to less memory. Very large batches will run out sooner than on a laptop.

Sources

Related reading