Image Converter: PNG, JPG, WebP and AVIF
Pick a target format and get the file back โ converted by your own browser, with the weight difference shown before you save.
Converted in your browser โ no upload, no queue, no waiting room
Both weights are exact โ the converted file is really encoded to produce that number, and it is the same file the Download button hands you.
Convert PNG to WebP and Cut Page Weight
Most of what makes a page slow is images, and most of those images are PNGs that should not be. Converting png to webp typically removes 60โ80% of the bytes with no visible difference, keeps the transparency PNG was chosen for, and is supported by every browser released since 2020. If you are optimizing a site, that one conversion is usually the single largest win available, and it is why this page leads with it rather than burying it in a dropdown. Written out longhand as png to web p, it is the same job.
AVIF goes further โ often another 20% below WebP at matching quality โ at the cost of slower encoding and slightly thinner support. Both are offered, and if your browser cannot write AVIF the page says so rather than handing you a PNG with the wrong extension on it.
Conversion happens on your own machine. Nothing is uploaded, so there is no size limit imposed by somebody's upload form, no queue behind other people's files, and no copy of your image sitting on a server you have never heard of. That is the practical difference between this and most of what a search for a picture converter or pic converter turns up.
WebP to JPG and WebP to PNG
The traffic runs the other way too. A site hands you a .webp, some older program
refuses to open it, and you need a webp to jpg conversion to get on with your
day. Drop the file in, pick JPG, download โ that is the whole of it. Same for
webp to png when you need to keep transparency, which JPG cannot carry.
However you phrase it โ convert webp to jpg, webp format to jpg, convert a webp to jpg, convert web p to jpg, or turning a webp in png โ the operation is one decode and one encode, and it finishes as fast as your browser can do both.
PNG and JPG
The oldest pairing in the list and still the most common. Going from convert png to jpg format trades transparency and lossless storage for a much smaller file, which is right for photographs and wrong for logos. Everyone writes the request differently โ format png to jpg, convert png into jpg online, turn png to jpg, convert a png to a jpg โ and a png format converter or png file format converter is the same thing again. Going back the other way, from JPG to PNG, gains you nothing but bytes: the detail a JPEG discarded is gone, and PNG will faithfully preserve the blur.
When you change to png you get alpha and lossless storage; when you change to jpg you get a fraction of the weight and a white background where transparency used to be. That background is yours to choose here, because the default of black โ what a canvas does if nobody fills it โ is almost never what anyone wants.
A note on names: .jpg and .jpeg are the same format with different
extensions, a leftover from MS-DOS allowing only three characters. So a request to
convert jpeg to jpg is really a rename, and this page will do it while
re-encoding. To convert pictures to jpeg in bulk you would want a desktop tool;
to convert picture to jpeg one at a time, this is quicker. A
jpeg image converter, an image to image converter, or anything
that promises to change image format โ including specifically
change image format to jpg โ describes what the buttons above do. The plain
request to convert image to jpg, or a jpg photo convert, is two
clicks.
AVIF
AVIF is the newest of the four and the most efficient, which is why photographs downloaded from
modern sites increasingly arrive as .avif and refuse to open in older software.
Converting avif to png keeps every pixel and any transparency;
avif to jpg produces a smaller, universally readable file. Either direction
works here, so this doubles as an avif to png converter when something on your
machine cannot read the format yet.
What This Page Will Not Do
Converting jpg to svg is not a format conversion at all. SVG describes shapes with mathematics; a photograph is a grid of pixels with no shapes in it. Turning one into the other requires tracing โ software guessing at outlines โ and the result is either a crude approximation or an SVG containing the original bitmap, which helps nobody. We do not offer it rather than offer it badly.
Png compression is likewise a different job. PNG is already lossless, and squeezing it further means smarter palette and filter choices, which is what tools like oxipng exist for. If you want a PNG to weigh less, the honest advice is to convert it to WebP โ the saving is an order of magnitude larger than anything a PNG optimizer can find.
HEIC and TIFF are absent too. Browsers cannot decode HEIC at all, and TIFF's multi-page, multi-compression variants would need a library and a great deal of testing for a format almost nobody sends any more.
ICO is not a target here, because an icon file holds several sizes at once and is almost always wanted as a site icon. The Favicon Generator builds it โ the .ico with its 16, 32 and 48 pixel versions, plus the PNG sizes phones and browsers ask for.
Transparency and Animation
Two things can be lost in a conversion, and the page warns about both. Transparency disappears when the target is JPG โ the format cannot store see-through pixels, so they take the background color you pick. Animation disappears whenever a GIF is involved, because a canvas reads only the first frame; what you get back is that frame as a still image.
Questions
-
WebP for almost everything: it handles photographs and transparency, weighs far less than PNG or JPG, and every current browser reads it. Use AVIF where you can serve a fallback, and keep PNG only for images that must stay pixel-exact.
-
Converting to PNG does not. Converting to JPG, WebP or AVIF re-encodes with loss, and re-encoding an already-lossy file compounds it. Convert from the best original you have rather than from a file that has been through this twice already.
-
Because your browser cannot write it. Reading AVIF and writing it are different things โ browsers learned to read it years ago, but writing one needs a built-in AV1 encoder, and none of them offer that to a canvas. The page tests this when it loads and grays the button out rather than handing you a file named
.avifthat is really a PNG. It will light up by itself if support arrives. Converting from AVIF works in any browser that can read it. -
Usually because you converted a lossy file to a lossless one โ a JPEG turned into a PNG will grow several times over, since PNG has to store the compression artifacts faithfully. Going the other way is where the savings are.
-
Only what your device can hold in memory. There is no server limit because there is no server involved; a very large photograph on an old phone is the only case likely to run out of room, and the page reports it rather than failing silently.