If some images are missing on the published page in Webflow but appear correctly in the Designer, it’s usually due to issues with image upload, publishing, or browser access paths.
1. Check If Images Are Added as Assets or Backgrounds
- Asset images (uploaded in the Asset Manager) are reliably published.
- Background images (set in the Style panel) may get omitted if tied to unused CSS classes or symbols.
- Ensure that background images are applied to elements actually used on the published site.
2. Publish to All Domains
- After changes, always click “Publish” and select all connected domains.
- If you only publish to one domain (e.g., staging), changes might not reflect on your main domain.
- Go to Webflow Designer > Top right Publish button > Select checkboxes for all domains.
3. Verify Paths for CMS or Dynamic Images
- CMS-loaded images must be correctly bound using dynamic fields in the Collection.
- If a CMS field is empty or deleted, the bound image will not display.
- Review the image field within the Collection item to ensure it's populated.
4. Clear Browser Cache or Try Incognito Mode
- Your browser may cache an earlier version of the page without the images.
- Try hard-refreshing (Shift + Reload) or open the site in Incognito mode to test.
- Ensure images use supported formats: JPG, PNG, SVG (for simple graphics), WebP.
- Large file sizes or corrupt files may fail to load.
- Re-upload smaller or re-exported versions of problematic images if needed.
6. Confirm No Custom Code is Blocking Images
- If you’re using custom code, it might conflict with image loading (e.g., via lazy-loading scripts or broken paths).
- Temporarily remove custom code from the Page Settings > Custom Code section to test.
7. Review Browser Console for Missing File Errors
- Open DevTools (F12) and check the Console or Network tab for 404 errors on broken images.
- This can show whether the image source path is invalid or blocked.
Summary
Missing images on a live Webflow site usually result from publishing issues, unused styles, empty CMS fields, or browser caching problems. Ensure all domains are published, check image bindings, and use Developer Tools to identify any path-related errors.