Convert JPG to PNG
Worth doing when a file has to stop degrading: PNG is lossless, so repeated edits keep every pixel. It cannot restore what the JPG already threw away.
🔒 100% client-side · zero server upload
Results
Everything runs in this browser tab. Nothing is uploaded.
Malaysian rules & edge cases
Nine conversions, one rule. Any of JPEG, PNG and WebP can become any of the three. The output type is read from the bytes the encoder actually produced — not from the label you picked — so a file named .webp is a real WebP or the tool says why not.
| Output | Transparency | Quality dial | Typical size |
|---|---|---|---|
| JPEG | No — transparent pixels take the background colour you choose (white by default) | 0.3–0.95 | Smallest for photos; the format every form, portal and print shop accepts |
| PNG | Kept | None — lossless | Largest. A photo converted from JPEG to PNG is usually 3–5× bigger, because PNG cannot throw detail away |
| WebP | Kept | 0.3–0.95 | Smallest of the three at the same visual quality; every current browser reads it, older Office installs do not |
What happens to the pixels. The EXIF orientation is read first and baked into the image, so a portrait photo stays portrait once the tag that described it is gone. Then the image is redrawn through a canvas and encoded again — which is why every conversion drops the camera model, the GPS fix, the timestamp, the software tag and the colour profile. Wide-gamut photos (Display P3, Adobe RGB) come back as sRGB: slightly less saturated, never shifted in hue.
What it does not do. It does not resize: 4000 px in stays 4000 px out, except an image above 16.7 megapixels, which is scaled into the canvas limit and says so on its row. It does not read HEIC, AVIF or GIF, and it cannot make a JPEG transparent — no tool can add an alpha channel that was never recorded.
Honest limit. WebP output needs a browser that can really encode it. Safari on iOS and macOS cannot, and asking for image/webp there silently returns a PNG — so this tool checks the type of the bytes it got and, when it is not WebP, saves a JPEG named .jpg and says so. AVIF output is not offered at all: no browser's canvas can encode it (Chrome answers a request for AVIF with a PNG), and a fake would be worse than an omission.
A batch is one download. Two or more images arrive as a single ZIP, built inside the tab, with duplicate names numbered (baju.jpg, baju-1.jpg) instead of overwriting each other. Nothing leaves the device: open the Network panel, press Run, and no request appears.
Before and after
Before
logo-kedai-kopi.png — 1000×1000 — transparent background
produk-shopee-01.jpg — 1200×900 stored, EXIF orientation 6 — iPhone 15 Pro — GPS 3.1390, 101.6869After
logo-kedai-kopi.jpg — 1000×1000 — transparency filled with white
produk-shopee-01.webp — 900×1200 upright — camera, GPS and date removedHow it works
- Drop your images, or press "Load sample data" for a transparent PNG logo and a product photo that really carries camera, GPS and orientation tags.
- Choose the output format. For JPEG, pick the colour that goes under transparent pixels; quality applies to JPEG and WebP only, because PNG is lossless.
- Press Run, check each row — real size, real dimensions, what was removed — then download one image or the whole batch as a ZIP. Nothing left this tab.
FAQ
Will the photo get sharper?
No. The detail a JPEG discarded when it was saved is gone for good; converting to PNG preserves what is left, exactly. Anyone promising "convert to PNG for better quality" is describing a one-way door, not a repair.
When is JPG to PNG actually the right choice?
When the next step is editing or compositing: a PNG survives repeated saves, and tools that stack layers prefer it. For a final web or WhatsApp image, JPG is far smaller — this conversion is a working step, not a delivery format.
Does this add transparency?
No. A JPEG has no alpha channel, so the PNG comes out fully opaque. Adding transparency needs an editor with a background-removal step; this tool never invents pixels that were not in the file.