Is FreeConvert safe?
Yes, on all the evidence a visitor can reach. But its policy keeps two deletion clocks — eight hours, three years — and only one of them is your file.
Nothing we came across while researching this page suggests FreeConvert is run badly, and we are not going to insinuate it. Files sit on Amazon infrastructure in Ireland, the company answers to Canadian law, and of the six converters in our comparison its privacy policy is by some distance the easiest to actually read — written as questions with a plain-language summary above each answer.
So this is not a warning. It is a careful look at two numbers that sit a few sentences apart in that policy, mean entirely different things, and are mistaken for one another almost every time somebody summarizes it.
Is FreeConvert safe? First, read both clocks
The policy states a deletion period twice. The two statements are near neighbors on the page, which is precisely why they get conflated.
The first clock is the file. In their own words: “Files uploaded to FreeConvert are automatically and permanently deleted after 8 hours.” Eight hours is the outer limit if you do nothing; the policy also describes a manual delete you can trigger sooner.
The second clock is you. Two sentences later, the subject quietly changes from files to personal data, which is deleted in identifiable form “a maximum of three years after it is no longer necessary.” That covers what an account holds — email address, billing address, IP address, subscription details — not the PDF you converted at lunchtime.
There is even a third hand on the dial. Billing records outlast both, because “we are obligated by Canadian law to maintain transaction and invoice data” for a minimum of six years.
Now watch what a single misread does. Somebody who meets only the three-year figure in a roundup concludes their converted document lingers on a server until 2029, and gets needlessly frightened. Somebody who meets only the eight-hour figure concludes every trace of them is swept away before dinner, and gets needlessly reassured. The policy itself is not to blame — it states both figures openly. The damage is done in the retelling, which is why we are quoting rather than paraphrasing.
What else the policy says, read on August 7, 2026
We went through FreeConvert’s privacy policy end to end on August 7, 2026. Everything here describes the document as it stood that day.
It carries no visible revision date. We note that plainly rather than pointedly: three of the six services we track are in the same position, and an undated policy is not evidence of anything except that you cannot tell how old the wording is. The document is candid about the consequence, since section 12 answers its own question with “Yes, this Privacy Policy is subject to change.”
On storage, the short version reads “We store all customer files on Amazon Web Services (Ireland).” — a specific named processor in a named jurisdiction, which is more than several comparable policies commit to. It also states, without hedging, that “You retain all rights and ownership of your files.”
Their security and compliance page describes encryption in transit, restricted staff access over VPN, intrusion detection, and per-job container isolation. What it does not do is name a standard or an assessor; the closest it comes is a general line about adhering to “widely recognized security practices” — no number, no certifying body. Two other services in this comparison publish an ISO 27001 certification with an auditor attached, and FreeConvert does not. That is a difference in what has been externally checked, not a finding about how well the servers are run. FreeConvert describes its practices; it does not point to an outside party who checked them. Before that reads as a criticism, note that we hold no certification either, and would be the last site entitled to make it one.
What we measured on the front page
On August 7, 2026 we pointed our own measurement script at www.freeconvert.com. It found
three third-party hosts: a Confiant integration CDN, Cloudflare’s insights endpoint, and
a Google Tag Manager frame. That places FreeConvert mid-field — the six services we track
ranged from zero to six on the same run, the same morning, with the same script.
The method deserves stating outright, because a number quoted without it is worse than no number. Our script fetches the markup a server returns and tallies the outside hostnames written into it. Anything a page assembles afterwards, in JavaScript, never appears — which covers a good deal of how advertising and measurement code actually arrives. So “three” means three outside hosts named in the delivered markup. It is emphatically not a count of everything the page ends up loading, and we would be misquoting our own tool if we let it stand as one.
Where both clocks run out of view
Every figure above came from a document, and a document is a statement of intent rather than an observation. Eight hours is a promise about a deletion nobody outside the company watches happen; three years is a promise about records nobody outside the company can enumerate. Whether a backup rotation quietly outlives the eight-hour mark, and who at the storage layer could reach a file inside it, are questions that resolve where no visitor is standing.
That limit is not particular to FreeConvert. It follows from the shape of any service that converts files on its own hardware, and our page on checking whether a tool runs locally sets out both what a browser can establish for itself and where that evidence stops. We have written the same paragraph about CloudConvert, for the same structural reason and with no more suspicion attached.
What FreeConvert can do that a browser tab cannot
Being honest about the gap is worth more here than being flattering about ourselves.
- Video at real scale. Long clips, high resolutions and priority CPU or GPU encoding run on their hardware, not on your laptop’s thermal budget. Their pricing page on August 7, 2026 listed maximum file sizes from 1.5 GB on the entry tier up to 20 GB at the top. A browser tab cannot promise anything of the kind.
- Encoder controls we do not expose. Bitrate, codec choice, CRF, target resolution — they surface knobs most converters hide behind a quality slider, ours included. If you know what CRF 18 means, they let you type it.
- Formats far outside our range. Archives, e-books, office documents, unit and time conversion, plus a catalog that keeps going after ours stops.
- Automation. An API with jobs and webhooks, an account with history, batch runs. We offer none of it, and are not planning to.
If the job in front of you is a forty-minute 4K clip, or three hundred files that have to be done by Thursday, use them and close this tab. Pretending otherwise would undercut everything else on this page.
When keeping it local is the better trade
The balance tips the other way when the file is personal, ordinary in size, and the operation is routine. Then the shortest path is the one where nothing travels — and where you can open the Network panel and watch nothing travel.
That is the narrow thing this site is for: GIF to MP4 when an animation needs to become a real video, compress GIF when it needs to fit under an upload limit, compress image for a photo that is too large to attach, and HEIC to JPG for a picture straight off an iPhone. Your machine does the work, so your machine sets the ceiling. That is the trade, stated honestly: a smaller ceiling, in exchange for a claim you can check yourself instead of read about.