Individual form controls automatically receive some global styling. All textual
<select> elements with
.form-control are set to
width: 100%; by default. Wrap labels and controls in
.form-group for optimum spacing.
Don't mix form groups with input groups
Do not mix form groups directly with input groups. Instead, nest the input group inside of the form group.
.form-inline to your form (which doesn't have to be a
<form>) for left-aligned and inline-block controls. This only applies to forms within viewports that are at least 768px wide.
May require custom widths
Inputs and selects have
width: 100%; applied by default in Bootstrap. Within inline forms, we reset that to
width: auto; so multiple controls can reside on the same line. Depending on your layout, additional custom widths may be required.
Always add labels
Screen readers will have trouble with your forms if you don't include a label for every input. For these inline forms, you can hide the labels using the
.sr-only class. There are further alternative methods of providing a label for assistive technologies, such as the
title attribute. If none of these is present, screen readers may resort to using the
placeholder attribute, if present, but note that use of
placeholder as a replacement for other labelling methods is not advised.
Use Bootstrap's predefined grid classes to align labels and groups of form controls in a horizontal layout by adding
.form-horizontal to the form (which doesn't have to be a
<form>). Doing so changes
.form-groups to behave as grid rows, so no need for
Examples of standard form controls supported in an example form layout.
Most common form control, text-based input fields. Includes support for all HTML5 types:
Type declaration required
Inputs will only be fully styled if their
type is properly declared.
Form control which supports multiple lines of text. Change
rows attribute as necessary.
Checkboxes and radios
Checkboxes are for selecting one or several options in a list, while radios are for selecting one option from many.
Disabled checkboxes and radios are supported, but to provide a "not-allowed" cursor on hover of the parent
<label>, you'll need to add the
.disabled class to the parent
Inline checkboxes and radios
.radio-inline classes on a series of checkboxes or radios for controls that appear on the same line.
Checkboxes and radios without label text
Should you have no text within the
<label>, the input is positioned as you'd expect. Currently only works on non-inline checkboxes and radios. Remember to still provide some form of label for assistive technologies (for instance, using
Note that many native select menus—namely in Safari and Chrome—have rounded corners that cannot be modified via
<select> controls with the
multiple attribute, multiple options are shown by default.
When you need to place plain text next to a form label within a form, use the
.form-control-static class on a
We remove the default
outline styles on some form controls and apply a
box-shadow in its place for
The above example input uses custom styles in our documentation to demonstrate the
:focus state on a
disabled boolean attribute on an input to prevent user interactions. Disabled inputs appear lighter and add a
disabled attribute to a
<fieldset> to disable all the controls within the
<fieldset> at once.
Caveat about link functionality of
By default, browsers will treat all native form controls (
<button> elements) inside a
<fieldset disabled> as disabled, preventing both keyboard and mouse interactions on them. However, if your form also includes
<a ... class="btn btn-*"> elements, these will only be given a style of
While Bootstrap will apply these styles in all browsers, Internet Explorer 11 and below don't fully support the
disabled attribute on a
readonly boolean attribute on an input to prevent modification of the input's value. Read-only inputs appear lighter (just like disabled inputs), but retain the standard cursor.
Block level help text for form controls.
Associating help text with form controls
Help text should be explicitly associated with the form control it relates to using the
aria-describedby attribute. This will ensure that assistive technologies – such as screen readers – will announce this help text when the user focuses or enters the control.