Choosing the right export format
CSS Variables work well for HTML, CSS and WordPress websites: for example, background: var(--sm-color-1). Tailwind CSS v4 uses @theme inline for variables that reference other custom properties, including light/dark roles. Tailwind CSS v3 uses theme.extend.colors in JavaScript. SCSS Maps require a Sass compiler. JSON Design Tokens are for design systems or tools that support the token structure. Flutter/Dart exports Color(0xAARRGGBB), Android exports res/values/colors.xml with #AARRGGBB, and SwiftUI exports sRGB components and opacity. Light/dark roles are named separately and do not switch automatically.
Design Tokens 2025.10: exported color tokens use $type: "color" and an sRGB object with components and a HEX fallback. Older string-based HEX tokens remain importable. sRGB alpha bytes are preserved; unresolved aliases and unsupported color spaces are not accepted.
Export a palette in three steps
- Add colors: paste
#2A6DF480, #14B8A6, #F59E0Band select Apply colors. - Choose output: use CSS variables for a website, Flutter/Android/Swift for an app, Tailwind v3/v4 for the respective framework, or SCSS/JSON for design tools. Import brand JSON to preserve semantic light/dark roles and 50–950 shades.
- Review and ship: copy or download the result, test it in your real website and check text/background contrast.
Alpha: input HEX8 uses RRGGBBAA, but Flutter/Android exports use AARRGGBB. If you import light/dark roles, select the correct group in your application; the generated code does not automatically follow device appearance.
Important: plain HEX values do not encode semantic text, background or button roles. Begin with Brand Color System if you need those roles. Exporting code does not automatically change a website or establish WCAG compliance.