How to Convert PNG to JPG Online Free

A PNG stores an image perfectly, pixel for pixel, and can include transparent areas. That makes it large. A JPG throws away detail your eye is unlikely to notice in exchange for a much smaller file, but it cannot be transparent. Converting PNG to JPG is the standard move when a screenshot or exported graphic is heavier than it needs to be and you do not need the transparency.

This is a lossless-to-lossy conversion, so the two big questions are how much quality you are willing to trade for size, and what to do about any transparent pixels, since JPG has no way to keep them. This guide explains what each format is actually doing, why the content of the image decides whether the trade is worth it, and how to avoid the common mistakes.

What changes when PNG becomes JPG

PNG uses lossless compression: the file rebuilds every pixel exactly. JPG uses lossy compression built around how human vision works, discarding fine color and detail that is hard to see. For a photograph saved as PNG, switching to JPG often cuts the file to a fraction of its size with no visible difference. For flat graphics with sharp edges and text, JPG is a worse fit, because its compression adds faint smudges and ringing around hard lines that PNG keeps crisp.

So the content decides the outcome. Photographic PNGs convert to JPG beautifully and get much lighter. Logos, screenshots of text, and diagrams usually look cleaner and often smaller staying as PNG or moving to WebP.

Lossless PNG versus lossy JPG

The two formats sit at opposite ends of the compression spectrum. PNG, the Portable Network Graphics format, is defined by a W3C specification and by RFC 2083, and it is lossless by design: it compresses using a combination of prediction filters and the DEFLATE algorithm, the same lossless method used in zip files.^[1] Before compressing, PNG runs each row through a filter that predicts each pixel from its neighbors and stores only the difference, which makes the DEFLATE pass far more effective on the smooth gradients and flat colors typical of graphics.^[2] Crucially, every pixel is reconstructed exactly, so a PNG never degrades no matter how many times it is opened and re-saved.

JPEG, standardized as ISO/IEC 10918 and wrapped in the JFIF interchange structure that produces a .jpg, works the opposite way.^[3] It is lossy: it converts color into a brightness-plus-color representation, discards much of the color detail because the eye is far more sensitive to brightness, transforms the image in 8-by-8 pixel blocks, and quantizes away the fine detail. This is wonderfully efficient for photographs and destructive for hard edges. Converting PNG to JPG therefore hands a perfect, lossless image to a compressor that will deliberately throw part of it away, which is exactly why it works for photos and hurts flat graphics.

How the conversion works under the hood

The converter first decodes the PNG, reversing its DEFLATE compression and filters to rebuild the exact grid of pixels the file describes, including an alpha channel if the PNG has transparency. Next, if transparency is present, it flattens the image: because JPEG has no alpha channel, every transparent or semi-transparent pixel must be composited onto a solid background color, blending partially transparent pixels with that background according to their opacity. Only then does it re-encode the flattened pixel grid with the JPEG algorithm at your chosen quality, and write out a standard .jpg.^[4]

Two things follow from this pipeline. First, the JPG's quality is set entirely by your quality setting, not by the PNG, because the image passes through a raw-pixel stage in the middle. Second, the flattening step is irreversible: once transparent pixels have been painted onto a background, there is no way to lift them back off, which is why choosing the right background color before you convert matters so much.

The transparency problem

This is the part people get caught by. If your PNG has transparent regions, JPG cannot store them. During conversion those transparent pixels have to be filled with a solid color, and if you do not choose one, the default is usually white or black. A logo with a transparent background will come out sitting on a white rectangle, which looks wrong on any colored page.

So before you convert a transparent PNG, decide what the background should be. If the image will always sit on white, filling with white is fine. If it needs to float on different backgrounds, JPG is the wrong target and you should keep the PNG.

Convert PNG to JPG, step by step

1. Open the converter and add your PNG

   Open the FileFormer image converter and drop your PNG in. It runs entirely in your browser, so the file never leaves your device.

