Image Optimization
The Compression Engine.
Right Format. Every Destination.
Automatic AVIF and WebP conversion per CMS destination. One original, five optimized outputs. 90% smaller on average.
Publish Optimized Images to Every CMS Automatically →Per-Destination Format Selection
One 3.8MB JPEG enters the pipeline. Five optimized files exit — each in the ideal format for its CMS destination.
Original Input
JPEG · 3.8MB
AVIF vs WebP: When to Use Each
AVIF
For modern CDN destinations
- 20–30% better compression than WebP
- Best for Contentful, Webflow
- Optimal Core Web Vitals impact
- Requires modern CDN support
- Syncific default for API-first CMS
WebP
For universal compatibility
- Near-universal browser support
- Best for WordPress, Shopify, HubSpot
- Reliable across all plugin environments
- Excellent compression vs JPEG
- Syncific default for traditional CMS
Impact on Core Web Vitals
LCP improvement switching from JPEG to AVIF delivery
average file size reduction vs original JPEG
manual optimization steps in the Syncific pipeline
Frequently Asked Questions
What image format should I use when publishing to Contentful? +
AVIF is the optimal format for Contentful. Contentful's delivery CDN (powered by Fastly/Imgix) fully supports AVIF and delivers it to browsers that support it, with automatic WebP fallback for older browsers. AVIF typically reduces file size by 85–92% compared to the original JPEG while maintaining equivalent visual quality.
Does Webflow support AVIF images? +
Yes. Webflow's hosting infrastructure supports AVIF format as of 2024. Syncific defaults to AVIF when publishing to Webflow destinations, delivering the best Core Web Vitals performance for image-heavy Webflow sites.
How does Syncific decide which image format to use per destination? +
Syncific applies format selection logic based on each destination's API and CDN capabilities: AVIF for Contentful, Webflow, and API-first destinations with modern CDN support; WebP for WordPress, Shopify, and HubSpot where plugin-based rendering and CDN limitations make WebP the safer default. You can override the format per destination in settings.
What is the difference between AVIF and WebP for CMS publishing? +
AVIF (AV1 Image Format) offers 20–30% better compression than WebP at equivalent quality, but requires a more modern CDN and browser support baseline. WebP has near-universal browser support and works reliably across all CMS plugin environments. Syncific automatically selects the better option per destination — AVIF where fully supported, WebP elsewhere.
Does image optimization happen automatically when I publish through Syncific? +
Yes. Every asset published through Syncific is automatically converted to the optimal format and compressed before delivery. No manual Photoshop export, no separate optimization tool, no upload-then-optimize workflow. The original file in your creative tool is never modified — Syncific optimizes a delivery copy.
How much smaller are AVIF images compared to JPEG when publishing to a headless CMS? +
In Syncific's publishing pipeline, AVIF conversions from JPEG originals average 85–92% file size reduction. A 3.8MB JPEG typically becomes a 287–420KB AVIF depending on content complexity. This translates directly to faster page loads, better Core Web Vitals scores, and lower CDN bandwidth costs.
Does image optimization affect Core Web Vitals scores? +
Significantly. Largest Contentful Paint (LCP) — the Core Web Vitals metric most affected by image size — improves by an average of 40–60% when switching from unoptimized JPEG to AVIF delivery. For image-heavy sites on Webflow or Contentful, optimized asset delivery is often the single highest-leverage LCP improvement available.
Every asset, every destination, always in the right format.
No plugin required on destination sites. Cancel anytime.