Does VERT.sh Upload My Files to a Server?

Updated

No. According to VERT.sh's own site, "all file processing is done on your device," so your files are not uploaded to a remote server for conversion. The site also states there is no file size limit, no ads, no tracking, and that the tool is completely open source. This makes VERT.sh a reasonable choice if your main concern is keeping documents, images, video, or audio local rather than sending them to a third-party service.

What "on your device" means in practice

When you drop or click to add a file, the conversion work runs in your browser on your own machine rather than on a remote machine. The practical consequences:

  • Your file content stays local. The bytes you convert are processed by code running in your browser session.
  • No upload wait tied to file size. Because there is no server round-trip for the file itself, the site advertises no file size limit. Very large files are still bounded by your device's memory and CPU.
  • No account or ad pipeline involved in conversion. The site states no ads and no tracking, so the conversion step isn't wrapped in an advertising or analytics flow.

One caveat worth stating plainly: "processed on your device" describes where the conversion happens, not a guarantee about every network request a web page can make. The site's open-source code is the thing you can actually inspect if you want to verify behavior rather than take the claim on faith.

How to verify the privacy claim yourself

Because VERT.sh publishes its source code, you don't have to rely on marketing copy. A workable check:

  1. Open the site and, in your browser's developer tools, switch to the Network tab.
  2. Clear the log, then drop in a test file and start a conversion.
  3. Watch for requests that carry the file's contents. With on-device processing, you should see the page's own assets load but not an upload of your file body.
  4. Cross-check against the linked source code to see how the conversion is wired up.

Expected result: conversion completes while the file itself isn't sent out. If you see a large outbound request containing your file, that contradicts the on-device claim and is worth investigating before using it on sensitive material.

When this matters, and when it doesn't

Situation Does local processing help?
Converting contracts, IDs, or internal documents Yes — the file isn't handed to a remote converter
Large video/audio files you'd rather not upload Yes — no upload step for the file
Files you'd happily post publicly anyway Less important, but still avoids a third-party copy
You need a guaranteed audit trail Only if you review the open-source code yourself

Limits to keep in mind

  • Device resources are the ceiling. On-device conversion uses your browser and hardware, so a very large file on a low-memory device may fail or run slowly even though there's "no file size limit."
  • The claim is the vendor's. The strongest evidence is the open-source code plus your own network check, not the tagline alone.
  • Browser-based tools still load a web page. Local file processing doesn't mean the page makes zero network requests; it means your file isn't uploaded for conversion.

If your goal is to convert files without shipping them to a server, VERT.sh's stated design matches that goal, and its open-source code gives you a way to confirm it rather than assume it.