I just added CSS export to OKLCH Pixel Palette and ran into a subtle compatibility detail worth sharing.
A custom property accepts almost any token sequence. That means this declaration can be stored even when the browser cannot render OKLCH:
--brand: oklch(62% 0.18 265);
The failure happens later when var(--brand) is used as a color, so putting a HEX declaration immediately before it is not a dependable fallback. The exported file now writes HEX custom properties first, then overrides them inside @supports (color: oklch(50% 0 0)).
Shipped a new CSS workflow today. Export now downloads a ready-to-use .css file with HEX custom properties first, then native OKLCH overrides inside @supports. That avoids the subtle fallback problem you get when an unsupported color function is stored directly in a custom property.
The generator is still free and browser-local, with 2–9 colors, six harmony modes, sRGB gamut fitting, lightness inspection, sprite previews, and PAL/GPL/HEX/JSON/TXT/PNG exports. I would especially value feedback from pixel artists and design-system developers about the next format to support.