Best Image Format for SEO: What Actually Affects Your Rankings
Google does not rank a page higher because its images are WebP. And yet image format is an SEO topic - because format decides file size, file size decides loading speed, and speed is a measured ranking input through Core Web Vitals, especially on the mobile connections most searchers actually use. This article separates the direct effects (almost none) from the indirect ones (very real), so you can spend effort where it counts.
The mechanism: format → weight → speed → rankings
Images are typically the heaviest part of a web page - often 60-80% of total bytes. Your Largest Contentful Paint (LCP) element, one of the three Core Web Vitals, is very often an image. A hero photo that drops from 900 KB as JPG to 550 KB as WebP, or 420 KB as AVIF, loads measurably sooner on a mid-range phone, and LCP is graded in milliseconds. No format is a ranking "signal" in itself; every format is a speed decision, and speed is graded.
The formats, ranked for search-driven pages
- WebP: the default recommendation in 2026. Lossy photos 25-35% smaller than JPG at equal quality, lossless mode and transparency included, supported by every modern browser. Convert with JPG to WebP or PNG to WebP.
- AVIF: the most efficient still format, often another 20% smaller than WebP, with excellent browser support. Its costs: slower encoding, and some content systems and social platforms still handle it awkwardly. If a file arrives as AVIF and a form rejects it, AVIF to JPG is the escape hatch.
- JPG: the compatibility king. Slightly heavier than WebP, universally accepted by every CMS, editor, platform and mail client on earth. A perfectly reasonable choice when your pipeline fights newer formats.
- PNG: right for screenshots, diagrams and graphics needing transparency or pixel-exactness - and wrong for photographs, where it can be five times the weight for zero visible benefit. Not sure what a file really is? Names lie; the Image Format Detector reads the bytes.
- SVG: for logos and icons, unbeatable: infinitely scalable at a few KB. Not a photo format, ever.
What does NOT matter (much)
The stored DPI in an image file is irrelevant to screens and to Google - only pixel dimensions count. File names and alt text, by contrast, do matter for image search: descriptive names (compress-jpg-example.webp, not IMG_4021.webp) and honest alt text help Google understand the picture. And no format rescues an oversized image: a 4000 px WebP in an 800 px column is still waste. Size the image to its slot first, format second, quality third.
A practical SEO image checklist
- Resize to the display slot (2x for retina), never upload camera originals.
- Default to WebP; AVIF where your pipeline supports it; JPG for maximum compatibility.
- Compress once, at the end, around quality 80 - Compress JPG and its siblings show the saving per file.
- Give the hero image priority (it is usually your LCP); lazy-load the images below the fold.
- Use descriptive file names and genuine alt text.
- Keep an untouched original of everything, so future formats are one conversion away.
One warning: do not game the text around images
Because file names and alt text genuinely help image search, they attract gaming: keyword-stuffed alt attributes ("best cheap shoes buy shoes online shoes") that describe nothing. That hurts twice - screen readers read the stuffing aloud to visually impaired visitors, and Google's image understanding is quite capable of noticing that an alt text does not match the picture. Write alt text the honest way: describe what the image shows, in one plain sentence, as if explaining it over the phone. If the image is decorative, an empty alt attribute is the correct, professional choice. The same applies to captions and surrounding text: relevance that reads naturally is the only kind that lasts through algorithm updates.
Serving different formats to different browsers
The theoretically perfect setup serves AVIF to browsers that support it, WebP as the next fallback, and JPG to the rest - via the HTML picture element or server-side content negotiation. In practice, for most sites the complexity buys little over simply publishing WebP, which every modern browser already renders: the extra saving of AVIF matters at very large scale, or on pages so heavy that every kilobyte is contested. Choose the simplest pipeline you will actually maintain; a well-compressed WebP published today beats a perfect negotiation setup planned for next quarter.
Format choice will not rescue weak content, and it will not sink strong content by itself. But on the competitive, mobile-first pages where SEO is actually contested, the lightest correct format is free speed - and free speed is free ranking headroom.