We've moved FigForm from figform.io to figform.com.
This is a small change on the surface, but it touches everything from logins and emails to embeds and webhooks. This post explains what changed, what stays the same, and what (if anything) you need to update.
TL;DR
- FigForm now lives at figform.com instead of figform.io.
- Your account, forms, responses, and billing are unchanged.
- Existing figform.io links continue to work via redirects.
- If you've hard-coded domains (embeds, webhooks, allowlists, CSP), you should update them to figform.com.
Why we moved
FigForm exists to help you ship brand-faithful, production-grade forms without touching code.
Having the product live on figform.com removes a small but constant mismatch:
- Your forms look like your product.
- Your form URLs now look like your vendor is a product company, not a side project.
- It's easier to remember, share, and trust: FigForm → figform.com.
This change also unifies our infrastructure (product, docs, and email) under a single primary domain so we can ship new features faster and with less DNS / auth friction.
What changed
App & dashboard
- Old:
https://figform.io/dashboard - New:
https://figform.com/dashboard
If you had the app bookmarked on .io, the redirect will take you to the .com domain.
Public form URLs
Anywhere you previously saw a public form URL on *.figform.io, you'll now see the .com equivalent.
Existing .io links will redirect to the .com version, so you don't have to scramble to update every live link today.
That said, we recommend updating high-traffic surfaces over time:
- Website CTAs
- Help center articles
- Social posts, email sequences, and ads
- QR codes in offline materials (for future prints)
Embeds
If you're using FigForm embeds, the safest long-term move is to replace figform.io with figform.com in your snippet.
Before:
After:
Redirects will catch most .io embed URLs, but updating to .com removes an extra hop and avoids surprises with strict CSP / ad blockers.
Emails
Our primary email identities are moving from @figform.io to @figform.com.
We'll continue to receive mail on the .io addresses, but you'll start seeing replies and system notifications from .com senders.
If you maintain sender allowlists or mail rules, you may want to add the .com versions.
What stays exactly the same
- Your account and login method
- All forms, themes, and designs
- All responses and historical data
- Your billing and subscription status
- Our product roadmap and pace of shipping
This is a domain migration, not a product migration.
FAQ
Will my old FigForm links break?
They'll continue working. They'll simply redirect from .io to .com.
Do I need to recreate my forms?
No. All forms, responses, and settings are untouched.
Does this change pricing or my plan?
No. Your subscription and usage stay exactly the same.
Will embeds or integrations stop working?
They should keep working thanks to redirects, but we recommend updating your domains (embeds, API clients, CSP, allowlists) to figform.com when convenient.
What about emails I already have in workflows?
We'll keep receiving mail on @figform.io. For new content, please use and share @figform.com.
Closing
FigForm exists to help you ship on-brand forms that feel like part of your product, not a bolt-on widget.
Moving to figform.com is a small but important step in making FigForm itself feel as polished and product-grade as the forms you build with it.
If you run into anything unexpected during the transition, we want to hear about it. You can reach us at our new support email: [email protected].
Thanks for building with FigForm. 💚