How to create custom user registration forms in WordPress

Go to Settings → General, enable Anyone can register under Membership, and save the changes. Set New User Default Role to the lowest role the account needs, normally Subscriber. Do not let visitors choose Administrator, Editor, or another privileged role from a public form.

WordPress’s built-in registration page is available through the registration URL generated by wp_registration_url(). It is a functional starting point, but it is not a branded front-end form by itself.

Decide which fields are genuinely required: username or email, password, name, consent, organisation, telephone number, or other profile data. Decide what happens after submission, including the redirect, welcome email, approval process, and assigned role.

Keep the first form short. Every extra required field creates another reason for a registration to fail, and sensitive information should not be collected unless you have a clear storage and privacy reason.

For a small customisation, use the core registration form and add fields with the register_form action. Validate those fields with registration_errors, then save accepted values after the account is created with the registration action documented for the core workflow. The extra fields are not saved automatically, so adding the HTML alone is not enough.

Place this code in a small site plugin rather than a parent theme’s functions.php, so a theme change does not remove the registration logic. Sanitise submitted values, escape output when redisplaying a failed form, and never trust a role or permission sent by the browser.

This route is reasonable for one or two fields. Its drawbacks are that you must handle validation, storage, error messages, styling, spam protection, redirects, email delivery, and future compatibility yourself. A custom form that creates users through a separate process also needs nonce checks and careful handling of duplicate usernames and email addresses.

If the core form is sufficient, add a clear Register link using the WordPress registration URL or your theme’s account navigation. If you need the form inside a normal page, with custom styling, profile editing, email verification, conditional fields, or a different registration flow, the core form alone is not enough.

Do not assume that a form plugin’s validation hooks are the same as WordPress core hooks. Support cases regularly show custom code failing because a plugin processes submissions through its own hooks instead of registration_errors.

Test a new account, an existing email address, an existing username, a blank required field, an invalid email address, a weak password, and a failed submission that must redisplay entered values. Check the assigned role and confirm that custom values appear in the user profile.

If the button appears to do nothing, check browser errors, caching, security plugins, form logs, and email delivery. Cached registration pages can cause nonce or permission failures, while security plugins can block legitimate submissions. Exclude registration and account pages from page caching before troubleshooting theme or custom code.

Install and activate Profile Builder Pro, create a front-end registration form, select the fields and role, then place the generated form shortcode on a page. This is the quicker option when you need front-end registration, profile editing, email verification, custom roles, conditional fields, or form placement outside the default WordPress login screen.

Configure the registration, login, and edit-profile pages, then test the same duplicate-account, validation, email, role, and caching cases before publishing. Use the manual route when the form is genuinely small; use the plugin route when maintaining the workflow would otherwise become your own development project.