Forms & Signup
Radio Buttons vs Dropdown in a Form A/B Test
Radio buttons show all options immediately but use more vertical space. A dropdown takes less space but requires another action to inspect the choices. Compare the same options where both controls are usable, and check platform behavior separately.
A/B test scenario. This page is a test plan, not the result of a real experiment.
- Forms & signup
- Form completion rate
Option A vs Option B
Two alternatives; neither is the incumbent.
- Changed
- Options
- Page
- Forms & signup
- Difference
- changed
Hypothesis
Radio buttons show every option up front, so users can compare and choose without an extra tap, while a dropdown saves space and can make the form look shorter. If seeing the options eases the decision, radio buttons may bring a higher form completion rate; if a shorter-looking form matters more, the dropdown may come out ahead.
Test plan
When to run this test
Long pauses at a single-select field in field analytics, validation errors from missing selections, or session recordings of visitors opening and closing the dropdown mark that field as a sticking point. With the right format, users get through the field faster and fewer abandon the form there. If the option set is so short or so long that one control is clearly a poor fit, use the control that suits the context instead. If you do test, start both arms with nothing selected and give the dropdown an empty "Select an option" entry, so the first option is not chosen by default.
How to measure success
Form completion rate
Compare successful submissions to see whether the selection format affects completion.
Also track
- Field completion timeMeasure time from first interaction with the field to a valid selection.
- Field-level abandonmentCompare visitors who reach the selection field but leave before completing the form.
- Invalid selection rateTrack invalid or missing choices; changing a valid preference is not an error.
How to set it up
- FormatCompare the same option set as radio buttons and as a dropdown.
- Keep constantKeep options, order, default selection and validation unchanged.
- CompletionRead completion of the field alongside form completion.
- ErrorsSeparate changed selections from validation errors.
- Keyboard and accessibilityCheck keyboard navigation, screen-reader announcements and mobile usability for both formats.
What to watch when reading the result
- 1A shorter field completion time does not pick the winner by itself; the form completion rate does. Count only invalid or missing choices in the invalid selection rate, and do not read a user changing a valid preference as an error.
- 2This comparison tells you only about the field and option set you tested; rerun it in another single-select field before applying it there. Review mobile and desktop separately, and make sure mobile keeps the platform's native dropdown and that keyboard and screen-reader behavior stays intact for both controls.
- 3A small or unclear difference does not prove that the two controls work equally well. Enter the smallest difference you care about and the current form completion rate in the sample size calculator, and compare the sample it gives per variant with what the test collected. If the test fell short of it, the difference may simply have gone undetected; then accessibility and space needs may decide the choice.
Frequently Asked Questions
How should option count guide radio buttons versus a dropdown?
Few short options may benefit from being visible together. Longer lists can suit a dropdown. There is no universal count cutoff. Consider task, labels, defaults and device, then test usable controls with the same options.
Should changing a selection count as an error?
No. A valid preference change is not a validation failure. Track invalid or missing choices separately from ordinary changes.
Can a preselected dropdown option create a problem?
Match the initial state between arms. If starting unselected, include an empty “Select an option” entry; otherwise a native select may initially choose the first item. Do not inflate completion through unnoticed defaults.
More tests in Forms & Signup
All testsAbove vs Left-Aligned Form Label A/B Test Example
Forms & signupForm completion rate
Labels above the input against labels aligned to its left. Read why scan path, vertical space and long or translated labels pull the decision both ways.
Floating vs Always-Visible Form Labels A/B Test
Forms & signupForm completion rate
The floating label that starts inside the field and rises on typing, compared with a label that never disappears. Setup, arms and completion metric.
One-Column vs Two-Column Form Layout A/B Test
Forms & signupForm completion rate
Fields laid out in two columns against the same fields stacked in one. Explains the zigzag scan problem, perceived length and how it gets measured.