Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My website form on Netlify no longer sends me anything

Short answer

Netlify finds forms when the site is built, so a form that was changed, rebuilt in JavaScript or renamed can silently stop being recognised. Notifications are a separate switch: they are sent only for verified submissions and only to confirmed recipients. Check the Forms tab for stored entries and the spam list first.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The visitor sees a thank-you page but no email reaches me.
  • It worked until my developer changed the page or redesigned the site.
  • The Forms tab in Netlify is empty, or shows no form at all.
  • Some messages arrive and others do not.
  • I changed the notification email address and now nothing comes.

Why does this happen?

  1. Netlify only discovers forms at build time

    Netlify reads the HTML of the site when a build finishes and looks for forms marked for it. Form detection also has to be switched on for the site, and after re-enabling it you must deploy again before anything is picked up. A form added or changed without a new deploy is not known to Netlify.

  2. The form is drawn by JavaScript, so the build never sees it

    Forms created in the browser by a framework are missing from the pre-built HTML, so the build cannot find them. Netlify's documented workaround is a hidden plain-HTML copy of the form with matching field names, or a hidden form-name field. Two forms with the same name on one site are another documented cause of failure.

  3. The way the form is sent was changed

    When a form is submitted from JavaScript, Netlify expects a URL-encoded body, not JSON. A file upload has its own limits: one file per field, an 8 MB request size and a 30-second timeout.

  4. Real enquiries were filtered as spam

    Every submission is checked for spam. Flagged ones go to a separate Spam submissions list instead of the verified list, and a person can move a false positive back to verified. Extra checks such as a honeypot or reCAPTCHA reject failures outright, and those do not appear in the spam list.

  5. The notification recipient is not valid any more

    Notifications go only for verified submissions. An outside address stays pending until its owner confirms it, and if confirmation is not available the address must be a member of the Netlify team, otherwise it is not saved.

What can I do about it today?

  1. Look in Netlify before blaming the emailOpen your site in Netlify and go to Forms. If entries are listed, the form works and the problem is in notifications or spam. If nothing is listed, the form is not being recognised.
  2. Check the Spam submissions listOpen the form's submissions and look at the Spam tab. A real customer message there can be changed back to verified by a person with access.
  3. Check the notification recipientUnder Forms, open Submission notifications. Make sure your address is listed, is not marked pending confirmation, and that you opened the confirmation email if one was sent. Check your own spam folder too.
  4. Send one test entry yourselfFill in the live form once with a clearly marked test message and see where it shows up. Note the time so it can be found later.
  5. Write down what changedNote the date the problem started and anything that changed around then: a redesign, a new developer, a new domain, a new plugin. This saves a lot of time for whoever investigates.
  6. Do not delete the form or the site settingsLeave existing submissions, the site and its domain as they are. Deleting things cannot bring lost enquiries back.

When should I bring someone in?

  • The Forms tab is empty or the form is missing, and the site was rebuilt or redesigned.
  • You are losing enquiries that carry money, bookings or support requests.
  • The form uses file uploads, or another system depends on the entries.

How do I handle it?

  1. Find out whether the form is registeredI compare what is in the built site with what Netlify lists under Forms, and check names, field names and the way the form is sent.
  2. Separate the three stagesA message can fail at three places: recognition at build time, storage as verified or spam, and the notification. I test each on its own so the fix goes to the right place.
  3. Make the form robustA form drawn by JavaScript gets a matching plain-HTML form, a clear form name and a visible error message for the visitor if the send fails.
  4. Keep a second copy of every entryImportant enquiries also go to a place you control, so one platform setting cannot silently lose them.
  5. Test with a real submissionI submit on the live site and confirm the entry and the email arrive before I call it done.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Are the missed messages gone?

Not necessarily. Entries Netlify received are stored under Forms, either as verified or in the Spam list. Entries rejected by a honeypot or reCAPTCHA check are not kept in the spam list.

Why did it stop after my site was redesigned?

Netlify only learns about forms when the site is built. A new design that draws the form in JavaScript, or renames it, can leave Netlify with nothing to recognise.

Can I send the notification to any email address?

Team members can be added directly. An address outside the team must be confirmed by its owner first, and until then it is shown as pending.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.