Figma Make Now Gives Your Website a Real Backend, Built In

Figma Make just got a built-in backend. With Payload, the open-source content management framework that joined Figma last year, you can now prompt an app and get a working database, admin panel, file storage, and user login alongside it. That is not a plugin or a third-party bolt-on. It is part of Make, hosted by Figma.

This matters because the gap between "I designed a thing" and "I shipped a thing people can actually use" has always been filled by plumbing that designers had to outsource. That gap just got a lot smaller.

What the Payload Integration Actually Gives You

When you prompt a website or app in Figma Make and ask for anything that involves content or data, Payload sets up the infrastructure behind it automatically. That includes:

• A database to store whatever your app collects or displays
• File storage for images, documents, and media
• User login so visitors or team members can have accounts
• An admin panel that non-technical teammates can use to create, edit, and publish content without touching a prompt

All of it lives inside Figma. The design, the code, and the content management system are in the same place, with the same host.

Payload also handles versioning, so editors can review past versions of content before publishing. Permissions are granular, meaning you can decide who on your team can edit copy, who can review submitted data, and who can publish. And if you have a batch of data to load, you can upload a CSV and ask the agent to turn it into a Payload collection rather than entering records one by one.

A Concrete Example: The Delivery Service Site

Figma's own documentation walks through a useful scenario. Say your team is launching a delivery service and the website needs to explain the offering and let prospective drivers apply. Previously, you would connect an external CMS to manage copy and images, and then work with an engineer to build a separate system for storing and reviewing applications.

With Payload in Make, both come out of the same prompt. The website and the backend for collecting driver applications are built together. The admin panel lets marketers update the homepage copy and lets a product manager review applicant submissions, all without opening a ticket or waiting on a developer.

That is a genuinely different workflow, not just a speed improvement on the old one.

How to Actually Use It: A Starting Workflow

If you want to try this today, here is a practical path in.

Start with a content-heavy prompt. Ask Make to build something that clearly needs data, such as an event listings page, a reading list, or a job board. Make will recognise the content management need and bring Payload in to set up the structure.

Check the admin panel immediately. Once your site is published, go to your site URL and add /admin at the end. That is your Payload admin panel. Poke around. Add a real entry. See what fields were generated and whether they match what your content actually needs.

Add custom fields early. The Figma team's own internal example, building a companion site for their Source Material YouTube series, added custom fields for things like binding type and cover finish. Those details shaped how each item appeared on a 3D shelf in the UI. The earlier you define what data your design actually depends on, the cleaner the connection between content and layout.

Give teammates direct access. Once you have the admin panel working, share it with whoever will manage content. The whole point is that a marketer or editor can update copy, swap images, tag content, and publish changes without going through you or through a prompt.

Secure your API keys inside Figma. If your app connects to an external service, such as an email provider for a newsletter signup, Figma now lets you store that service's API key securely inside Figma itself rather than setting up a separate project in a tool like Supabase. That removes one more step that used to require engineering help.

Where This Fits in Vibe-Coded Projects

For designers who are already building with AI, the sticking point has rarely been the front-end. Prompting a good-looking interface is fast now. The friction lives in the moment you ask: but where does the data actually go? Who updates the content after launch? How do I let a teammate edit the blog without breaking anything?

Payload in Make is a direct answer to that cluster of questions. IBM's Noah Trevino used it to give his team version-controlled, self-serve content management for internal websites, handing over existing design screens and a field list and getting back a working draft. That kind of handoff, from design intent to a managed, living site, is exactly what was missing from the AI-to-build pipeline.

What to Watch and What Is Still Open

A few honest questions remain. Payload is open source, and you can self-host or extend it outside Figma if you need to. That flexibility is real and worth knowing about, especially if your project grows beyond what Figma's hosting covers.

It is also worth noting that Payload downloads have grown 6x in the past year, making it the fastest growing open-source CMS on NPM according to Figma. That is a signal the community is healthy, but the integration inside Make is still relatively new. Edge cases, especially around complex data relationships or custom authentication flows, may still need a developer to sort out.

The clearest takeaway: if you have been stopping short of launching something because the backend felt like someone else's job, that excuse just got a lot harder to justify.