# Frequently Asked Questions

We, in no way, discourage the use of TailwindCSS. In fact, we think everyone should try Tailwind before they try Twind. It is an absolutely incredible tool with amazing documentation and the entire backbone of this project!

Twind takes a different approach by removing the build step and generating the styles at run-time, which can be a useful approach for existing apps built on frameworks.

We encourage you to try both and see which one is a better fit for you and your project.

Twind works with all existing Tailwind classes and configuration. However, Twind offers extended utilities, variants, and syntaxes which are all listed in the Extended Functionality Guide.

Twind was designed with performance in mind from the start and is in the top two fastest CSS-in-JS solutions. We've put together some benchmarks if you are interested in learning more.

Coming soon...

If your project uses JavaScript/TypeScript, it should work with Twind. This includes vanilla JavaScript/TypeScript, React, React Native, Vue, Angular, Solid, AlpineJS, NextJS, Gatsby, Nuxt, 11ty, and virtually any other JavaScript framework.

Please note that usage with some frameworks, including SSR frameworks, requires additional configuration. We've put together several usage guides to help get you started.

Twind works with all major browsers but requires a polyfill for IE11 and some older browsers. Please see the Legacy Browsers guide for more information.

Yes! With Twind, dark mode is always available. Please see the configuration guide for more info.

Yes, but with a little extra configuration. Please check out the configuration guide for more info.

Yes, Twind is written in TypeScript and includes all type definitions with the modules. Please see the TypeScript usage guide for more info on how to use Twind in your TypeScript app.

We've put together a Getting Started guide to get you up in running in under a minute.

We've put together a Tailwind Migration Guide and are working on more.

Tailwind provides a twind/css package to help you incorporate raw CSS into your project. This package exposes a css function that lets you define your CSS using JavaScript object notation. Please check out our CSS-in-Twind Guide for more information.

Twind provides a first-class approach to writing global styles via the twind/css module.

We've put together a Global Styles Guide for your convenience.

Twind provides several ways to override styles, including an !important modifier, apply function, and override variant.

Please see the Overwriting Styles Guide for more information.

The twind/css package exposes a theme helper for use with the css function. View the docs here.

Twind provides a twind/server package to assist with static extraction needed for SSR apps. Please see the SSR Usage Guide for more information.

There is also a working example Next App to get you up in running.

The purpose of the shim is to allow you to take advantage of Twind without the use of the tw function. This is useful for certain situations:

• You are incrementally refactoring an existing Tailwind app.
• You just want to get up and running quickly (prototyping)

There could be performance implications of using the shim on large or highly dynamic apps due to a requirement to parse entire class attributes. However, these differences should be negligible for most static sites.

Please check out The Shim Guide for more information.

Yes, get it here.

Yes, we are active both on Github Discussions and Discord.

• Github Discussions: https://github.com/tw-in-js/twind/discussions
• Link to join Discord server: https://chat.twind.style

Hey, thanks for your interest! There are several ways that you can contribute to this project from spreading the word to fixing bugs to creating new features. We've put together a Contributing Guide to get you started.