Documentation User Guide

Multi-Step Forms

This page explains how to use multi-step forms in Elzo Forms.

Use a multi-step form when a form is too long to feel comfortable on one screen and you want to guide visitors through it in smaller sections.

When to use a multi-step form

Use a multi-step form when you need to collect several groups of information.

Good examples include:

  • application forms;
  • registration forms;
  • quote request forms;
  • support request forms;
  • project request forms;
  • longer contact or intake forms.

A multi-step form can make a longer form feel easier because visitors see one section at a time.

When not to use a multi-step form

Do not split a short form into steps without a reason.

If a form only asks for a name, email address, and message, one page is usually easier.

Use steps when they help visitors understand the form, not only to make the form look more complex.

Plan the form structure

Before creating steps, group your fields by purpose.

For example:

  1. Contact details
  2. Request details
  3. Additional information
  4. Confirmation

Each step should have a clear purpose.

Avoid putting unrelated fields together in the same step.

Create a multi-step form

To create a multi-step form:

  1. Open the form in the Elzo Forms builder.
  2. Add the fields you need.
  3. Add step breaks or step sections using the available multi-step controls.
  4. Move fields into the correct step.
  5. Review the order of the steps.
  6. Save the form.
  7. Open the form on the frontend.
  8. Submit a sample entry to confirm the full flow works.

The exact control names may depend on your installed version. Use the builder interface as the source of truth.

Keep each step focused

Each step should ask for a small group of related information.

For example, a project request form may use:

  • Step 1: Contact details
  • Step 2: Project details
  • Step 3: Files or notes
  • Step 4: Review and submit

Do not put too many fields in one step. If a step becomes too long, divide it into clearer sections.

Use clear step labels

If your form displays step labels, use simple names.

Good examples:

  • Contact Details
  • Request Details
  • Additional Notes
  • Submit Request

Avoid labels that are too vague, such as Step 1 or More Info, unless the context is obvious.

Use conditional logic carefully

Conditional logic can work with multi-step forms, but it needs careful checking.

A conditional field may appear or hide based on values from a previous step.

After adding conditional logic to a multi-step form:

  1. Open the form on the frontend.
  2. Go through the form using a value that should show the conditional field.
  3. Go through the form using a value that should hide the conditional field.
  4. Submit a sample entry in both cases.
  5. Confirm that required fields do not block submission when hidden.

Hidden required fields are a common source of submission problems.

Check the visitor flow

After building the form, go through it like a visitor.

Check that:

  • the first step is easy to understand;
  • each step has a clear purpose;
  • navigation between steps works;
  • required fields show useful messages;
  • conditional fields appear when expected;
  • the final submission works;
  • the saved entry contains the expected information.

Do this before adding advanced workflows or automations.

Keep the form maintainable

Long forms can become difficult to maintain.

Use these practices:

  • keep field labels clear;
  • group related fields together;
  • remove fields you do not need;
  • avoid unnecessary conditional rules;
  • check the form after major changes;
  • document complex form behavior for your team.

Troubleshooting

Visitors cannot move to the next step

Check required fields on the current step. A required field may be empty or hidden.

A field appears on the wrong step

Open the builder and check where the field is placed. Move it to the correct step and save the form.

A hidden required field blocks submission

Review the field’s required setting and conditional logic. If the field can be hidden, make sure the form can still be submitted when it is hidden.

The form works in the builder but not on the frontend

Clear caching and optimization tools, then check the frontend again. Also check for JavaScript errors caused by theme or plugin conflicts.

  • Create and Publish Your First Form
  • Field Settings
  • Conditional Logic for Fields
  • Troubleshooting Forms That Do Not Submit

Applies to

  • Elzo Forms
  • Elzo Forms PRO
  • WordPress admin
  • Frontend form display

Last reviewed

2026-07-04

 
Contact us