June 15, 2026β€’5 min read

Tailwind v3.0 Is Out: JIT, Arbitrary Values, and Plenty More

Tailwind CSS v3.0 shipped with a pile of performance upgrades that make styling more fun. Which features are worth trying first?

Read in Indonesian

Good news! Tailwind v3.0 is officially out, yay! πŸ€©πŸŽ‰

If you don't know it yet, Tailwind is a popular CSS framework for prettying up a website's look. Unlike most frameworks, Tailwind frees you from writing manual CSS lines to lay out a design. How does that work? We'll cover that another time so this doesn't run long.

Yesterday, to be exact on December 9, 2021 (you can peek at the repository here), Tailwind shipped its third version. This release brings significant performance gains, workflow improvements, and a pile of new features. So what's worth trying? Let's go through it! πŸ˜„

Key takeaways

  • JIT (Just-in-Time) is now the default mode, which makes builds far faster with no need for PurgeCSS.
  • Arbitrary values let you write custom values directly in HTML classes using square brackets.
  • A richer new color palette arrives together with an intuitive opacity modifier that uses a slash.

New Features and Sharp Improvements in Tailwind v3.0

As the most awaited release so far, the Tailwind team packed in plenty of neat features that lift productivity and make developer experience (DX) stronger.

Tailwind CSS v3.0 has got to be our most exciting release ever...

tailwindcss.com

The most notable new features include:

  • Just-in-Time (JIT) mode as the default, which used to sit in preview.
  • A new color palette, including extra colors for box shadow and text decoration.
  • Arbitrary values, a fun way to write inline styles while still using utility class.
  • Print modifiers, to make print layout easier to control.
  • Aspect ratio, native support for aspect ratios with no padding tricks.
  • Play CDN, to try Tailwind JIT right in the browser instantly.
  • And many more utility classes!

Since the feature list overflows, we'll focus on the three main ones I think matter most. For the full list, head to the official Tailwind CSS site. While you're there, read the docs, which are friendly and easy to learn from!

Making Websites More Colorful

Tailwind v3.0 arrives with plenty of fresh color palettes. Tailwind's default colors have never disappointed. Better yet, the team claims every scheme was picked by hand (hand-crafted), not churned out by an automatic script generator. You can even see the proof in the JavaScript color config file in their GitHub repo.

Tailwind includes an expertly-crafted default color palette out-of-the-box that is a great starting point if you don’t have your own specific branding in mind.

tailwindcss.com

From gray, red, orange, and purple variations down to black and white, everything is there. The shades are arranged in neat steps with precise contrast from light to dark.

πŸ“· Illustration: a chart of the default Tailwind CSS color palette, with brightness gradations from scale 50 to 900.

Still not happy with the defaults? Want to use your own custom color? Just register it in the tailwind.config.js config file.

In this latest version, Tailwind also adds color support for box shadow, text decoration, and caret color (the blinking cursor line in a text box).

It doesn't stop there. There's also a neat feature called opacity modifier, which changes the transparency (opacity) of the color you apply. The trick is easy and intuitive: add a slash / followed by the opacity percentage you want.

HTML
<p class="bg-red/50 text-black">
  Teks hitam dengan latar belakang merah transparan 50%
</p>

Arbitrary Values: Inline Style with Style

Before, adding a custom size or color meant opening the config file and editing it. No more hassle now. Tailwind v3 introduces a special annotation for putting custom values straight into an existing utility class. Just use square brackets [...] after the utility name.

For instance, if you want text at font size 77px in the blue #0366D6, you just write the HTML class like this:

HTML
<p class="text-[77px] text-[#0366D6]">
  Teks ini berwarna #0366D6 dengan ukuran 77px
</p>

Practical, right? No more flipping back to the config file for one or two unique elements! 🀩

Want more complex styling, like a custom box-shadow? That works too:

HTML
<div class="shadow-[0_35px_60px_-15px_rgba(0,0,0,0.3)]">
  <!-- Sama seperti properti CSS box-shadow: 0 35px 60px -15px rgba(0, 0, 0, 0.3) -->
</div>

Even with this bracket trick, we can write CSS custom properties that Tailwind doesn't support by default. It feels like writing inline style, but in a tidy and integrated format.

You can learn the full trick in the official Tailwind CSS docs.

Hello JIT, Goodbye PurgeCSS!

Here's the champion feature, the one I think is most revolutionary in this release. JIT (Just-in-Time) mode was already introduced in Tailwind v2.1, but its status then was still preview. It worked normally without real trouble, yet it still felt different from a stable feature.

Before, if you used Tailwind v2.2 with JIT mode on, the terminal printed a warning that the feature was still in preview and not recommended for production.

πŸ“· Illustration: the terminal warning about the experimental status of JIT mode in Tailwind CSS version 2.2.

Now JIT mode is claimed to be truly mature and officially the default in Tailwind v3.0. So we can say goodbye to PurgeCSS! 🀟

A little flashback: before JIT, Tailwind used tree-shaking with help from PurgeCSS. During development you got a giant CSS file holding every utility class, about 3MB in size. Only at production build did the system scan the HTML files and remove unused utility classes to shrink the file.

With JIT the flow flips 180 degrees. Tailwind starts from an empty CSS file. Every time you add a utility class in an HTML file or component, the JIT engine generates the matching style instantly.

The biggest win is performance. Compilation runs far faster than traditional PurgeCSS. I compared it directly on the same project, and the difference saved up to 15 seconds! That project happened to use Nuxt and PostCSS 8.

On top of that, the CSS file during development stays as lean as the production version. No more slow terminal from processing a huge CSS file while you code.

On the subject of variants, the newest Tailwind means no more registering active, focus, or hover in tailwind.config.js, since JIT generates them automatically. The arbitrary values feature we discussed also works thanks to this JIT mode.

Sticking with Tailwind?

Those are the standout features Tailwind v3.0 brings. So, tempted to try them on your project right away? Or already preparing the migration to this new version?

Drop by the Tailwind installation page to start trying it, or check the Tailwind CSS GitHub repository for the development details.

Happy coding πŸ‘‹

Get better at shipping code.

Join the other developers getting tech updates, tips, and relaxed tutorials in their inbox every week.

Stay in the loop

Tech updates, coding tips, and relaxed insights straight to your inbox every week.

No spam. Unsubscribe anytime.

Read next

See all

For developers who learn by struggling

Β© 2026 Inva.dev.