Form is the parent block. It holds the field blocks and carries every form-level setting, while the fields only know about their own label, name and validation. Insert it from the Forming Form Builder category of the inserter.
What it does when you insert it
- Adds a starter contact form: Name (required text), Email (required email), Message (textarea) and a Send button, so you have something working immediately. Delete or replace any of it.
- Generates a stable form ID and stores it in the block. That ID is how a submission finds its way back to the right form, and how entries are grouped. If you duplicate a form on the same page, the copy gets its own ID automatically.
- Limits what can go inside it to field blocks: the 12 free fields, Forming Pro’s fields, and any field a developer registers.
Form
| Setting | Notes |
|---|---|
| Form name | A name for you, such as “Contact form” or “Quote request”. It labels the form in Forming → Forms, the Entries inbox, the dashboard and CSV exports. Visitors don’t see it. |
Notifications
| Setting | Notes |
|---|---|
| Recipient email(s) | One address, or several separated by commas. Invalid addresses are dropped. If none are left, the Default recipient(s) from Forming → Settings → General are used, then your site’s admin email. |
| Email subject | Defaults to New form submission on {site name}. |
| From name | The display name on the notification. Falls back to the default in Settings. |
| From email | The sending address. Use one on your own domain. See Email Notifications for why. Falls back to the default in Settings. |
If the form contains an Email field, the first valid address a visitor enters becomes the notification’s Reply-To, so clicking Reply answers the person who wrote in.
After submit
Success behavior offers two choices:
- Show a message: the form resets and the message appears in the form’s response area, an ARIA live region that screen readers announce. Leave Success message empty to use the Default success message from Settings, or Thanks! Your submission has been received.
- Redirect to a URL: after a successful submission, the browser goes to the Redirect URL. It’s best when you track conversions on a thank-you page. If the URL is empty, the form shows the message instead.
Spam protection
| Setting | Default | Notes |
|---|---|---|
| Honeypot field | On | A hidden field people never see but bots tend to fill in. |
| Submission time-trap | On | Rejects submissions completed implausibly fast (under two seconds). The timestamp is signed, so bots can’t forge it. |
| CAPTCHA | Off | Adds the CAPTCHA provider chosen under Forming → Settings → Spam protection: reCAPTCHA, hCaptcha or Turnstile. If no provider is set up yet, the panel links to those settings. |
A submission caught by the honeypot or time-trap receives the ordinary success response, but is never stored or emailed, so an automated attacker gets no signal about what tripped it. The per-visitor rate limit and Akismet are site-wide settings. Details are on Spam Protection & CAPTCHA.
Storage
Store submissions is on by default. Each valid submission becomes an entry under Forming → Entries.
Turn it off when the notification email is enough, or when you’d rather not keep personal data on the server. Notifications still send with storage off. See Entries & Storage.
Design controls
The Form block supports the block editor’s own design tools, which apply to the whole form:
- Color: text, background and gradients
- Typography: font family, size and line height (inherited by the fields inside)
- Border: color, style, width and radius
- Shadow
- Dimensions: padding, margin and Block spacing, which sets the gap between fields
- Alignment: wide and full
- Anchor: an HTML ID, useful for linking straight to the form
See Styling & Layout.
More than one form on a page
That works fine. Each Form block carries its own ID and its own settings, such as different recipients or different success behavior, and submissions are matched back to the right one. Field names only need to be unique within a form. Forming → Forms flags any two forms that share an ID.
Pro settings
Forming Pro doesn’t add a separate builder. Its fields appear in the same inserter and use the same Form block settings. See Pro Field Blocks.