When this tool is useful
Photographs, scans, and screenshots that do not need transparent pixels or pixel-perfect edges.
How local processing works
PNG pixels are decoded locally, composited onto a fixed white background, then encoded as JPEG at the selected quality.
How to use it
- Choose the source files.
- Review the available settings and page order.
- Process locally, inspect the result, and download it.
Important limitations
Logos, text-heavy graphics, and transparency can look worse in JPEG. PNG may remain the better choice for those assets.
Verify the downloaded result
Reopen the downloaded file in its destination application, check dimensions or page count and visible content, and keep the source until the result has been accepted.
Private by design
Your files stay in this browser. The tool does not upload the source or output to our servers.
Questions and answers
Does this tool upload my files?
No. Processing happens in your browser; closing the page clears the working session.
Will the output always match the source exactly?
Logos, text-heavy graphics, and transparency can look worse in JPEG. PNG may remain the better choice for those assets.
What should I check before using the result?
Reopen the downloaded file in its destination application, check dimensions or page count and visible content, and keep the source until the result has been accepted.
Which browsers and devices are supported?
Use a current browser with JavaScript, workers, canvas, WebAssembly where the format requires it, Blob downloads, and enough memory. Reopen important downloads in the destination application.
Concrete input and output example
Input a 3000×2000 PNG scan at 9MB and export JPEG quality 88. A much smaller JPG is plausible, but small type and sharp diagram edges should be compared before deleting the PNG.
Browser compatibility notes
Reviewed against the implementation and required web APIs on 2026-08-12. Use a current browser where these APIs are available and verify important output on your device.
- Chrome / Edge (current desktop)
- Requires local decode, canvas, encoding, Blob download, and enough memory; verify the downloaded image.
- Firefox (current desktop)
- Uses the same standard local APIs; color rendering can differ slightly from Chromium.
- Safari (current desktop)
- Uses canvas and Blob downloads; available memory and codec behavior remain WebKit-controlled.
A tool-specific question
Why do letters look fuzzy after PNG to JPG?
JPEG is optimized for continuous-tone photos and can add ringing around hard text edges. Keep PNG for UI, logos, and small type.