Use Bootstrap’s custom button styles for actions in forms, dialogs, and more with support for
multiple sizes, states, and more.
Base class
Bootstrap has a base .btn class that sets up basic styles such as padding and content
alignment. By default, .btn controls have a transparent border and background color, and
lack any explicit focus and hover styles.
Accessibility tip: Using color to add meaning only provides a visual indication,
which will not be conveyed to users of assistive technologies like screen readers. Please ensure the
meaning is obvious from the content itself (e.g., the visible text with a
sufficient color contrast) or is
included through alternative means, such as additional text hidden with the
.visually-hidden class.
Disable text wrapping
If you don’t want the button text to wrap, you can add the .text-nowrap class to the
button. In Sass, you can set $btn-white-space: nowrap to disable text wrapping for each
button.
Button tags
The .btn classes are designed to be used with the <button> element.
However, you can also use these classes on <a> or
<input> elements (though some browsers may apply a slightly different rendering).
When using button classes on <a> elements that are used to trigger in-page
functionality (like collapsing content), rather than linking to new pages or sections within the
current page, these links should be given a role="button" to appropriately
convey their purpose to assistive technologies such as screen readers.
In need of a button, but not the hefty background colors they bring? Replace the default modifier
classes with the .btn-outline-* ones to remove all background images and colors on any
button.
Use icon buttons for actions that can be represented with simple icons. Icon buttons maintain square
proportions and use the same proportional sizing system as regular buttons.
Make buttons look inactive by adding the disabled boolean attribute to any
<button> element. Disabled buttons have pointer-events: none applied
to, preventing hover and active states from triggering.
To cover cases where you have to keep the href attribute on a disabled link, the
.disabled class uses pointer-events: none to try to disable the link
functionality of <a>s. Note that this CSS property is not yet standardized for
HTML, but all modern browsers support it. In addition, even in browsers that do support
pointer-events: none, keyboard navigation remains unaffected, meaning that sighted
keyboard users and users of assistive technologies will still be able to activate these links. So to
be safe, in addition to aria-disabled="true", also include a
tabindex="-1" attribute on these links to prevent them from receiving keyboard
focus, and use custom JavaScript to disable their functionality altogether.
Create responsive stacks of full-width, “block buttons” like those in Bootstrap 4 with a mix of our
display and gap utilities. By using utilities instead of button-specific classes, we have much greater
control over spacing, alignment, and responsive behaviors.
Here we create a responsive variation, starting with vertically stacked buttons until the
md breakpoint, where .d-md-block replaces the .d-grid class,
thus nullifying the gap-2 utility. Resize your browser to see them change.
You can adjust the width of your block buttons with grid column width classes. For example, for a
half-width “block button”, use .col-6. Center it horizontally with .mx-auto,
too.
Additional utilities can be used to adjust the alignment of buttons when horizontal. Here we’ve taken
our previous responsive example and added some flex utilities and a margin utility on the button to
right-align the buttons when they’re no longer stacked.
The button plugin allows you to create simple on/off toggle buttons.
Visually, these toggle buttons are identical to the
checkbox toggle buttons. However,
they are conveyed differently by assistive technologies: the checkbox toggles will be announced by
screen readers as “checked”/“not checked” (since, despite their appearance, they are fundamentally
still checkboxes), whereas these toggle buttons will be announced as “button”/“button pressed”. The
choice between these two approaches will depend on the type of toggle you are creating, and whether
or not the toggle will make sense to users when announced as a checkbox or as an actual button.
Toggle states
Add data-bs-toggle="button" to toggle a button’s active state. If
you’re pre-toggling a button, you must manually add the .active class
andaria-pressed="true" to ensure that it is conveyed
appropriately to assistive technologies.
You can create a button instance with the button constructor, for example:
const bsButton =newbootstrap.Button('#myButton');
Method
Description
dispose
Destroys an element’s button. (Removes stored data on the DOM element)
getInstance
Static method which allows you to get the button instance associated with a DOM element, you
can use it like this: bootstrap.Button.getInstance(element).
getOrCreateInstance
Static method which returns a button instance associated with a DOM element or creates a new
one in case it wasn’t initialized. You can use it like this:
bootstrap.Button.getOrCreateInstance(element).
toggle
Toggles push state. Gives the button the appearance that it has been activated.