formpit

Framer

Framer Form Not Working? 8 Reasons and How to Fix Them

Framer Form Not Working? 8 Reasons and How to Fix Them

Your Framer form looks right, the button animates, and then nothing arrives. Framer forms fail for a small number of reasons, and most take a minute to fix once you know where to look. Here they are, roughly in order of how often they happen.

First check: are you testing on the published site? Submissions from the canvas preview don't count. Publish, open the live URL in a private window, and submit from there.

How Framer forms deliver submissions

Framer's native Form component sends each submission to a destination you choose in its settings: an email address, a Google Sheet, or a webhook URL that another service receives. If no destination is set, or the one that's set can't receive the data, the form looks fine but nothing arrives.

1. No destination set

Select the Form component and look at its settings in the right panel. If the email, Google Sheets or webhook destination is empty, Framer has nowhere to send the submission. Add one, then publish again.

2. The site wasn't republished

Changes to a form, including its destination, only go live when you publish. If you edited the form and didn't publish, the live site is still running the old version.

3. Testing in the editor preview

The canvas preview is for looks. Test on the published site, ideally in a private window so cached versions of the page don't get in the way.

4. The emails are in spam

If the destination is email, check your spam and promotions folders and search for the form's name. Mark the first one as "Not spam" and add the sender to your contacts. Some company mail servers quarantine form notifications before you ever see them; ask whoever runs your email to check.

5. Duplicate or hidden fields

Each input needs its own name. Two inputs with the same name overwrite each other, so one answer disappears. A required field you've hidden on some breakpoints can also block the form from submitting at all, because the visitor can't fill it in. Check every breakpoint.

6. The webhook URL is wrong

If you send submissions to a webhook, copy the URL again from the receiving service. A missing character or an old, deleted endpoint means every submission fails quietly. Send a test submission and check the receiving service, not just Framer.

7. A custom code form with the wrong action

If you built the form yourself in an Embed or code component, check the <form> tag: the action must be the full URL including https://, the method must be POST, and every input needs a name. Our list of common HTML form mistakes covers the rest.

8. You need more than Framer's form handling

Framer's forms get submissions to you, and for many sites that's enough. They don't give you an inbox where you can see which messages you've answered, reply from the dashboard, or get reminded about leads you forgot. That's when people send their Framer forms to a form backend instead.

Sending your Framer form to Formpit

There are two ways, depending on whether you want to keep Framer's form design.

Keep Framer's Form component: use the webhook destination

  1. Create a free form at Formpit and copy its endpoint, such as https://formpit.com/f/abc123.
  2. In Framer, select the Form component and set its destination to Webhook, with your Formpit endpoint as the URL.
  3. Publish and send a test from the live site. It should appear in your Formpit inbox within a second.

Formpit accepts JSON as well as normal form posts, so it can read what Framer sends. If the test doesn't arrive, use the embed method below, which always works.

Use an embedded HTML form

Insert an Embed component, choose HTML, and paste a form like this:

<form action="https://formpit.com/f/YOUR_FORM_ID" method="POST">
  <input name="name" placeholder="Name" required>
  <input name="email" type="email" placeholder="Email" required>
  <textarea name="message" placeholder="Message" required></textarea>
  <input name="_gotcha" style="display:none" tabindex="-1" autocomplete="off">
  <button type="submit">Send</button>
</form>

Style it with CSS inside the embed to match your site, and set a redirect to a Framer thank-you page in Formpit's form settings. The HTML form generator can build the fields for you.

Either way, every submission is emailed to you and kept in an inbox where you can reply, tag and track it, with spam filtering included. The free plan covers 500 submissions a month.

Quick checklist

  • A destination is set on the Form component.
  • The site has been published since the last change.
  • You tested on the live URL, in a private window.
  • Every input has a unique name, and no required field is hidden.
  • You've checked spam and promotions for the notification.
  • Any webhook or custom action URL is copied exactly, with https://.

Frequently asked questions

Why is my Framer form not sending emails?

Most often no destination is set on the Form component, the site wasn't republished after a change, or the notification is in spam.

Do Framer form submissions work in the preview?

No. Test on the published site, ideally in a private window.

Can I send a Framer form to a webhook?

Yes. Set the Form component's destination to Webhook and paste the receiving service's URL, then publish and send a test.

More from the blog

How to Make an RSVP Form in Google Forms (and a Simpler Way)How to Make an HTML Form Send Email (4 Ways, With Code)Webflow Form Submission Limit (2026): What It Is and How to Get Past It