How to Create a Multi-Step Form (Pages, Progress Bar, Logic)

To create a multi-step form, insert a New page block (type /page) wherever a section ends, name each page, then open Settings and switch on Progress bar. Respondents get Next and Back buttons and keep their answers as they move. In Qwenvo this is free.

Plan the steps first

Sketch the pages on paper before you open the editor. One idea per page works well: who you are, what you need, how to reach you. Put easy questions on page one. Put the longest or most sensitive page last, when people have already invested effort.

Build it in the editor

1. Create a form and type your first group of questions with /.
2. Where the first section ends, type /page and choose New page. Everything you type next goes onto page two.
3. Repeat for each step. Open a page's settings to give it a clear name, which helps when you set up logic.
4. Finish with a Thank-you page: add a page, switch on 'Thank you' in its settings and add your message. Use @ to personalise it.
5. Click Preview and walk through the form, using Back as well as Next.

Add a progress bar

Open Settings and switch on Progress bar. It sits above the page and fills as people move through the pages that your logic can reach. The thank-you page does not count towards it. For help see progress bar and multi-page forms.

Auto-jump for quick pages

In Settings under Behaviour, switch on Auto-jump to next page. When a page holds a single choice, dropdown, rating or linear-scale question, the form advances the moment it is answered. This suits a quick poll or a short quiz where each page is one question. It is the wrong setting for pages with several fields, so leave it off there.

Skip pages with logic

Add a conditional logic block and use Jump to page to send people to the page that fits their answer. A visitor who says they are a returning customer can jump past the intro page. Pages that no rule reaches are skipped, and required questions apply only to pages the person actually saw. The conditional logic guide covers the rule options.

Let people come back later

Two settings help long forms. Save answers for later keeps unsent answers in the respondent's browser so they can finish later; it is on by default. Partial submissions captures answers from people who start and never submit, so you can see where they left and follow up. The reasoning is in free partial submissions.

A simple structure that works

• Page 1: one or two easy questions, such as name and email.
• Page 2: the main topic, with logic that shows only relevant follow-ups.
• Page 3: optional details and a Long answer for anything else.
• Thank-you page: confirm what happens next. If you need a template, the job application form and client intake form are both multi-page.

Mistakes to avoid

• Unnamed pages. 'Page 4' is hard to find when you set up a jump.
• Auto-jump on a page with many fields. People move on before filling in the rest.
• No Back button thinking. People change answers; test that earlier answers stay.
• Testing only the main path. Check every logic branch in Preview.

One limit to know: if two teammates edit the same form at the same moment, the last save wins. Agree who is editing before a big change, and use the 90-day version history to restore an earlier design.

Polish the last page

The final button matters. In Settings under Behaviour, change the Submit button label from the default 'Submit' to words that fit, such as 'Send my application'. Then open Customize and check page width, button shape and colours; the colour picker shows the contrast of button text on its background, so you do not ship an unreadable button. A calm, consistent look across pages makes a long form feel shorter.

Questions people ask

How many steps should a multi-step form have?

As few as it takes to group the questions sensibly. Two to four steps is common, but your content decides.

Can respondents go back?

Yes. Next and Back buttons are added, and answers are kept as people move between pages.

Can I hide the Back button?

Yes, with custom CSS: .fl-form .fl-back { display: none; }. Custom CSS is free; see add custom styles.

Should I use a single page instead?

For very short forms, yes. The trade-offs are in multi-step vs long form.