Are online file converters safe?

The honest answer is that most of them upload your file, most of the time nothing bad happens, and you have no way of knowing which occasion is which. That is an uncomfortable position to be in with a passport scan.

This page is written by a site with an obvious interest in the answer, so it is built to be checked rather than believed: a test you can run against any converter, this one included, and a plain account of what this site does load.

What normally happens to your file

On a conventional converter, pressing the button sends your document to a server. It is written to disk, a program runs on it, the result is written to disk, you download it, and both copies are deleted on a schedule. Along the way the file may pass through a content delivery network, sit in a queue, be backed up, and be visible to the staff and contractors who maintain any of that.

Almost none of this is sinister. It is simply the easier way to build a website: server-side conversion means one implementation that works in every browser, and the tools to do it have existed for decades. The cost is that your file now exists somewhere you do not control, under a retention policy you did not read, in a jurisdiction you did not choose.

Most of the time that is fine, because most files are holiday photographs. The files people actually bring to converters are frequently not: passport scans for visa applications, signed contracts, payslips for a landlord, medical letters, bank statements, photographs of children.

The test, in four steps

This works on any site and needs no technical knowledge beyond following instructions.

  1. Open the developer tools. Press F12 on Windows, or Command-Option-I on a Mac. A panel appears. Click the Network tab.
  2. Convert a file. Any file, and preferably a large one — a few megabytes makes the next step unmistakable.
  3. Look for a request the size of your file. The Network tab lists every request the page makes, with sizes. An upload appears as a row whose size is roughly your file's, usually a POST. If your file is 4 MB and nothing in that list is anywhere near 4 MB, it did not leave.
  4. Then disconnect. Once the page has loaded, turn off your wi-fi and convert another file of the same kind. If it still works, no server is involved — that is not an opinion, it is arithmetic. If it fails, that proves less than it seems: a page can still need to fetch the code that reads a format, and code is not your file. Step 3 is what shows an upload.

The second test is the one that settles it, because the first can be argued with and this one cannot. A page that works offline is doing the work on your machine.

What this test cannot tell you

Being straight about the limits matters more than the reassurance:

What makes it worth doing anyway is that it moves the question from "do I trust this organisation" to "did the bytes leave the machine", and the second question has an answer you can see.

What this site loads, since you are here

Everything on QuillFile runs in your browser and no file is ever sent anywhere. The page is not, however, free of external requests, and claiming otherwise would fail the test above in about four seconds.

Advertising. Google AdSense loads from pagead2.googlesyndication.com. It pays for the domain. It sees the page you are on, as any ad script does; it cannot see your files, because your files are never in the page's network traffic for anything to see.

Analytics. Google Analytics loads from googletagmanager.com and reports which pages are visited. The tool sends two events and nothing else: that a file was chosen, and that a conversion finished. Neither carries a parameter — no file name, no size, no type, no format, not even a count. Events record that something happened; a tracker records what it happened to, and that line is the whole difference between the two.

Those are the only two hosts, and the build fails if a third appears — the list lives in the repository as a named set rather than a rule that can quietly widen. What the site does and does not collect is set out in privacy and terms.

When uploading is completely fine

It would be dishonest to end with "never upload anything". Plenty of the time it is the right call, and pretending otherwise is marketing rather than advice.

Upload without worrying when the file is already public or destined to be, or is a holiday photograph, or a document you would happily email to a stranger; when the organisation is one you already have a relationship with; or when the job genuinely needs a server. OCR, real PDF font subsetting and video transcoding all fall into that last category, and a browser tool claiming to do them well is the thing you should be suspicious of.

Think harder about identity documents, anything with a signature on it, medical and financial records, material covered by an NDA, and photographs of other people's children. The common thread is not secrecy but consequence: these are the files where a copy existing somewhere unknown is a problem even if nobody ever looks at it.

One thing a converter will not do for you

Whether or not a file is uploaded, it may be carrying more than you think. Photographs store the place they were taken, the camera and the date; PDFs and Word documents record the author, the organisation and the software. Converting a photo usually strips that as a side effect of redrawing it — but not always, and the exceptions are the ones that catch people. If removing it is the point rather than a side effect, Clean does it deliberately.

Questions

Do online converters keep my files?

Most keep them for a period and say so somewhere in the terms: a few hours is typical, sometimes twenty-four. That is a technical necessity rather than a plot, because the file has to exist on their machine long enough for you to download the result. The question worth asking is not whether they delete it but who could reach it in the meantime, and that is not something you can verify from outside.

Is it safe to convert a passport scan online?

Not on a site that uploads it, unless you know the organisation and would send them the document anyway. An identity document is the highest-value thing most people ever convert, and uploading one means a copy exists on infrastructure you cannot inspect, in a jurisdiction you did not choose. Use something that does the work on your own machine, and check that it does rather than taking the claim on faith.

How can I tell if a site is uploading my file?

Open your browser’s developer tools, go to the Network tab, and convert something. An upload appears as a request whose payload is roughly the size of your file. The stronger test is to disconnect from the internet after the page has loaded and try again: if the conversion still works, no server was involved, and if it fails, one was. The full procedure is below.

Are paid converters safer than free ones?

Not inherently. Paying changes the business model, which removes one incentive to be careless with your data, but the file is still uploaded and the same questions apply. A free tool that never receives your file is architecturally safer than a paid one that does, and the test for which is which takes ninety seconds and does not depend on anybody’s marketing.

Related: how this site works, what EXIF data is, and removing metadata from a file.