Convert PNG to JPG online, free

The ratio depends on how much detail and color variation the image holds, not its pixel size. Two screenshots of the same dimensions can compress quite differently.

The lesson is narrow and useful. If your PNG holds photographic content or a busy screenshot, JPG shrinks it hard. If your PNG holds flat color and crisp edges, the savings drop and the costs rise, which is the next part of the story.

The transparency tradeoff, front and center

This is the single fact that decides whether converting helps or wrecks an image. JPG has no alpha channel. It cannot store a transparent pixel at all. PNG can, and many PNG files rely on that.

When imgkilo converts a PNG with transparent areas to JPG, those areas must become a solid color, because JPG needs a value for every pixel. The converter fills transparency with white. For a huge range of images that is exactly what you want.

Think of a photo with a transparent border, a screenshot with rounded corners cut out, or a scan with a faint transparent margin. Flatten any of those onto white and the result looks identical to viewing the PNG on a white page.

The trouble begins when transparency is doing real work. A company logo exported as a transparent PNG is built to sit on a dark website header, a colored email banner, or a printed flyer. Convert it to JPG and that transparent space turns into a hard white rectangle.

Drop the logo onto a navy header and you get an ugly white box around it. The same failure hits icons, badges, stickers, watermarks, and any graphic meant to float over a background that is not white.

So the test is simple. Ask what sits behind the transparent pixels in real use. If the answer is white, or it does not matter, convert freely. If the answer is a color or a photo, keep the PNG or move to a format that preserves the alpha channel.

When you should convert PNG to JPG

Photos saved as PNG are the clearest case. Cameras and phones already shoot JPG, but images get re-saved as PNG by editing tools, screenshot utilities, and design apps all the time. A photo has no transparency and no hard edges that JPG struggles with, so conversion gives you the full size cut with no downside.

Large screenshots are the second strong case. A full-screen capture of a web page, a spreadsheet, or an app window is photographic enough that JPG handles it well, and these files are often too big to email. Converting a 3 MB screenshot to a 250 KB JPG makes it pass upload limits and load fast for whoever opens it.

Scanned documents and receipts fit here too. A scan is a flat photo of paper, and JPG at high quality keeps the text readable while shrinking the file enough for portals that cap uploads at 100 KB or 200 KB. Anything bound for a web page as a content photo, a blog header, a gallery image, or an avatar belongs as JPG so the page stays light.

The common thread is clear. Continuous tone, no meaningful transparency, and a destination that cares about file size. When those three line up, PNG to JPG is the right move every time.

When you should not convert

Logos and brand marks top the list. They are usually transparent, they often contain sharp type, and they end up on backgrounds you do not control. Converting them to JPG breaks both the transparency and the crisp edges in one step.

Icons and line art share the same problems. A 32 pixel icon or a black-on-white diagram is mostly hard edges and flat fills, exactly the content PNG stores well and JPG handles badly. You gain little size and add visible fuzz around every line. If you are unsure which format suits an image, the MDN image format reference lays out the tradeoffs clearly.

Anything that needs perfectly sharp text edges should stay as PNG. Think of UI mockups with small labels, code snippets captured as images, or infographics dense with type. JPG smears the boundary between black text and white background just enough to look soft when zoomed. If the image is mostly words, PNG keeps them crisp.

Anything that must keep transparency stays out of JPG too. If you need both small size and a working alpha channel, that is a different job than this tool does. You can convert to WebP instead, which keeps the transparent pixels and still compresses hard, or keep it as a compressed PNG when you want lossless edges.

Quality settings and what JPG does to text

JPG is lossy, which means every save throws away some detail to save space. How much it throws away is the quality setting. At the top of the range the loss is invisible. As you push quality down, artifacts appear, and they show up first and worst around hard edges.

This matters for screenshots because screenshots are full of hard edges: the border between a button and its background, the stroke of a letter against white. JPG can add faint halos or speckles around those edges, an effect called ringing. On a photo you will never notice it. On a screenshot full of small text, low quality makes the type look slightly smudged.

The fix is to keep quality high for anything text-heavy. imgkilo defaults to quality 88, which holds text crisp for almost every screenshot. If a capture is dense with small labels, nudge it to 92.

Reserve the lower settings, 75 to 80, for pure photos where the extra compression buys real size and the eye forgives the loss. There is no single correct number, but the rule of thumb is steady: more text means higher quality.

One more habit worth keeping. JPG loss compounds every time you re-save. Convert from the original PNG once, at the quality you want, and keep that JPG. Do not convert a JPG to JPG over and over, because each pass degrades the image further.

The screenshot size problem on macOS and Windows

Both macOS and Windows save screenshots as PNG by default, and that default is why so many people need this conversion. A screen capture on a modern high-resolution display can be 8 megapixels or more, and PNG stores all of it. A single screenshot at 3 to 6 MB is normal.

That size collides with everyday limits. Email providers cap attachments, often at 25 MB total, and a handful of PNG screenshots eats that fast. Support portals, job forms, and bug trackers often reject anything over a few hundred KB. Chat tools accept the file but make everyone wait while it loads.

Converting the screenshot to JPG solves all of it at once. A 4 MB PNG capture becomes a 400 KB JPG that looks the same on screen, attaches without complaint, and uploads under almost any cap. Because screenshots have no transparency to lose, there is no tradeoff to weigh beyond the small care around text quality covered above.

If you take a lot of screenshots, the batch matters. Select a folder of PNG captures, drop them all onto imgkilo at once, and get a single ZIP of JPGs back. Up to 100 files at 50 MB each go in one batch, processed in parallel right in the browser tab.

Practical jobs this tool is built for

Trimming an email attachment is the most common one. You have three or four PNG photos to send, and together they break the size limit. Convert them to JPG at quality 85 and the same set drops well under the cap with no visible change, so the message goes through.

Getting under a portal upload cap is the next. Bank verification, government forms, and account dashboards often demand a JPG under a fixed size. Convert your PNG scan or photo and most images land inside a 200 KB ceiling at once. If you need to hit an exact KB target like 100 KB, the sibling tool iterates the quality for you.

Preparing photos for the web rounds it out. A product photo, a blog image, or a gallery thumbnail saved as PNG is dead weight on a page. Converting to JPG cuts most of the bytes, which means faster loads and lighter pages for visitors and search engines alike.

Across all of these, the work happens on your device. The PNG is redrawn onto a Canvas, encoded as JPG, and handed back, with no file ever leaving your browser. Free, no account, no ads, and ready for the next batch the moment the first one finishes.