Tailwind CSS IntelliSense alternatives in 2026

Q: Is eslint-plugin-tailwindcss free to use?

The plugin is available to everyone for free. It installs with npm as a development dependency. The project is made for Tailwind CSS v4.

Q: Does NormWind cost money?

NormWind is free with no paid tier. It is released under the MIT license. You can install it from npm as a dev dependency, or run it with npx. Check your Tailwind version first, since NormWind works with Tailwind CSS v4 projects.

Compare Tailwind CSS IntelliSense with other tools for class checks, class ordering and class merging.

By SayDeploy · 2026-10-12

SayDeploy is published by LunarWerx, which makes some of the tools compared here.

This page compares Tailwind CSS IntelliSense with other tools for checking, ordering and merging Tailwind classes. Each option is described using only what its own source says it does, so you can match each tool to the job you need done.

Option	What it does	Install or platforms
Tailwind CSS IntelliSense	Autocomplete, syntax highlighting, and linting for Visual Studio Code users. ^[1]	Needs tailwindcss installed before it activates. ^[1]
prettier-plugin-tailwindcss	Automatically puts classes into a recommended order. ^[2]	Requires Prettier v3, ESM-only as of v0.5.x. ^[2]
eslint-plugin-tailwindcss	Checks Tailwind CSS usage with 9 rules. ^[3]	Installs with npm as a development dependency. ^[3]
tailwind-merge	Merges Tailwind CSS classes in JavaScript without style conflicts. ^[4]	Works in all modern browsers and maintained Node versions. ^[4]
NormWind	Finds shorthand pairs and arbitrary values, and can rewrite them. ^[5] ^[5]	Installs from npm as a dev dependency, or runs with npx. ^[5]

Why developers look past Tailwind CSS IntelliSense

Tailwind CSS IntelliSense enhances the Tailwind development experience for Visual Studio Code users with autocomplete, syntax highlighting, and linting. ^[1]

The extension needs tailwindcss installed before it activates. ^[1] Activation also depends on the Tailwind version in your project. For v4 and later, it needs a CSS file that imports a Tailwind stylesheet. ^[1] For v3 and earlier, it uses a Tailwind config file in the workspace. ^[1]

A reader who works outside Visual Studio Code, or who wants checks that run as part of a shared build, will find that the options below cover different ground. Each one is described in the section that names it.

prettier-plugin-tailwindcss: puts Tailwind classes in a recommended order

prettier-plugin-tailwindcss is a Prettier plugin for Tailwind CSS version 3.0 and later. ^[2] Prettier is a tool that formats code. The plugin automatically puts classes into a recommended order. ^[2] As of v0.5.x, the plugin requires Prettier v3 and is ESM-only, meaning it loads only in the modern JavaScript module format. ^[2] For Tailwind CSS v4 and later, a stylesheet path option points at the CSS stylesheet and resolves that path relative to a base directory. ^[2] The base directory defaults to the current working directory. ^[2]

eslint-plugin-tailwindcss: checks Tailwind usage in code

eslint-plugin-tailwindcss is an ESLint plugin for Tailwind CSS usage. ^[3] ESLint is a tool that checks code for problems.

The plugin is available to everyone for free. ^[3] It installs with npm, the JavaScript package manager, as a development dependency. ^[3]

tailwind-merge: merges Tailwind classes in JavaScript without conflicts

The page states that tailwind-merge supports Tailwind v4.0 up to v4.3. ^[4]

Check the package documentation for how it merges classes in JavaScript, which browsers and Node versions it runs on, and how TypeScript types are provided.

NormWind: audits Tailwind class names and can rewrite them

NormWind is made by the team that publishes this site. NormWind finds Tailwind class pairs like px-4 py-4 that can be written as one shorthand like p-4. ^[5] It also flags arbitrary values, which are custom values in square brackets such as rounded-[24px], when they match a named class such as rounded-3xl. ^[5]

A fix mode rewrites findings in Vue, Svelte, Astro and HTML files, and a broader fix mode also covers JavaScript and TypeScript files. ^[5] A preview mode shows which files a fix would change without writing anything to disk. ^[5] Before it merges classes, it compares the generated CSS before and after, and it skips the merge if the two differ. ^[5]

Its output can be plain text, JSON, or SARIF 2.1.0, a report format that GitHub code scanning reads. ^[5] It ships as a GitHub Action that annotates pull requests inline. ^[5] A diff mode reports only findings on lines changed since a git reference such as origin/main. ^[5] A baseline records current finding counts per file, so only new findings fail the check. ^[5]

NormWind is free with no paid tier. ^[5] It is released under the MIT license. ^[5] It works with Tailwind CSS v4 projects, and its automated checks run on Ubuntu, Windows and macOS. ^[5] You can install it from npm as a dev dependency, or run it with npx. ^[5]

How to pick the right Tailwind CSS IntelliSense alternative

Start with the job you need done. Tailwind CSS IntelliSense is for Visual Studio Code users, so check your editor first. ^[1]

Choose the Prettier plugin when the job is putting classes into a consistent order as files are formatted. Check your Prettier version first because the plugin requires Prettier v3 and is ESM-only as of v0.5.x. ^[2]

Choose eslint-plugin-tailwindcss when Tailwind usage should be checked by ESLint. ^[3]

Choose tailwind-merge when the job is class merging and your Tailwind version falls within the supported range of v4.0 up to v4.3. ^[4] Check the package documentation for how merging works in JavaScript before you rely on it.

Choose NormWind when the goal is finding shorthand pairs and arbitrary values, or running a check on each pull request. ^[5] ^[5] ^[5] Its GitHub Action can report only the lines changed since a git reference such as origin/main. ^[5] ^[5] Check your Tailwind version first, since NormWind works with Tailwind CSS v4 projects. ^[5]

Each of these tools does a different job, so match the tool to the job rather than treating them as swaps for one another.

Frequently asked questions

Is Tailwind CSS IntelliSense a formatter?

Tailwind CSS IntelliSense enhances the Tailwind development experience for Visual Studio Code users with autocomplete, syntax highlighting, and linting. ^[1] The Prettier plugin is a different kind of tool: it automatically puts classes into a recommended order. ^[2] Check which job you need done before you install either one.

Is eslint-plugin-tailwindcss free to use?

The plugin is available to everyone for free. ^[3] It installs with npm as a development dependency. ^[3] The project is made for Tailwind CSS v4. ^[3]

Does NormWind cost money?

NormWind is free with no paid tier. ^[5] It is released under the MIT license. ^[5] You can install it from npm as a dev dependency, or run it with npx. ^[5] Check your Tailwind version first, since NormWind works with Tailwind CSS v4 projects. ^[5]

Does Tailwind CSS IntelliSense work with newer Tailwind versions?

For Tailwind CSS v4 and later, activation requires a CSS file that imports a Tailwind CSS stylesheet. ^[1] For v3 and earlier, activation uses a Tailwind config file in the workspace. ^[1] The extension needs tailwindcss installed before it activates. ^[1] Check which of these applies to your project before you rely on it.

Can NormWind run in CI pipelines?

NormWind ships as a GitHub Action that annotates pull requests inline. ^[5] Its baseline option records current per-file finding counts, so only new findings fail the check. ^[5] The audit exits with code 1 when it finds anything, so it can fail an automated check. ^[5] Its reports can be plain text, JSON, or SARIF 2.1.0 for GitHub code scanning. ^[5]

NormWind is free with no paid tier. ^[5]

Try NormWind