Put Your Figma Site on Your Own Domain: DNS Checklist
Yes, and it's a DNS change, not a rebuild. You add the record your publishing tool gives you at your domain registrar, leave your MX (email) records untouched, wait for the certificate to issue, then test both the root domain and www. What record you add depends on where the site is published: Figma Sites asks for a TXT and a CNAME; a plugin publisher like Figment typically asks for a single A record pointing at an IP address. Below is the worksheet for both, plus what to check before and after you flip the switch.
What records does Figma Sites need?
Per Figma's help article on managing a custom domain (checked 2026-09-23), the flow is:
- Publish your site first — you need a live site before you can attach a domain.
- In the Sites file, go to Settings → Domains → Add connected domain, and enter your domain.
- If you're connecting an apex domain (
example.com) or awwwsubdomain, Figma asks whether to redirect one to the other. - Figma generates a TXT record and a CNAME record specific to your domain — add both at your registrar.
- Back in Figma, click Refresh to verify.
| Type | What it's for | Where you get the value |
|---|---|---|
| TXT | Proves you control the domain | Generated by Figma when you add the domain |
| CNAME | Points the domain at Figma's hosting | Generated by Figma when you add the domain |
One documented gotcha: if you're connecting an apex domain and it won't verify, check for a leftover AAAA record on the same host (@) — Figma's own troubleshooting note says a conflicting AAAA record can block the connection, and to remove it. This is only available on paid Figma plans with a Full seat; see Can you publish a Figma site on the free plan? for the plan breakdown, and Professional caps you at 10 connected domains (Organization and Enterprise are unlimited).
What records does a plugin publisher like Figment need?
Different tools generate different records because they route traffic differently. Figment's publish flow (in-app, under Site Settings → Domain Settings) gives you one record:
| Type | Name/Host | Value |
|---|---|---|
| A | @ (the root) | An IP address shown in your publish dialog |
Add that single A record at your registrar and you're done — no separate www record in Figment's current flow. If your registrar won't let you set an A record on the bare root (some older ones require a redirect service instead), that's a registrar limitation, not a Figment one; most modern registrars support it.
Whichever platform you're on, don't just copy this table blindly — always use the exact value your tool shows you at the moment you add the domain, not a value from a screenshot in this post.
Where do I add these at my registrar?
Every registrar buries DNS settings somewhere slightly different, but nearly all of them use one of three labels: DNS, DNS Management, or Advanced DNS, usually reachable from the domain's own settings page (not your account-wide settings). If you bought the domain through the same platform you're publishing with, some plugin publishers can offer to set the records for you automatically — check your publish dialog before doing it by hand.
How long until it's live?
For Figma Sites, Figma's own article says certificate issuance "typically takes up to 15 minutes, but can sometimes require additional time" — if you're still not seeing it after 30 minutes, that's when to check for the AAAA-record conflict above. Plugin publishers vary; most propagate within the hour once the record is saved correctly, though DNS changes can theoretically take up to 48 hours to reach every resolver worldwide.
Pre-cutover checklist
- Screenshot or export your domain's current DNS records before changing anything (so you can revert if something breaks)
- Confirm your MX (email) records are separate from the record you're about to add or change — don't touch them
- Confirm the site is already published and working on its default subdomain
- Have the exact record value from your publishing tool open in another tab, not copied from memory
Post-cutover test list
- Load the root domain (
example.com) in a private/incognito window - Load
www.example.comand confirm it redirects the way you chose (or loads independently, if you didn't set a redirect) - Check for a valid padlock/SSL — a certificate that hasn't finished issuing yet will show a browser warning
- Click through a few internal links and confirm they resolve on the new domain, not the old subdomain
- Send yourself a test email to confirm mail still works, since MX records are separate from the site records you just touched
- Re-check any analytics or tracking script you rely on, since a domain change can affect first-party cookies
Before you're in this position at all, it's worth having a design that's ready to publish cleanly — the Figma-to-website checklist and Figma to Website: How to Publish Your Design cover the publish step this domain change sits on top of.
Sources: Figma Help: Manage a custom domain for your site (checked 2026-09-23); Figma pricing FAQ (checked 2026-09-23); Figment's in-app publish/domain-settings flow (checked 2026-09-23).
