Convert an image between formats without handing it to a server.
Pick a file, pick a format, and the page re-encodes it right here: AVIF, WebP, JPEG, PNG, GIF, or SVG at the resolution you started with, plus an ICO holding every size a favicon needs. As many times as you like.
- Seven output formats
- Nothing uploaded
- Full resolution kept
Drop one or more images here, or click to browse
Decode, re-encode, done.
1. Your browser decodes it
Drop in anything the browser can already display (JPEG, PNG, WebP, AVIF, GIF) and it is decoded into raw pixels in the page. No copy of the file is sent anywhere, because nothing here uploads.
2. You choose the target
AVIF for the smallest file, WebP for a safe middle, JPEG for maximum compatibility, PNG when you need it lossless, and GIF, SVG, or a favicon ICO when something specific asks for one. The table further down says which wins where.
3. A WebAssembly codec re-encodes it
AVIF, WebP, JPEG, and PNG go through the same WebAssembly codec builds Squoosh uses, running on your own processor: lossy at quality 75, PNG carrying every pixel across exactly. GIF, SVG, and the favicon ICO are assembled by the page itself.
4. You download the result
The new file is built in memory and handed to your browser as a download. Nothing is stored, queued, or retained. Close the tab and every trace of it is gone.
A converter that never sees your file.
Online converters are usually an upload form: your image goes to a server, gets converted, and sits in a temporary directory for as long as that service feels like keeping it. This page has no upload at all. The decode and the encode both happen in the tab you are looking at.
That has a side effect worth knowing about: re-encoding rebuilds the file from raw pixels, so every scrap of metadata the original carried (camera model, GPS coordinates, timestamps, editing history) is left behind. Converting is also a way of stripping.
Nothing is kept between runs either. There is no history, no account, and no cache of your images; the only thing the page holds is the picture, or the batch, currently on screen.
- Price
- Free, with no account and no cap on how many files you convert
- Batch
- Drop several images at once to convert them together and download the set as one zip
- Input
- JPEG, PNG, WebP, AVIF, GIF, BMP, and SVG. Vectors are rasterized on the way in
- Output
- AVIF, WebP, or JPEG at quality 75; PNG losslessly; GIF, SVG, or a favicon ICO
- GIF
- One frame, 256 colours, one-bit transparency. Animation is not carried
- SVG
- The image embedded at full resolution, not traced into paths
- Favicon
- An ICO holding 16, 32, 48, and 64 pixel versions, each fitted rather than cropped
- Transparency
- Preserved by AVIF, WebP, and PNG; JPEG has no alpha channel
- Metadata
- Dropped, because the file is rebuilt from pixels
- Where it runs
- Your browser, on WebAssembly codec builds
Which one you actually want.
AVIF for anything going on the web
It is the smallest of them at a given quality, often by a wide margin on photographs, and every current browser displays it. The cost is encoding time: AV1 is heavy to compress, so a large image takes a moment.
PNG for flat colour, not photographs
Screenshots, logos, diagrams, and anything with hard edges or large single-colour areas stay crisp and compress well. A photograph in PNG is simply a very large file with no visible benefit.
Avoid lossy round trips
Every pass through JPEG, WebP, or AVIF throws away detail that no later conversion brings back. Convert from the best original you have rather than from something already re-encoded twice.
Watch out for transparency going to JPEG
JPEG cannot store an alpha channel. If your source has transparent areas, choose AVIF, WebP, or PNG. Otherwise those areas come out filled in solid.
SVG here is a wrapper, not a tracing
The image is embedded inside the SVG at full resolution, so the file goes anywhere an SVG is expected, but enlarging it still shows pixels. Turning a photograph into real vector paths is a different job, and this is not it.
A favicon wants something square and simple
The ICO holds 16, 32, 48, and 64 pixel versions, and anything not square is fitted inside with transparent padding rather than cropped. At 16 pixels a detailed photograph becomes mud. A logo or a single letter survives.
Everything else.
Is it free?
Completely. No account, no watermark, no daily limit, no paid tier. Your own machine does the encoding, so there is no per-file cost for us to pass on.
Do you upload my images?
No. Decoding and encoding both run inside the page, and no copy of your file is transmitted to Doxlore or anywhere else. You can watch it work with your network tab open.
Which format should I pick?
AVIF if the file is going on the web and you want it small; WebP if you want most of that benefit with the widest possible support; JPEG when something old has to open it; PNG for screenshots, graphics, and anything that needs to stay lossless.
Can I choose the quality?
Lossy output is written at quality 75, which is a good default for photographs. If what you need is a specific file size rather than a specific format, the compressor is the tool for that: it steps quality down until the result fits.
Can I convert several at once?
Yes. Drop more than one file and the page switches to a list: pick a format, convert the whole set, and take the results away one by one or as a single zip. Every file is still decoded and encoded in your browser, exactly as one is.
Does converting remove EXIF and GPS data?
Yes. The output is rebuilt from decoded pixels, so no metadata block survives the trip. If stripping is the whole point, the EXIF strip tool does it without changing your format.
What about animated GIFs or animated WebP?
Only the first frame is converted, in both directions: an animation put in comes out as a single picture, and GIF output is one frame too. This is a still-image converter.
Is the SVG a real vector?
No, and it is worth being clear about that. The SVG holds your image inside it at full resolution, which makes it a valid SVG that opens anywhere one is expected, but scaling it up shows pixels, because there are no paths to redraw. Tracing an image into vector shapes is a different operation and this page does not do it.
How do I use the favicon file?
Download it as favicon.ico and drop it at the root of your site; browsers request it from there without being told to. It holds 16, 32, 48, and 64 pixel versions in one file, so each context picks the size it wants instead of scaling a single image badly.
Is there a file size limit?
Only what your device can hold in memory. Ordinary photos are fine everywhere; a very large panorama can run a phone out of memory, and downscaling first fixes it.
Why does AVIF take longer than the others?
AV1 does far more work to find a small representation of the image. The wait is the reason the file comes out smaller than the same picture as WebP or JPEG.