How it works
Do not take our word for it. Here is how to check, in your own browser, in about a minute.
Verify it yourself
Every claim on this site is checkable with a tool already built into your browser. You do not need to trust a badge, a certificate, or a privacy policy.
- Open your browser’s developer tools Press F12, or Ctrl+Shift+I on Windows and Linux, or Cmd+Option+I on a Mac. A panel opens beside or below the page.
- Switch to the Network tab and clear it This tab lists every single request the page makes. Click the clear button (a circle with a slash) so you are starting from an empty list.
- Convert a file Go to any converter, drop in a photo, and run it. Watch the Network tab while it works.
- Read what appeared You will see nothing during the conversion itself. Before it, you may see the page, its stylesheet, the worker script, and — only for HEIC — a codec file. Every one of those comes from this domain, and none of them carries your image.
- Now try the decisive test: go offline Tick the "Offline" box in the Network tab, or unplug your network entirely, then convert another file. It still works. Software cannot upload your photo to a server it has no connection to.
The offline test is the one that settles it. Every other guarantee depends on reading code or trusting a policy. This one is a physical fact about your network connection.
Why it works this way
A conventional image converter is a website with a server behind it. You upload your photo, the server does the work, and you download the result. That design means your file leaves your device, and you have no way to know what happens to it next — whether it is logged, cached, backed up, scanned, or kept.
This site has no server doing that work, because browsers no longer need one. Modern browsers can decode and encode images natively, and can run that work on a background thread so the page stays responsive. When you drop a file here, it is read directly from your disk by the page, handed to a background worker in your own browser, converted, and handed back. It never becomes a network request, because there is nowhere for it to go.
For formats the browser cannot read on its own — HEIC being the main one, because Apple uses a patent-encumbered codec no browser except Safari licenses — a small decoder is downloaded the first time you need it. It is served from this same domain, it is code rather than a service, and it runs on your device like everything else.
There is a commercial consequence worth being open about: because your device does the work, this costs us essentially nothing per user. We are not absorbing a server bill that we will eventually need to recover by studying your files or selling something derived from them. The incentive that usually makes free tools untrustworthy is not present here.
What this tool cannot do
A page that lists only strengths is advertising. These are the real limitations, including the ones that might send you somewhere else.
- It cannot work in a browser with JavaScript disabled The conversion runs on your device, which means it runs as code in your browser. Everything you can read on these pages works without JavaScript, but the tool itself does not.
- It cannot beat a desktop app on very large batches Your browser limits how much memory a tab may use. For hundreds of 50 MP images at once, dedicated desktop software will be faster and more reliable. For anything up to a few dozen photos, this is comfortably quicker than uploading them somewhere.
- It cannot keep your files between visits Nothing is stored. Reload the page and your queue is gone, because we never wrote it anywhere. That is deliberate — silently keeping copies of your photos would undermine the entire point — but it does mean you should download your results before closing the tab.
- It cannot recover quality that was already lost Converting a heavily compressed JPEG to PNG does not restore detail. No tool can. Lossless formats preserve exactly what they are given, artifacts included.
- It cannot promise every format on every browser Some formats depend on what your specific browser can decode or encode. AVIF and JPEG XL support in particular varies. Where we cannot perform a conversion, we say so plainly instead of failing halfway through.
- It cannot prove anything about a version you did not check The verification above tests the code running in your browser right now. That is the honest limit of what any web tool can offer — which is why we tell you how to check rather than asking you to believe us.