Registration Form template
Create an account or event registration with the smallest set of fields you will actually use. Copy the accessible markup, adjust the fields, and publish it with Core Forms.
What your visitor sees
Plain semantic HTML rendered through the same default form theme Core Forms applies on the front-end. Try it — this demo confirms inline and sends nothing.
Demo only. On your site, the same markup wires into the normal Core Forms action loop — email, Slack, Google Sheets, webhook, whatever you configure.
The HTML behind it
Copy this block, paste into Core Forms → Add New Form → Fields tab, save. Field names map to merge tags automatically in your action templates.
<p><label for="reg-name">Full name</label><input id="reg-name" name="NAME" type="text" autocomplete="name" required aria-required="true"></p>
<p><label for="reg-email">Email</label><input id="reg-email" name="EMAIL" type="email" autocomplete="email" required aria-required="true"></p>
<p><label for="reg-org">Organization <span>(optional)</span></label><input id="reg-org" name="ORGANIZATION" type="text" autocomplete="organization"></p>
<p><label for="reg-plan">What are you registering for?</label><select id="reg-plan" name="PLAN" required aria-required="true"><option value="">Choose one</option><option>Free account</option><option>Workshop</option><option>Membership</option></select></p>
<p><label><input name="TERMS" type="checkbox" value="yes" required aria-required="true"> I agree to the terms and privacy policy</label></p>
<p><button type="submit">Register</button></p>
What this registration form template is for
Use this for a membership, a workshop, or a site account. Email plus a unique identifier is the core. Extra fields should change what happens after submit.
This version asks only for information needed to complete that job. Do not collect a password on a public HTML form unless the destination hashes it on the server and you have a real account system. For WordPress users, create the user from a verified submission instead of storing the password in the form table.
The markup uses explicit labels, useful autocomplete values, and fieldsets for grouped choices. You can edit every line instead of working around a locked template schema.
Every field, and why it's there
| Field | Type | Required | Why it's there |
|---|---|---|---|
| Full name | text | Yes | Display name for the account or badge. |
email | Yes | Login identity and confirmation route. | |
| Organization | text | Optional | Useful for B2B events. Skip it for consumer signups. |
| Ticket or plan | select | Yes | What they are registering for. |
| Consent | checkbox | Yes | Terms or privacy acceptance, named on the page. |
From this HTML to a working form
- 1
Create the form from a template
In Core Forms, add a new form and choose the Registration Form starting point, or paste the HTML below into code mode.
- 2
Remove what you will not use
Delete unnecessary fields, update the labels and choices, then set the success message to explain what happens next.
- 3
Test the whole path
Submit the form with realistic data. Verify validation, the saved submission, notification email, autoresponder, and any integration action.
Three upgrades worth considering
Show fields only when needed
Keep the first view short and reveal follow-up questions from an earlier answer.
Use conditional logic →Route the submitted data
Send the result to email, a CRM, a spreadsheet, or a signed webhook after validation.
Explore integrations →Check the funnel
Measure starts, successful submissions, and field drop-off after the form has real traffic.
Use form analytics →Registration Form template questions
Is this registration form template free to copy?
Yes. The HTML on this page is free to copy and adapt. Core Forms is required only if you want its WordPress submission handling, inbox, actions, analytics, and other plugin features.
Can I change or remove fields?
Yes. The form is plain HTML. Remove any field you cannot justify, rename fields before collecting data, and keep every label associated with its control.
Does the template save submissions in WordPress?
Core Forms can save successful submissions in its WordPress inbox. Storage is a per-form setting, so you can disable it for forms whose data should not be retained.
Can the form send a confirmation email?
Yes. Add an autoresponder action, map its recipient to the submitted email field, and state what the person should expect next.
How should I test it?
Use realistic valid data, missing required data, a malformed email address, keyboard-only navigation, and a narrow mobile viewport. Also verify every configured action and redirect.
The template is free. The plumbing is the product.
Core Forms turns this HTML into stored submissions, spam-filtered email, and 70+ integrations.