---

Forms

Examples and usage guidelines for form control styles, layout options, and custom components for creating a wide variety of forms.

Form Control

Style textual inputs and textareas with support for multiple states.

Checks & radios

use our custom radiobuttons and checkboxes in forms for selecting input options.

Input group

Attach labels and buttons to your inputs for increased semantic value.

Layout 

Create inline, horizontal, or complex grid-based layouts with your forms.

Select 

Improve browser default select elements with a custom initial appearance.

Rang 

Replace browser default range inputs with our custom version.

Floating labels 

Create beautifully simple form labels that float over your input fields.

Validation

Validate your forms with custom or native validation behaviors and styles.

Overview

Bootstrap form controls expand on our Rebooted form styles with classes. Use these classes to opt into their customized displays for a more consistent rendering across browsers and devices.
Be sure to use an appropriate type attribute on all inputs (e.g., email for email address or number for numerical information) to take advantage of newer input controls like email verification, number selection, and more.
Here is a quick example to demonstrate Bootstrap form styles. Keep reading for documentation on required classes, form layout, and more.

Form text

Block-level or inline-level form text can be created using .form-text.Form text below inputs can be styled with .form-text. If a block-level element will be used, a top margin is added for easy spacing from the inputs above.

Disabled forms

Add the disabled boolean attribute on an input to prevent user interactions and make it appear lighter. Add the disabled attribute to a <fieldset> to disable all the controls within. Browsers treat all native form controls (<input>, <select>, and <button> elements) inside a <fieldset disabled> as disabled, preventing both keyboard and mouse interactions on them.
However, if your form also includes custom button-like elements such as <a class="btn btn-*">...</a>, these will only be given a style of pointer-events: none, meaning they are still focusable and operable using the keyboard. In this case, you must manually modify these controls by adding tabindex="-1" to prevent them from receiving focus and aria-disabled="disabled" to signal their state to assistive technologies.

---