What Squarespace serves automatically
Three behaviours ship by default on Squarespace 7.1 for editor-uploaded images. (1) Auto-WebP conversion: any JPEG or PNG uploaded through Image Block, Gallery Block, or Commerce product images is served as WebP to browsers that support it. (2) Responsive srcset: multiple variants at different widths (typically 100w, 300w, 750w, 1500w, 2500w) are generated and served via the picture element. (3) Fallback: JPEG or PNG is served to older browsers that do not support WebP. All three behaviours are automatic — no setting, no toggle, no plugin.
What about AVIF?
AVIF is the next-generation image format with another 30-50% compression improvement over WebP. Browser support reached ~94% of global users by Q1 2026 per caniuse.com, which means most users could receive AVIF if the server supported it. The constraint on Squarespace is the platform: as of Q2 2026, Squarespace's image pipeline serves WebP and JPEG/PNG, not AVIF. There is no public timeline for AVIF support. The honest 2026 framing is: WebP is what you get; AVIF is what you might get later.
The source-resolution lever
Squarespace's auto-WebP compression compounds with smaller source dimensions. A photo uploaded at 5,000px wide compresses to WebP at ~2-3MB. The same photo resized to 1920px wide before upload compresses to WebP at ~400-600KB. The visual result is identical at any normal viewport. The payload is 4-7x smaller. The implication: source-resolution capping is a larger optimisation than the WebP conversion itself.
Source-dimension cap recommendations
Four caps cover almost every Squarespace use case. Full-bleed hero: 1920px wide. In-section images that span most of the column: 1200px wide. Small inline images (icons, thumbnails): 600px wide. Product images for ecommerce zoom: 2000px wide to support the zoom interaction. For retina displays, double the cap is overkill in 2026 — Squarespace's responsive srcset picks the right variant for the viewport, and the 1920px source still generates a sharp 1500w retina variant.
Verify the WebP is actually serving
Two verification methods. (1) Open Chrome DevTools, Network tab, reload the page, filter by Img. Each image row shows the served Content-Type — image/webp confirms WebP is being served. (2) Run PageSpeed Insights and check the 'Serve images in next-gen formats' audit — it passes when WebP is serving. If the audit fails, the platform-level WebP behaviour has not been triggered, usually because the image is a CSS background or a Code Block embed rather than an Image Block.