WebP or AVIF for dealership car photos, and when JPEG still does the job

When a vehicle page feels slow, the photos are often the heaviest part of the page. For dealerships, the real question is not only which format looks best, but which one keeps file weight down without making paintwork, wheels, or interior detail look over-compressed. In practice, the choice usually comes down to JPEG, WebP, and sometimes AVIF.

The short answer for dealership listings

For most dealerships, WebP is the safe default today. It has broad support, usually produces smaller files than JPEG, and is easier to fit into ordinary website workflows. AVIF can shrink files even further, but it makes the most sense when the site or image pipeline already handles it cleanly. JPEG is still fine as a fallback or source format inside internal workflows, but it is rarely the best final format on public listing pages.

Why format choice matters on VDP pages

On a VDP, the main vehicle image is often one of the largest elements on the page. If that image arrives late, both the buyer experience and the page's LCP can suffer. If every listing carries 25 large JPEGs straight from a phone or camera, the page gets heavy fast, especially on mobile networks and inventory sites with many near-identical detail pages.

When WebP is usually the right call

• You want smaller image weight without rebuilding the entire platform.
• You publish a high volume of listings each week and need a format that behaves well at scale.
• You want a better final delivery format than JPEG for both stock pages and VDP pages.
• You need something that works well in modern browsers without special handling.

WebP is often the best compromise for dealership listings. The gain usually shows up in how quickly pages feel when several vehicle photos need to load, not in one isolated file. For a dealership with hundreds of active vehicles, that difference is practical, not academic.

When AVIF is worth testing

AVIF becomes interesting when the team already has an automated image pipeline and wants to squeeze more weight out of cover images and galleries. That can matter if the site struggles with mobile Core Web Vitals on VDP pages. Still, switching formats just because AVIF is newer is a bad reason. If quality gets inconsistent, exports slow down, or compatibility becomes messy, the real-world gain shrinks quickly.

Three mistakes that matter more than the wrong format

• The first vehicle image is lazy loaded even though it should load early.
• The same oversized image is sent to both mobile and desktop instead of responsive sizes.
• Original images are pushed straight to the site without a clear max width or compression standard.

That is why image format should be treated as one part of a bigger image workflow. The right format helps, but it helps even more when the lead image gets proper priority, the rest of the gallery loads intelligently, and every listing uses image sizes that match the actual layout.

A simple recommendation for dealerships

Keep the originals internally if you need them, but publish finished listing pages in WebP if you want the safer default. Test AVIF on cover images or a smaller VDP set if your platform supports it well. Then measure real load behavior and visual quality on dark paint, glass reflections, and interior shots, not just file size inside an export tool.

If the team already standardizes background style, branding, and final image finish in the same workflow, it makes sense to lock image formats, max widths, and export rules into that process as well. Carbooth fits best as a finishing layer inside that workflow, not as a substitute for technically sound image delivery on the site itself.