The case for and against. What Tailwind CSS does well, and when it costs too much.
For. What works in its favour.
- Very fast development — build designs directly in HTML.
- Consistent design via pre-defined token system.
- Easy responsive design with built-in breakpoints.
- Simple dark mode with class or CSS variable.
- Minimal bundle size in production (usually < 10kB).
- Used by OpenAI, Shopify, GitHub, NASA, etc.
- You prefer a utility-first approach to writing custom CSS.
- You work in a team that values development speed.
Against. What to plan for.
- HTML can become very verbose with many classes.
- Learning curve to memorize class names.
- Less flexible than custom CSS for very specific designs.
- Requires a build step to purge unused CSS.
- You have a very large existing CSS codebase.
- You prefer a 'component-first' approach over utility-first.