2. Choose JPG and a background color

   Select JPG as the output. If the image has transparency, set the fill color to whatever the JPG will sit on, most often white.

3. Set the quality level

   Around 80 to 90 percent keeps the image looking sharp while shedding most of the size. Drop lower only if you need a very small file and can accept softer detail.

4. Convert and download

   Convert, compare the preview to the original, and save. If edges look smudged, the source was probably a graphic that belongs in PNG.

The quality setting and generation loss

JPEG's quality slider is really a control on how aggressively the encoder quantizes each block's frequency detail. A high setting keeps most of that detail and produces a large, near-perfect file; a low setting discards more of it and produces a small, visibly softer one. The relationship is not linear: going from quality 100 to 90 usually drops the file size sharply while barely touching the look, whereas going from 60 to 50 saves less and hurts more. For most photographic PNGs, a setting around 80 to 90 sits in the sweet spot where the file is much smaller and the difference is hard to see.

The subtler hazard is generation loss. Every time a JPG is opened, edited, and re-saved, the lossy compression runs again and removes a little more detail, and those losses accumulate. A PNG never suffers this because it is lossless. So if an image is still a work in progress that you will edit repeatedly, keep it as a PNG and only export to JPG once, at the very end, when the file is final.

Chroma subsampling and colored text

There is a second, quieter reason JPG mistreats graphics, and it explains why colored text and thin colored lines suffer the most. JPEG separates each pixel into a brightness component and two color (chroma) components, then usually stores the color at half or a quarter of the resolution of the brightness. This trick, called chroma subsampling, is nearly invisible on photographs, where color changes gradually, and it saves a lot of space. On a hard boundary between two different colors of similar brightness, though, such as red text on a green background, the low-resolution color channel cannot keep up with the sharp edge, and the color smears across it.

This is why a screenshot of colored code or a chart with thin colored lines can look noticeably degraded as a JPG even at a high quality setting: the brightness edges stay reasonably crisp, but the colors bleed. PNG has no such step, because it stores every pixel's full color exactly. When you must convert a graphic to JPG anyway, using the highest quality setting reduces the damage, and some encoders let you disable chroma subsampling entirely, but the cleaner answer for colored graphics is simply to keep them in PNG or move to WebP.

Why the PNG was large in the first place

It is worth understanding why a photographic PNG is often several times larger than the JPG it converts to, because that gap is the entire motivation for the conversion. PNG's lossless compression works by predicting each pixel from its neighbors and then packing the differences with DEFLATE. On a graphic with big flat areas of solid color, those differences are nearly all zero, so the file compresses superbly. On a photograph, though, almost every pixel differs slightly from its neighbors because of natural texture, gradients, and sensor noise, so the differences are large and varied, and there is very little for the lossless packer to remove. PNG faithfully stores all of that variation, which is exactly why a photo saved as PNG stays big.

JPG attacks the same photograph from the other direction. Instead of storing every tiny variation, it decides which variations the eye will not miss and discards them outright. That is why the conversion can cut a photographic PNG to a fraction of its size while looking the same: it is removing the very detail PNG was dutifully preserving. Flip the content to a screenshot or a logo, though, and the logic reverses. Flat graphics were cheap for PNG to store and are hard for JPG to store cleanly, so converting them saves little and costs sharpness. The size of the original PNG is a strong hint: a surprisingly large photographic PNG is the ideal candidate for JPG, while a small, flat PNG rarely benefits.

Real-world scenarios and settings

What the image contains, and whether it has transparency, decides the right move:

When to keep the PNG instead

Do not convert to JPG when the image needs a transparent background, when it is mostly text or line art, or when it will be edited and re-saved repeatedly. Each JPG save re-applies lossy compression, so an image that is opened, edited, and exported many times slowly degrades. PNG has no such penalty because it is lossless.

Reach for JPG when the source is photographic, the transparency is not needed, and the file is simply too big for email, a web page, or an upload limit. For anything with hard edges or transparency, keep the PNG or try WebP, which can compress like JPG while still supporting transparency.