Conversions that never leave your device
Most file converters work the same way: you send the file, a server changes it, you download the result. For a narrow set of conversions that round trip is unnecessary — your browser can already do the work itself. When it can, Private Mode does, and the file is never sent anywhere at all.
- The file is never uploaded — there is no request to intercept
- Nothing is stored, so there is nothing to delete afterwards
- Works without an account and counts against no quota
- Offered only when your browser can genuinely do it
Try it
Choose a file and a target format. If your browser can do that conversion itself, a Private Mode option appears above the button.
Drop your file here, or click to browse
Supports all major formats
How it works
- 01
Your browser is asked what it can do
Browsers disagree about which image formats they can read and write, and they disagree quietly — ask Safari for WebP and it hands back a PNG without complaining. So rather than guessing from the browser's name, the page encodes a single pixel and checks what actually came back, and decodes a real image of each format in question. Your browser is measured, not assumed.
- 02
The conversion runs on this page
The file is read from your disk by the page itself, decoded, redrawn and re-encoded. For PDFs the pages are rendered by a reader bundled with the site. At no point is a request made — you can watch the network panel and see nothing happen.
- 03
The result is handed straight to you
The converted file exists only in your browser's memory until you save it. There is no copy on a server to expire, no record in your history, and nothing anybody could hand over.
- 04
Anything else goes the normal way
If the conversion is one your browser cannot do, Private Mode is not offered — the file is uploaded, converted and deleted on the usual schedule. You are never quietly switched between the two.
What it covers, and what it does not
Between common image formats. PNG, JPG, WebP, GIF, BMP, ICO, SVG and AVIF can be read; PNG and JPG can be written everywhere, and WebP everywhere except Safari, which has never shipped a WebP encoder. HEIC can be read only on Safari, because no other browser decodes it.
Images into PDF, and PDF pages back into images. Both use libraries already bundled with the site, so nothing extra is downloaded and no request is made.
Not video, audio, Office documents, ebooks, archives, fonts or camera RAW. No browser contains a codec for any of them. Doing that work locally would mean shipping a large WebAssembly toolchain, and the multi-threaded builds require a browser isolation mode this site cannot enable without breaking parts of the page.
Not HEIC to JPG outside Safari — the conversion most people arrive from a phone to perform. Chrome, Firefox and Edge cannot decode HEIC at all, so that one still goes to the server. Saying otherwise would be easier and would be untrue.
What you give up
No share link, no cloud export and no entry in your history — all three describe a file on a server, and there isn't one.
Large files are slower than uploading them. The work happens on your device, so it is limited by your device rather than ours.
Colour profiles, EXIF data and animation do not survive. An animated GIF becomes its first frame; a photo loses the camera metadata attached to it.
When this matters
Documents you would rather not send
A payslip, a passport scan, a contract. The safest file to send is the one you did not send.
Working offline
Once the page is open the conversion needs no connection, so it works on a plane or in a dead spot.
A quick change on a large batch
Turning a folder of screenshots into JPGs costs nothing in bandwidth and nothing in quota.
Networks you do not control
On a shared or corporate connection, a file that is never transmitted cannot be logged in transit.
Questions
How can I be sure the file was not uploaded?
Open your browser's developer tools, choose the network panel, and convert. With Private Mode on you will see no request carrying the file — not a smaller one, none. That is a check you can perform yourself, which is the only kind of privacy claim worth making.
Why is it not available for my conversion?
Because your browser cannot do it. The option appears only when the browser has proven it can read your file's format and write the one you asked for. Rather than offer it and fail, or offer it and quietly produce the wrong format, it is simply not shown.
Is it faster?
Usually, for small files, because nothing is transmitted twice. For large files it is often slower: a server converts faster than a laptop, and uploading is not always the slow part. The trade is privacy, not speed.
Does it use my daily conversions?
No. The limits exist to share out server capacity, and a conversion that runs on your own device uses none of it. It also works without an account.
Is the quality the same?
For the formats it supports, the pixels are the same. What is lost is everything around them: colour profiles, EXIF data and animation frames do not survive a trip through the browser's drawing surface. If you need those preserved, use the normal path.
Why not do every conversion this way?
Because a browser contains no codec for video, audio or documents. Adding them means shipping a WebAssembly toolchain of tens of megabytes, and the fast builds of those need a browser isolation mode that would break other parts of this page. We would rather do a small thing honestly than a large thing badly.