Tailwind vs Bootstrap: what actually changes

Tailwind and Bootstrap solve different problems: Bootstrap ships ready components, Tailwind ships the utilities to write them. If the site needs its own visual identity, Tailwind wins; if you need an internal dashboard in a week, Bootstrap wins.

The difference shows up in bytes and in lines you have to write. The full minified CSS of Bootstrap 5 weighs 232,108 bytes, read from the CDN on 1 November 2026. The Bootstrap record in the EneUI catalogue holds 13 source files for 50,755 bytes, while the shadcn/ui record holds 61 for 242,735.

What arrives with the install

Weight is a decision, not a number

Bootstrap hands over a complete stylesheet: grid, typography, forms, utilities and components. That is an advantage when you use that surface and a cost when you use a tenth of it. The Sass build lets you drop modules, but you have to know how the partials depend on each other.

Tailwind generates only the classes that appear in the scanned files. The output starts at a few kilobytes and grows with the project, while Bootstrap CSS starts at 232,108 bytes and shrinks with configuration. Comparing two single numbers proves nothing: the surface you actually use decides.

# il CSS completo di Bootstrap 5, misurato dalla CDN
curl -s https://cdn.jsdelivr.net/npm/bootstrap@5/dist/css/bootstrap.min.css | wc -c

# il CSS che Tailwind genera dal tuo progetto
npx @tailwindcss/cli -i ./src/app.css -o ./dist/app.css --minify
wc -c ./dist/app.css

# quante classi Bootstrap restano nelle pagine
rg -o "btn|col-|navbar|modal" src --glob "*.tsx" | wc -l

The third command is the migration dashboard: the number must fall with every converted page. When it reaches zero, Bootstrap can leave the project without a big bang.

Where Bootstrap still wins

Bootstrap holds 102,655 questions on Stack Overflow, ten times the `tailwind-css` tag. That number measures installed base, not quality: it means every question about grid, breakpoints and navbar already has a public answer. For a team shipping a dashboard to a client, that documentation is worth more than elegant utilities.

The limit to write down

Named limitation of Tailwind: it ships no components and no behaviour. Modal, dropdown, tooltip and accessible menus must be rebuilt on headless primitives, and that work is not included in converting classes. The 1,556 blocks in the EneUI catalogue shorten the path, but 1,459 declare "see source" as their licence: check it before you publish.

Licences and dependencies

Bootstrap is MIT and Tailwind is MIT, so the licence does not decide. Behaviour work does: if the site uses five Bootstrap plugins, the migration costs more than the CSS part. The licence of copied blocks is a second check, separate from the library one.

The starting point is /components/lib/bootstrap, the destination is /components/lib/shadcn and utilities live in /components/cat/tailwind. To understand the model before converting pages, read what Tailwind CSS is and the three-phase migration in Bootstrap to Tailwind; the measured library comparison is in React UI libraries 2026.