Add an option to copy the hex code of a color in the colors section.

[ferisso]

Add the ability to click on a color to copy its hex code.

[babakfp]

Did they really not add a copy button! Where am I going to get my colors now? Unbelievable!

There is a button on top left, where you can switch to the old site...

[victormihalache]

This is almost a must when making a design and you know you'll be using those colors in the code

[philipp-spiess]

@babakfp

Where am I going to get my colors now? Unbelievable!

Here's a temporary workaround straight from the source: https://github.com/tailwindlabs/tailwindcss/blob/next/packages/tailwindcss/theme.css#L8-L273 Alternatively you can use your browser's DevTools.

[foxt]

You can also just switch back to the V3 docs, which I think uses the same colours as V4, but its still annoying, especially if the colours are different

https://v3.tailwindcss.com/docs/customizing-colors

[mislam]

I always needed the hex codes. I understand that removing the codes makes the color table look cleaner. But at least keep the click to copy option, so that we can get the hex code. It's a must have for designers and developers who make great use of it.

[drmzio]

Looks like someone made a PR #1945 for it but there's an issue:

Because the color space of oklch is bigger than that of rgb, it means that converting from one into the other is losing information and as a result of that you will not end up with the same color.

🙃

[philipp-spiess]

Hey folks! I definitely owe you all an update on this one.

Tailwind CSS v4 uses colors in the oklch color space, so showing any values in the docs page in a narrower color space would always be odd. On the other hand we totally understand that your other design tools might not support that color space and we can definitely see it being useful to copy values from the docs straight into your designs.

One nice observation we've made, though, is that some tools are able to convert form oklch to rgb for you. E.g. when you paste an oklch(…) value into Figma, it gets converted automatically:

Screen.Recording.2025-02-20.at.17.12.40.mov

Because of that and the fact that we haven't come up with a nice UX to allow you to select wether you want to copy oklch or (approximated) hex values, and because we didn't want to stall this any further, we're going to land this with showing and copying the oklch colors for now.

However, I have also implemented an easter-egg for you all: If you hold down shift we'll show and allow you to copy the (old) hex codes. I hope this is going to be useful, but I feel like it's better than doing nothing and being in analysis paralysis 😅