--- layout: default title: Getting started slug: getting-started lead: "An overview of Bootstrap, how to download and use, basic templates and examples, and more." base_url: "../" ---

# Download Bootstrap

There are a few easy ways to quickly get started with Bootstrap, each one appealing to a different skill level and use case. Read through to see what suits your particular needs.

### Compiled CSS, JS, and fonts

The fastest way to get Bootstrap is to download the compiled and minified versions of our CSS and JavaScript, along with the included fonts. No documentation or original source files are included.

Download Bootstrap

### Additional downloads

#### Download latest source code

Get the original files for all CSS and JavaScript by downloading the latest version directly from GitHub.

#### Clone or fork via GitHub

Clone the entire project or fork your own version of Bootstrap to make it your own by visiting us on GitHub.

#### Install with Bower

Install and manage the original files for all CSS and JavaScript, along with a local copy of the docs, using Bower.

{% highlight bash %}$ bower install bootstrap{% endhighlight %}

### Bootstrap CDN

The folks over at NetDNA have graciously provided CDN support for Bootstrap's CSS and JavaScript. To use, swap your local instances for the Bootstrap CDN links listed below.

{% highlight html %}
{% endhighlight %}

#### LESS compilation

If you download the original files, you need to compile Bootstrap's LESS files into usable CSS. To do that, Bootstrap only officially supports Recess, Twitter's CSS hinter built on top of less.js.

# What's included

Within the download you'll find the following directories and files, logically grouping common assets and providing both compiled and minified variations.

Once downloaded, unzip the compressed folder to see the structure of (the compiled) Bootstrap. You'll see something like this:

{% highlight bash %} bootstrap/ ├── css/ │ ├── bootstrap.css │ ├── bootstrap.min.css │ ├── bootstrap-theme.css │ ├── bootstrap-theme.min.css ├── js/ │ ├── bootstrap.js │ ├── bootstrap.min.js └── fonts/ ├── glyphicons-halflings-regular.eot ├── glyphicons-halflings-regular.svg ├── glyphicons-halflings-regular.ttf └── glyphicons-halflings-regular.woff {% endhighlight %}

This is the most basic form of Bootstrap: compiled files for quick drop-in usage in nearly any web project. We provide compiled CSS and JS (`bootstrap.*`), as well as compiled and minified CSS and JS (`bootstrap.min.*`). Fonts from Glyphicons are included, as is the optional Bootstrap theme.

#### jQuery required

Please note that all JavaScript plugins require jQuery to be included, as shown in the starter template.

# Basic template

Make use of a super basic HTML template, or dive into a few examples we've started for you. We encourage folks to iterate on these examples and not simply use them as an end result.

Copy and paste the HTML from below to get started with a bare bones Bootstrap document.

{% highlight html %}

# Hello, world!

{% endhighlight %}

# Examples

Build on the basic template above with Bootstrap's many components. Check out some of the more advanced tips for how to customize and build on top of them.

#### Starter template

Nothing but the basics: compiled CSS and JavaScript along with a container.

#### Grids

Multiple examples of grid layouts with all four tiers, nesting, and more.

#### Jumbotron

Build around the jumbotron with a navbar and some basic grid columns.

#### Narrow jumbotron

Build a more custom page by narrowing the default container and jumbotron.

#### Navbar

Super basic template that includes the navbar along with some additional content.

#### Static top navbar

Super basic template with a static top navbar along with some additional content.

#### Fixed navbar

Super basic template with a fixed top navbar along with some additional content.

#### Sign-in page

Custom form layout and design for a simple sign in form.

#### Sticky footer

Attach a footer to the bottom of the viewport when the content is shorter than it.

#### Sticky footer with navbar

Attach a footer to the bottom of the viewport with a fixed navbar at the top.

#### Justified nav

Expand on the default navbar and more to create justified navigation links.

#### Offcanvas

Build a toggleable off-canvas navigation menu for use with Bootstrap.

#### Carousel

Customize the navbar and carousel, then add some new components.

#### Non-responsive Bootstrap

Easily disable the responsiveness of Bootstrap per our docs.

#### Bootstrap theme

