PNG to JPG converter

Start with the deliverable, not the format

Illustrative scenario: Priya exports a badge from her design tool as PNG, then a conference form rejects the upload because the field only accepts JPG. Her real requirement is not "make it smaller" — it is a JPG that still reads correctly on the cream page the badge sits on. That framing changes which settings matter.

A delivery target usually has three demands: the container (JPG), the size ceiling, and legibility at the size people will actually look at. Write those down first, then pick settings to satisfy them, instead of converting and hoping.

• Container: JPG has no alpha channel, so transparency must be resolved before encoding
• Size: quality is the lever, not a guaranteed ratio — the same PNG can shrink a lot or barely move
• Legibility: text, thin borders and small grey captions degrade before anything else does

Work backwards to the three settings

This route exposes exactly three controls: Background for transparent areas, Quality, and Size. There is no custom colour field — the background is chosen from White, Black and Paper.

1. Pick the background that matches where the JPG will be displayed, not the image itself
2. Set Quality: 90 is the default and a fair starting point for photographs; drop to 70–80 for email and chat
3. Leave Size on Original unless the target has a pixel limit — 75%, 50% and 25% are fixed steps, not a slider
4. Convert one file first, look at it, then run the rest of the batch

The background decides whether edges look intact

The canvas is filled with your chosen colour and your PNG is drawn on top, so semi-transparent pixels blend into that swatch rather than vanishing. A dark logo flattened onto White gets a pale halo around the strokes; flattened onto Paper it sits on a warm ground that matches a cream page. Soft drop shadows from UI screenshots blend well onto White or Paper and turn muddy onto Black.

Photos rarely carry meaningful alpha, so the default White is harmless there. The choice matters most for cut-out artwork, overlays and anything with feathered edges.

What disappears on the way out

JPG is a different representation, not a renamed PNG. Knowing what is dropped is the difference between a surprise and an expected result.

• Alpha is gone — transparent and partly transparent pixels become your background colour
• Colour profile and embedded text metadata are not carried into the output
• An animated PNG decodes as its first frame only; animation is not preserved
• Dimensions stay unchanged unless you chose a smaller Size step
• Detail discarded by JPEG's lossy block compression cannot be recovered later by converting back to PNG

Check the result before you send it

Compare the two file sizes rather than assuming a saving. Flat-colour graphics are the common surprise: PNG's dictionary-style compression handles large areas of one colour very well, while JPEG smears banding and ringing around hard edges, so a logo or screenshot can come out larger and softer as JPG. That is a normal outcome, not an error.

1. Open the JPG at the size it will be displayed, not zoomed to 100%
2. Look at text and thin borders first — they are the earliest casualties at low quality
3. Check the flattened edge against the real background colour of the destination page
4. If the JPG is bigger than the PNG, keep the PNG or try WebP instead

Converting to JPG is a delivery decision, not an upgrade. You are trading exact pixels and transparency for a file every viewer and mail client opens without question.

How this route is intended to be used

When to keep PNG instead

Transparent stickers, favicons, charts with crisp lines, screenshots of UI and anything you will crop or re-export later all benefit from lossless storage and alpha. If the goal is simply a smaller file rather than a JPG specifically, WebP often beats JPEG at similar visual quality — that route is on this site as PNG to WebP.

• Keep PNG when the asset needs transparency or will be edited again
• Keep PNG for text-heavy captures where readable edges matter
• Choose JPG when the destination is a photo attachment, a form upload or a gallery page
• Batch work is capped at 10 files per run, each up to 25 MB

Questions