Input
JPG
Output
PNG
Runtime
Browser

Convert JPG to PNG Online

Create a lossless PNG copy of a JPG in your browser for editing, compatibility, or a future transparency workflow.

Local processingNo sign-upBatch and ZIP export

Convert on this device

Files stay in this browser tab. Nothing is uploaded to Tool Swim.

Private by design

Drop JPG files here

Up to 40 MB per file, 20 files, and 120 MB of source data per batch.

What the output keeps

Metadata

Canvas output removes EXIF, GPS, captions, and most embedded metadata.

Animation

This source format is treated as a single static image.

Color profiles

The browser decodes color before export; wide-gamut and HDR appearance can change.

A practical guide

Example: product-photo.jpg → product-photo.png

Move a compressed product photo into a PNG-based editor workflow before adding labels or transparent layout space.

Why turn a JPG into a PNG

JPEG is built for compact photographic images. PNG is a lossless raster format with strong support across browsers, editors, presentation tools, and content systems. Converting a JPG to PNG can help when the next application rejects JPEG, when a workflow standardizes assets as PNG, or when repeated editing would otherwise add another round of JPEG compression on each save. The new PNG stores the pixels it receives without introducing a fresh lossy encoding step.

The conversion cannot recover information that JPEG already discarded. Existing block artifacts, ringing around edges, and softened details become part of the PNG. File size often increases substantially because PNG must describe photographic variation losslessly. That increase is expected and does not mean the image gained resolution or detail.

Transparency starts after conversion

A JPG has no alpha channel, so converting it does not automatically remove a background. The initial PNG will normally look opaque because every source pixel remains present. The benefit is that PNG can hold transparency after you edit it with a background-removal or selection tool. If the JPG contains a white studio background, that white is ordinary image data until an editor deliberately makes those pixels transparent.

Soft edges deserve attention. Hair, shadows, glass, and antialiased logos may include colors blended with the old background. Simply deleting pure white can leave a pale fringe. Refine the edge in an editor, then keep the edited PNG as the master for transparent uses.

What happens to metadata and color

Browser conversion decodes the JPG and redraws it before exporting PNG pixels. This canvas path normally drops EXIF fields such as camera model, capture time, GPS coordinates, copyright notes, and the orientation tag. The browser usually applies decoded orientation to the visible pixels, but you should still open the result and confirm it is upright. Remove metadata intentionally only when that matches your recordkeeping and privacy needs.

Color appearance can depend on how the browser reads an embedded ICC profile and how it writes the output. A normal screen image will often look consistent, yet profile-critical brand, print, medical, or scientific imagery needs a color-managed application and a verified export rather than an assumed match.

Lossless does not mean unchanged bytes

PNG compression is lossless for the decoded pixel values, but the output is a new file with a new encoding. Different encoders can choose different filters and compression strategies, so two visually and pixel-identical PNGs may have different sizes and checksums. This is normal recompression. It matters when a system expects an exact file hash, but not when the destination simply needs the same displayed pixels.

Animated JPEG variants and unusual multipart files are not preserved as animation. A browser canvas uses a single decoded image, so only the first available frame becomes the PNG. Use a specialized sequence tool for multi-frame sources.

Check the PNG before using it

Compare the result at its natural pixel dimensions. Look closely at edges and gradients to distinguish old JPEG artifacts from conversion problems. Confirm that the width and height match the source and that the file opens in the intended editor or upload form. Because PNG photographs can be large, test real page performance before choosing the result as a web delivery asset.

Keep the original JPG if it came directly from a camera or supplier. It may contain useful metadata and will often be much smaller. Use the PNG as a working derivative, and make any later JPEG or WebP delivery copy from the cleanest available master rather than repeatedly converting between lossy files.

If the PNG is headed into an editing workflow, plan the next operation before converting a large collection. Cropping, masking, and adding type can benefit from a lossless intermediate, but simple photo placement often does not. Test one representative image in the actual editor, including save and export behavior, before processing the rest. Some applications silently convert imported PNGs or downsample oversized canvases, which removes the advantage you expected. Record the original dimensions and compare the editor's final export with the browser-created PNG. For web publishing, generate the eventual JPEG or WebP from the edited PNG only once, use the display dimensions the page needs, and keep that delivery file separate from the larger working copy.

Questions and answers