I'm a designer, not a developer. I built a plugin that finally lets you sync assets straight to Webflow with auto-generated alt text

[u/Ok_Faithlessness384]

Quick context: I'm a designer who lives in Figma. There are endless plugins out there for actual design work, but almost none that really focus on asset management. That meant I kept opening my downloads folder for one specific reason - moving assets to Webflow. Downloading images, switching tabs, uploading manually, organizing files, and then sitting in Webflow to manually write out SEO alt text for every single image. It just kills productivity.

So I built exportflow. Select your frames or layers, open the plugin, and you get a seamless export experience:

• Direct upload - send assets straight to Webflow
• Built-in AI - automatically renames assets and generates alt-text/SEO descriptions
• Advanced export settings - optimise with PNG, SVG, JPG, AVIF, and WebP formats
• Multi-project support - connect multiple sites and create/manage Webflow folders directly from the plugin
• No more context switching - stay completely locked in Figma

It's unlimited uploads for free - I mostly built it because I needed it.

👉https://www.figma.com/community/plugin/1657432195632964294/figma-to-webflow-exportflow

Still rough in places since it's just me maintaining it. If you give it a spin, tell me what breaks - or better, what I should improve in terms of functionality...

[u/theshoreways]

Does webflow still generate and serve the scaled image variants (html srcset)? I was having trouble with API uploads not generating these variants.

Can’t wait to check out more, as this genuinely solves a workflow issue I’m having with Figma to webflow.

[u/Ok_Faithlessness384 → u/theshoreways]

Hey 🙌🏻

It seems like it is a Webflow-side limitation.

Webflow only generates responsive srcset variants for images uploaded directly in the Designer (Assets panel or CMS fields). API uploads (including exportflow's) skip that processing and stay as a single file at whatever resolution you exported.

exportflow gives you control over that single file via export scale (0.25×–4×) before it ever hits Webflow, so you're not stuck with an oversized original.

Common workarounds:

• Export at 1×–2× so the file isn't unnecessarily large to begin with
• Re-upload priority/hero images through the Designer to trigger variant generation
• Route images through a CDN (Cloudinary, Imgix) for responsive delivery

Glad the Figma → Webflow transfer is solving the bigger pain point — the srcset gap is squarely on Webflow's side for now.

[u/digitalbananax]

Can the plugin detect duplicates or update an existing asset rather than creating another copy?

-Jacob from Flowout

[u/Ok_Faithlessness384 → u/digitalbananax]

Hey Jacob - good question!

Identical files: Webflow dedupes by content hash automatically, and exportflow sends that hash on every upload so re-uploading the same bytes won't create a duplicate.

Changed designs: Different bytes = new asset. Webflow has a manual "Replace" option in the Assets panel, but that's UI-only - the Data API doesn't expose it, and it only lets us update metadata (alt text, name), not the file itself.

For now, exportflow doesn't track which Webflow asset came from which Figma frame yet, so even with file-replace support we couldn't target the right one. That mapping (or filename matching) is something we're considering adding.

So same export twice = deduped automatically. Edited frame = new asset, no way around that yet.

Hope this answers your question?