Turn brand swatches into checked interface colour roles
Give a small interface named colours, readable pairs and an exportable handoff instead of a loose row of swatches.
A small colour-role table, one annotated interface card and an exported colour file with a named revision.
Original FreeStack editorial workflow, checked 16 November 2026.
About this guide & its examples
The fictional studio card below illustrates colour roles, not a provider screenshot, tested accessibility result or customer project.
Illustrations are FreeStack concepts, not provider screenshots. Check the free limits below and test your own files before delivery.
Free boundaries before you start
What’s free, whether you need an account, and when we last checked.
Paleta · checked 2026-11-16
Free personal/commercial browser colour tools, no usage limit or signup. Proprietary software; outputs are yours under provider terms. Browser-local saved palettes have no account sync or server backup. Export files you need to keep; verify critical colour values.
No account or signup required.
Penpot · checked 2026-11-16
Ongoing $0 Professional cloud plan; core design tools, unlimited teams and no file-count cap within storage. Published free boundaries: eight members, 10GB storage and seven-day autosaved history/recovery. Paid governance and capacity separate.
Account required for hosted design files.
A small example to aim for
One swatch need not do every job.
Tell us what you need to make.
Send enquiryCheck: Add your project details.
Concept only. These colours carry no tested contrast-pass claim. Not a provider screenshot or customer result.
Illustrative example · adapt it to your project.
Jump to a step
Name the output before choosing colours
Make one fictional studio enquiry card: title, body, primary button, secondary link and error message. List surface, text, muted-text, action and error roles. Write what each does before selecting values; do not build a full design system for a one-card job.
Keep brand identity separate from readable use
Open Paleta and enter your authorised brand swatches. Assign the values to semantic roles in the token tool. A bright brand colour can remain an accent while a darker related tone carries small text. Keep the original swatches so the adaptation is explicit.
Check actual foreground and background pairs
In the contrast checker enter each intended text/background pair, not just adjacent swatches. Record the values, ratio and intended text size. Follow the linked checker guidance and independently verify critical values. Test button labels and error text as well as headings. Do not claim a complete accessibility pass from a colour-pair result.
Apply the roles to one card
In Penpot make a working card with your real-length sample copy. Apply the approved values consistently and label the error with words, not red alone. Show normal, focus and error states in separate frames where useful. Recheck if the background or text size changes; a previously passing pair may not represent the new state.
Export a small, reviewable handoff
From Paleta copy the chosen CSS or JSON output into a named file. Keep role names, values, check date and known limits in a short companion note. Compare the exported values with the card. Export a visual from Penpot separately and inspect it. This is a deliberate handoff, not a tested token-sync integration.
Save the kit and pay for a named need
Export Paleta work you want to retain outside the browser. Save this toolkit to keep Paleta and Penpot together in FreeStack. Editorial upgrade triggers: required cross-device history, governed permissions, a larger team or storage beyond the free boundary. Prove the small card first; a paid tool does not settle the role or readability decisions.
Your workflow, connected.
Follow the steps and carry the output into the next stage. These are suggested handoffs, not automatic integrations.
Provider information
Check current plans and documentation before committing to a workflow.
A couple of useful questions
Why name a colour by its job?
Surface, text and action describe intended use. A name such as blue-500 describes appearance but does not tell the next person whether to use it for body text or a background. Keep the approved value and its role together.
What is free?
Paleta explicitly permits personal and commercial projects with no signup or usage limit. Saved palettes are local to one browser; export a copy. Its software is proprietary, not open source. Penpot Professional is ongoing $0 with core design tools, unlimited teams and files within storage. Its published free boundaries include eight members, 10GB storage and seven-day history/recovery; paid governance and extra capacity are separate.
Do these tools automatically exchange tokens?
No automatic integration is claimed. Copy reviewed values deliberately and compare the result. Paleta offers several export formats; check the actual file and receiving tool rather than assuming every format imports directly.
Has FreeStack tested these colours?
No. The illustrated values are fictional and carry no contrast-pass claim. Perform and record your own pair checks. No external-tool hands-on test or accessibility audit was performed for this guide.
What would you try?
Share your result or ask a specific question about this workflow.
Join the conversation