Ask five professionals which format to use for Web Design and you'll get five confident, conflicting answers. The data is less ambiguous: each format buys a specific trade-off, and Web Design rewards some trade-offs much more than others.
The 2026 shortlist
| Format | Compression | Transparency | Animation | Support (2026) |
|---|---|---|---|---|
| WebP | Lossy and lossless | Yes | Yes | over 96% of browsers in use in 2026 (caniuse) |
| AVIF | Lossy and lossless | Yes | Yes | over 93% of browsers in 2026, including Chrome, Firefox, Safari and Edge |
| JPEG | Lossy | No | No | every browser and device made in the last 25 years |
| PNG | Lossless | Yes | No | every browser since the early 2000s |
| SVG | Vector | Yes | Yes | all modern browsers |
Five formats cover effectively every Web Design scenario. What separates them is below.
Start with WebP
25-34% smaller than an equivalent JPEG, per Google's published study, with support across over 96% of browsers in use in 2026 (caniuse). For most Web Design work that combination — smaller files, near-universal support, transparency and animation included — makes WebP the sensible starting point. The WebP converter turns existing JPEG/PNG libraries into WebP in batches.
AVIF: when every kilobyte counts
AVIF goes further: roughly half the size of a comparable JPEG, and about 20% under WebP. Encoding is slower and very old browsers miss it (over 93% of browsers in 2026, including Chrome, Firefox, Safari and Edge), so the classic pattern is AVIF first with a fallback. Try one hero image through the AVIF converter and compare.
JPEG and PNG: the safety net
JPEG remains the file that opens absolutely everywhere — email clients, ancient CMS installs, kiosk software. PNG keeps its role wherever Web Design needs sharp edges, text or transparency: a 1080p screenshot is typically 150-400 KB; a 12-megapixel photo can exceed 15 MB.
Don't rasterize your logos
Logos, icons and diagrams belong in SVG: icons usually weigh 1-10 KB, less than a single photo thumbnail, and they stay crisp at any resolution. Exporting a logo as a 2,000-pixel PNG when an 8 KB SVG exists is the most common self-inflicted wound in Web Design.
Putting it together
Photographs go modern (WebP or AVIF) with a JPEG fallback where compatibility is unknown. Graphics and UI go PNG or SVG. Everything gets resized to its real display dimensions before upload — serving a 4000-pixel image in an 800-pixel slot is pure waste — and below-the-fold images get loading="lazy".
The quality dial matters more than the tool: JPEG at 80-85% is visually identical to 100% for most photos and roughly half the size.
Measuring the result
Run the page through PageSpeed Insights before touching anything and note two numbers: total image weight and Largest Contentful Paint. Those are your baseline.
Convert the images, redeploy, run the same test. On image-heavy pages the LCP shift is usually visible on the first re-test — that delta, not a blog's promise, is what justifies rolling the change across the whole site.
If the numbers barely move, your bottleneck is elsewhere — scripts or server response — and you just saved yourself from optimizing the wrong thing.
The rest of the image checklist
Filenames describe the subject in plain words with hyphens — search engines read them, and so do you in six months. Alt text describes the image for screen readers and image search in one natural sentence, not a keyword pile.
Dimensions in the HTML (width and height attributes) stop layout shift, the CLS half of Core Web Vitals. Large previews need one meta line — max-image-preview:large — for Google Discover to show your images at full size.
None of these depend on the format, and all of them compound with it: a light, well-described, properly-sized image is the complete package for Web Design.
Where the rules bend per platform
WordPress converts uploads to WebP on modern versions but keeps the original — uploading lighter files still pays. Shopify and most e-commerce platforms recompress aggressively; feed them the highest-quality source and let the CDN do the dirty work.
Email is the conservative corner: stick to JPEG and PNG, keep total weight low, and assume the oldest client in the audience.
Web Design: quick decisions
Photos and hero images: WebP, or AVIF where you control the stack. Logos, icons, diagrams: SVG, with PNG as the raster fallback. Screenshots and UI captures: PNG.
Email attachments and downloads: JPEG, because it opens on whatever the recipient has. Short animations: animated WebP over GIF — same clip, a fraction of the megabytes. Print handoffs: TIFF or high-resolution PNG, never a web-compressed file.
Tape this list next to the upload button: every Web Design decision above repeats weekly, and deciding once beats re-debating it per file.
What happens to EXIF and metadata
Every photo from a camera or phone carries hidden baggage: capture date, device model, exposure settings and — on phones — often GPS coordinates. Conversion is one of the moments where that baggage can be kept or dropped.
For files headed to the public web, dropped metadata is a privacy feature: nobody needs your home coordinates embedded in a product photo.
The practical rule: treat the original as the metadata archive and the converted copy as the public version. That division of labour answers most privacy and copyright questions before they come up.
The three classic errors
Serving originals. Uploading camera files straight from the device puts multi-megabyte images behind every thumbnail. Resize to display dimensions first; the format choice comes second.
One format for everything. Photos, screenshots and logos compress on different curves — forcing them all into one format guarantees at least one of them is badly served.
Never measuring. PageSpeed Insights and Lighthouse both show exactly how many kilobytes your images cost. Run the test once before and once after converting, and the improvement stops being theoretical.
What this means for page speed
Images are usually the heaviest asset class on a page, so format choice flows straight into Largest Contentful Paint — the Core Web Vitals metric Google weighs for ranking. Lighter images, earlier paint, better scores: the chain is that direct.
The compounding is what surprises people: 200 KB saved per image across a forty-image page is eight megabytes a visitor never downloads.
Measure before and after with PageSpeed Insights — the image-weight line item makes the improvement concrete instead of theoretical.
Common Questions
What single format should I pick for Web Design if I must choose one?
WebP. It compresses 25-34% under JPEG, supports transparency, and reaches over 96% of browsers in use in 2026 (caniuse) — the rare case where the convenient answer and the technically correct one match.
How much speed do modern formats actually buy?
On image-heavy pages, converting a JPEG library to WebP typically trims a quarter to a third of image weight; AVIF roughly halves it. Since images dominate page size, that translates directly into faster loads and better Core Web Vitals.
Should logos be PNG or SVG?
SVG whenever the logo exists as vector art — a few kilobytes, infinitely sharp. PNG is the fallback for raster-only logos or platforms that reject SVG uploads.
Does Google rank pages by image format?
Not directly — Google ranks the outcome. Image weight drives Largest Contentful Paint, and Core Web Vitals feed rankings, so a lighter format improves SEO through speed rather than through the file extension itself.
How many formats should one Web Design project use?
Usually three: a modern format for delivery, a universal fallback, and SVG for vector assets. More than that and the upload rules stop being memorable, which is when mistakes creep back in.
Do stock photos need converting before upload?
Often yes — stock sites deliver maximum-quality JPEGs sized for print, not for pages. Resize to display dimensions and convert to your delivery format, and a 12 MB download becomes a 200 KB asset.
Start small: convert one page's images this week, measure the load time before and after, and let the result decide how far you roll it out.
Written by Giovanni Picaro, a web developer who has been building image tools and optimizing sites since 2019. Sources: MDN image format reference and Google web.dev. Last reviewed: 2026.