FreeTinyPNG

JPG to PNG

Convert JPEG to PNG losslessly, in your browser, with no upload.

A JPG file icon on the left, an arrow with sparkles in the middle, and a PNG file icon on the right

How to convert JPG to PNG

  1. Drop your JPG files into the box above, or click to select. Multiple files work fine.
  2. Wait a moment while the tool re-encodes each image inside your browser.
  3. Download each PNG individually, or use Download all for the whole batch.

Everything happens on your device. Files never get uploaded anywhere.

Why convert JPG to PNG?

JPG is a lossy photographic format; PNG is a lossless general-purpose format. Converting from JPG to PNG doesn’t recover any of the detail JPG threw away during its original compression, but it does give you a file that:

  • Preserves every pixel from that point forward (no further quality loss across edits).
  • Supports transparency if you later add an alpha channel.
  • Works with tools and pipelines that require PNG input (some older CMSes, certain graphic design exports).

The most common use cases we see:

  • Preparing an image for editing in Photoshop, Affinity, or similar tools. Working in PNG means subsequent saves don’t accumulate JPG artifacts.
  • Adding transparency to a JPG (e.g. removing a background). JPG can’t hold alpha; PNG can.
  • Feeding a pipeline that demands PNG, like certain favicon generators, older e-commerce platforms, or print-layout software.

For simple sharing or web publishing, keep the original JPG. Converting to PNG will only make the file larger without improving what the viewer sees.

How much bigger will the PNG be?

Significantly. A typical 1 MB JPG photograph becomes a 4–6 MB PNG after conversion. PNG’s lossless compression works well on flat colors and hard edges, but natural photographic detail is exactly what PNG handles badly.

If you care about file size, don’t convert photographs to PNG for delivery. Keep them as JPG or convert to WebP instead. See our JPG to WebP / PNG to WebP guide.

When to use this tool (and when not to)

Good fits:

  • You need a lossless working copy for editing.
  • You need to add transparency or other features PNG supports.
  • A specific tool demands PNG input.
  • You’re archiving an image and file size isn’t a concern.

Bad fits:

  • You want smaller files. JPG is already the smaller format for photos.
  • You think PNG is “higher quality” than JPG. It isn’t — it’s higher fidelity preservation. Once JPG compression has happened, PNG can’t undo it.
  • You’re publishing to the web. Stay with JPG, or convert to WebP or AVIF.

How the tool works

When you drop a JPG file in, the browser:

  1. Decodes it into a bitmap in memory.
  2. Paints it onto an HTML5 canvas.
  3. Re-encodes the canvas as a PNG using the browser’s native PNG encoder.
  4. Offers you the resulting PNG as a download via an in-memory blob URL.

All four steps happen in your browser’s JavaScript engine. There’s no server involved. You can verify this by opening DevTools, switching to the Network tab, and watching while you process a file. You won’t see any outbound request carrying your image data.

Preserving transparency vs. flattening

JPG files never carry alpha (transparency). If you start with a JPG, the resulting PNG will be fully opaque. If you want to add transparency, you’ll need to do that in an image editor after conversion — the tool can’t invent transparency that didn’t exist in the source.

Metadata and EXIF

The conversion re-encodes through a canvas, which strips EXIF metadata, color profiles beyond sRGB, and any other non-pixel chunks. This is usually what you want for privacy (no GPS, camera model, or timestamps leaked), but be aware that color profiles are also dropped. For most web uses this isn’t a problem; for color-critical workflows, handle profile conversion in your editor.

If metadata stripping is the main reason you’re converting, our dedicated EXIF stripper keeps the original format while scrubbing metadata.

Common mistakes

  • Converting JPG to PNG and expecting smaller files. PNG is bigger for photographic content.
  • Assuming conversion “upgrades” the image quality. JPG’s lossy compression isn’t reversible.
  • Converting a JPG photograph to PNG before publishing to the web. This increases page weight without visible benefit.
  • Forgetting that canvas re-encoding strips metadata. If you need the color profile, keep the original.

A note on batch size

The tool processes files serially in the browser to avoid memory spikes. A batch of 50 high-resolution photos will take a minute or two to finish, with each file completing one at a time. Larger batches are fine; very large single files (over a few hundred MB) may strain the browser’s memory.

Frequently asked questions

Is this free? Are there limits?
Yes, free with no signup, no watermark, and no rate limit beyond your device's capacity.
Will my files be uploaded anywhere?
No. Everything happens in your browser via the Canvas API. Verify with DevTools → Network tab.
Will the PNG be larger than the JPG?
Yes, typically 4–6× larger for photographs. PNG's lossless compression is less effective on natural images.
Can I add transparency after converting?
Yes, but you'll need an image editor. JPG has no transparency information, so the converted PNG starts fully opaque.
Does this tool strip metadata?
Yes. The canvas re-encoding process drops EXIF, GPS, and other metadata automatically. For explicit metadata stripping that preserves the original format, use our EXIF stripper.