react-autosuggest, react-bootstrap-typeahead, and react-select are React component libraries that provide autocomplete, typeahead, or select-with-search functionality for forms and user interfaces. They help users quickly find and select from a large set of options by filtering results as they type. While all three solve similar problems, they differ significantly in design philosophy, integration requirements, customization capabilities, and built-in features like multi-select, async loading, and styling approaches.
When you need an autocomplete, typeahead, or searchable dropdown in a React app, these three libraries are frequent contenders. But they serve different engineering trade-offs — from "bare-metal control" to "batteries-included." Let’s compare how they handle real-world scenarios.
react-autosuggest gives you raw building blocks. You render everything — input, suggestions list, individual items — and manage most state yourself. It’s a toolkit, not a finished product.
react-bootstrap-typeahead assumes you’re using Bootstrap. It ships with Bootstrap-compliant markup and styling, so it “just works” in Bootstrap projects but feels foreign elsewhere.
react-select is a full-featured, self-contained component. It handles rendering, accessibility, keyboard nav, and state internally, exposing hooks for customization instead of raw control.
All three require you to provide suggestions based on user input. Here’s how each sets up a basic single-select autocomplete.
react-autosuggestYou must define how to render the input and each suggestion, plus handle change and selection events:
import Autosuggest from 'react-autosuggest';
const getSuggestionValue = suggestion => suggestion.name;
const renderSuggestion = suggestion => <div>{suggestion.name}</div>;
function MyComponent() {
const [value, setValue] = useState('');
const [suggestions, setSuggestions] = useState([]);
const onSuggestionsFetchRequested = ({ value }) => {
setSuggestions(getSuggestions(value)); // your filtering logic
};
const onSuggestionsClearRequested = () => setSuggestions([]);
return (
<Autosuggest
suggestions={suggestions}
onSuggestionsFetchRequested={onSuggestionsFetchRequested}
onSuggestionsClearRequested={onSuggestionsClearRequested}
getSuggestionValue={getSuggestionValue}
renderSuggestion={renderSuggestion}
inputProps={{
value,
onChange: (_, { newValue }) => setValue(newValue)
}}
/>
);
}
react-bootstrap-typeaheadProvides a ready-made input with Bootstrap styling. You pass options and handle selection:
import { Typeahead } from 'react-bootstrap-typeahead';
function MyComponent() {
const [selected, setSelected] = useState([]);
return (
<Typeahead
id="basic-typeahead"
onChange={setSelected}
options={myOptions} // array of strings or objects
placeholder="Choose a state..."
selected={selected}
/>
);
}
react-selectMost declarative: pass options and let it handle everything:
import Select from 'react-select';
function MyComponent() {
return (
<Select
options={myOptions} // { value: '...', label: '...' }
onChange={selectedOption => console.log(selectedOption)}
placeholder="Select an option..."
/>
);
}
react-autosuggestNo built-in styles. You write all CSS. This gives total freedom but requires implementing hover states, focus rings, and ARIA attributes yourself.
react-bootstrap-typeaheadUses Bootstrap’s CSS classes (form-control, dropdown-menu, etc.). To customize, override Bootstrap variables or write targeted CSS. Limited JS-based theming.
react-selectSupports deep theming via a styles prop (inline styles) or className/classNamePrefix for CSS. Also offers a components prop to replace any internal part (e.g., DropdownIndicator, Option).
// react-select theming example
const customStyles = {
control: (base) => ({ ...base, backgroundColor: '#f0f0f0' }),
option: (base, state) => ({
...base,
backgroundColor: state.isFocused ? '#e0e0e0' : 'white'
})
};
<Select styles={customStyles} options={options} />
react-autosuggest: Not built-in. You’d need to manage an array of selections and render tokens yourself.react-bootstrap-typeahead: Enable with multiple prop. Renders selected items as removable badges.
<Typeahead multiple ... />
react-select: Enable with isMulti prop.
<Select isMulti options={options} />
react-autosuggest: Handle via onSuggestionsFetchRequested (as shown earlier).react-bootstrap-typeahead: Use onSearch prop to fetch options.
<Typeahead
onSearch={query => fetch(`/search?q=${query}`).then(res => res.json())}
...
/>
react-select: Use AsyncSelect component.
import AsyncSelect from 'react-select/async';
const loadOptions = (inputValue) =>
fetch(`/search?q=${inputValue}`).then(res => res.json());
<AsyncSelect loadOptions={loadOptions} />
react-autosuggest: Implement manually by checking if input value matches no suggestion.react-bootstrap-typeahead: Enable with allowNew prop.react-select: Use CreatableSelect component.
import CreatableSelect from 'react-select/creatable';
<CreatableSelect options={options} />
react-autosuggest: You must implement ARIA attributes (aria-activedescendant, aria-expanded), arrow key navigation, and screen reader announcements yourself.react-bootstrap-typeahead: Includes basic ARIA roles and keyboard support (arrow keys, Enter, Escape) out of the box.react-select: Most comprehensive built-in accessibility. Full keyboard navigation, ARIA compliance, and screen reader support without extra work.All three packages are actively maintained with recent releases:
react-autosuggest: Latest version published in 2023; no deprecation notice.react-bootstrap-typeahead: Actively updated for Bootstrap 5 compatibility.react-select: Regular releases with new features and bug fixes.None are deprecated, so all are safe for new projects — choose based on fit, not longevity concerns.
| Scenario | Best Choice |
|---|---|
| Building a custom design system with unique autocomplete UX | react-autosuggest |
| Already using Bootstrap and need a quick, consistent typeahead | react-bootstrap-typeahead |
| Need multi-select, async, creatable, or virtualized lists with minimal effort | react-select |
| Require full control over every DOM element and interaction | react-autosuggest |
| Prioritize accessibility and keyboard navigation out of the box | react-select |
Think of these as points on a spectrum:
react-autosuggest = “Give me the gears — I’ll build the car.”react-bootstrap-typeahead = “I drive a Bootstrap-branded vehicle — give me matching parts.”react-select = “I need a reliable, feature-packed sedan that just works.”Your team’s design constraints, feature requirements, and appetite for implementing low-level details should drive the decision — not popularity or bundle size alone.
Choose react-autosuggest if you need maximum control over markup, styling, and behavior with minimal assumptions. It’s ideal when you’re building a custom-designed UI that doesn’t follow Bootstrap or other design systems, and you’re comfortable implementing features like keyboard navigation, focus management, and accessibility attributes yourself. However, be prepared to write more boilerplate for common interactions like selection handling and input state management.
Choose react-bootstrap-typeahead if your project already uses Bootstrap (especially v4 or v5) and you want a typeahead component that blends seamlessly with Bootstrap’s form styles and spacing. It provides solid out-of-the-box functionality including multi-select, async support, and tokenization, but customization beyond Bootstrap’s aesthetic requires overriding CSS or using limited theming hooks. Avoid if you’re not using Bootstrap or need deep structural changes to the component.
Choose react-select if you need a highly feature-rich, accessible, and customizable select component with strong support for complex use cases like async loading, creatable options, virtualized lists, and extensive theming. It’s well-suited for admin dashboards, data-heavy applications, and scenarios requiring robust keyboard navigation and screen reader support. Its larger API surface and opinionated structure may be overkill for simple autocomplete needs, but it saves significant development time for advanced requirements.
Looking for maintainers!
Unfortunately, I don't have the time to maintain this project anymore. If you are interested to help, please reach out to me on Twitter @moroshko.
Check out the Homepage and the Codepen examples.
yarn add react-autosuggest
or
npm install react-autosuggest --save
You can also use the standalone UMD build:
<script src="https://unpkg.com/react-autosuggest/dist/standalone/autosuggest.js"></script>
import React from 'react';
import Autosuggest from 'react-autosuggest';
// Imagine you have a list of languages that you'd like to autosuggest.
const languages = [
{
name: 'C',
year: 1972
},
{
name: 'Elm',
year: 2012
},
...
];
// Teach Autosuggest how to calculate suggestions for any given input value.
const getSuggestions = value => {
const inputValue = value.trim().toLowerCase();
const inputLength = inputValue.length;
return inputLength === 0 ? [] : languages.filter(lang =>
lang.name.toLowerCase().slice(0, inputLength) === inputValue
);
};
// When suggestion is clicked, Autosuggest needs to populate the input
// based on the clicked suggestion. Teach Autosuggest how to calculate the
// input value for every given suggestion.
const getSuggestionValue = suggestion => suggestion.name;
// Use your imagination to render suggestions.
const renderSuggestion = suggestion => (
<div>
{suggestion.name}
</div>
);
class Example extends React.Component {
constructor() {
super();
// Autosuggest is a controlled component.
// This means that you need to provide an input value
// and an onChange handler that updates this value (see below).
// Suggestions also need to be provided to the Autosuggest,
// and they are initially empty because the Autosuggest is closed.
this.state = {
value: '',
suggestions: []
};
}
onChange = (event, { newValue }) => {
this.setState({
value: newValue
});
};
// Autosuggest will call this function every time you need to update suggestions.
// You already implemented this logic above, so just use it.
onSuggestionsFetchRequested = ({ value }) => {
this.setState({
suggestions: getSuggestions(value)
});
};
// Autosuggest will call this function every time you need to clear suggestions.
onSuggestionsClearRequested = () => {
this.setState({
suggestions: []
});
};
render() {
const { value, suggestions } = this.state;
// Autosuggest will pass through all these props to the input.
const inputProps = {
placeholder: 'Type a programming language',
value,
onChange: this.onChange
};
// Finally, render it!
return (
<Autosuggest
suggestions={suggestions}
onSuggestionsFetchRequested={this.onSuggestionsFetchRequested}
onSuggestionsClearRequested={this.onSuggestionsClearRequested}
getSuggestionValue={getSuggestionValue}
renderSuggestion={renderSuggestion}
inputProps={inputProps}
/>
);
}
}
| Prop | Type | Required | Description |
|---|---|---|---|
suggestions | Array | ✓ | These are the suggestions that will be displayed. Items can take an arbitrary shape. |
onSuggestionsFetchRequested | Function | ✓ | Will be called every time you need to recalculate suggestions. |
onSuggestionsClearRequested | Function | ✓* | Will be called every time you need to set suggestions to []. |
getSuggestionValue | Function | ✓ | Implement it to teach Autosuggest what should be the input value when suggestion is clicked. |
renderSuggestion | Function | ✓ | Use your imagination to define how suggestions are rendered. |
inputProps | Object | ✓ | Pass through arbitrary props to the input. It must contain at least value and onChange. |
containerProps | Object | Pass through arbitrary props to the container. Useful if you need to override the default props set by Autowhatever, for example, for accessibility. | |
onSuggestionSelected | Function | Will be called every time suggestion is selected via mouse or keyboard. | |
onSuggestionHighlighted | Function | Will be called every time the highlighted suggestion changes. | |
shouldRenderSuggestions | Function | When the input is focused, Autosuggest will consult this function when to render suggestions. Use it, for example, if you want to display suggestions when input value is at least 2 characters long. | |
alwaysRenderSuggestions | Boolean | Set it to true if you'd like to render suggestions even when the input is not focused. | |
highlightFirstSuggestion | Boolean | Set it to true if you'd like Autosuggest to automatically highlight the first suggestion. | |
focusInputOnSuggestionClick | Boolean | Set it to false if you don't want Autosuggest to keep the input focused when suggestions are clicked/tapped. | |
multiSection | Boolean | Set it to true if you'd like to display suggestions in multiple sections (with optional titles). | |
renderSectionTitle | Function | ✓ when multiSection={true} | Use your imagination to define how section titles are rendered. |
getSectionSuggestions | Function | ✓ when multiSection={true} | Implement it to teach Autosuggest where to find the suggestions for every section. |
renderInputComponent | Function | Use it only if you need to customize the rendering of the input. | |
renderSuggestionsContainer | Function | Use it if you want to customize things inside the suggestions container beyond rendering the suggestions themselves. | |
theme | Object | Use your imagination to style the Autosuggest. | |
id | String | Use it only if you have multiple Autosuggest components on a page. |
Array of suggestions to display. The only requirement is that suggestions is an array. Items in this array can take an arbitrary shape.
For a plain list of suggestions, every item in suggestions represents a single suggestion. It's up to you what shape every suggestion takes. For example:
const suggestions = [
{
text: "Apple"
},
{
text: "Banana"
},
{
text: "Cherry"
},
{
text: "Grapefruit"
},
{
text: "Lemon"
}
];
For multiple sections, every item in suggestions represents a single section. Again, it's up to you what shape every section takes. For example:
const suggestions = [
{
title: "A",
suggestions: [
{
id: "100",
text: "Apple"
},
{
id: "101",
text: "Apricot"
}
]
},
{
title: "B",
suggestions: [
{
id: "102",
text: "Banana"
}
]
},
{
title: "C",
suggestions: [
{
id: "103",
text: "Cherry"
}
]
}
];
This function will be called every time you might need to update suggestions. It has the following signature:
function onSuggestionsFetchRequested({ value, reason })
where:
value - the current value of the inputreason - string describing why onSuggestionsFetchRequested was called. The possible values are:
'input-changed' - user typed something'input-focused' - input was focused'escape-pressed' - user pressed Escape to clear the input (and suggestions are shown for empty input)'suggestions-revealed' - user pressed Up or Down to reveal suggestions'suggestion-selected' - user selected a suggestion when alwaysRenderSuggestions={true}alwaysRenderSuggestions={true})This function will be called every time you need to clear suggestions.
All you have to do in this function is to set suggestions to [].
Note: When alwaysRenderSuggestions={true}, you don't have to implement this function.
When user navigates the suggestions using the Up and Down keys, the input value should be set according to the highlighted suggestion. You design how suggestion is modelled. Therefore, it's your responsibility to tell Autosuggest how to map suggestions to input values.
This function gets the suggestion in question, and it should return a string. For example:
function getSuggestionValue(suggestion) {
return suggestion.text;
}
Use your imagination to define how suggestions are rendered.
The signature is:
function renderSuggestion(suggestion, { query, isHighlighted })
where:
suggestion - The suggestion to renderquery - Used to highlight the matching string. As user types in the input, query will be equal to the trimmed value of the input. Then, if user interacts using the Up or Down keys, the input will get the value of the highlighted suggestion, but query will remain to be equal to the trimmed value of the input prior to the Up and Down interactions.isHighlighted - Whether or not the suggestion is highlighted.It should return a string or a ReactElement. For example:
function renderSuggestion(suggestion) {
return <span>{suggestion.text}</span>;
}
Important: renderSuggestion must be a pure function (we optimize rendering performance based on this assumption).
Autosuggest is a controlled component. Therefore, you MUST pass at least a value and an onChange callback to the input. You can pass any other props as well. For example:
const inputProps = {
value, // usually comes from the application state
onChange, // called every time the input value changes
onBlur, // called when the input loses focus, e.g. when user presses Tab
type: "search",
placeholder: "Enter city or postcode"
};
The signature is:
function onChange(event, { newValue, method })
where:
newValue - the new value of the inputmethod - string describing how the change has occurred. The possible values are:
'down' - user pressed Down'up' - user pressed Up'escape' - user pressed Escape'enter' - user pressed Enter'click' - user clicked (or tapped) on suggestion'type' - none of the methods above (usually means that user typed something, but can also be that they pressed Backspace, pasted something into the input, etc.)The signature is:
function onBlur(event, { highlightedSuggestion })
where:
highlightedSuggestion - the suggestion that was highlighted just before the input lost focus, or null if there was no highlighted suggestion.Provides arbitrary properties to the outer div container of Autosuggest. Allows the override of accessibility properties.
const containerProps = {
dataId: 'my-data-id'
// ... any other properties
};
This function is called when suggestion is selected. It has the following signature:
function onSuggestionSelected(event, { suggestion, suggestionValue, suggestionIndex, sectionIndex, method })
where:
suggestion - the selected suggestionsuggestionValue - the value of the selected suggestion (equivalent to getSuggestionValue(suggestion))suggestionIndex - the index of the selected suggestion in the suggestions arraysectionIndex - when rendering multiple sections, this will be the section index (in suggestions) of the selected suggestion. Otherwise, it will be null.method - string describing how user selected the suggestion. The possible values are:
'click' - user clicked (or tapped) on the suggestion'enter' - user selected the suggestion using EnterThis function is called when the highlighted suggestion changes. It has the following signature:
function onSuggestionHighlighted({ suggestion })
where:
suggestion - the highlighted suggestion, or null if there is no highlighted suggestion.By default, suggestions are rendered when the input isn't blank. Feel free to override this behaviour.
This function gets the current value of the input and the reason why the suggestions might be rendered, and it should return a boolean.
For example, to display suggestions only when input value is at least 3 characters long, do:
function shouldRenderSuggestions(value, reason) {
return value.trim().length > 2;
}
You can use the second reason argument to finely control exactly when the suggestions are rendered. The possible values are closely related to those for onSuggestionsFetchRequested, plus a few extra cases:
'input-changed' - user typed something'input-focused' - input was focused'input-blurred' - input was un-focused'escape-pressed' - user pressed Escape to clear the input (and suggestions are shown for empty input)'suggestions-revealed' - user pressed Up or Down to reveal suggestions'suggestions-updated' - the suggestions were updated'render' - the component is re-renderingWhen shouldRenderSuggestions returns true, suggestions will be rendered only when the input is focused.
If you would like to render suggestions regardless of whether the input is focused or not, set alwaysRenderSuggestions={true} (shouldRenderSuggestions is ignored in this case).
Set alwaysRenderSuggestions={true} if you'd like to always render the suggestions.
Important: Make sure that the initial value of suggestions corresponds to the initial value of inputProps.value. For example, if you'd like to show all the suggestions when the input is empty, your initial state should be something like:
this.state = {
value: "",
suggestions: allSuggestions
};
When highlightFirstSuggestion={true}, Autosuggest will automatically highlight the first suggestion. Defaults to false.
By default, focusInputOnSuggestionClick={true}, which means that, every time suggestion is clicked (or tapped), the input keeps the focus.
On mobile devices, when the input is focused, the native keyboard appears. You'll probably want to lose the focus when suggestion is tapped in order to hide the keyboard.
You can do something like this:
<Autosuggest focusInputOnSuggestionClick={!isMobile} ... />
where isMobile is a boolean describing whether Autosuggest operates on a mobile device or not. You can use kaimallea/isMobile, for example, to determine that.
By default, Autosuggest renders a plain list of suggestions.
If you'd like to have multiple sections (with optional titles), set multiSection={true}.
multiSection={true})When rendering multiple sections, you need to tell Autosuggest how to render a section title.
This function gets the section to render (an item in the suggestions array), and it should return a string or a ReactElement. For example:
function renderSectionTitle(section) {
return <strong>{section.title}</strong>;
}
If renderSectionTitle returns null or undefined, section title is not rendered.
multiSection={true})When rendering multiple sections, you need to tell Autosuggest where to find the suggestions for a given section.
This function gets the section to render (an item in the suggestions array), and it should return an array of suggestions to render in the given section. For example:
function getSectionSuggestions(section) {
return section.suggestions;
}
Note: Sections with no suggestions are not rendered.
You shouldn't specify renderInputComponent unless you want to customize the rendering of the input.
To keep Autosuggest accessible, renderInputComponent MUST:
inputProps to the inputExample:
const renderInputComponent = inputProps => (
<div>
<input {...inputProps} />
<div>custom stuff</div>
</div>
);
Note: When using renderInputComponent, you still need to specify the usual inputProps. Autosuggest will merge the inputProps that you provide with other props that are needed for accessibility (e.g. 'aria-activedescendant'), and will pass the merged inputProps to renderInputComponent.
You shouldn't specify renderSuggestionsContainer unless you want to customize the content or behaviour of the suggestions container beyond rendering the suggestions themselves. For example, you might want to add a custom text before/after the suggestions list, or to customize the scrolling behaviour of the suggestions container.
The signature is:
function renderSuggestionsContainer({ containerProps, children, query })
where:
containerProps - props that you MUST pass to the topmost element that is returned from renderSuggestionsContainer.children - the suggestions themselves. It's up to you where to render them.query - Same as query in renderSuggestion.For example:
function renderSuggestionsContainer({ containerProps, children, query }) {
return (
<div {...containerProps}>
{children}
<div>
Press Enter to search <strong>{query}</strong>
</div>
</div>
);
}
When renderSuggestionsContainer returns a composite component (e.g. <IsolatedScroll ... /> as opposed to a DOM node like <div ... />), you MUST call containerProps.ref with the topmost element that the composite component renders.
For example:
import IsolatedScroll from "react-isolated-scroll";
function renderSuggestionsContainer({ containerProps, children }) {
const { ref, ...restContainerProps } = containerProps;
const callRef = isolatedScroll => {
if (isolatedScroll !== null) {
ref(isolatedScroll.component);
}
};
return (
<IsolatedScroll ref={callRef} {...restContainerProps}>
{children}
</IsolatedScroll>
);
}
Autosuggest comes with no styles.
It uses react-themeable that allows you to style your Autosuggest component using CSS Modules, Radium, Aphrodite, JSS, Inline styles, and global CSS.
For example, to style the Autosuggest using CSS Modules, do:
/* theme.css */
.container { ... }
.input { ... }
.suggestionsContainer { ... }
.suggestion { ... }
.suggestionHighlighted { ... }
...
import theme from "theme.css";
<Autosuggest theme={theme} ... />
When not specified, theme defaults to:
{
container: 'react-autosuggest__container',
containerOpen: 'react-autosuggest__container--open',
input: 'react-autosuggest__input',
inputOpen: 'react-autosuggest__input--open',
inputFocused: 'react-autosuggest__input--focused',
suggestionsContainer: 'react-autosuggest__suggestions-container',
suggestionsContainerOpen: 'react-autosuggest__suggestions-container--open',
suggestionsList: 'react-autosuggest__suggestions-list',
suggestion: 'react-autosuggest__suggestion',
suggestionFirst: 'react-autosuggest__suggestion--first',
suggestionHighlighted: 'react-autosuggest__suggestion--highlighted',
sectionContainer: 'react-autosuggest__section-container',
sectionContainerFirst: 'react-autosuggest__section-container--first',
sectionTitle: 'react-autosuggest__section-title'
}
The following picture illustrates how theme keys correspond to Autosuggest DOM structure:

The only reason id exists, is to set ARIA attributes (they require a unique id).
When rendering a single Autosuggest, don't set the id (it will be set to '1', by default).
When rendering multiple Autosuggest components on a page, make sure to give them unique ids. For example:
<Autosuggest id="source" ... />
<Autosuggest id="destination" ... />
npm install
npm start
Now, open http://localhost:3000/demo/dist/index.html and start hacking!