Convert JPG to PNG Online
Save a JPG as PNG when a presentation or editing workflow needs lossless storage for subsequent saves. This preserves the decoded image without another JPEG compression pass, but cannot restore detail already lost in the original JPG.
Your JPG image is decoded and converted in your browser on your own device without any server upload. Both the source and PNG preview stay in temporary tab memory and are cleared when you close or reload the page.
Drop your image here
or choose an image from your device
Accepts JPG images. PNG keeps every pixel exactly, so the copy is often larger than the JPG you started with.
Need your documents as one PDF? Convert images to PDF.
If the lossless copy is too wide for a document, reduce its pixel dimensions with Resize Image.
Converting a JPG to PNG gives you a lossless copy to keep editing — every re-save from this point on stores pixels exactly rather than re-compressing them. Done entirely in your browser, no upload involved.
About JPG to PNG
What this conversion changes and what it doesn't
The JPG is decoded to raw pixels and re-encoded as PNG, which stores every pixel exactly with no further loss. It does not undo the compression the JPG already applied — any blockiness or softness baked into the source is carried into the PNG unchanged. What you gain is a stopping point: further edits and saves from here won't degrade the image further.
Why file size jumps up
JPG throws away detail the eye barely notices to get small; PNG has to record every pixel it's given. In a measured test on a 1920 × 1080 landscape JPG (384 KB on disk, decoding to 8.29 MB of 32-bit RGBA canvas memory), re-encoding to lossless PNG produced a 2.41 MB file because PNG must preserve every high-frequency pixel variation and existing 8×8 JPEG block boundary. That's the cost of losslessness, not a fault in the conversion — see JPG vs PNG for a side-by-side breakdown.
Settings
No quality control, by design
PNG encoding is lossless, so there's nothing to adjust here — pick the file, convert, download. If the resulting PNG is too large for your use, that's a job for the PNG Compressor with WebP or JPG output, not for this tool.
When to use it
- Preparing a JPG photo to edit repeatedly without stacking new compression damage each save.
- Adding a transparent background to a photo in an editor that needs an alpha channel to work with.
- Meeting an upload requirement that specifically asks for PNG.
Limitations to know
- Detail already lost by the original JPG encoder cannot be recovered.
- The output is always larger than the source, sometimes by 5–10x.
- The PNG starts fully opaque — transparency has to be added afterwards in an editor.
Common problems and fixes
Why does my converted PNG look exactly as blurry as the JPG?
Because the blur was already in the JPG. Converting to PNG freezes the current state losslessly — it can't restore detail an earlier compression pass discarded.
The PNG file is enormous compared to the JPG. Is that normal?
Yes, that's expected for photographic content — PNG stores every pixel exactly. If you need a small file, keep it as JPG or convert onward to WebP.
Can I make the background transparent during this conversion?
No — the source JPG has no alpha data to preserve. You'd need a background-removal tool or manual editing after converting to PNG.
How to use it
- 1Drop a JPG (or JPEG) file onto the upload area, or click it to browse. Files stay on your device — nothing is uploaded.
- 2Check the metadata line: the original size and pixel dimensions are read from the decoded file, not from the filename.
- 3Press Convert. The JPG is decoded to a canvas and re-encoded as a lossless PNG, so no further detail is lost from this point.
- 4Compare the before and after byte counts, then download. Expect the PNG to be larger — that is normal and explained below.
What happens to your file
Your JPEG is decoded in this tab and written into a lossless PNG canvas without sending the photo to a conversion server. Both the selected file and preview live in temporary browser memory; use Download to save the PNG to your device before refreshing. Usage analytics may record format and approximate megapixel bracket, never your photo pixels or filename.
PNG keeps every pixel exactly, so the copy is often larger than the JPG you started with.
Full details are in the Privacy Policy.
When not to use this
Converting a JPEG to PNG will not remove the blocky artefacts already baked into the photo, and it will not create a transparent background around your subject.
If your goal is a smaller attachment, this is the wrong direction: the lossless copy usually weighs more. Use the JPG Compressor instead and keep the photograph as a JPEG.
Frequently asked questions
When does converting a JPG to PNG actually make sense?
Convert when you plan to edit and re-save the image repeatedly, when you want to add an alpha channel for background erasure in a graphics editor, or when a strict upload portal only accepts .png files.
Is there any size limit?
There's no fixed megabyte cap. Because decoding happens in your browser's memory rather than on a server, the only limit is your own device: we estimate the decoded size of the image and either process it normally, process it in chunks with a warning, or explain clearly when it's beyond what any browser tab can hold.
Can I batch-convert several JPGs to PNG?
Not in one action — each file is dropped, converted and downloaded individually. That keeps the browser tab's memory usage predictable even for large photos.
Does the PNG keep the JPG's colour profile?
The canvas re-encode works in the browser's sRGB space, so a JPG tagged with an unusual colour profile (e.g. Adobe RGB from a camera) can shift slightly. Most consumer photos are already sRGB and convert without a visible change.
Why does the tool show two different byte counts before I even convert?
The metadata line reads the JPG's real file size and pixel dimensions from the decoded image, not from the filename or a guess — that number is what the PNG's size gets compared against afterwards.