How To Improve UX of Web Forms

Forms are like conversations between people. They help automate things and reduce a bureaucracy if done right.

By creating forms, you build an interface where dialogue happens. So, the goal here is to make sure that the form asks the right questions at the right time.

One Column vs. Multiple

There are many debates on whether a form should fit one screen even if we have to design it in multiple columns. Of course, it depends on a case, and sometimes it can be beneficial to use all the space on the screen, but in a general case, it's a bad practice.

People must scan forms that designed in multiple columns in a Z pattern. If a form in a single column then the path to completion is straight to the bottom. So it's hard to do it wrong and skip mandatory fields or fields that are beneficial for a user after the completion of the form.

One Column vs. Multiple

Order the Form Logically

It's unusual to ask for someone's address before their name.

Reduce The Number Of Input Fields To A Minimum

Hide optional fields in an expandable box below the form, or move them to an additional panel on the side.

Remove fields that unnecessary or can be combined with others.

To make your forms simpler, you need to combine several input fields into one if possible. For instance, if you have a date into three fields, like a day, month and year.

Reduce the number of input fields to a minimum

Complex Forms Can Be Split Over Multiple Pages

A step count helps with navigation and with showing the user where they are at in the process. Huge forms lead to cognitive overload and demotivation of completion. Simplify and split it using tabs or expandable blocks/steps on one page to break big forms on smaller chunks.

Complex Forms Can Be Split Over Multiple Pages

Forms Grouping

Group fields to make the process of completion done by batches. For example, you can create a group with personal information, another group with payment details, one more for shipping details.

Forms Grouping


Place labels on the left of fields in case of large forms and on top for smaller forms.

Make label texts short. Leave big sentences for explanation text below or near an input field. Leave only essentials. Always try to reduce the number of words and get to the point right away. People don't read it, they quickly scan.

Use sentence case instead of title case. We shouldn't focus on each word on a label, and there is no context there. Sentence case is slightly easier and thus faster to follow grammatically than title case. One thing is for sure: never use all caps, or else the form would look unprofessional and be difficult to scan.

Be consistent and keep vocabulary in place. Use common words related to the product.



It's an excellent solution for small forms like login, leaving your phone to call you back, or something like that. However, they work poorly in big forms with lots of data.

The problem is that people fill out a lot of different data and at the end of this flow you don't remember which field means what? You can guess or double-check. However, if you want to check what it meant you need to remove data from it to see the placeholder again.

The good solution for it is floating labels. They look like placeholders, but when you click on it, the placeholder becomes a label on top of the value that you enter.

We can use both labels and placeholders. However, each one has its purpose. For example, labels ask for data, placeholder shows the example of this data, and you already know an approximate answer or a format in what you need to enter asked information.



Don't forget to distinguish primary from secondary action. Make these buttons visually different. Moreover, if one of the buttons is about going back or canceling then make sure that it's on the left of the primary action, such as confirmation or submission.

The confirmation button should be right below the last input field. So, it's like a continuation of the form and end of it at the same time.

Be specific with names. Don't use general naming like "Submit" or "Done." Let people know what action are they doing by pushing this button and even let them know what is next. That helps to build confidence and make it look professional.


Forms Design Automation Library

Default values

Almost all people who use forms that you create select values. We should have some by default there. Alternatively, it can be pre-defined information that users already dealt previously and it can be taken from his profile or somehow calculated.


Avoid as much filling in as possible. Allow pre-population from existing records with duplicate/copy functions.

That is relevant to the growing trend of machine learning. So a modern interface can help filling up forms taking into account previous experiences. For example, a tax form can be calculated automatically taking data from different sources like financial account, transactions, previous submissions.


Leave space for feedback on the field entries. That should help provide users with quick verification for field entry data. Complex and usual fields might also benefit from advice. That helps balance the screen with useful information.

Give users an undo function to roll back changes or reset a form to its default state.

Immediate field validation adds points to confidence and professionalism.

Provide a visual indicator of the current field. It allows us to have more concentration on a current field and to return to work faster after interruption or break.

Use predictive search for fields with lots of pre-defined options.

Autocompletion is also very helpful when you have huge lists of options in select boxes.


Additional things

For desktop, forms make sure that you have autofocus on the first input field when you open a particular form. Moreover, it's good if you can move between elements with the Tab key.

In mobile experience, it's good to match keypad type with the type of data that you're are going to enter.

Hope that was useful. I'll be updating this article with more thorough information and examples. So if you want to be up to date, then please use the small form below to subscribe on updates.

Join my email list and get new posts

It's for my own eyes only. Your email is safe with me.


Max Snitser

Max is a digital product designer and indie maker. He helps some of the best companies in the world to build products used by Millions. He is a creator of the SPRY Blogging Platform, Nightfall Design System, and the Design Patterns Library. Besides his technical background, he is a writer of the book about Independent design business. Also, created this blog as a domain for the most thorough and data-driven content on topics: Design, Remote Work, Blogging, and Technologies.