Best image format for websites: JPEG, PNG, SVG, WebP, AVIF
Short answer Photos: WebP or AVIF, with JPEG as the fallback. Logos and icons: SVG. Screenshots and anything needing a see-through background: PNG or lossless WebP. Google Search reads all of these, so the format won't hurt rankings on its own. The win is smaller files, which make pages load faster on a phone.
Want help applying this to your business? Talk it through on a free 30-minute call.
Book a callWhich image format should I use?
Match the format to what's in the picture. File size is what changes; Google reads every format below.
| What the image shows | Use | Fallback |
|---|---|---|
| Photos of your work, team, shop or products | AVIF or WebP | JPEG |
| Logo, icons, simple drawings | SVG | PNG |
| Screenshots, charts, text on an image | Lossless WebP or PNG | PNG |
| Anything with a see-through background | WebP or PNG | PNG (JPEG can't do it) |
| Short animation | WebP or AVIF | GIF |
Sources: MDN Web Docs, Google for Developers.
Two terms help. Lossy compression throws away detail you barely see to make the file much smaller; it suits photos. Lossless keeps every pixel; it suits text, logos and sharp edges, where blur shows. MDN puts it plainly: photos "can usually tolerate lossy compression," while screenshots, diagrams, logos and line art should use lossless (MDN).
Does image format affect SEO?
Not directly. Google lists what it can index:
"Google Search supports images referenced in the src attribute of img in the following file formats: BMP, GIF, JPEG, PNG, WebP, SVG, and AVIF." (Google Search Central: Google image SEO best practices)
So an AVIF or WebP photo can show in Google Images just like a JPEG. Advice that JPEG and PNG index more reliably is out of date: Google added AVIF on August 30, 2024, and said you don't need to do anything special to have AVIF files indexed (Google Search Central Blog).
Format matters through speed. Google notes that images "are often the largest contributor to overall page size, which can make pages slow and expensive to load" (Google Search Central). Speed is a small ranking factor and a bigger factor in whether a caller waits: Core Web Vitals and Google ranking.
JPEG XL is the one newer format to hold back on. Browsers are adding it, but it isn't on Google's supported list above, so don't make it the only version of an image (MDN).
JPEG vs PNG vs SVG vs WebP vs AVIF compared
| Format | Type | Best for | Transparency | Watch out for |
|---|---|---|---|---|
| JPEG | Lossy | Photos, as the fallback | No | Blurry edges around text |
| PNG | Lossless | Screenshots, logos with transparency | Yes | Big files when used for photos |
| SVG | Vector (drawn from shapes) | Logos, icons, diagrams | Yes | Useless for photos |
| WebP | Lossy or lossless | Photos and graphics | Yes | Very old browsers only |
| AVIF | Lossy or lossless | Photos, the smallest files | Yes | No gradual preview while loading |
| GIF | Lossless, 256 colors | Old simple animations | Yes | Large and grainy; WebP or AVIF beat it |
Sources: MDN, Google for Developers.
Vector vs raster. JPEG, PNG, WebP and AVIF store a grid of pixels (raster), so they blur when blown up. SVG stores shapes and stays sharp at any size, which is why MDN calls it "ideal for user interface elements, icons, diagrams" (MDN). Your logo should be SVG if your designer has the vector file.
WebP vs JPEG: how much smaller?
Google, which created WebP, publishes these figures (Google for Developers):
"WebP lossless images are 26% smaller in size compared to PNGs. WebP lossy images are 25-34% smaller than comparable JPEG images at equivalent SSIM quality index."
SSIM is a standard score for how close a compressed image looks to the original. So at the same visible quality, a 300 KB JPEG hero photo becomes roughly 200–225 KB as WebP. WebP also handles transparency and animation, so one format can replace JPEG, PNG and GIF on most sites (same page).
AVIF vs WebP: which is better?
AVIF usually makes smaller files; WebP is the safer default. MDN says AVIF "offers slightly better compression" than WebP but "does not support progressive rendering," meaning it won't show a rough preview while it downloads (MDN). WordPress's core team says AVIF images "can be up to 50% smaller than JPEGs while maintaining the same image quality" (Make WordPress Core).
Google's blog says AVIF is "supported by all major web browsers" (Google Search Central Blog). Both are fine for a service business site. Pick the one your website platform produces with no extra work.
How to switch to WebP or AVIF without losing rankings
- Check what your platform already does. Some builders convert for you. Wix says background images are "automatically converted to AVIF format on your live site" (Wix Help Center). WordPress accepts AVIF uploads from version 6.5 "as long as your hosting environment supports AVIF" (Make WordPress Core). Platform choice: Wix, Squarespace or WordPress for SEO.
- Don't convert everything at once. Google's advice:
"It's not recommended to blindly make sweeping changes to images across a website: take the time you need to evaluate which format works best for your specific needs." (Google Search Central Blog)
- Redirect changed file names. If `roof-repair.jpg` becomes `roof-repair.avif`, Google says to "set up server-side redirects" from the old address to the new one (same page). Missed redirects are a common cause of lost traffic after a rebuild: traffic dropped after a website redesign.
- Keep a fallback in the code. When a page offers AVIF or WebP through the HTML `picture` element, Google says "always specify a fallback URL using the src attribute" (Google Search Central). That is usually a JPEG or PNG.
- Resize before you convert. A 4,000-pixel phone photo shown 800 pixels wide is wasted bytes in any format. Then test the page in PageSpeed Insights.
Format is one piece of image work. Alt text still matters: Google says to avoid "filling alt attributes with keywords" because it hurts users and "may cause your site to be seen as spam" (Google Search Central). More on page basics: on-page SEO for service pages.
Example
Illustrative cases, not measured results.
A landscaper's gallery page
Forty job photos as 1.5 MB JPEGs straight from a phone. Resized to 1,200 pixels and saved as WebP, each is a fraction of that size, and the page loads on mobile data before the visitor gives up.
A dental office logo
The logo is a blurry 600-pixel PNG. The designer sends the SVG; it stays crisp on every screen and weighs a few kilobytes.
A plumber on WordPress
He bulk-converts every image to AVIF with a plugin that renames files. Old image addresses break in Google Images. Adding redirects from each old `.jpg` to its new file fixes it.
FAQ
Is WebP better than PNG?
For most web uses, yes. Lossless WebP is 26% smaller than PNG and keeps transparency, per Google for Developers. Keep a PNG fallback if your platform asks for one.
Should I use SVG for photos?
No. SVG describes shapes, not pixels, so it suits logos, icons and diagrams. Use AVIF, WebP or JPEG for photos (MDN).
Does Google Images index WebP and AVIF?
Yes. Both are on Google's list of supported formats, alongside JPEG, PNG, GIF, SVG and BMP (Google Search Central).
Is GIF still OK for animations?
It works, but MDN suggests WebP, AVIF or APNG for animation and PNG for still images (MDN). A short video often beats a long GIF.
Do I need to convert my old images?
Not urgently. Start with the largest images on your busiest pages, usually the top photo. Google warns against sweeping changes and asks for redirects if file names change (Google Search Central Blog).
Different for you?
- Site still slow after fixing images: Core Web Vitals and Google ranking.
- Rankings fell after you changed images or rebuilt the site: traffic dropped after a website redesign.
- Your builder won't let you change formats: Wix, Squarespace or WordPress for SEO.
- Want the whole page right, not just images: on-page SEO for service pages.
- Want a fast site built and kept fast: Website Agent.