There is no single best format for every website photo. Start by comparing lossy AVIF, WebP and JPEG at a quality level that still looks good at the image’s real display size. Prefer AVIF or WebP when the measured file is smaller and your visitors can receive it; keep a suitable fallback for older or constrained browsers. JPEG remains a practical compatibility choice. If the image is not a photograph—such as a logo, screenshot or diagram—the answer changes.
Choose the format by image type
Photographs contain continuous tones and usually tolerate carefully tuned lossy compression. Text, icons and hard edges do not: artifacts around letters or lines are immediately visible. Decide from the asset’s content, required transparency or animation, audience compatibility and measured output rather than from a format name alone.
| Asset or requirement | Good starting point | What to verify |
|---|---|---|
| Photograph | Compare lossy AVIF, WebP and JPEG | Visual quality at the rendered size, encoded bytes, decode and delivery support, and a fallback for the actual audience |
| Screenshot, diagram, line art or logo | PNG, or lossless WebP/AVIF where supported | Text and edges must remain crisp; lossy ringing may be more objectionable than a larger file |
| Transparent artwork | PNG, WebP or AVIF | JPEG has no alpha channel, so it cannot preserve transparent pixels |
| Scalable vector artwork | SVG | Use SVG for genuinely vector shapes, not a photorealistic scene |
| Animation | WebP, AVIF or APNG when supported | Whether animation is needed, frame quality, file size and browser support; GIF is broadly recognized but often less efficient |
AVIF, WebP and JPEG for photographs
AVIF
AVIF is a modern lossy or lossless choice worth testing for photographic assets. It can produce a useful reduction, but the result depends on the source, encoder and quality setting. Measure your own images and provide a fallback when the audience or delivery stack requires one.
WebP
WebP supports lossy and lossless compression and can carry transparency. Google for Developers reports that WebP lossless images were 26% smaller than PNGs and that WebP lossy images were 25–34% smaller than comparable JPEGs at equivalent quality. Those are published comparisons, not guarantees: content, encoder settings and the visual-quality target change the result.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →#1 Best Overall
JPEG
JPEG remains a broad-compatibility fallback for photographs. It is unsuitable when the image must include transparency, and repeated re-encoding can compound visible artifacts. Use a quality setting that looks clean at the size visitors see, then compare the bytes with AVIF and WebP.
Transparency, graphics and SVG
Choose PNG, WebP or AVIF when an alpha channel is required. PNG is a dependable option for screenshots and graphics with text; lossless WebP or AVIF may be smaller where your browser and image pipeline support them. Inspect the actual edges, small type and flat-color regions rather than assuming that the smallest file is the best-looking one.
SVG is a source format for vector artwork: icons, diagrams and logos made from paths and shapes remain sharp at any scale. It is not a practical replacement for encoding a complex photograph.
Serve modern formats without breaking compatibility
The HTML picture element lets the browser select a modern source and fall back to an ordinary img. Keep the fallback appropriate to the asset: JPEG is common for an opaque photo, while PNG is common for a sharp graphic or transparency.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →<picture>
<source type='image/avif' srcset='/images/hero.avif'>
<source type='image/webp' srcset='/images/hero.webp'>
<img src='/images/hero.jpg' width='1600' height='1067'
alt='A hiker crossing a ridge at sunrise' loading="eager" decoding='async'>
</picture>Use dimensions that match the rendered slot (or include responsive srcset and sizes) so the browser does not download a needlessly large image. Test the fallback path, not only the newest browser you use yourself.
Server-side content negotiation
An image service or web server can inspect the request’s Accept header and return AVIF, WebP or a fallback. This centralizes format selection, but the cache must vary correctly on Accept, and the server must send the matching Content-Type. Verify that your CDN, cache and origin agree on the variants before deploying the approach site-wide.
A repeatable quality-and-size workflow
- Classify the asset. Mark it as a photograph, sharp graphic, transparent artwork, vector or animation.
- Set the real display target. Record the CSS dimensions and the largest device pixel ratio you intend to support; do not judge a thumbnail at 400% zoom.
- Encode candidates. Produce AVIF, WebP and JPEG for a photo; PNG or lossless modern formats for text-heavy graphics. Keep the encoder and quality settings documented.
- Inspect critical details. Check faces, foliage, gradients, shadows, small labels, diagonals and transparent halos at the rendered size and at a closer inspection size.
- Measure bytes and loading. Compare transferred size, dimensions and decode behavior on representative devices and connections. A smaller file is useful only if it still looks acceptable and does not create a slower decode path for your audience.
- Publish a fallback. Use
pictureor correctly configured content negotiation, then test a browser that takes the fallback branch. - Monitor real pages. Images can be Largest Contentful Paint candidates, so oversized files can delay loading. Format conversion alone does not guarantee a ranking improvement; measure page performance and user experience.
Performance decisions beyond the file extension
- Dimensions first: Do not send a 3000-pixel image into a 600-pixel card. Generate responsive widths and let
srcset/sizesselect one. - Above-the-fold priority: Avoid lazy-loading the image that is the page’s main above-the-fold content; lazy-load images that start below the viewport when appropriate.
- Cache deliberately: Give immutable, fingerprinted variants long cache lifetimes. When filenames cannot change, plan an invalidation strategy.
- Keep metadata purposeful: Remove unnecessary camera metadata from public derivatives, but preserve information your workflow or accessibility process genuinely needs.
- Validate delivery: Confirm the response’s MIME type, compression, cache status and selected variant in browser developer tools.
Common mistakes and fixes
Using JPEG for transparent artwork
JPEG cannot store alpha. Export a PNG, WebP or AVIF variant and check the edges against both light and dark backgrounds.
Converting every image to one format
A universal conversion can damage screenshots, logos or line art. Classify assets and use lossless encoding where text and edges demand it.
Trusting an average compression claim
Published WebP comparisons are tendencies. Your image’s texture, noise, palette, encoder and quality target may produce a smaller or larger result. Keep the claim qualified and measure your own output.
Serving AVIF or WebP without a fallback
Older browsers, embedded webviews and unusual crawlers may not accept the modern source. Add an img fallback and verify it is reachable.
Expecting an SEO boost from a format switch
Smaller images may improve transfer time, and images can affect LCP, but the available guidance does not establish that changing formats alone raises rankings. Treat SEO as a measured performance outcome, not a format promise.
Automate screenshot and visual checks without browser setup
If your format workflow needs repeatable captures of pages, you can use ScreenshotNeo, a website screenshot API and MCP server. It is useful for checking how AVIF/WebP fallbacks, transparent assets and responsive layouts actually render.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsRank #4
Or skip the browser setup
One GET request returns a PNG, JPEG, WebP or PDF. The service accepts the consent banner like a visitor and removes more than 60 known consent platforms, newsletter popups and chat widgets before capture; each cleanup step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads and cache hits cost nothing, and response headers identify the page verdict and whether the request was billed.
curl -G 'https://api.screenshotneo.com/v1/shot' -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for parameters. The same request in Python:
import requests
r = requests.get('https://api.screenshotneo.com/v1/shot', params={'access_key': 'YOUR_API_KEY', 'url': 'https://stripe.com'}, timeout=90)
r.raise_for_status()
open('shot.webp', 'wb').write(r.content)And in Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`${res.status} ${res.statusText}`);
const fs = await import('node:fs/promises');
await fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer()));Options relevant to image-format validation
- Full-page capture with lazy images loaded, or one element selected by CSS selector.
- Dark mode, 12 device presets, arbitrary viewport sizes and retina scale.
- PDF output with paper size, margins, landscape mode and page ranges.
- HTML/CSS-to-image, custom CSS and JavaScript, clicks before capture, hidden selectors, and waits for a selector, delay or network idle.
- Blocking ads, trackers, requests or resource types; custom headers, cookies, user agent and Authorization.
- Timezone and geolocation, transparent background, image resizing, and cache TTLs you choose.
- Signed links for public
<img>tags, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, a usage API and an OpenAPI specification. - Parameter names used by other screenshot APIs also work, which can simplify migration.
- An MCP server exposes
take_screenshot,get_page_infoandcapture_pdfto Claude, Cursor and other MCP clients.
Plans include every feature: Free provides 1,000 shots per month without a card; Starter is $5 for 3,000; Growth $15 for 15,000; Pro $39 for 60,000; Scale $99 for 250,000; and Business $249 for 1,000,000. Yearly billing provides two months free.
Create a free ScreenshotNeo account to get 1,000 screenshots a month with no card.
Recommended Free Tools
Practical decision checklist
- Is the asset a photo, graphic, transparent image, vector or animation?
- Which of AVIF, WebP and JPEG meets your visual-quality threshold at the smallest measured size?
- Does the image need an alpha channel, animation or infinite scaling?
- Will the actual audience receive the modern source, and is a tested fallback present?
- Are dimensions, responsive sources, caching and loading behavior optimized independently of format?
- Have you measured LCP and transferred bytes instead of assuming a ranking effect?
Frequently Asked Questions
Should I keep the original camera files after making web derivatives?
Yes. Keep an untouched master outside the delivery pipeline so you can generate a different size, quality level or format later without repeatedly recompressing the web copy.
Best Value
How do I compare two encoders fairly?
Use the same source, pixel dimensions and visual-quality target, then compare the rendered result and transferred bytes on representative devices. Record encoder versions and settings so the result can be reproduced.
Can a fallback be a different crop?
It can, but keep the subject and meaning equivalent. A format fallback should normally change encoding, not unexpectedly change the content visitors see.
The Bottom Line
For most photographic pages, compare AVIF, WebP and JPEG at acceptable visual quality, deliver the smallest trustworthy result your audience can receive, and keep a suitable fallback. Use PNG or lossless modern formats for crisp or transparent graphics, SVG for vector artwork, and measure real loading performance rather than promising an SEO gain from an extension alone.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
