Built for simple, private conversion
- Batch conversion — Drop in a whole folder. Files convert one after another.
- ZIP download — Take the finished batch as a single archive.
- Works offline — Install it once and convert with no connection at all.
- No registration — No account, no email, no verification step.
- No watermark — The output is your image and nothing else.
- No file size cap — Limited only by your own device memory.
Keep SwapFormat handy
Install it and your conversion tools keep working even when you're offline. Nothing to download from an app store.
Why in-browser conversion is better
Most free converters work by uploading your file to a server, processing it there, and handing back a download link. That model has three problems. Your photos end up on somebody else's disk, subject to whatever their retention policy happens to be. Large files take as long to upload as they do to convert. And the site has to pay for that processing, which is why so many of them impose file limits, queues, or watermarks.
Doing the work locally removes all three. There is no upload step to wait through, no cap on how many files you convert, and nothing to retain because nothing was ever transmitted. You can verify this yourself: open your browser's developer tools, watch the Network tab while you convert something, and you will see no request carrying image data. Load the page, disconnect from the internet, and the converters still work.
Which format should you pick?
JPG when the file is going to another person or into a form. It is the most universally supported image format in existence, at the cost of larger files than modern alternatives and no support for transparency.
PNG when you need transparency, when the image contains text or sharp edges, or when it will be edited repeatedly. Lossless, so nothing degrades on re-saving — but substantially larger for photographs.
WebP when the destination is a website. Roughly 25–35% smaller than JPG at the same visual quality, supported by every current browser, and less well supported by desktop software.
What these tools cannot do
Worth stating plainly. Browsers can decode AVIF but cannot write it, so there is no "convert to AVIF" here — that needs a server or a desktop encoder. HDR images are tone-mapped down to standard dynamic range when converted to JPG, because JPG has no way to represent them. EXIF metadata, including GPS coordinates, is not carried across; for sharing photos publicly that is usually what you want, but if you need the metadata preserved, these are the wrong tools. And Live Photos yield only the still frame.