Figma announced in an official blog post on October 15, 2026 that Payload, the open-source content framework, is now integrated into Figma Make. When you prompt a website into existence in Make, the system now also sets up a database, file storage, user login, and an admin panel, so a design ships with a working data backend for the first time.
Generating a page with AI site builders was never the hard part. The hard part is everything behind the page: event listings someone has to update, form submissions someone has to collect, copy edits that turn into engineering tickets. Payload fills exactly that gap. Designers draft with real content, marketers edit copy, swap images, review submissions, and check version history in the built-in admin panel, and developers customize deeply with Payload's open-source framework. Everyone works on the same content, with permissions split by role. Figma pointed to its own marketing team as an example: for a companion site to a video series, each episode's title, cover, and custom fields live in Payload and are maintained in the admin panel instead of being edited prompt by prompt.
Two more releases in the same batch deserve attention. Figma Specs entered open beta: teams can write design guidelines, decisions, and context into documents linked to the canvas, then hand them to coding agents through MCP, so agents follow established rules instead of guessing from scratch each time. The Figma agent on the canvas also became generally available, code layers moved into public beta, and Figma MCP gained 20 new partner integrations, with improved guidance that Figma says reduces agent errors and token usage.
What this changes in practice
The real shift is in who does what. Prototyping rewards speed, and prompting is enough there. Shipping to real users requires content management, permissions, and data storage. With Payload inside Make, that whole stretch collapses into one tool: small teams building event pages, signup pages, or content sites can skip wiring up an external CMS and maintaining a separate account system. The limits are worth noting, though. Payload is available on all plans, with access rolling out to all accounts over the coming weeks. The hosting infrastructure for Payload-backed projects is still in beta and free for now, so long-term cost stays unknown until pricing is announced. On the plus side, content and apps can be taken outside Figma, and Payload itself remains self-hostable, so the exit door is not closed. For teams already prototyping in Make, the test is simple: if your pages need continuously updated content or collect user submissions, this release is worth a serious trial; for one-off demos, your current workflow does not need to change.
