# Contact form on Netlify without Netlify Forms

> Swap the data-netlify attribute for a Wrenform action URL. The same form keeps working if the site ever leaves Netlify.

Last updated 2026-11-17. Web version: https://wrenform.com/docs/hosting/netlify

```html
<form action="https://wrenform.com/f/YOUR_FORM_ID" method="POST">
  <input type="text" name="name" required>
  <input type="email" name="email" required>
  <textarea name="message" required></textarea>
  <input type="text" name="_honey" style="display:none" tabindex="-1" autocomplete="off">
  <button type="submit">Send</button>
</form>
<!-- Optional: a timing check against bots, and data-ajax to submit in place -->
<script src="https://wrenform.com/js/v1/form.js" defer></script>
```

## Why move

Netlify Forms works well while a site stays on Netlify: Netlify finds the form when it deploys. Teams move when:

- the site may leave Netlify, or the same form must work on several hosts;
- the form is built with JavaScript and needs a hidden HTML copy just so the build detects it;
- they want submissions stored in the EU, with a DPA accepted in the dashboard.

For Netlify's own plans and limits, see our [dated comparison](/alternatives/netlify-forms).

## Steps

1. [Create a form](/sign-in) in Wrenform and copy its form ID.
2. Remove `netlify` or `data-netlify`, `netlify-honeypot` and `data-netlify-recaptcha` from the form, and the hidden `form-name` input if you added one.
3. Set `action` to `https://wrenform.com/f/YOUR_FORM_ID` and keep `method="POST"`.
4. Rename your honeypot input to `_honey`. It's a field people never see, so only bots fill it in.
5. Set **Redirect to** in the form's settings if you had a custom success page. See [redirects](/docs/redirects).
6. Deploy, then add your `netlify.app` address and your custom domain under **Allowed origins**.

Netlify only processes forms that carry its own attribute, so once it's gone, Netlify leaves the form alone and the browser posts it to Wrenform. Old submissions stay in Netlify; export them there if you need them.

## Limits on Wrenform

The Free plan includes 250 submissions a month. Spam doesn't count toward it. Paid plans are on [pricing](/pricing).

## Test it

Open the deployed page and send the form. You should land on your thank-you page, and the submission shows in your dashboard and arrives by email.

## Common problems

- **The submission still shows up in Netlify.** A `netlify` attribute or a hidden `form-name` input is left on the form, or in a static copy of it.
- **`origin_not_allowed`.** Add every address the site answers on: the `netlify.app` one, the custom domain, `www`. See [errors](/docs/errors#origin_not_allowed).
- **No email arrives.** A new recipient must confirm first. See [troubleshooting](/docs/troubleshooting#the-confirmation-email-never-arrived).

## Next steps

- [Netlify Forms compared with Wrenform](/alternatives/netlify-forms): dated facts from Netlify's docs.
- [Vercel](/docs/hosting/vercel) and [GitHub Pages](/docs/hosting/github-pages): the same form on other hosts.
- [Spam](/docs/spam): how the filter works.
