figma guide
Figma Sites: Publish a Marketing Page
Publish a marketing page in Figma Sites when Figma can host it. Finish the page first. Use Framer or your own code when the site must leave Figma.
Intermediate Designers who want a marketing page or portfolio live from Figma, and need to know when that host is the wrong one.
- Published
- Updated
- Oct 01, 2026
- Read time
- 6 min
- Level
- Intermediate
- Editor
- Abdus Salam
Tools in this guide
-
Design the page and publish it on Figma's hosting. Not a code export.
Paid plan to publish
-
Design files you can copy into a Sites file. Still the source for product UI.
Quick answer
Use Figma Sites when the marketing page or portfolio can live on Figma’s hosting. You design it in a Sites file and publish it to a figma.site address, or to a custom domain after that. You do not get the site’s code out of Figma for your own server. If the page has to live in your codebase, or in Framer or Webflow, this is the wrong host. The other paths are on Ship.
Figma’s help center still describes Sites as an open beta released at Config 2025. Check Publish, update, or unpublish a site before you follow a click path. The controls move.
Who this is for
- Designers shipping a landing page, a portfolio, or a small marketing site that can stay on Figma’s hosting.
- Marketers who will update copy in the Sites file and publish again, without an engineering sprint for each headline.
This is not the path for a product UI. App screens stay in a design file and go through what to finish before Dev Mode. It is also not the path when you already know the page will be rebuilt in Framer or Webflow.
What to finish in Figma first
Do this in the Sites file before you publish. Figma includes every webpage on the canvas in the published site, including dynamic CMS subpages. During the beta, move any page that is not ready into a different file.
- Real copy. Headlines, buttons, and form labels should be the words that will ship.
- One desktop layout and the smaller breakpoints you will actually support. Figma’s Sites overview says breakpoints are how you fit different screen sizes.
- A title people will see in the browser tab and in search results. Figma’s publish window uses that title.
- Images that are meant to be public. A GIF or WebP that does not play on the live site may be over Cloudflare’s limit for animated images. Figma’s help page says the width times the height times the frame count, divided by 1,000,000, has to be 50 or less.
- A note for yourself on what is a one-off block and what will change later. Figma’s Sites page describes a CMS for updating text and visuals from a dedicated view so the layout stays locked. Use that for rows that will change. Do not invent a second copy of the same section on the canvas.
Anyone on a Figma plan, including a free Starter team, can create a Sites file. Publishing to the web is on paid plans. The Education plan includes one published site and may be subject to bandwidth limits. A Starter plan has to be upgraded before the site can go live.
What transfers, and what you rebuild
| In a Figma Design file | In the published Sites site |
|---|---|
| Layout, type, and copy you copy into Sites | The page, after you place it in the Sites file |
| A static mock of hover and scroll | Interactions you add in Sites |
| A design file the engineers still build from | Nothing. Sites does not export code you can host yourself |
| Unfinished pages left on the canvas | Those pages, because publish includes every webpage on the canvas |
Figma’s Sites page says you can copy work from a Figma Design file and keep the layout and typography. Treat that as a head start. Rebuild breakpoints and links in the Sites file. If you have not decided Sites is the right host, read Figma vs Framer for marketing sites first.
A practical sequence
These steps match Figma’s help center as checked on 1 October 2026. If a label has moved, use the publish article linked above.
- Create a Sites file from the file browser, or open
https://www.figma.com/site/new. Figma’s Sites overview says both work, and that any plan can create the file. - Bring the page in from a Figma Design file if you already designed it there. Then delete frames you will not publish.
- Set the site title and the other settings Figma lists before publish: SEO, accessibility, the social preview, and password protection if the page is not public yet.
- Move unfinished pages to another file.
- Click the File icon in the left navigation bar, then Publish in the left sidebar. Review the title, the URL, any issues, and who can view the site. Publishing is not blocked by open issues, but Figma recommends fixing them first.
- Publish. The site goes live at a random
figma.sitesubdomain, such ashttps://hut-grid-glade.figma.site. Figma’s help page says you cannot change that assigned subdomain. Add a custom domain if you need your own URL. On Organization and Enterprise plans you can also restrict the site to people logged into the organization. - Open the live URL on a phone-width window and with a keyboard. Compare it to the frame for type, color, and logo clear space.
- Later edits stay on the canvas until you publish an update. Deleting a webpage in the file does not remove it from the live site until that update is published.
To take the site down, open Site settings, then General if Figma asks for it, then Unpublish. Publishing again reuses the same domain. You can also republish an older published version. That restores the generated files from that publish. It does not change the canvas.
What stays in Figma
The design file still owns product UI, the component library, and brand rules that other pages use. The Sites file owns this marketing page. When a headline changes, decide whether that is a page edit (Sites, then publish an update) or a brand change (the design file, then the Sites file).
Figma’s help page says you cannot export the site’s code to publish it somewhere else. A page that must live in your repository goes through Figma to code, not through Sites.
Common mistakes
- Publishing from a Starter plan and expecting a public URL. Creating the file is free. Publishing needs a paid plan.
- Leaving draft pages on the canvas. They are part of the published site.
- Editing the canvas and sending the client the old URL before you publish an update.
- Trying to download the site as code. Figma says that export is not available.
- Picking Sites for a product app, then discovering the engineers have nothing to deploy.
FAQ
Can I publish a Figma Site on the free plan?
You can create the file on a free Starter plan. Publishing to the web is on paid plans. The Education plan includes one published site, with possible bandwidth limits.
Can I change the figma.site address?
No. Figma assigns a subdomain and the help page says you cannot change it. Add a custom domain after the first publish. If you unpublish and publish again, Figma reuses the same domain.
Where is the site hosted?
Figma’s help page says sites are hosted on Amazon Web Services in the United States, and that the domain and routing are served by Cloudflare.
Bottom line
Publish the marketing page in Figma Sites when Figma’s hosting is acceptable and you do not need the code. Finish the copy, move unfinished pages out of the file, then publish from the File icon. If the page has to live in Framer, Webflow, or your own codebase, stop here and take that path instead.
§ Keep reading