---
layout: docs
title: Input group
group: components
---
[//]: # DO NOT EDIT IT WILL BE OVERWRITTEN - copy of bootstrap documentation generated by grunt docs-copy-bootstrap-docs
{% callout info %}
**Bootstrap Reference Documentation**
This is reference documentation from Bootstrap.
It is being rendered with Material Design for Bootstrap to demonstrate default styling.
See addons(TODO: add link) for additional Material Design elements.
{% endcallout %}
Easily extend form controls by adding text, buttons, or button groups on either side of textual ``s.
## Contents
* Will be replaced with the ToC, excluding the "Contents" header
{:toc}
## Basic example
Place one add-on or button on either side of an input. You may also place one on both sides of an input. **We do not support multiple add-ons on a single side, nor multiple form-controls in a single input group.**
{% example html %}
@
@example.com
https://example.com/users/
$.00
{% endexample %}
## Sizing
Add the relative form sizing classes to the `.input-group` itself and contents within will automatically resize—no need for repeating the form control size classes on each element.
{% example html %}
@
@
@
{% endexample %}
## Checkboxes and radio addons
Place any checkbox or radio option within an input group's addon instead of text.
{% example html %}
{% endexample %}
## Button addons
Buttons in input groups are a bit different and require one extra level of nesting. Instead of `.input-group-addon`, you'll need to use `.input-group-btn` to wrap the buttons. This is required due to default browser styles that cannot be overridden.
{% example html %}
{% endexample %}
## Buttons with dropdowns
{% example html %}
{% endexample %}
## Accessibility
Screen readers will have trouble with your forms if you don't include a label for every input. For these input groups, ensure that any additional label or functionality is conveyed to assistive technologies.
The exact technique to be used (`