Showcase
What you’ll build.
Recipes for the forms people actually ship: every one on a single endpoint, spam-filtered, delivered by email and to your inbox. Pick one, see exactly what lands in your inbox, and copy the code.
Eight recipes, one endpoint
Pick a pattern · switch between the preview and the code
Contact form
All plansThe classic. Name, email, message: live on a static site in three minutes.
Uses_mtf_honeypotSubject settingReply-To setting
Set the subject to “New enquiry from {{name}}” in the form’s notification settings.
Cheat sheet
Four special fields do all the work
Every recipe above is a normal form plus some of these hidden inputs. Anything else you name is stored and emailed as-is.
| Field | What it does | Example |
|---|---|---|
| _mtf_subject | Sets the notification email’s subject for this submission. Use a different value per form, or per topic with a select, to route enquiries. {{field}} inserts a submitted value. | <input type="hidden" name="_mtf_subject" value="New lead"> |
| _mtf_redirect | Where the browser goes after a successful plain-HTML submit, on one of the form’s allowed domains. Without it, visitors see a hosted success page. | <input type="hidden" name="_mtf_redirect" value="https://yoursite.com/thanks"> |
| _mtf_reply_to | Names the field whose value becomes the notification’s Reply-To, so hitting reply goes to the right person. By default it is the form’s Reply-To setting, usually the email field. | <input type="hidden" name="_mtf_reply_to" value="work_email"> |
| _mtf_honeypot | Spam trap. Hidden from people, tempting to bots. Any value drops the submission as spam. | <input name="_mtf_honeypot" tabindex="-1" aria-hidden="true" …> |
Any stack
Bring your own front end
The endpoint doesn’t care how the form is built. Plain HTML works first; everything else layers on without breaking it.
Browse platformsBuild yours.
Pick a pattern, point it at your endpoint, and watch the first submission land.
Create free endpoint