JPG to PNG

The conversion creates a new file from the pixels your browser decodes. It does not restore an earlier camera original, undo JPEG artifacts or automatically remove a background. PNG makes the next save lossless, but the source pixels have already passed through JPEG compression.

What changes when JPG becomes PNG

JPEG and PNG solve different storage problems. JPEG is generally effective for photographs because it uses lossy compression. The W3C PNG specification defines a lossless raster format with optional alpha transparency, but converting an opaque JPEG does not invent alpha values.

The main benefit is not a visual upgrade. It is avoiding an additional lossy format when the next application requires PNG or when you plan to add transparency, text, shapes or other edits later in software that supports those operations.

How to convert JPG to PNG on this page

1. Add JPG files. Choose or drop up to 30 .jpg or .jpeg files. Each file can be up to 40 MB, and the complete batch can total up to 200 MB.
2. Choose dimensions. Keep the browser-decoded dimensions, or limit the longest side to 4096, 2560, 1920 or 1600 pixels. Smaller images are not enlarged.
3. Convert. The browser decodes each JPEG, optionally resizes the pixels and creates a PNG with Canvas.
4. Inspect the result. Review the preview, actual bytes, source and output dimensions, JPEG frame type, sample precision, color-component count and known metadata status.
5. Download. Save one PNG or package all successful conversions in a ZIP archive.

There is no PNG quality slider because this implementation uses the browser's lossless PNG encoder. A slider would imply a lossy visual-quality choice that the current tool does not provide.

Lossless output does not restore JPEG detail

“Lossless PNG” describes how the new PNG stores the pixels it receives. It does not describe the full history of those pixels.

If the JPG contains block boundaries, ringing around text, smeared texture or color banding, those effects become part of the decoded image. The PNG stores them faithfully. It cannot infer which pixels existed before the JPEG was created.

The same rule applies to repeatedly edited JPEGs. Converting the latest JPG to PNG stops future PNG saves from adding JPEG loss, but it does not reverse the loss from earlier exports. Keep an original RAW, TIFF, PSD, PNG or high-quality camera file when future editing quality matters.

This distinction connects directly to the result panel: compare the preview rather than expecting sharper detail, and check whether the dimensions were retained. If the PNG appears different beyond expected browser color handling or resizing, do not discard the source JPG.

Why the PNG can be much larger

JPEG deliberately discards information that human vision may notice less in photographs. PNG must encode the complete decoded pixel pattern without that type of loss. Natural photographs contain many small variations in color, noise and texture, which are expensive for PNG compression.

A 2 MB JPEG can therefore become a 10 MB, 20 MB or larger PNG. Those numbers are only illustrative; the actual result depends on dimensions and pixel content. A flat illustration or simple screenshot that was unnecessarily stored as JPEG may show a smaller difference, while a noisy camera photo can expand dramatically.

Do not use JPG to PNG as a file-size reduction method. If the destination accepts JPEG and smaller bytes are the goal, use Image Compressor or reduce dimensions. If the destination specifically requires PNG, the larger file may be an unavoidable result of the format choice.

ZIP download keeps multiple files together, but PNG files are already internally compressed. ZIP may provide little additional size reduction for the image data itself.

Choose dimensions for the next task

Keeping original dimensions preserves the browser-decoded width and height. Choose this when another application needs the same pixel grid, when you plan to annotate or edit the image, or when the required size is not yet known.

A longest-side limit resizes only larger images:

• 4096 or 2560 pixels retains substantial detail for large displays and continued editing.
• 1920 pixels is practical for many presentations, websites and ordinary screen use.
• 1600 pixels can reduce memory and transfer size when very high resolution is unnecessary.

For example, a 4000 × 3000 JPEG limited to 1920 pixels becomes 1920 × 1440. A 1200 × 800 JPEG remains 1200 × 800 because the tool does not upscale it.

Resizing is a real quality change. It removes pixels before PNG encoding. The result report shows both source and output dimensions so you can verify the change instead of relying only on the selected preset.

Transparency, metadata and color

PNG supports transparency, but a normal JPEG source does not tell the converter which pixels should be transparent. White, black or any other background is part of the visible image. This page does not perform segmentation, background removal or color-based deletion, so the PNG remains opaque.

The source inspector identifies baseline or progressive JPEG frames and reports common APP and comment segments, including EXIF, XMP, ICC, IPTC/Photoshop and comments when detected in the scanned marker data. These are source observations, not retained output features.

Canvas export creates a new PNG from decoded pixels. It does not copy source GPS, camera settings, orientation tags, captions, copyright fields or embedded color profiles. Browser decoding may apply orientation and color management before drawing. Use a metadata-aware or color-managed desktop workflow when those fields and profiles must remain verifiable.

Metadata removal can reduce accidental sharing, but it is not a complete privacy guarantee. Inspect the generated file before publishing sensitive images.

