Webflow Embed vs native elements
Updated 8 October 2026
Use native elements for layout and content, for example sections, text, buttons and images. You can edit native elements in the Designer, clients can edit them in the Editor, and the CMS can bind to them. Use an Embed only for items that Webflow cannot make: third-party widgets, tracking scripts, canvas and complex SVG.
What changes when the code is in an Embed
- The Style panel cannot show or change the code. For each change, you must edit the code.
- Clients who use the Editor cannot change the text in the Embed.
- CMS fields cannot bind to the Embed, except through custom field embeds.
- Interactions cannot target elements in the Embed.
When to use an Embed
- Third-party widgets, for example booking, chat and forms from other services
- Tracking scripts and consent scripts
- Canvas, WebGL and complex inline SVG
- Code that a different system changes each time you publish
How to change Embed code to native elements
If an Embed contains layout and text, convert the code. Paste the code into FlowPaste. Press ⌘V or Ctrl+V in the Designer. Then delete the Embed.
Some code cannot be native, for example pseudo-elements, keyframes and SVG. FlowPaste keeps that code in a smaller Embed next to the new elements.
Questions
Is an Embed bad for SEO?
No, not directly. Search engines read the HTML in an Embed and in native elements. The problem is maintenance: people forget content in an Embed, and an Embed is difficult for a person who does not write code to update.
Do embeds need a paid Webflow plan?
Yes. To add or edit a Code Embed element, you must have a paid Webflow plan. This is 1 more reason to use native elements for layout.