Convert any image to JPG online, free

So the trade is clear and worth stating plainly. You convert to JPG to guarantee the file opens anywhere, accepting that it may be larger than a modern format would be. When a real piece of software or a real upload form has to read your image, that guarantee is what counts.

How each source format is handled, honestly

PNG and WebP are the easy cases for photographic content. A PNG photo or screenshot usually shrinks dramatically as a JPG, often by 70 to 90 percent. A WebP photo converts cleanly too, though a lossless WebP graphic may grow. If either has a transparent background, that transparency is flattened onto white, which matters more for graphics than photos.

AVIF and HEIC or HEIF are the modern, efficient formats, and converting them to JPG almost always makes the file larger. A 150 KB AVIF can become a 350 KB JPG; a HEIC off an iPhone behaves the same way. For HEIC specifically the file is decoded in your browser first, then re-encoded as JPG, so an iPhone photo that nothing on your PC can open becomes a universal one. The HEIC to JPG and AVIF to JPG pages cover those two cases in depth.

GIF and SVG are the two formats with real caveats. An animated GIF is reduced to its first frame only, because JPG cannot hold animation. An SVG is a vector, so it is rasterised at its natural pixel size into a fixed-resolution JPG; if you need control over the output dimensions or crisp edges, convert the SVG to PNG instead, which suits flat graphics far better.

Across all of these the pipeline is identical underneath. Your browser decodes the source into raw pixels, paints them onto an HTML canvas, fills any transparency with white, and encodes the canvas as JPG. The same five lines of logic handle a PNG, a HEIC, and an SVG, which is why a mixed folder converts in one pass without you sorting it first.

The transparency trap, and where it bites

This is the single fact that decides whether converting to JPG helps or wrecks an image. JPG cannot store a transparent pixel. None of them. So any alpha channel in a PNG, WebP, AVIF, GIF, or SVG has to become a solid colour, and the converter chooses white.

For most files that is invisible. A photo has no transparency to lose. A screenshot with rounded corners cut out, viewed on a white page, looks identical once flattened. If white is what sits behind the transparent pixels in real use, or if it simply does not matter, convert freely and never think about it.

The damage starts when transparency is doing real work. A logo exported with a clear background is built to float over a coloured website header, a dark email banner, or a printed flyer. Turn it into a JPG and that clear space becomes a hard white rectangle, so the mark sits in an ugly box wherever the background is not white.

The same failure hits icons, badges, stickers, and watermarks. The honest test is one question: what sits behind the transparent area when the image is actually used? If the answer is a colour or a photo, keep the alpha channel by converting to PNG instead of JPG.

When NOT to choose JPG at all

Graphics, logos, and brand marks are the clearest no. They usually carry transparency, they often contain sharp type, and they land on backgrounds you do not control. JPG breaks both the alpha channel and the crisp edges in a single step, so a logo converted to JPG looks worse and boxes itself in white.

Screenshots full of small text and diagrams are the second case to watch. JPG is lossy, and its artefacts show up first and worst around hard edges, the boundary between black text and a white background. A photo never reveals this, but a dense UI capture or an infographic can look faintly smudged where the type meets the page.

Line art, charts, code captured as an image, and anything with flat colour and crisp strokes belong in PNG too. These are exactly the images PNG stores efficiently and JPG handles badly, so you gain little size and add visible fuzz around every edge. The MDN image type reference lays out which format suits which content.

The rule that covers all of it is short. Photos go to JPG; graphics and anything that needs transparency go to PNG. If your image is mostly continuous tone and tolerates a little lossy compression, JPG is right. If it is mostly hard edges, flat fills, or a clear background, send it to PNG instead.

Quality settings without the guesswork

JPG is lossy, so a quality slider controls how much detail survives the encode. imgkilo defaults to quality 90, which keeps the result visually identical to the source for ordinary photos while holding the file reasonably small. For the vast majority of conversions you never need to touch it.

Raise quality to around 92 when the JPG is bound for print or a high-resolution display, where every bit of detail earns its place. The file grows a little, but a photo lab or a large screen rewards the extra data. There is rarely a reason to go above 95, where the size climbs fast for gains the eye cannot see.

Lower quality to roughly 82 only when you are fighting a tight upload limit and can accept faint softening around hard edges. On a pure photo the loss at 82 is hard to spot; on a screenshot with small text it starts to look soft, so keep text-heavy images higher.

One habit prevents avoidable damage. JPG loss compounds every time you re-save, so convert from the original once, at the quality you want, and keep that JPG. If you only have a JPG already and want it smaller, compress it directly rather than re-converting, which avoids stacking a second round of loss.

Converting a mixed folder in one drop

Real folders are messy. A download directory might hold a HEIC from your phone, a couple of PNG screenshots, a WebP saved from a site, and an SVG someone emailed you. This page exists so you can drop all of that together and get a clean set of JPGs back without sorting anything by hand first.

Up to 100 files at 50 MB each go in one batch, and each is decoded and re-encoded in parallel using a worker pool in your browser. A set of twenty mixed images finishes in a few seconds; larger photographic files take a little longer because each is fully decoded, but the work spreads across your machine's cores rather than queuing one at a time.

Every file keeps its original name with the extension swapped to .jpg, and the whole batch arrives as a single ZIP. Because nothing uploads, the only limit is your device's memory, not a server quota or a paid tier. There is no watermark, no per-file fee, and no cap on how many batches you run back to back.

If the destination is a specific output format rather than JPG, the bulk image converter lets you pick the target for a mixed folder. And if you need the JPGs under an exact KB ceiling for a form, run the results through compress to size, which iterates quality to hit a target like 100 KB or 200 KB per file.

Where converting to JPG actually pays off

Upload forms are the most common wall people hit. Job portals, bank verification pages, school admission sites, and marketplaces frequently accept only JPG or JPEG and reject everything else outright. Convert whatever you have to JPG and the form takes it without complaint, no matter what the source format was.

Sharing with someone on older or locked-down software is the next. You have a HEIC or AVIF that opens fine on your device but lands as a broken thumbnail on a colleague's older Mac or work laptop. A JPG sidesteps the whole problem because their machine already reads it, with nothing to install.

Printing and physical output rounds it out. Print shops, kiosks, and photo labs often run software that has never heard of HEIC or AVIF and may stumble on WebP. A high-quality JPG prints without a last-minute format scramble, which is exactly why labs ask for it.

The common thread is destination, not preference. The modern formats are better to keep for the web, where they load faster. JPG is the format you reach for the moment a real form, a real piece of software, or a real printer has to read the file and cannot handle anything newer.