Yes, it's possible to manage a list of image sources externally and reference them in Webflow, but Webflow has limitations on dynamic scripting and external data rendering. Here's how to accomplish a similar effect using available methods.
1. Use Webflow CMS for Image Lists
- Create a CMS Collection where each item represents an image with fields like Name, Image URL, Alt Text, etc.
- This allows you to iterate through the item list using a Collection List and template elements.
- Benefit: Fully native, no code needed beyond normal CMS setup.
- Limitation: Webflow CMS has caps (e.g., 10,000 items max) depending on your plan.
2. Use a Third-Party JSON File + Custom Code (Limited Use)
You can host a JSON file on an external server (like GitHub, Firebase, or a headless CMS).
Then, in Webflow embed code, use JavaScript to fetch and loop through the JSON to display images.
Example usage: Place this in Embed elements on the page (note: limited inside Collection Lists and Webflow Designer).
Keep in mind: Custom JavaScript only runs on the published site, not in Designer or Preview.
Webflow does not allow full control over page hydration, so this method is best for display-only blocks outside CMS pages.
3. Use External Embeds (e.g., Cloudinary, Airtable + Softr)
- Services like Cloudinary allow you to host images and even serve image galleries dynamically.
- Or use Airtable + integration tools like Zapier/Integromat or widgets like Softr to embed curated content into Webflow pages.
- You can embed iframe or third-party widgets for display—but customization may be limited.
4. Avoid Too Much Inline Code in Webflow
- Webflow’s code embed widget is meant for small snippets, not large datasets or script-heavy operations.
- For performance and stability, shift data-heavy tasks outside Webflow to be rendered via client-side JavaScript.
Summary
You can offload image lists using Webflow CMS, external JSON + JavaScript, or third-party services. However, Webflow doesn't support full dynamic iteration over external data natively, so any custom functionality must be injected via code and will only work on the published site.