Convert JPG to PNG

Turn JPG images into PNG files right in your browser. No upload, no signup, no watermark.

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.

Processed in your browser

Drop your image here

or choose an image from your device

Accepts JPG images · No fixed size limit — we adapt to what your device can handle. Very large files may take longer or show a warning.

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. A 400 KB JPG commonly becomes 2–4 MB as a PNG. That's the cost of losslessness, not a fault in the conversion.

Settings and output

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

  1. 1Drop a JPG (or JPEG) file onto the upload area, or click it to browse. Files stay on your device — nothing is uploaded.
  2. 2Check the metadata line: the original size and pixel dimensions are read from the decoded file, not from the filename.
  3. 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.
  4. 4Compare the before and after byte counts, then download. Expect the PNG to be larger — that is normal and explained below.

Frequently asked questions

Why is my PNG bigger than the JPG I started with?

PNG stores every pixel exactly, while JPG throws detail away to get small. A photo that was 400 KB as a JPG is routinely 2–4 MB as a PNG. You are paying for losslessness from here on, not recovering what the JPG already discarded.

Does converting to PNG improve the image quality?

No. JPG compression is permanent, so any blockiness or softness in the source is baked into the PNG too. What PNG gives you is a file that won't degrade further when you edit and re-save it.

Will the PNG have a transparent background?

Not automatically. JPG has no transparency information, so the converted PNG is fully opaque. It does gain an alpha channel, which means you can erase to transparent in an editor afterwards.

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.

Related guides