JPG to PNG without inventing transparency
Use jpg to png when a tool, a publisher, or a build step asks for PNG and the picture you have is a JPEG. The output starts as PNG. The photo does not gain transparency it never had: every pixel that was opaque stays opaque. Quality is on the page because this converter shares its controls, but the useful fact is the wrapper. Expect the PNG to be larger than the JPEG. The work stays in this tab.
Loading tool…
or drop / paste
How to turn jpg to png
- Add a JPEG. Drop, paste, or Choose files. Up to one hundred JPEGs can be wrapped in one run, all to the same output.
- Leave the output on PNG. That is the default here. Switching to JPG does nothing useful, and switching to WebP is a different page, jpg to webp.
- Do not expect a background colour to punch a hole in the photo. The background field matters when the source has alpha. A JPEG does not. The PNG will be a solid picture.
- Ignore the urge to chase a smaller file with the quality slider. PNG output stores the decoded pixels. If the JPEG was the size you needed, the PNG will usually be heavier.
- Press Convert images and download the PNG. More than one result can be a ZIP. Open it and confirm the corners are still opaque before you send it on.
JPG to PNG options explained
Output defaults to PNG. The JPEG is decoded and written as PNG. No alpha channel is invented. A white sky stays white pixels, not clear pixels.
The background colour, default #ffffff, is used when a source has transparency and the destination cannot store it. On a JPEG input there is nothing to paint. Changing the colour does not erase the photo.
Quality defaults to 80 on the shared control. For this hop the PNG is the decoded picture, not a second JPEG. Do not read the slider as a way to make the PNG lossy. Compress png is the page that can posterise on purpose.
The file often grows. PNG is a poor way to store a camera photo. Use this page because something demanded PNG, not because you wanted fewer bytes. Compress jpeg is the page for a smaller JPEG.
A wrapper, not a cut-out
People open jpg to png hoping the background will fall away. It will not. The JPEG never stored which pixels were background. The PNG holds the same rectangle, including the sky, the paper, and the white margin. Cutting that out is a different job, and this site does not do it.
What you do get is a PNG that other tools will accept: a lossless container around the pixels as decoded. Text in the photo stays as blurry or as sharp as the JPEG already was. The conversion does not sharpen and does not add pixels.
Why the PNG is usually larger
A camera JPEG is already a compact lossy file. Wrapping those decoded pixels in PNG stores them without that JPEG packing, so the download is often several times larger. That is expected. If the next step only checks the extension, the larger file is still the right output.
If you needed both a PNG and a small file, you will be disappointed by quality alone. After the wrap, compress png can try a lossless OxiPNG pass. It will not return you to the JPEG size. Colour reduction would, and it is lossy on purpose. Decide that on the compress png page, not by accident here.
What stays behind in the JPEG
The new PNG is a fresh file. Do not assume camera, date, or GPS notes are the point of this page. If sharing the photo without those notes is the actual task, remove exif data remuxes the JPEG so the pixels stay identical. Converting to PNG is the wrong tool for a metadata-only edit.
Dimensions do not change. A sideways picture stays sideways until you rotate it. This page does not apply a crop. One hundred files is the batch limit, and they all become PNG with the same limitation: opaque pixels in, opaque pixels out.
Limits, formats and output
| Accepted input | JPEG |
|---|---|
| Files per batch | 1–100 |
| Soft size warning | 50 MB each |
| Hard stop | 500 MB total in memory |
| Output | The chosen image format, or a ZIP for a batch |
| Account | None. The tool runs in this tab. |
Your file never leaves your device
This JPEG is wrapped as a PNG by code in this browser tab. The work runs in a Web Worker in this tab, using WebAssembly for the heavy parts, and the result comes back as a local blob. This site does not upload the file, store it, or log its name.
To verify: load the page, turn on airplane mode, and drop the file again. It still finishes. Or open DevTools, choose Network, and watch the run: there is no upload. The architecture is described on How it works.
Frequently asked questions
Will the PNG have a transparent background?
No. JPG to PNG does not invent transparency. The JPEG had no alpha channel, so the PNG is opaque. White or coloured areas stay painted pixels. This page cannot tell a sky from a subject.
Why is the file bigger?
The JPEG was lossy and compact. The PNG stores the decoded pixels without that packing, so it usually grows. That is the trade for a PNG extension. If you wanted a smaller photo, stay on compress jpeg instead.
Does the background colour do anything?
Not on a JPEG source. The colour is for transparency in other hops, and it defaults to #ffffff. A JPEG has nothing clear to composite. Editing the field will not knock out the photo.
Does quality 80 blur the PNG?
The PNG is the decoded JPEG written out as PNG. The quality slider is the shared converter control. It does not posterise the PNG. The softness you see was already in the JPEG.
Can I wrap a batch?
Yes, up to one hundred JPEGs, all saved as PNG. Download a ZIP when more than one file is ready. Check the sizes. A folder of camera photos can become a much larger ZIP than the folder you started with.
Will GPS be removed?
This page is a format change, not the metadata tool. The download is a new PNG of the pixels. For a JPEG whose pixels must stay identical while camera, date, and GPS are removed, use remove exif data.
Last updated 2026-09-26. By Tam.