Forms
Everywhere else, adding a form to a static site means opening an account with a second company and pasting their code into your page. Here it is a block on your own site. The messages land in your portal and in your email, with the reply-to set to whoever wrote in.
A website made of files can show a form. It cannot do anything when somebody presses Send, because there is nothing on the other end. That is the whole reason "add a contact form to a static site" usually turns into a second subscription, somebody else's branding on your thank-you page, and a free-tier ceiling you find out about on a busy week.
Forms is an app on your own site instead. You switch it on, add a Form section to a page in the editor, and publish. From that moment the form is live, and what people write lands somewhere you already look.
It is a block you add in the editor, so it needs a site built from one of our designs. The questions live in your site's own published pages — that is how a tampered page is stopped from inventing a field. A site you publish as your own folder of files, by zip, the CLI or Git, has no design behind it to put a form in. Worth knowing before you plan around it. Every design in the gallery can carry a form, so the one you pick is a question of looks rather than features.
Where it goes
Everything lands in the portal, always, grouped by what the form was for — contact, newsletter, RSVP or quote — so a hundred sign-ups don't bury the one person asking for a quote.
The notification goes to your account's address with the reply-to set to whoever wrote in, so pressing Reply on your phone writes to your customer rather than to us. Turn the notification off per site if a site gets loud; the Inbox still gets every one.
Export the lot from the Inbox whenever you like. Messages are kept for 180 days and then deleted, so anything you need for longer is yours to take.
The form itself
Up to twelve questions on a form. You write all of it.
Each question is a line in your own words and an answer type: text, email, phone, long text, a list of choices, or yes/no. Mark each one required or not.
The heading, the supporting line, the words on the button and the thank-you message are all yours. The page carries no branding of ours — it is your website, and our name has no business on it.
Contact, newsletter, RSVP or quote. That is not decoration: it is how your Inbox groups what comes in.
There is a note back to the sender you can switch on and write yourself — your subject, your words, sent in your site's name, with replies coming to you. It is off until you turn it on, because an automatic reply nobody wrote reads worse than none at all.
A suspect message is kept and marked, never thrown away.
A filter that silently eats a real enquiry is worse for you than one you can glance at and dismiss. Obvious spam is stored in the Inbox with the reason and is not emailed to you. A borderline one is forwarded with a line saying why it was flagged, so you can judge it yourself. The form also works with JavaScript turned off, because a form that needs a script to submit is a form that fails for somebody.
What it costs
Forms is never included with a design. Every site buys it, on purpose: a form on a page nobody paid for would be a form that quietly does nothing, and a contact form that swallows enquiries is worse than no contact form at all.
| Level | Price | What you get |
|---|---|---|
| Starter | 99¢ a month | Five forms, 250 messages a month |
| Studio | $4.99 a month | Twenty-five forms, 2,000 messages a month, file uploads |
| Unlimited | $10.99 a month | As many forms as you like, file uploads |
Per site, and on top of that site's own 99¢ a month. Add-ons ride the same schedule as the site — a yearly site's Forms is billed yearly — and appear as their own line on Billing. Remove it from the site's Apps page and the form stops working on the published site; the messages you already have stay in the portal and stay exportable.
Against the usual alternative
| A separate form service | Forms here | |
|---|---|---|
| Accounts to hold | Two | One |
| Where the visitor's message is sent | Another company's address | Your own |
| Where replies go | Wherever you configured | Your inbox, reply-to the sender |
| Branding on the thank-you page | Usually theirs | None |
Quick answers
No. Forms is never included with a design — every site buys it, from 99¢ a month on top of the site's own 99¢. Bookings comes with premium designs and Shop with advanced ones, but a form is the one thing every site pays for.
No. The form is a block you add in the editor, and its questions live in your site's own published pages, so it belongs to a site built from one of our designs. A site published as a zip, from the CLI or from Git has no design behind it to put a form in.
Both to your site's Inbox in the portal, always, and to your account's email address with the reply-to set to whoever wrote in.
180 days, then they are deleted. Export them as a spreadsheet from the Inbox at any time.
The form stops working on the published site. The messages you already have stay in the portal and stay exportable.
No second company, nothing to paste into your page, and no branding of theirs on your thank-you. Read the step-by-step walkthrough in put a working contact form on a static site, or see Bookings and Shop for the other two apps.