Four in-depth guides on choosing formats, compressing for the web, handling iPhone HEIC photos, and keeping your images private. Want more? Browse all 16 in our full guides library.
Pick the wrong image format and you either bloat your page with needless megabytes or wreck the quality of a logo. The choice comes down to three questions: does the image need transparency, is it a photo or a graphic, and does it need to load fast on the web?
PNG is lossless. Every pixel is preserved exactly, and it supports full alpha transparency with 256 levels of partial opacity. That makes it perfect for logos, icons, screenshots, line art, and anything with sharp edges or text. The cost is file size: a photograph saved as PNG can be five to ten times larger than the same image as JPG, with no visible benefit.
JPG (also written JPEG) is lossy. It discards image data your eye is unlikely to notice in order to shrink the file dramatically. For photographs at 80–90% quality, the result is visually identical to the original at a fraction of the size. The trade-off: JPG cannot store transparency, and re-saving the same JPG repeatedly slowly degrades it.
WebP is the modern compromise. It supports both transparency and lossy compression, and at the same visual quality it typically produces files 25–35% smaller than JPG. Every current browser supports it. The only reason not to use WebP everywhere is legacy compatibility with very old software.
The quick rule
Photograph for the web? JPG at 80%, or WebP for even smaller files.
Logo, icon, or anything with transparency? PNG, or WebP if your targets support it.
Want the best of both? Export your main format and a WebP copy alongside it — the converter above does this in one click with the "Also export WebP" option.
Property
PNG
JPG
WebP
Compression
Lossless
Lossy
Both
Transparency
Yes
No
Yes
Best for
Graphics, logos
Photos
Web everything
Typical size (photo)
Largest
Small
Smallest
Browser support
Universal
Universal
Modern
Animation
APNG (rare)
No
Yes
Optimization
How to Compress Images for Web Performance Without Losing Quality
Images are the heaviest thing on most web pages, which makes them the biggest opportunity to speed a site up. The good news: you can usually cut image weight by 70–90% with no visible loss, if you do two things in the right order.
Step one: resize before you compress
The most common waste is serving an image far larger than it's displayed. A 4000-pixel-wide photo shown in an 800-pixel slot forces the browser to download and shrink five times more data than needed. Resize the image to the largest dimension it actually appears at first — that alone often halves the file before any compression.
Step two: find the quality sweet spot
For almost every photograph, 80% quality is the sweet spot. It removes detail your eye genuinely cannot perceive while cutting file size by half or more. Drop below about 60% and you start to see blocky artifacts in skies, gradients, and shadows. Push above 90% and you pay in bytes for detail nobody notices.
Rule of thumb: resize to display size, then export at 80% quality. Most images shrink 70–90% with no difference you can see on screen.
Why this beats "just compress harder"
Aggressive compression on an oversized image still leaves you with a bloated file full of detail that gets thrown away on display. Resizing first means every byte you keep is a byte that actually reaches the viewer's screen. Combine the two and you get the smallest possible file at the quality you chose — which is exactly what the quality slider and resize presets in the tool above let you do together.
iPhone & HEIC
Opening HEIC Photos on Windows: The Complete iOS Guide
You copied photos off your iPhone, opened them on a Windows PC, and got files ending in .HEIC that won't preview or open. You're not doing anything wrong — this is by design, and there are two clean ways around it.
Why HEIC exists
Since iOS 11, iPhones save photos as HEIC (High Efficiency Image Container) by default. It's a genuinely better format — roughly half the file size of JPG at the same quality, with support for richer colour. The catch is that Windows, Android, and most websites can't read it without extra software, because the underlying compression is patent-encumbered.
Option 1: Convert the HEIC files you already have
The fastest fix is to convert your existing HEIC photos to standard JPG. The HEIC to JPG tab in the converter above does this instantly and entirely in your browser — your photos are never uploaded anywhere. Drop them in, download JPGs, done. This is the right choice when you've already got HEIC files to share or edit.
Option 2: Stop your iPhone making HEIC files
To prevent the problem going forward, change your camera format: open Settings → Camera → Formats → Most Compatible. From then on, your iPhone captures photos as JPG. Existing HEIC photos are unaffected — this only changes new ones.
You never need to buy a codec from the Microsoft Store. Converting in the browser is free, private, and works on any device.
Privacy
Why Client-Side Conversion is the Future of Image Data Privacy
Most online image converters work the same hidden way: you "upload" your file, their server processes it, and sends a result back. It feels instant, but in those few seconds your private photo, contract scan, or screenshot has travelled to a company's computer you'll never see — and often been written to disk there, however briefly.
The problem with server-side tools
Once your file leaves your device, you lose control of it. You're trusting a privacy policy you didn't read, a retention schedule you can't verify, and a server you can't audit. For casual memes that may be fine. For anything sensitive — medical images, legal documents, unreleased work, personal photos — it's a real exposure.
How client-side conversion is different
Client-side means the work happens entirely inside your own browser, using built-in web technology: HTML5 Canvas for drawing and re-encoding, and WebAssembly for heavier decoding like HEIC. Your file is read into your browser's memory, processed there, and offered back to you as a download. It never touches a network.
No uploads — nothing to intercept, log, or leak.
No server storage — there's no copy of your file anywhere but your device.
Faster — there's no upload-and-wait round trip, so large batches finish quicker.
Works offline — once the page is loaded, conversions run with no connection at all.
For anyone handling confidential or corporate images, this isn't a nice-to-have feature — it's the only model that can honestly promise privacy. That's why every tool on this site runs locally, and why the badge at the top says "safe for corporate data" without an asterisk.