JPEG to PNG converter

JPG → PNG preserves the decoded JPEG pixels in a lossless container, but it cannot undo JPEG compression damage.

Converted with Image engine · nothing stored
Free: 5 conversions a day · 5 MB each
Higher limits →

From real runs

What you get — and what changes

Element	Result	What happens
Decoded pixels	Kept	The JPG is decoded and written to PNG without adding a new lossy compression pass.
Original JPEG artifacts	Kept	Block edges, mosquito noise, and softened detail from the JPG remain visible in the PNG.
Transparency	Lost	A normal JPG has no alpha channel, so the PNG starts fully opaque unless you edit transparency after conversion.
File size	Changed	PNG is commonly larger than JPG for photos because it stores the decoded pixels losslessly.
Metadata	Changed	EXIF and ICC handling depends on the decoder and PNG writer; use the original JPG for camera metadata.
Future edits	Kept	After conversion, repeated saves as PNG avoid additional JPEG losses while you annotate or composite the image.

Decoded pixels Kept
The JPG is decoded and written to PNG without adding a new lossy compression pass.
Original JPEG artifacts Kept
Block edges, mosquito noise, and softened detail from the JPG remain visible in the PNG.
Transparency Lost
A normal JPG has no alpha channel, so the PNG starts fully opaque unless you edit transparency after conversion.
File size Changed
PNG is commonly larger than JPG for photos because it stores the decoded pixels losslessly.
Metadata Changed
EXIF and ICC handling depends on the decoder and PNG writer; use the original JPG for camera metadata.
Future edits Kept
After conversion, repeated saves as PNG avoid additional JPEG losses while you annotate or composite the image.

Sample conversions

Photo required by a PNG-only form

Input: A 3000×2000 JPG portrait with mild compression artifacts around hair and a form that only accepted PNG uploads.
Output: A PNG that the form accepted. The hair artifacts looked exactly like the JPG because no lost detail was recovered.

Annotation workflow

Input: A JPG screenshot of a dashboard that needed arrows and labels added in an editor.
Output: A larger PNG used for downstream edits. Later saves did not add another round of JPEG compression.

A real JPEG → PNG run

We converted our JPEG sample (42 KB) with Image engine on 2026-10-20. It took 294 ms and produced a 133 KB PNG file, 3.1× larger than the input. The engine raised 1 warning, listed below.

Input · sample.jpg · 42 KB

1200 × 800 px, baseline

Width: 1,200
Height: 800
Encoding: baseline

Output · sample.png · 133 KB

1200 × 800 px, 8-bit, colour type 2

Width: 1,200
Height: 800
Encoding: 8-bit, colour type 2

Image metadata stripped from output.

Options and when to change them

width: Resize during conversion if the PNG-only target also has pixel-dimension limits.
height: Use with width for exact dimensions; leave unset to preserve the JPG's aspect ratio.
stripMetadata: Enable when camera EXIF from the JPG should not be carried into any PNG metadata chunks the encoder writes.

Do it yourself

ImageMagick 7

bash

magick in.jpg out.png

The command changes the container and compression method, not the image quality already lost in the JPG.

Pillow 11

bash

from PIL import Image

Image.open("in.jpg").save("out.png")

PNG output is lossless from the decoded JPG pixels, so it is often bigger than the input photo.

JPEG to PNG by API or MCP

The HTTP API and the MCP server run the exact engine this page uses (Image engine); the response carries the same warnings the web converter shows. Check support first with GET /api/v1/pairs?from=jpg&to=png.

curl

curl -X POST https://filetypeconverters.com/api/v1/convert \
  -H "Authorization: Bearer $FTC_API_KEY" \
  -F "file=@input.jpg" -F "from=jpg" -F "to=png" \
  -F 'options={"dpi":96}' \
  --output output.png

Options this engine accepts for JPEG → PNG

Key	Applies to	Type	Default
dpi	Reading JPEG	number	96
width	Writing PNG	number	0
height	Writing PNG	number	0
fit	Writing PNG	contain · cover · fill	contain
quality	Writing PNG	number	90
background	Writing PNG	string	#ffffff
stripMetadata	Writing PNG	boolean	true

API reference

When this is the wrong conversion

Do not use JPG → PNG to improve a blurry or over-compressed photo; find the original if quality matters.
Keep JPG for web photo delivery when broad compatibility and small files are the goal.
Use an editor with background removal if you need transparency; conversion alone cannot infer an alpha channel.

JPEG to PNG questions

Does JPG → PNG improve image quality?

No. It prevents another lossy save after conversion, but it cannot recover detail discarded by the original JPEG compression.

Why did the PNG get much larger?

PNG stores photo pixels losslessly. A JPEG photo is already compressed with a lossy model that is usually smaller.

Will JPG → PNG create transparency?

No. The PNG is opaque because the JPG has no alpha channel. Add transparency later in an image editor if needed.

When is JPG → PNG useful?

Use it when a target accepts only PNG or when you want to make lossless annotations after starting from a JPG.