We Just Moved FigForm to figform.com – Here’s What It Means

FigForm started as a simple idea:

“What if building a form felt like designing in Figma – but shipped to production with one script tag?”

We’ve now moved the product from figform.io to figform.com.
On the surface, it’s “just” a domain change. But it’s also a good moment to explain who FigForm is built for and how it fits into your stack.

Quick TL;DR

• FigForm now lives at figform.com instead of figform.io.

• Your account, forms, responses, and billing are unchanged.

• Existing figform.io links keep working via redirects.

• If you’ve hard-coded domains (embeds, webhooks, CSP, allowlists), it’s worth updating them to figform.com over time.

What FigForm actually does

FigForm is a Figma-like form builder focused on brand-faithful, visually rich forms.

• You drag, position, and style form components like you would in a design tool.

• You can use AI to bootstrap questions, microcopy, and flows instead of starting from a blank canvas.

• You publish with a single script tag or link.

• You get simple analytics out of the box and webhooks to send data wherever you want.

No marketplaces, no template bloat. Just a canvas, components, and enough plumbing to run forms in production.

What actually changed with figform.com

Here’s the concrete stuff that shifted under the hood.

App & dashboard

• Old: https://figform.io/dashboard

• New: https://figform.com/dashboard

If you hit the old URL, you’ll be redirected to the new domain.

Public form URLs

Anywhere you previously saw a public form on *.figform.io, you’ll now see the .com version.

All existing .io links continue working via redirects.
Over time, it’s worth updating:

• Website CTAs and in-app links

• Help center docs

• Email sequences and social posts

• Future QR codes or printed materials

Embeds

If you’re embedding FigForm in your product or website, the safest long-term move is to update your snippets.

Before:

<script src="https://figform.io/f/FORM-ID"></script>

After:

<script src="https://figform.com/f/FORM-ID"></script>

Redirects will catch most .io embed URLs, but removing the extra hop is better for:

• Strict CSP setups

• Some ad blockers / filters

• Latency and edge cases

Emails

We’re moving primary email identities from @figform.io to @figform.com.

• You’ll still reach us on the .io addresses.

• You’ll start seeing replies and system emails from @figform.com.

• If you maintain allowlists or rules, it’s worth adding the .com senders.

What didn’t change

This is a domain migration, not a product pivot.

• Your account, login, and forms are intact.

• Your themes, designs, and responses are untouched.

• Your billing and subscription stay the same.

• The roadmap is still focused on:

  • better branded forms,

  • smoother AI-assisted creation,

  • and more reliable pipes for getting data into your own stack.

If you’re already using FigForm

You don’t have to do anything immediately.
If you want to be tidy, here’s a quick checklist:

• Update embed URLs from .io → .com

• Update any hard-coded API clients or webhooks

• Add @figform.com to email allowlists / rules

• Swap visible links on your site and docs over time

If you’re just discovering FigForm on Indie Hackers

FigForm is for you if:

• You care about your brand more than you care about using a generic widget.

• You want forms that feel like part of your product, not a survey bolted on the side.

• You like the idea of a Figma-like editor, AI-assisted content, simple analytics, and webhooks instead of a giant “forms platform”.

You can now find us at https://figform.com, and if you hit any weird edge cases during the domain transition, email us at support@figform.com – I want to hear about them.

Thanks for following along (and for caring enough about forms to read this far). 💚