# Comparison (https://yak.style/docs/comparison)

> Compare yak with styled-components, Emotion, Linaria, StyleX, Panda CSS, Tailwind and CSS Modules on runtime cost, Server Components support and DX.

The world is not always <IconYes /> or <IconNo />. The following table is simplified. The best choice depends on your use case and preferences. [Why yak](/docs/why-next-yak) explains the trade-offs behind yak's design.

If you believe that a feature is missing, needs clarification or is incorrect, please create an issue or PR in the [GitHub repository](https://github.com/galaxuslabs/yak).

<ComparisonTable />

<sup>1)</sup> Input Delay - Injecting styles during streaming or render can cause long delays on low
end devices because of style invalidations

<sup>2)</sup> Zero Runtime - No code for CSSOM insertions or updates

<sup>3)</sup> Zero SSR Overhead - During SSR no code is generating CSS

<sup>4)</sup> Compile time optimized - Minimizing compile time (e.g. by using Rust)

<sup>5)</sup> yak supports Vite (since next-yak 9.1.0) and Storybook (via `@yak/storybook`)