Do not take our word for it
Every image converter on the internet says your files are safe. Most of them upload everything. Here is how to find out which kind you are looking at, in under a minute, without trusting anybody.
Check 1: watch the network
Open your browser's developer tools with F12, or Cmd + Option + I on a Mac, and switch to the Network tab. Clear the list. Now convert a file. On a server-side converter you will see a large upload request appear the moment you drop the file in, with your image as its payload, followed by a download of the result. On this site you will see the page's own scripts load and then nothing at all while the conversion happens, because the conversion is happening inside the tab you are looking at.
The one request you may legitimately see is a WebAssembly file: the AVIF encoder if you are exporting AVIF, or the video engine on the video tools. Those are downloads from this domain, going one direction only. Nothing of yours is in them.
Check 2: pull the plug
This is the test that cannot be faked, and it takes ten seconds. Load a conversion page. Then turn off your wifi, or switch on airplane mode, or tick "Offline" in the Network tab of developer tools. Do not reload. Now convert a file.
It still works. It has to, because everything needed to do the job is already on your device. A converter that sends your file to a server for processing physically cannot do this, no matter what its privacy policy says. That is the whole argument on one page.
The one caveat, stated plainly: the AVIF encoder and the video engine are fetched on first use. If you have never exported AVIF or converted a video before, those two need one online run before they are cached. Everything else works offline from the first visit.
Check 3: read what the page is allowed to do
The site sets a Content-Security-Policy header that restricts where the page is permitted to send data. It is a rule your browser enforces, not a promise the site makes: a script on the page cannot post your image anywhere the policy does not list, even if it tried, because the browser blocks the request before it leaves. You can read the header yourself in the Network tab, under the document request, or with curl -sI https://imageconvert.tools/.
What this does not claim
Being straight about the edges is the point, so here is what is outside the promise.
- Your files stay on your device during conversion. What you do with the result afterwards is between you and wherever you send it.
- The site is served over the internet like any other, so your browser's request for the page itself is visible to your network and to the host, exactly as it is for every website you visit. What is not visible is the content of your files, because they are never part of a request.
- The WebAssembly engines are hosted here rather than on a public CDN. That is deliberate: a CDN would mean a third party observing which of our visitors converts video. It also means the download is slower than it could be. We think that is the right trade.
- No account, no cookie wall, and no analytics that needs consent. If a cookie banner ever appears on this site, something has gone wrong.
Why this is the one thing the big converters cannot copy
CloudConvert, Convertio and the rest are not being dishonest when they say they delete your files. They probably do. But their product is server-side conversion: the file has to reach a machine they own before anything can happen to it, and that is not a policy choice, it is the architecture. They could not switch to a local pipeline without giving up the formats and the file sizes a server can handle and a browser cannot.
Which is also the honest reason to use them sometimes. If you need a format no browser can decode, or a file too large for your device's memory, a server-side converter is the right tool and this one is not. ImageConvert.tools covers the common formats, on your own hardware, without the upload.
The mechanics of all this are written out in full on how this converter actually works, down to which decoder handles which format and what happens to your EXIF data.