PNG to JPG Converter

A PNG to JPG converter re-encodes a lossless PNG file as a JPEG, which is a lossy format built for photographs. PNG stores every pixel exactly, which is why a screenshot, a design export or a rendered chart leaves the app large and stays large. JPEG throws away detail the eye is poor at noticing, and for anything photographic or screenshot-like it produces a file a fraction of the size.

That size gap is the reason most people end up here. Gmail refuses a message once its attachments pass 25 MB. A handful of full-resolution desktop screenshots saved as PNG can push a message past that before you have typed a word. Drop those files here, leave Quality at 90% and each row shows the size before and after and how much smaller or larger the JPG came out, so you can see whether the batch now fits. The same arithmetic sits behind upload forms that cap a receipt or an ID photo at 2 MB.

Two things change on the way across. JPG has no alpha channel, so any transparent area is filled with white before encoding, and the file row says so when it happens. A logo on a transparent background becomes a logo on a white rectangle, which looks fine on a white page and obvious on a dark one. The conversion also runs through a canvas, so EXIF, GPS coordinates and color profiles are dropped. For a screenshot there is nothing to lose. For a camera photo you lose the capture date along with the location.

The converter reads the first bytes of each file instead of trusting the extension, so a PNG somebody renamed to .jpg years ago still converts correctly, and a file in another format, such as HEIC or TIFF, is turned away with a link to the converter for it rather than failing with a shrug. Everything runs client-side: nothing is uploaded, and once the page has loaded it keeps working with the network off. There is no cap on file size in bytes, though an image above 100 megapixels is refused because a browser tab cannot hold it. Free, no signup, with a daily limit on conversions.

• Conversion is client-side: images are decoded and re-encoded inside this tab with the built-in Canvas API, not a downloaded WebAssembly codec. The image files are never uploaded to a server.
• Before a batch runs, the page asks the Toolz server whether your daily limit allows it. That request names the tool and carries a device identifier, plus your account token if you are signed in.
• After a batch, the page records how many files converted, their combined size in bytes and the output format. File names, pixel data and image dimensions are not sent.
• If that check cannot reach the server, the conversion runs anyway, which is why the page keeps working offline once it has loaded.
• EXIF fields, GPS coordinates and embedded color profiles are not carried into the JPG, because the file is rebuilt from the decoded pixels alone. To strip metadata from a JPG without re-encoding it, use the EXIF remover.
• Converted files are held in the tab's memory until you remove them, press Clear All or close the tab. The converter keeps nothing in browser storage except the device identifier the daily limit uses.