Fix your exported Framer forms
Framer doesn't offer HTML export itself, so if you've taken your site to static hosting you've used an export tool — and discovered the form looks perfect but submits nowhere. Framer's form backend stayed on Framer. The fix is a form backend that lives anywhere: this one.
Why the form died
Framer forms submit to Framer's platform. Static exports (via third-party export tools) carry the markup but not the backend. The usual advice in export guides is "replace the form with a third-party form service" — that's this page.
The fix
Because export tools produce varying markup, the most reliable approach is to point the exported <form> element at Static Contact directly:
- Sign up (free, no credit card) and grab your Form's access code.
- Find the
<form>tag in your exported HTML and set itsactionandmethod:
- Make sure each input has a
nameattribute (some exports drop them) — the names become the labels in your email. - Set a custom redirect in your Form settings to send visitors back to a thank-you page on your own domain after submitting.
Submitting with fetch()?
If your exported site submits forms from JavaScript, post the fields form-encoded to the same endpoint and ask for JSON back:
The endpoint answers AJAX callers with JSON and open CORS, so this works from any domain. Include the botbuster script (or its fields) so submissions pass bot checks.
Moving off other platforms too?
Same play, different markup: Webflow exports, Carrd forms, and Netlify Forms.