# Put Your Figma Site on Your Own Domain: DNS Checklist

Canonical: https://figment.so/blog/figma-custom-domain-dns-checklist

Yes, moving a Figma site to your own domain is a DNS change, not a rebuild. Add the record your publishing tool shows, leave MX records alone, wait for the certificate, then test the root domain and www.

**Yes, and it is a DNS change, not a rebuild.** You add the records 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`. Figma Sites asks for a TXT record and a CNAME record. A plugin publisher like Figment typically asks for a single A record that points at an IP address. The worksheet below covers both, plus what to check before and after you switch.

## What DNS records does Figma Sites need?

Figma Sites needs a TXT record and a CNAME record, both generated for your domain. Per Figma's help article on managing a custom domain, the flow is:

1. Publish your site first. You need a live site before you can attach a domain.
2. In the Sites file, go to **Settings → Domains → Add connected domain** and enter your domain.
3. If you connect an apex domain (`example.com`) or a `www` subdomain, Figma asks whether to redirect one to the other.
4. Figma generates a **TXT record** and a **CNAME record** for your domain. Add both at your registrar.
5. 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 |

If an apex domain will not verify, check for a leftover **AAAA** record on the same host (`@`). Figma's troubleshooting note says a conflicting AAAA record can block the connection, and to remove it.

Custom domains on Figma Sites need a paid Figma plan with a Full seat. See [Can you publish a Figma site on the free plan?](/blog/figma-site-free-plan) for the plan breakdown. Professional caps you at 10 connected domains (Organization and Enterprise are unlimited).

## What DNS record does a plugin publisher like Figment need?

Figment's publish flow (in the 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 the domain is set up. Figment's current flow has no separate `www` record. If your registrar does not let you set an A record on the bare root (some older ones require a redirect service), that is a registrar limit; most modern registrars support it.

Custom domains on Figment need a paid plan: Pro ($49 a month, or $39 a month billed yearly) includes up to 10, and Studio ($199 a month, or $159 a month billed yearly) up to 50. Free sites stay on a figment.so address. Pro and Studio start with a 30-day free trial. See [pricing](/pricing).

Whichever platform you use, always enter the exact value your tool shows when you add the domain, not a value from a screenshot in this post.

## Where do I add these records at my registrar?

Look for **DNS**, **DNS Management** or **Advanced DNS**, usually on the domain's own settings page rather than your account-wide settings. If you bought the domain through the platform you publish with, check your publish dialog first: some publishers can set the records for you.

## How long until the domain is live?

For Figma Sites, Figma's own article says certificate issuance "typically takes up to 15 minutes, but can sometimes require additional time". If nothing works after 30 minutes, check for the AAAA conflict above. Plugin publishers vary: most propagate within the hour once the record is saved correctly, though DNS changes can take up to 48 hours to reach every resolver worldwide.

## What should I check before switching DNS?

- [ ] Screenshot or export your domain's current DNS records so you can revert if something breaks.
- [ ] Confirm your MX (email) records are separate from the record you are about to add or change, and do not touch them.
- [ ] Confirm the site is published and working on its default subdomain.
- [ ] Keep the exact record value from your publishing tool open in another tab, not copied from memory.

## What should I test after switching DNS?

- [ ] Load the root domain (`example.com`) in a private or incognito window.
- [ ] Load `www.example.com` and confirm it redirects the way you chose (or loads on its own, if you set no redirect).
- [ ] Check for a valid padlock. A certificate that has not finished issuing shows a browser warning.
- [ ] Click 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. MX records are separate from the site records you changed.
- [ ] Re-check any analytics or tracking script you rely on, since a domain change can affect first-party cookies.

To get the design ready before this step, see the [Figma-to-website checklist](/blog/figma-to-website-checklist) and [Figma to Website: How to Publish Your Design](/blog/how-to-create-website-figma).

## Where do these facts come from?

[Figma Help: Manage a custom domain for your site](https://help.figma.com/hc/en-us/articles/31414274019863-Manage-a-custom-domain-for-your-site); [Figma pricing FAQ](https://www.figma.com/pricing-faq/); Figment's in-app publish and domain-settings flow; [Figment pricing](/pricing).
