About this tool
JPG (also called JPEG) is the most universally compatible image format. Every email client, every printer, every old document scanner, every mobile device opens JPGs. PNG, WebP, GIF, and HEIC each have their advantages, but when you need maximum compatibility - a print order, an old CMS, an Office document, a passport agency - JPG is the safe choice.
This tool re-encodes any source image to JPG in your browser. Quality slider lets you trade off file size against fidelity (typical sweet spot: 80-85). Transparency from PNG/WebP is flattened against a configurable background color (default white). EXIF metadata is stripped on save unless you opt in to keep it.
How it works
Open the source
Drop or pick a PNG, WebP, GIF, BMP, or HEIC image.
Pick a quality
Default 85 works for almost everything. Drop to 70-75 for big size savings; raise to 95+ for archival.
Pick a background color (transparency only)
JPG has no transparent pixels. Pick white (default), black, or a custom color to fill where the source was transparent.
Download the JPG
The result saves as filename.jpg. The original is unchanged.
Use cases
Print labs
Most print order systems require JPG. PNG screenshots and WebP downloads have to be converted first.
iPhone HEIC photos
iPhones save HEIC by default. Many older Windows / Android apps cannot open HEIC. Converting to JPG fixes the compatibility.
Email attachments
JPG attachments display inline in every email client. PNG and WebP can show as broken thumbnails.
Office documents
Word, PowerPoint, and Excel embed JPGs cleanly. WebP support varies by Office version.
Web pages with broad legacy support
Sites supporting browsers older than 2015 should serve JPG fallbacks alongside WebP.
Format and spec details
| Source formats | PNG, WebP, GIF (first frame), BMP, HEIC, AVIF, TIFF |
|---|---|
| Output format | Progressive JPG / JPEG |
| Quality range | 0-100, default 85 |
| Transparency handling | Flattened to user-picked background color |
| EXIF metadata | Stripped by default; opt-in to preserve |
Tips and best practices
- For photos: quality 80-85 is the universal sweet spot. Bigger files give you no visible benefit.
- For graphics with hard edges or text: keep PNG. JPG block artifacts on text are very visible.
- For the web: consider WebP first - typically 30% smaller than JPG. Use Image to WebP.
- Convert HEIC to JPG before sending to a Windows user, a print lab, or a third-party app that does not support HEIC yet.
Why convert images to JPG
JPG is the universal photographic format - every device, browser, and print pipeline supports it. Lossy compression makes files 5-10x smaller than PNG for the same visible quality, which is why social platforms, email, and CMS uploads all default to JPG.
Image format comparison
| Format | Compression | Transparency | Animation | Color depth | Browser support |
|---|---|---|---|---|---|
| JPG / JPEG | Lossy | No | No | 8-bit | Universal (since 1992) |
| PNG | Lossless | Yes (alpha) | No (APNG ext.) | 8/16-bit + alpha | Universal (since 1996) |
| WebP | Both | Yes | Yes | 8-bit + alpha | All modern (96% global) |
| AVIF | Lossy (AV1) | Yes | Yes | 10/12-bit HDR | Chrome, Firefox, Safari 16+ |
| GIF | Lossless palette | 1-bit | Yes | 256 colors | Universal |
| HEIC / HEIF | Lossy (HEVC) | Yes | Yes | 10-bit HDR | iOS, macOS, Win10+ |
File size comparison (same 1920x1080 photo)
WebP is ~40% smaller than JPG for the same visible quality. AVIF is ~60% smaller, but still has slower encoders and limited compatibility with older Windows tools.
When NOT to convert
- To JPG, if you have transparency: JPG drops alpha. The transparent pixels render as your chosen background colour.
- To JPG repeatedly: every save loses quality (generation loss). Re-edit from the original whenever possible.
- To PNG, if you need small files: PNG can be 5-10x larger than JPG. Use only when transparency or lossless quality is required.
- To WebP, if your audience is on very old systems: IE11 and pre-2020 email clients (Outlook 2019, etc.) don't render WebP.
How browser-based conversion works
This tool uses the HTML5 Canvas API. When you drop a file:
- FileReader reads the image into a binary blob that stays in your browser memory.
- An <img> element decodes the blob to a bitmap.
- A <canvas> of matching dimensions is created, and the bitmap is drawn onto it.
- canvas.toBlob() re-encodes the bitmap to your target format at your chosen quality.
- URL.createObjectURL produces a download link to that blob.
The original file never uploads anywhere - all of the above happens in your tab. The encoded output exists only in your browser until you download it.
Quality settings demystified
JPG and WebP quality is a 0-100 scale. It's not linear - quality 85 keeps ~95% of perceived detail at ~25% of the file size compared to quality 100. The sweet spot for photos is quality 80-85. Drop to 70-75 for thumbnails, raise to 95+ for archival masters.
Privacy and offline operation
Every operation in this tool runs client-side using your browser's built-in APIs (Canvas, Web Audio, WebAssembly). No data is uploaded. After the initial page load you can disconnect from the internet and the tool keeps working.
We use Google Analytics and AdSense for the page itself, but neither sees the content of the files you process.
Frequently asked questions
Why are my converted JPGs huge?
Quality 95+ stores nearly all detail and produces near-source file sizes. Drop to 80-85 for a 60-80% size reduction with no visible loss.
Does converting PNG to JPG lose quality?
Yes - PNG is lossless and JPG is lossy. The first save introduces compression artifacts. For archival or screenshots, keep PNG.
Can I keep transparency?
Not in JPG - the format does not support transparency. Convert to PNG or WebP if you need transparent pixels.
What about HEIC photos from my iPhone?
iPhone photos save in HEIC format by default. This tool reads HEIC where the browser supports it (Safari 13+, Chrome 119+ via flag) and converts to widely-compatible JPG.
Is the file metadata preserved?
EXIF is stripped on save by default for privacy (GPS, camera serial, etc.). Toggle the "Preserve EXIF" option to keep it.
Are uploaded images sent to a server?
No. All conversion happens in your browser using the Canvas API. The file never leaves your device. You can disconnect from the internet after the page loads and the tool still works.
Will the converted file have the same dimensions?
Yes by default. The canvas is sized to match the source image's intrinsic width and height. EXIF orientation is automatically applied so phone photos won't appear rotated.
What happens to EXIF and metadata?
Most converters (including this one) strip EXIF on re-encode for privacy. GPS coordinates, camera serial number, and timestamps are all removed unless explicitly preserved by an option.
Can I convert in bulk?
Yes - drop multiple files at once. Each is converted independently and produces its own download link. Large batches may slow your browser; convert 20-50 at a time.
Why is my converted file larger than the original?
Usually because the original used a more efficient algorithm. Converting a JPG to PNG always makes the file larger (PNG is lossless). Converting an AVIF to JPG also typically grows the file.
Does HEIC work in this browser?
Safari 13+ and Chrome 119+ (with flag) decode HEIC natively. Other browsers fall back to JavaScript decoders that work but are slower. The tool will tell you if your browser cannot read your file.
What's the best image format for 2026?
Depends on the use case. For new web content: WebP for most images, AVIF if you can serve format negotiation, PNG for transparency, SVG for vectors. JPG remains the safe universal fallback. Phone screenshots: PNG or WebP lossless.
Does converting reduce quality?
Lossy-to-lossy (JPG to WebP) introduces a small additional loss. Lossless-to-lossy (PNG to JPG) introduces visible loss but smaller files. Lossless-to-lossless (PNG to WebP lossless) is pixel-perfect.
Why does JPG support vary by browser?
Different browsers adopted different formats at different times. WebP: universal as of 2020. AVIF: Chrome 85+, Firefox 93+, Safari 16+. HEIC: native to iOS/macOS, limited elsewhere. Modern best practice is multi-format
Should I use AVIF for everything?
Not yet. AVIF is ~30% smaller than WebP at the same quality but takes 10-100x longer to encode and isn't supported in older browsers. Use AVIF for hero images where bandwidth matters; WebP everywhere else.
How do I batch-convert hundreds of images?
This tool processes one at a time in the browser. For large batches, use desktop tools: ImageMagick (cross-platform CLI), Squoosh CLI (per-file), or build-time pipelines like sharp (Node), Pillow (Python), or imgix/Cloudinary (managed).
Are my images uploaded to a server when I convert here?
No. All conversion happens in your browser using the HTML5 Canvas API. The image stays in your tab's memory; nothing is sent. Verify by opening browser DevTools, Network tab - no upload requests fire.