Contentful is now officially part of Salesforce! Read more
Digital experiences often take shape in Figma, a collaborative design platform where designers combine layout, imagery, interaction, and brand expression into experiences teams can review and refine. Y
et the content behind those designs often lives elsewhere, creating a gap between the carefully selected examples shown in Figma and the structured entries, assets, and relationships in Contentful that are intended for the live experience.
When those workflows meet only later, designers have less time to see how Figma components respond to real content, and content teams have fewer opportunities to identify structural or editorial mismatches.
Contentful for Figma, a new widget now available in the Figma Community, brings those workflows together. By connecting component properties to Contentful fields, designers can test real headlines, assets, and references while the design is still flexible, helping teams spot and resolve issues before they affect the final experience.
Bringing real content into a Figma design often means manually copying individual Contentful fields from an entry into a component, creating a static snapshot that’s separate from its source. Any content update means another round of copying and pasting.
Contentful for Figma replaces that copy-and-paste process with a direct relationship between structured content and the components designed to display it. Designers can map Contentful fields to Figma properties like text and images. Each saved connection, known as a binding, preserves that relationship.
Once established, bindings stay with the Figma file’s library, allowing designers to attach different Contentful entries to Figma instances without recreating the bindings each time. This gives design and content teams a shared view of how each component connects to the content model.
With those bindings in place, designers can now test how the same design responds to real-world content variations.
Take a homepage hero, for example. In an initial Figma design, it may look polished with a short headline, a single line of supporting copy, and a perfectly proportioned landscape image.
But that same hero could be reused across campaigns with different messaging and imagery. Applying multiple real entries shows how the component handles those differences: one headline may wrap onto three lines, another campaign may omit supporting copy, and an image’s focal point may disappear within the original crop.
Beyond a single component, teams can bring multiple Figma instances together with Contentful entries, references, and nested content. Reviewing a complete page shows how content and layout work together across the broader experience.
Testing different entries does more than expose issues. It helps define how a component should behave as the content varies.
For the hero, that might mean making room for longer headlines, adjusting the layout when supporting copy is absent, or preserving an image’s focal point across different crops.
With the bindings saved, design and content teams can return to the entries that revealed these issues and review them together in the design. Designers can assess whether the component accommodates the range of content, while content teams can see how content choices interact with the design.
That shared review clarifies the component’s expected behavior before handoff and communicates not only how a component should look and adapt to real content, but also the design and content decisions behind that behavior.

Today, component-level bindings make full-page reviews possible, but Contentful for Figma also points toward a broader opportunity.
That future could include design-readiness checks, earlier visibility into missing components or design-system gaps, and a smoother path from approved Figma designs to experiences in Contentful.
The same connections could also give AI clearer context for delivery: instead of interpreting pixels, it could draw on the links between components and content, along with design tokens, images, and supporting metadata.
Contentful for Figma brings representative content into design validation, so designers can test components before handoff. The widget is now available for paid Contentful plans.
To get started, you’ll need a Figma account and a Contentful account that can access the space and environment you want to connect. Your existing Contentful permissions determine which content you can view or update in Figma.
Once you’re ready, install Contentful for Figma from the Figma Community and follow the Contentful Help Center setup guide.
Inspiration for your inbox
Subscribe and stay up-to-date on best practices for delivering modern digital experiences.
Ready to start building?
Put everything you learned into action. Create and publish your content with Contentful — no credit card required.