Check the generated PNG

Review the result in this order:

1. Orientation: confirm the browser-decoded image is upright and no edge is missing.
2. Dimensions: compare source and output width and height to verify whether the size limit applied.
3. Visible artifacts: remember that existing JPEG blocks, halos and softness are expected to remain.
4. File size: compare actual bytes; a large increase is common for photographs.
5. Opacity: confirm that the PNG still includes the original visible background.
6. Metadata: assume source metadata and profiles are not present in the output.

The result also reports whether the source frame is progressive or baseline/sequential. That affects how a JPEG can load, not the visible purpose of the final PNG. The PNG is newly encoded and does not preserve the JPEG scan structure.

Illustrative JPG to PNG examples

Prepare a JPEG for annotation

Assume a 2400 × 1600 JPEG will be opened in an editor that expects PNG. Keep the dimensions and convert. The output remains 2400 × 1600 and is saved losslessly, but any JPEG artifacts remain visible and the PNG may be much larger.

Reduce a camera photo before creating PNG

Assume a 6000 × 4000 JPEG is needed only for a 1920-pixel presentation slide. Choose the 1920-pixel longest-side limit. The PNG becomes 1920 × 1280, reducing the pixel count before lossless encoding.

Convert a batch for a PNG-only system

Assume twelve JPEG files are accepted only as PNG by a legacy workflow. Keep the required dimensions, convert the batch, inspect any failed-file notice and download the successful results as one ZIP.

Illustrative examples. Exact PNG bytes depend on the decoded pixels, dimensions and browser encoder.

When JPG to PNG is useful

Conversion is reasonable when:

• A specific application or upload field requires PNG.
• You need a lossless intermediate before adding text, shapes or transparency in another editor.
• A development workflow expects PNG assets.
• You want to avoid another JPEG encoding step during a later save.

Keep the JPG when it is already accepted, storage or transfer size matters, and no PNG-specific workflow follows. For photographs, PNG often adds bytes without adding visible information.

Local conversion and alternatives

The converter services reviewed for this guide cover broader hosted workflows:

• CloudConvert supports a hosted multi-format conversion process and additional conversion controls.
• Convertio is useful when source files come from supported cloud storage or a wider output-format catalog is needed.
• FreeConvert provides a hosted workflow with additional image settings and import options.

base97 is narrower. Its verified differences are local browser processing, JPEG marker and frame inspection, an intentionally absent fake PNG quality control, per-file failure isolation, detailed output comparison and individual or ZIP downloads. It does not claim smaller PNG files or restored image quality.

This version does not support URLs, cloud imports, server conversion, background removal, transparency creation, palette optimization, PNG compression-level selection, metadata retention, per-file settings or exact target sizes.

Troubleshoot JPG to PNG conversion

The file is rejected before conversion

The page checks the JPEG start marker and searches for a supported frame header. Renaming another file to .jpg does not create a JPEG. Export or obtain the source again in the correct format.

The PNG is much larger

This is expected for many photographs. Reduce the longest side if the destination permits smaller dimensions, or keep the JPG when PNG is not required.

The image is not sharper

PNG stores the decoded JPEG pixels losslessly; it does not reconstruct missing information. Find an earlier or higher-quality source when sharper detail is required.

The background is still visible

The background is made of ordinary opaque JPEG pixels. Use a dedicated background-removal or masking workflow after conversion if transparency is needed.

Orientation or colors differ

The browser may apply JPEG orientation and color information while decoding, but Canvas does not copy the original metadata or profile to the output. Use a color-managed metadata-aware application when exact preservation is required.

Conversion becomes slow

Large decoded images require substantial browser memory. Convert fewer files at once or reduce the source dimensions. This page blocks images above 12,000 pixels on either side or 60 megapixels.

JPG to PNG FAQ

Does converting JPG to PNG improve image quality?

No. PNG prevents another lossy encoding step, but it cannot restore detail, color precision or clean edges already lost in the JPEG source. The visible pixels normally remain equivalent to the browser-decoded JPG unless you also resize them.

Why is the PNG larger than the JPG?

JPEG is designed to compress photographic content by discarding information. PNG stores the decoded pixels losslessly, so photographs with many colors and textures often require substantially more bytes as PNG.

Will JPG to PNG create a transparent background?

No. A normal JPEG has no alpha channel, so the decoded pixels are opaque. This page converts those opaque pixels to PNG and does not identify or remove a background.

Does the PNG keep EXIF, GPS or an ICC profile?

No. The source report can detect several common JPEG metadata segments, but the Canvas-created PNG does not copy EXIF, GPS, XMP, IPTC, comments or ICC profiles from the source.

Are my JPG files uploaded to base97?

No. The current tool checks, decodes, resizes, encodes and packages the selected files with browser-side code on the current device. It does not send those image files to a base97 server.