Load the optional Bootstrap theme for a visually enhanced experience.

# Disabling responsiveness

Don't want your site or application to be scaled on different devices? With a little bit of work, you can disable the responsive features of Bootstrap so that mobile users see your full desktop-version site. Read below or check out the non-responsive example.

### Steps to disable responsive views

To disable responsive features, follow these steps. See it in action in the modified template below.

1. Remove (or just don't add) the viewport `<meta>` mentioned in the CSS docs
2. Remove the `max-width` on the `.container` for all grid tiers with `max-width: none !important;` and set a regular width like `width: 970px;`. Be sure that this comes after the default Bootstrap CSS. You can optionally avoid the `!important` with media queries or some selector-fu.
3. If using navbars, undo all the navbar collapsing and expanding behavior (this is too much to show here, so peep the example).
4. For grid layouts, make use of `.col-xs-*` classes in addition to or in place of the medium/large ones. Don't worry, the extra-small device grid scales up to all resolutions, so you're set there.

You'll still need Respond.js for IE8 (since our media queries are still there and need to be picked up). This just disables the "mobile site" of Bootstrap.

### Bootstrap template with disabled responsive

We've taken the above steps and applied them to an example. Read it's source code to see the specific changes called out.

View non-responsive example

# Migrating from 2.x to 3.0

Folks looking to upgrade to v3 should use this section as a general upgrade guide. We've outlined some of the major changes and provided tables that highlight key changes. For an overview, read the announcement blog post.

## Major class changes

Reference table for classes that have changed between v2.x and v3.0.

Bootstrap 2.x | Bootstrap 3.0
--- | ---
`.container-fluid` | `.container`
`.row-fluid` | `.row`
`.span*` | `.col-md-*`
`.offset*` | `.col-md-offset-*`
`.brand` | `.navbar-brand`
`.nav-collapse` | `.navbar-collapse`
`.nav-toggle` | `.navbar-toggle`
`.btn-navbar` | `.navbar-btn`
`.hero-unit` | `.jumbotron`
`.icon-*` | `.glyphicon .glyphicon-*`
`.btn` | `.btn .btn-default`
`.btn-mini` | `.btn-xs`
`.btn-small` | `.btn-sm`
`.btn-large` | `.btn-lg`
`.visible-phone` | `.visible-sm`
`.visible-tablet` | `.visible-md`
`.visible-desktop` | `.visible-lg`
`.hidden-phone` | `.hidden-sm`
`.hidden-tablet` | `.hidden-md`
`.hidden-desktop` | `.hidden-lg`
`.input-small` | `.input-sm`
`.input-large` | `.input-lg`
`.checkbox.inline` `.radio.inline` | `.checkbox-inline` `.radio-inline`
`.input-prepend` `.input-append` | `.input-group`
`.add-on` | `.input-group-addon`
`.thumbnail` | `.img-thumbnail`
`ul.unstyled` | `.list-unstyled`
`ul.inline` | `.list-inline`

## What's new

We've added a few new elements and changed some existing ones. Here's their new or updated classes.

Element | Description
--- | ---
Panels | `.panel .panel-default` `.panel-body` `.panel-title` `.panel-heading` `.panel-footer` `.panel-collapse`
List groups | `.list-group` `.list-group-item` `.list-group-item-text` `.list-group-item-heading`
Glyphicons | `.glyphicon`
Jumbotron | `.jumbotron`
Tiny grid (<768 px) | `.col-xs-*`
Small grid (>768 px) | `.col-sm-*`
Medium grid (>992 px) | `.col-md-*`
Large grid (>1200 px) | `.col-lg-*`
Offsets | `.col-sm-offset-*` `.col-md-offset-*` `.col-lg-offset-*`
Push | `.col-sm-push-*` `.col-md-push-*` `.col-lg-push-*`
Pull | `.col-sm-pull-*` `.col-md-pull-*` `.col-lg-pull-*`
Input groups | `.input-group` `.input-group-addon` `.input-group-btn`
Form controls | `.form-control` `.form-group`
Button group sizes | `.btn-group-xs` `.btn-group-sm` `.btn-group-lg`
Navbar text | `.navbar-text`
Navbar header | `.navbar-header`
Justified tabs / pills | `.nav-justified`
Responsive images | `.img-responsive`
Contextual table rows | `.success` `.danger` `.warning` `.active`
Contextual panels | `.panel-success` `.panel-danger` `.panel-warning` `.panel-info`
Modal | `.modal-dialog` `.modal-content`
Thumbnail image | `.img-thumbnail`
Well sizes | `.well-sm` `.well-lg`
Alert links | `.alert-link`

## What's removed

The following elements have been dropped or changed in v3.

Element | Removed from 2.x | 3.0 Equivalent
--- | --- | ---
Form actions | `.form-actions` | N/A
Search form | `.form-search` | N/A
Fluid container | `.container-fluid` | `.container` (no more fixed grid)
Fluid row | `.row-fluid` | `.row` (no more fixed grid)
Navbar inner | `.navbar-inner` | N/A
Dropdown submenu | `.dropdown-submenu` | N/A
Tab alignments | `.tabs-left` `.tabs-right` `.tabs-below` | N/A

## Additional notes

We've made many underlying changes in v3 that are not immediately apparent. Base classes, key styles, and behaviors have been adjusted for flexibility and our mobile first approach.

- Text-based form controls are now 100% wide. Wrap inputs inside `<div class="col-*"></div>` to control input widths.
- `.badge` no longer has contextual (-success,-primary,etc..) classes.
- `.btn` must also use `.btn-default` to get the "default" button.
- `.container` and `.row` are now fluid (percentage-based).
- Images are no longer responsive by default. Use `.img-responsive` for fluid `<img>` size.
- The icons, now `.glyphicon`, are now font based. They also require a base and icon class (e.g. `.glyphicon .glyphicon-asterisk`).
- Typeahead has been dropped, in favor of using Twitter Typeahead.
- Modal markup has changed significantly. The `.modal-header`, `.modal-body`, and `.modal-footer` sections now get wrapped in `.modal-content` and `.modal-dialog` for improved mobile styling and behavior.
- JavaScript events are namespaced. For example, to handle the modal "show" event, use `'show.bs.modal'`. For tabs "shown" use `'shown.bs.tab'`, etc..

For more information on upgrades and code snippets from the community check out Bootply.

# Browser support

Bootstrap is built to work best in the latest desktop and mobile browsers, meaning older and less advanced browsers might receive a less stylized, though fully functional, version of certain components.

### Supported browsers

Specifically, we support the latest versions of the following:

- Chrome (Mac, Windows, iOS, and Android)
- Safari (Mac and iOS only, as Windows has more or less been discontinued)
- Firefox (Mac, Windows)
- Internet Explorer
- Opera (Mac, Windows)

Unofficially, Bootstrap should look and behave well enough in Chromium for Linux and Internet Explorer 7, though they are not officially supported.

### Internet Explorer 8 and 9

Internet Explorer 8 and 9 are also supported, however, please be aware that many CSS3 properties—e.g., rounded corners and shadows—are not supported by IE8. The `placeholder` attribute is also not supported in either of these versions.

In addition, Internet Explorer 8 requires the use of respond.js to enable media query support.

### IE Compatibility modes

Bootstrap is not supported in the old Internet Explorer compatibility modes. To be sure you're using the latest rendering mode for IE, consider including the appropriate `<meta>` tag in your pages:

{% highlight html %} {% endhighlight %}

See this StackOverflow question for more information.

### Windows Phone 8 and Internet Explorer 10

Internet Explorer 10 doesn't differentiate device width from viewport width, and thus doesn't properly apply the media queries in Bootstrap's CSS. To address this, you can optionally include the following CSS and JavaScript to work around this problem until Microsoft issues a fix.

{% highlight css %} @-webkit-viewport { width: device-width; } @-moz-viewport { width: device-width; } @-ms-viewport { width: device-width; } @-o-viewport { width: device-width; } @viewport { width: device-width; } {% endhighlight %} {% highlight js %} if (navigator.userAgent.match(/IEMobile\/10\.0/)) { var msViewportStyle = document.createElement("style") msViewportStyle.appendChild( document.createTextNode( "@-ms-viewport{width:auto!important}" ) ) document.getElementsByTagName("head")[0].appendChild(msViewportStyle) } {% endhighlight %}

For more information and usage guidelines, read Windows Phone 8 and Device-Width.

### Safari percent rounding

In the latest Safari for Mac, its rendering engine has a little trouble with the long decimal places of our `.col-*-1` grid classes, meaning if you have 12 individual columns you'll notice they come up short compared to other rows of columns. There's not much we can do here (see #9282) but you do have some options:

- Add `.pull-right` to your last grid column to get the hard-right alignment
- Tweak your percentages manually to get the perfect rounding for Safari (more difficult than the first option)

We'll keep an eye on this though and update our code if we have an easy solution.

### Modals and mobile devices

#### Overflow and scrolling

Support for `overflow: hidden` on the `<body>` element is quite limited in iOS and Android. To that end, when you scroll past the top or bottom of a modal in either of those devices' browsers, the `<body>` content will begin to scroll.

#### Virtual keyboards

Also, note that if you're using inputs in your modal – iOS has a rendering bug which doesn't update the position of fixed elements when the virtual keyboard is triggered. There are a few work arounds for this, including transforming your elements to `position: absolute` or invoking a timer on focus to try to correct the positioning manually. This is not handled by Bootstrap, so it is up to you to decide which solution is best for your application.

### Browser zooming

Page zooming inevitably presents rendering artifacts in some components, both in Bootstrap and the rest of the web. Depending on the issue, we may be able to fix it (search first and then open an issue if need be). However, we tend to ignore these as they often have no direct solution other than hacky workarounds.

# Third party support

While we don't officially support any third party plugins or add-ons, we do offer some useful advice to help avoid potential issues in your projects.

### Google Maps

If you're using Google Maps on a Bootstrapped project, you might run into some display problems due to our use of `* { box-sizing: border-box; }`. Previously, you may have also ran into issues with the use of `max-width` on images. The following snippet should avoid all those problems.

{% highlight css %} /* Fix Google Maps canvas * * Wrap your Google Maps embed in a `.google-map-canvas` to reset Bootstrap's * global `box-sizing` changes. You may optionally need to reset the `max-width` * on images in case you've applied that anywhere else. (That shouldn't be as * necessary with Bootstrap 3 though as that behavior is relegated to the * `.img-responsive` class.) */ .google-map-canvas, .google-map-canvas * { .box-sizing(content-box); } /* Optional responsive image override */ img { max-width: none; } {% endhighlight %}

# Accessibility

Bootstrap follows common web standards, and with minimal extra effort, can be used to create sites that are accessibile to those using AT.

### Skip navigation

If your navigation contains many links and comes before the main content in the DOM, add a `Skip to content` link immediately after your opening `<body>` tag. (read why)

{% highlight html %}
Skip to content
The main page content.
{% endhighlight %}

### Nested headers

Another "gotcha" has to do with how you nest your `<header>` elements. Section 508 states that your largest header must be an `h1`, and the next header must be an `<h2>`, etc. This is hard to achieve in practice, but if the largest header on your site is smaller than Bootstrap's default 38px, you should consider modifying your stylesheets before using a smaller header element.

### Additional resources

- "HTML Codesniffer" bookmarklet for identifying accessibility issues
- The A11Y Project
- MDN accessibility documentation

# License FAQs

Bootstrap is released under the Apache 2 license and is copyright {{ site.time | date: "%Y" }} Twitter. Boiled down to smaller chunks, it can be described with the following conditions.

#### It allows you to:

- Freely download and use Bootstrap, in whole or in part, for personal, company internal or commercial purposes
- Use Bootstrap in packages or distributions that you create

#### It forbids you to:

- Redistribute any piece of Bootstrap without proper attribution
- Use any marks owned by Twitter in any way that might state or imply that Twitter endorses your distribution
- Use any marks owned by Twitter in any way that might state or imply that you created the Twitter software in question

#### It requires you to:

- Include a copy of the license in any redistribution you may make that includes Bootstrap
- Provide clear attribution to Twitter for any distributions that include Bootstrap

#### It does not require you to:

- Include the source of Bootstrap itself, or of any modifications you may have made to it, in any redistribution you may assemble that includes it
- Submit changes that you make to Bootstrap back to the Bootstrap project (though such feedback is encouraged)

The full Bootstrap license is located in the project repository for more information.

# Customizing Bootstrap

Customizing Bootstrap is best accomplished when you treat it as another dependency in your development stack. Doing so ensures future upgrades are as easy as possible while also familiarizing yourself to the intricacies of the framework.

Once you've downloaded and included Bootstrap's CSS into your templates, you can move on to customizing the included components. To do so, create a new stylesheet (LESS, if you like, or just plain CSS) to house your customizations.

#### Compiled or minified?

Unless you plan on reading a good chunk of the compiled CSS, go with the minified. It's the same code, just compacted. Less bandwidth is good, especially in production environments.

From there, include whatever Bootstrap components and HTML content you need to get your template setup. It's best to have a rough idea in mind of modifications to make and content to include, so be sure to spend a brief amount of time on that before moving on.

### Customizing components

There are varying degrees to customizing components, but most fall into two camps: light customizations and complete visual overhauls. Luckily, there are plenty of examples of both.

We define light customizations as mostly surface layer changes, things like a color and font changes to existing Bootstrap components. A great example of this is the the Twitter Translation Center (coded by @mdo). Let's look at how to implement the custom button we wrote for this site, `.btn-ttc`.

Instead of using the provided Bootstrap buttons, which only require just one class to start, `.btn`, we'll add our own modifier class, `.btn-ttc`. This will give us a slightly custom look with minimal effort.

{% highlight html %}
{% endhighlight %}

In the custom stylesheet, add the following CSS:

{% highlight css %} /* Custom button -------------------------------------------------- */ /* Override base .btn styles */ /* Apply text and background changes to three key states: default, hover, and active (click). */ .btn-ttc, .btn-ttc:hover, .btn-ttc:active { color: white; text-shadow: 0 -1px 0 rgba(0, 0, 0, 0.25); background-color: #007da7; } /* Apply the custom-colored gradients */ /* Note: you'll need to include all the appropriate gradients for various browsers and standards. */ .btn-ttc { background-repeat: repeat-x; background-image: linear-gradient(top, #009ED2 0%, #007DA7 100%); ... } /* Set the hover state */ /* An easy hover state is just to move the gradient up a small amount. Add other embellishments as you see fit. */ .btn-ttc:hover { background-position: 0 -15px; } {% endhighlight %}

Customizing Bootstrap components takes time, but should be straightforward. Look to the source code often and duplicate the selectors you need for your modifications. Placing them after the Bootstrap source makes for easy overriding without complication. To recap, here's the basic workflow:

- For each element you want to customize, find its code in the compiled Bootstrap CSS. Copy and paste the selector for a component as-is. For instance, to customize the navbar background, just snag `.navbar`.
- Add all your custom CSS in a separate stylesheet using the selectors you just copied from the Bootstrap source. No need for prefacing with additional classes or using `!important` here.
- Rinse and repeat until you're happy with your customizations.

Going beyond light customizations and into visual overhauls is just as straightforward as the above custom button. For a site like Karma, which uses Bootstrap as a CSS reset with heavy modifications, more extensive work is involved, but well worth it in the end.

#### Alternate customization methods

While not recommended for folks new to Bootstrap, you may use one of two alternate methods for customization. The first is modifying the source .less files (making upgrades super difficult), and the second is mapping source LESS code to your own classes via mixins. For the time being, neither of those options are documented here.

### Removing potential bloat

Not all sites and applications need to make use of everything Bootstrap has to offer, especially in production environments where bandwidth literally becomes a financial issue. We encourage folks to remove whatever is unused with our Customizer.

Using the Customizer, simply uncheck any component, feature, or asset you don't need. Hit download and swap out the default Bootstrap files with these newly customized ones. You'll get vanilla Bootstrap, but without the features *you* deem unnecessary. All custom builds include compiled and minified versions, so use whichever works for you.