Image Converter
Move between JPEG, PNG and WebP without a server in the middle.
Drop an image to convert
Pick the format you need and the picture is re-encoded into it. The pixels stay the size they are — this tool changes the wrapper, not the canvas.
Choose image JPG · PNG · WEBP · AVIF · GIF (first frame) · SVGBefore & after
Drag the handle · arrow keys nudge itBoth halves are the same pixel count, so the divider is showing you encoder damage and nothing else. Push it over a sky, a face or small text — those fail first.
- Input
- —
- Output
- —
- Pixels
- —
- Original file
- —
- Converted file
- —
- Change
- —
Output format
JPEG opens on literally everything and carries no alpha channel, so anything transparent gets a matte colour painted behind it. Its encoder has been tuned for photographs for thirty years, which is still why it wins on soft, detailed images.
WebP keeps the alpha channel and typically lands 25–35% smaller than JPEG at the same perceived quality. Every browser current at the time of writing decodes it; anything older than about 2020 does not.
PNG is lossless and keeps alpha, which makes it the right answer for logos, icons, screenshots and anything with flat colour or hard edges. On a photograph it will be several times the size of the same picture as JPEG.
Quality
Converting usually means going from lossless to lossy, so this is the dial that decides what the conversion costs. 85% is a safe default for a picture someone will look at properly; 60% is fine for a thumbnail that lives in a list.
PNG ignores this slider and it has been disabled rather than left looking broken. Lossless means there is nothing to trade, and the file size is set by the pixel count instead — which this tool does not change.
Transparency
Measured from a small sample of the image, so thin feathered edges may not be counted.
Only JPEG needs this. Transparent pixels are painted onto the colour above before the encoder sees them; white is the usual choice, but mid grey survives a light page and a dark one, and a colour pulled from the artwork itself will look deliberate rather than pasted.
Conversion is not a rescue. A JPEG saved as PNG is a much larger file holding exactly the same damage — the artefacts are in the pixels by then, and no container takes them back out. Convert down to a lossy format once, at the quality you want, and keep the original.
The canvas in the middle
A conversion is three steps, and the middle one is where the losses live. The file is decoded into raw pixels, those pixels are drawn onto a canvas, and the canvas is encoded into the target format. Every format in the list can be decoded into that middle state and every one can be written out of it, which is what makes conversion between any two of them possible — and the middle state is the lowest common denominator of the whole set.
Eight bits per channel, because that is what a canvas holds. GIF and 256-colour PNG arrive indexed and leave as full truecolour, so a small palette image can come back several times larger even though nothing about it was lossy. Animation does not survive at all, because a canvas has one frame; an animated GIF converts to a still of its first frame. An embedded colour profile is dropped unless it is sRGB, so a wide-gamut original can come back flatter. Sixteen-bit files lose their extra precision. None of this appears in the stat line, and all of it is worth knowing before the original is thrown away.
Lossless does not mean unchanged. A PNG that goes through the canvas and comes back as a PNG has every pixel preserved exactly and is still a different file: the text chunks, the physical-size header and the colour profile are gone, the bit depth may have widened, and the encoder that writes the result is not the one that wrote the original. Pixel-exact is a statement about the image, not about the file, and file metadata is what most tooling actually reads.
Alpha is a channel, not a colour
Formats that carry transparency store a fourth value per pixel saying how much of whatever is underneath shows through. Formats that do not have no way of writing that value down, so a transparent image moving into one has to be flattened against something — and the choice of that something is visible. Black produces the familiar dark box behind a logo; white makes a pale logo vanish on a pale page. The matte control exists to pick the colour the image is actually going to sit on.
Flattening costs more than the background, too. The edge of a shape drawn on a transparent canvas is not solid: each boundary pixel is a blend of the shape and whatever was behind it, which is what keeps the outline from looking like a staircase. Composited onto a new colour, those blended pixels keep the old background mixed into them, and the result is a light or dark fringe tracing the whole silhouette. It is most obvious on text and thin line art, and it is the reason a flattened logo sometimes looks chewed along its edges rather than cleanly cut.
Where the format stops mattering
Format and quality are not competing for the same bytes, and knowing which one is doing the work tells you which control to reach for. Container overhead is a fixed cost: a JPEG carries its header, its quantisation tables and often a thumbnail; a PNG carries chunks; WebP carries a RIFF-style container. At small dimensions that overhead can be most of the file, which is why converting a 64-pixel icon from PNG to JPEG can make it larger:
64 × 64 icon ~500 bytes of container overhead
~200 bytes of actual image data
-> the wrapper is the file. Format choice dominates.
1600 × 1200 photo ~700 bytes of container overhead
~400 KB of image data
-> the wrapper is noise. Format and quality dominate.
Below roughly ten kilobytes the difference between the three formats stops being worth a decision — the bytes saved are smaller than the variation between two encodes of the same file. Above a couple of hundred kilobytes it is the largest lever on the page, and a move from JPEG to WebP takes off a third of the weight without the softening that comes from leaning harder on a lossy encoder. The quality slider decides how much quality you are willing to trade. The format decides whether the trade was necessary at all.
Converting in the direction that helps
Direction matters as much as the target. A photograph saved as PNG lands several times larger than the JPEG it came from, because PNG writes every pixel down exactly and the JPEG did not. A JPEG turned into WebP gets a smaller file containing the same damage — the compression happened when the JPEG was written, the artefacts are part of the pixels now, and no container takes them back out. That is why the useful direction is always from the original: an uncompressed master exported once into whatever the destination wants, rather than a chain of conversions hoping the last one cancels the earlier ones.
If a file needs to be a different size as well as a different format, change the size first — a shrunken image has less detail to encode, so the format decision is made on fewer pixels and the result is smaller for both reasons. The Image Resizer handles that half, and the Image Compressor is the one to reach for when the format is already right and only the bytes need attention.
Reference
Which format to convert to, and what you give up
| Format | Compression | Transparency | Animation | Right for |
|---|---|---|---|---|
| JPEG | Lossy. The classic lossy format, with an encoder tuned for photographs. | No | No | Photographs, and little else. Text, flat colour and hard edges pick up ringing around the letterforms first. |
| PNG | Lossless. Every pixel is written down exactly as it was. | Yes | No | Screenshots, logos, line art, and any image that will be edited again. On a photograph the file lands several times the size of the same picture as JPEG. |
| GIF | Lossless, but capped at 256 colours in each frame. | One bit — a pixel is fully opaque or fully clear, with nothing between. | Yes | Legacy. The case that still holds up is a short animation small enough that support is not worth questioning. |
| WebP | Lossy and lossless modes, both in the same format. | Yes | Yes | The general-purpose answer today. Typically 25–35% smaller than JPEG at the same perceived quality, and it carries alpha. |
| AVIF | Lossy and lossless modes, from a newer and much slower encoder. | Yes | Yes | Smaller than WebP at low bitrates. A deliberate choice rather than a default, because both encoding and decoding cost more. |
| SVG | None in the sense the others mean — it stores shapes and curves, not pixels. | Yes | Yes, through CSS or SMIL | Logos, icons and diagrams that must stay sharp at any size. Converting a photograph into it is not a useful operation. |
| BMP, TIFF | None, or light (RLE, LZW, ZIP). | Rarely used in practice | No | Print, scanning and archival work. Neither belongs on a web page. |
| Re-encoded JPEG | Lossy again, on every save, and the errors compound. | No | No | Nothing. Each pass quantises what the last one left behind. Keep one lossless master and export from that. |
Every cell here describes the format itself, so most of the decision is made before the quality slider comes into it. The last row is not a format at all: a second trip through a lossy encoder is damage nothing takes back.
Most size problems are settled by the format, before the quality slider is touched at all. A 4 MB photograph does not come down to a sensible weight by nudging 85% to 80% — moving it into WebP takes off a third of the bytes without the softness that comes from leaning harder on a lossy encoder. The slider decides how much quality you are willing to trade. The format decides whether the trade was necessary.
The direction you convert in matters as much as the target. A photograph saved as PNG lands several times larger than the JPEG it came from, because PNG writes down every pixel exactly and the JPEG did not. And a JPEG converted into WebP cannot recover detail the JPEG encoder already discarded: the new file may be smaller, but the pixels being compressed are the damaged ones.
AVIF is the strongest of these on paper, and its smaller files are real. They are paid for in encoding time. It is markedly slower to produce than JPEG or WebP, which is invisible on a single image and hard to miss on a folder of several hundred. For a large batch, WebP is usually the sensible stop; save AVIF for the images where the last few kilobytes are worth the wait.
Questions
Conversion, answered plainly
Does turning a JPEG into a PNG improve the quality?
No. The compression happened when the JPEG was written and the artefacts are now part of the image data. Saving that as PNG preserves them exactly — losslessly, and at several times the file size. PNG is the right target when you are working forward from an uncompressed original, not when you are trying to undo a lossy one.
Which format should I actually ship?
A photograph goes out as WebP, or JPEG if something downstream refuses WebP. A logo, icon, chart or screenshot with flat colour and hard edges goes out as PNG. A photograph that needs transparency goes out as WebP. Below roughly 10 KB the difference between the three stops mattering, and above 200 KB it usually matters more than anything else on the page.
What happens to the file while it's being converted?
The browser decodes it into raw pixels in this tab's memory, draws those pixels onto a canvas, and encodes that canvas into the format you picked. There is no endpoint here to post it to, and no queue to wait behind, so a 4 MB photograph converts as fast as your machine can chew through four million pixels. Nothing is kept afterwards: close the tab and the pixels are gone.
Can I convert a GIF, an AVIF, an SVG or a HEIC?
It depends on what your browser can decode, and that is the honest limit. GIF loads as its first frame, with the animation dropped. AVIF works in current Chrome, Firefox and Safari. SVG is rasterised at whatever size its own width and height declare, and one without those attributes usually fails. HEIC — the format an iPhone writes — decodes in Safari and mostly nowhere else, so the fix for those is to export as JPEG from the phone first.
My transparent logo came out with a coloured box behind it
That is JPEG doing what JPEG does: it has no alpha channel, so transparent pixels must become some solid colour. Tools that pick black for you produce the familiar black box. Set the matte colour above to whatever the logo will sit on, or choose PNG or WebP as the output and keep the transparency intact.
Why only one image at a time?
Because the comparison is the point. Dropping a second file replaces the first, so the divider always refers to the picture on screen and the settings you last chose. The format and quality buttons keep their values between files, so working through a folder is a drop and a download per image.
Will converting a JPEG to WebP make it look better?
No. WebP is the more efficient container, so the same picture takes fewer bytes — that is not the same thing as the picture improving. Whatever the JPEG encoder discarded is already gone from the pixels, and re-encoding those pixels writes the same damage down again in a newer wrapper. What you get is a smaller file at the quality you already had.
Why did my PNG get bigger when I converted it to JPEG?
It should not have, and if it did, look at the quality slider before assuming the tool is wrong. Near 100% the encoder preserves almost everything, and its overhead can genuinely exceed a PNG of flat colour, which compresses extremely well — a screenshot or a logo with a handful of colours is the cheap PNG case. Pull the quality down to around 80% and the JPEG comes out ahead, usually by a wide margin.
Can I convert a GIF and keep the animation?
Only into a format that carries it. WebP and AVIF can both hold an animation; JPEG and PNG cannot, and converting to either gives you the first frame alone. This tool reads a GIF as a still, so it has no frames to hand on in any case — for a moving GIF you need an editor that works frame by frame.