Image tools
Convert, compress and vectorise — none of it leaves your device.
20 tools
In this category
- HEIC to JPGYour photos never leave your device.Runs locally
- Compress ImageSmaller files, without handing them over.Runs locally
- WebP to JPGFor every program that still refuses to open .webp.Runs locally
- PNG to JPGMuch smaller files — when the image is a photograph.Runs locally
- JPG to PNGLossless from here on — but read this first.Runs locally
- HEIC to PNGWhen you need transparency or a lossless copy.Runs locally
- JPG to WebPMeaningfully smaller at the same quality setting.Runs locally
- PNG to WebPThe only common target that keeps transparency and gets small.Runs locally
- WebP to PNGFor transparency plus software that will not open .webp.Runs locally
- AVIF to JPGThe newest format, converted to the one everything reads.Runs locally
- AVIF to PNGWhen the AVIF has transparency you cannot afford to lose.Runs locally
- GIF to PNGOut of 256 colours and 1-bit transparency.Runs locally
- BMP to JPGBMP stores every pixel raw. The savings are enormous.Runs locally
- SVG to PNGVector to pixels — a one-way trip, so choose the size well.Runs locally
- Convert to JPGOne page for every format that needs to become a JPG.Runs locally
- Resize imageSay the size you need. See it before you commit.Runs locally
- Compress JPGMozJPEG, running on your own processor.Runs locally
- Compress PNGGenuinely lossless. Not a palette reduction in disguise.Runs locally
- Compress WebPAlready the efficient format — squeeze it further.Runs locally
- PNG to SVGReal paths you can edit — not a bitmap hidden inside an .svg file.Runs locally
Almost every image problem is one of two problems: the file is in a format something refuses to open, or the file is too big for where it needs to go. These tools cover both, plus the harder case of turning a picture made of pixels into real vector geometry.
Format or size — decide which problem you have first
If a program, upload form or website rejects your file, you have a compatibility problem and you want a converter. The target is almost always JPG when the image is a photograph, or PNG when it contains text, sharp edges or transparency.
If the file opens fine but is rejected for being too large, or makes a page load slowly, you have a size problem and you want a compressor. Converting a format will sometimes fix a size problem as a side effect — a photo saved as PNG becoming a JPG usually shrinks dramatically — but reaching for a converter when you actually needed a compressor is how people end up re-encoding an image three times for no reason.
How to pick the target format without guessing
Photographs belong in JPG for maximum compatibility, or WebP if the destination is a website and you control it. WebP is roughly 25 to 35 per cent smaller than JPG at comparable quality and every current browser supports it — but plenty of desktop software and upload forms still do not.
Screenshots, logos, line art, diagrams and anything containing text belong in PNG. JPEG cannot represent hard edges cleanly; it surrounds letters with visible ringing no matter how high you push the quality, and for flat colour it is often larger than PNG as well.
Anything that needs a transparent background belongs in PNG or WebP. JPG has no alpha channel at all, so transparency is filled with solid colour during conversion. This is the single most common unpleasant surprise in image conversion.
If your source is HEIC from an iPhone or AVIF from a modern website, you are converting for compatibility rather than quality, and the choice is simply JPG for photographs or PNG when transparency matters.
What compression really costs
JPEG and WebP compression works by discarding detail that human vision is poor at noticing. The quality number is not a percentage of anything — it is a knob on the encoder, and its relationship to file size is steeply non-linear. Going from 100 to 90 usually removes a large share of the bytes with almost no visible change. Going from 60 to 50 saves far less and is much more likely to show blocking in smooth areas such as sky or skin.
For web and messaging, 70 to 80 holds up almost always. For print or further editing, stay at 90 or above, because every re-encode compounds the loss from the last one. Compressing the same file repeatedly always degrades it — the savings shrink each time while the damage accumulates.
PNG compression is different: it is lossless, so a PNG optimiser rearranges and re-encodes the data without changing a single pixel. The saving is smaller and it is completely safe to run more than once.
The one conversion that is not really a conversion
PNG to SVG is a different kind of operation. The other tools here re-encode a grid of pixels; vectorising has to invent shapes — it traces the boundaries between colour regions and writes them out as path geometry with real coordinates.
That works beautifully for logos, icons and flat illustrations, and badly for photographs, where the tracer has to produce thousands of paths and the SVG usually ends up larger than the original. Be aware that a large number of free "PNG to SVG" sites do not vectorise at all — they base64-encode your PNG inside an SVG wrapper, which is a bitmap wearing a different file extension.
Frequently asked questions
Which format should I convert my iPhone photos to?
JPG, unless you need transparency. HEIC is efficient but poorly supported outside Apple devices, and JPG is the one raster format essentially every program written in the last thirty years can read.
Why did my PNG get bigger after I converted it to JPG?
Because it was probably a screenshot. PNG is extremely efficient on flat colour, while JPEG has to spend extra data describing sharp edges it cannot represent cleanly. Keep screenshots and text images as PNG.
Does converting an image improve its quality?
No. Quality already lost to compression cannot be recovered, and re-encoding into a lossless format such as PNG preserves the existing artefacts perfectly while making the file larger.
Is there a limit on file size or how many images I can process?
No. There is no account, no hourly quota and no watermark. The only ceiling is your device memory, because the work happens on your own processor.
How do I verify that my images are not uploaded?
Open developer tools, go to the Network tab, and convert a file. No request carries your image. The Content-Security-Policy on this site also restricts connections to our own origin, and your browser enforces that regardless of what our code tries to do.