Back to compare picker

Search suggestions vs Autocomplete

Use search suggestions to guide query formulation. Use autocomplete when the user must complete or choose a known value.

Learn the decision

Match the interaction to the person's task

Use search suggestions to guide query formulation. Use autocomplete when the user must complete or choose a known value.

Search suggestions

Use it when: The system can predict likely queries.

Make this state clear: Typing state with suggestions.

Observe the result: Users can keep typing, choose a suggestion, dismiss suggestions, or submit their own query.

Study the full pattern →

Autocomplete

Use it when: The list is long but values are known.

Make this state clear: Empty input state.

Observe the result: Typing filters suggestions while preserving the exact typed value.

Study the full pattern →

Practice the judgment: Imagine this situation: Submitting a suggestion before the user confirms it. Write the person's goal, choose one of these patterns, and show the state that helps the person continue. Use the decision rules and source trail below to explain your choice.

Review the underlying principle →

Decision dimensions

Dimension Search suggestionsAutocomplete
UI or UX UI + UX - Suggested-query surfaceUI + UX - Input widget with suggestion behavior
UI guidance Keep suggestions visually tied to the current input.Expose clear visual states for expanded, focused, highlighted, and selected options.
UX guidance Help the person reach a clear task outcome.Preserve typed input and make selection reversible before submission.
Good UI Suggestions appear directly below the search field with active row, readable labels, and optional matched text.Persistent label above the input, readable text size, clear popup alignment, and visible highlighted option.
Bad UI Promoted results styled the same as typed query suggestions.Placeholder-only label that disappears after typing.
Good UX Users can keep typing, choose a suggestion, dismiss suggestions, or submit their own query.Typing filters suggestions while preserving the exact typed value.
Bad UX Auto-submitting the top suggestion.Automatically forcing the first suggestion into the field.
Best fit The system can predict likely queries.The list is long but values are known.
Avoid when Suggestions are low quality or biased toward irrelevant content.The task is open-ended query exploration.
Required state Typing state with suggestions.Empty input state.
Accessibility burden Expose the suggestions list and active option.Expose combobox expanded state, active descendant, and option labels.
Common misuse Showing unrelated promoted results as suggestions.Using autocomplete where users expect broad search results.

Search suggestions

UI or UX
UI + UX - Suggested-query surface
UI guidance
Keep suggestions visually tied to the current input.
UX guidance
Help the person reach a clear task outcome.
Good UI
Suggestions appear directly below the search field with active row, readable labels, and optional matched text.
Bad UI
Promoted results styled the same as typed query suggestions.
Good UX
Users can keep typing, choose a suggestion, dismiss suggestions, or submit their own query.
Bad UX
Auto-submitting the top suggestion.
Best fit
The system can predict likely queries.
Avoid when
Suggestions are low quality or biased toward irrelevant content.
Required state
Typing state with suggestions.
Accessibility burden
Expose the suggestions list and active option.
Common misuse
Showing unrelated promoted results as suggestions.

Autocomplete

UI or UX
UI + UX - Input widget with suggestion behavior
UI guidance
Expose clear visual states for expanded, focused, highlighted, and selected options.
UX guidance
Preserve typed input and make selection reversible before submission.
Good UI
Persistent label above the input, readable text size, clear popup alignment, and visible highlighted option.
Bad UI
Placeholder-only label that disappears after typing.
Good UX
Typing filters suggestions while preserving the exact typed value.
Bad UX
Automatically forcing the first suggestion into the field.
Best fit
The list is long but values are known.
Avoid when
The task is open-ended query exploration.
Required state
Empty input state.
Accessibility burden
Expose combobox expanded state, active descendant, and option labels.
Common misuse
Using autocomplete where users expect broad search results.
Decision rules
  • Prefer search suggestions when several query paths may be useful.
  • Prefer autocomplete for constrained values such as addresses, products, people, or codes.
  • Keep typed input editable and never force an irrelevant suggestion.
Inspect live examples
Failure modes
  • Submitting a suggestion before the user confirms it.
  • Using autocomplete where free-form search is expected.
  • Showing stale suggestions that do not match the current input.

Saved items