Hex Lists or Swatches: How Should You Store a Color Palette?

A palette screenshot is easy to make and hard to use. It looks like the brand. It pastes as a bitmap. The next person still types the hex by hand, often wrong. A plain-text token list is ugly and paste-perfect. Official color styles / variables / Creative Cloud Library colors are the system of record. Windows clipboard history is a 25-item, 4 MB, text / HTML / bitmap scratch pad that forgets unpinned items at restart.

Use each layer on purpose.

Three layers of a palette

The picture is a communication aid. It is not a specification. Ten 64-pixel swatches in Win+V waste ten of twenty-five slots on bitmaps that cannot be searched for #0B6E4F.

How to Grab a Color Hex and Keep It is the single-value sibling. How to Hand Assets to a Developer Without Slack Soup is where the list should land.

Official homes for color

Figma. Color can live as fills, as color styles, and — on files that use them — as variables. Official component and library guidance: publish styles with the team library so other files consume them. Eyedropper samples fills on the canvas. Figma's eyedropper help notes that sampling outside the desktop app window is a macOS permission feature and is not currently supported on the Figma desktop app for Windows or in the browser. On Windows, pick from the file or type the hex. Do not invent a Windows-wide eyedropper inside Figma.

Adobe Creative Cloud Libraries. Adobe documents Libraries as a place to collect colors (and other assets) and reuse them across Photoshop, Illustrator, InDesign, and more. A library color is a swatch the suite understands. A PNG of a swatch is not.

Canva Brand Kit. Brand colors are first-class. A pasted bitmap of a palette is a decoration on a story.

CSS / design tokens in git. For engineering, this is the real record. The Figma file should match it, not replace it.

When those exist, stop screenshotting the palette into history.

The working list that pastes

Keep a palette.txt (or a fenced block in the ticket) like this:

# Acme product — 2026-08
color/bg/page        #F7F5F2
color/bg/elevated    #FFFFFF
color/text/primary   #1A1A1A
color/text/muted     #5C5C5C
color/cta/bg         #0B6E4F
color/cta/text       #FFFFFF
color/border/subtle  #E6E1DA
color/danger         #B42318

Why text wins:

• It pastes into CSS, JSON, and Slack without OCR
• Windows history can store it (text, well under 4 MB)
• It can be pinned for the week and deleted on Friday
• Diff tools can see a hex change; they cannot see a new PNG swatch
• Dark and light pairs can be two blocks in one file — How to Keep a Dark-Mode and Light-Mode Pair

Copy the block, not ten separate values, when the whole ramp is in play. Copy one line when a single token is needed. Win+V then shows readable text instead of ten brown squares.

Leave Automatically sync text that I copy off if the list includes an unreleased rebrand.

When a visual swatch is justified

Make a picture when:

• A stakeholder cannot read hex
• The meeting is about feeling, not tokens
• Print production needs a labeled chip next to a CMYK build (and even then the PDF is the deliverable)

Export one labeled strip from Figma or Illustrator as acme-palette-product.png and put it in the brand folder. Do not explode it into twelve clipboard bitmaps. Keeping Brand Assets Off the Desktop and On a Shelf.

For print, a screen hex is not a press color. Working With Print Shops: PDF First, Clipboard Never.

Photoshop and Affinity

Photoshop: the official copy/paste article is about selections, not about a color library. Foreground color copy is not a documented "copy hex to clipboard" feature in the same sense as Figma's hex field. Use the color picker value, type or copy the hex from the field if the build shows it, and store it in the text list. Creative Cloud Library colors are the Adobe-native reuse path.

Affinity: paste of a bitmap swatch creates pixels. Paste of text creates text. Use Paste Special on Windows if the wrong format wins. Affinity Photo and Designer on Windows: Paste Notes.

Neither app will turn ten screenshots into a maintainable ramp.

Contrast and accessibility are not clipboard jobs

WCAG contrast is math on pairs, not a pretty strip. Keep the pair in the text list (text/primary on bg/page) and check it in a contrast tool. A swatch PNG will not fail a pull request when someone lightens muted text.

Dark / light and 1× branding

If the product has two themes, keep two columns or two blocks in the same text file. Do not keep only the light strip in Win+V and hope someone remembers the dark hex. Visual pairs belong together as files when they are pictures. How to Keep a Dark-Mode and Light-Mode Pair.

Exporting marketing color bars at 1× and 2× is an image problem, not a token problem. Exporting @1x and @2x Without Losing the Pair.

A weekly habit

1. Tokens live in Figma variables or git
2. palette.txt is generated or copied from that source — never the other way around for long
3. Pin the text list in Win+V only during implementation week
4. One optional PNG strip in the brand folder for slides
5. Friday: unpin, clear history, do not leave the unreleased ramp on a shared PC

Best Clipboard Setup for Photoshop Users and Figma Desktop vs Figma Web: Paste Behavior Differs if the hex is bouncing between those apps.

A hover shelf can hold the palette.txt file and the strip PNG for drag-out. Edge-Drop is optional for that. It is not a design token manager. If the team already has Style Dictionary, Figma variables, or Creative Cloud Library colors, those beat any clipboard.

Worked example: shipping one new CTA color

1. Designers agree #0B6E4F in a Figma variable color/cta/bg
2. Add the same name to Creative Cloud Libraries if Photoshop ads use it
3. Append one line to palette.txt and commit it with the ticket
4. Copy that line into Win+V for the afternoon of CSS
5. Export one updated strip PNG into the brand folder for the next all-hands slide
6. Do not also pin ten old swatches

QA then greps the repo for #0B6E4F and the token name. Nobody OCRs a PNG.

Troubleshooting

Ten tiny images feel like a palette. A list is a palette that other software can paste. Keep the picture for the meeting. Keep the hexes as text. Keep the system in a library.

Windows limits for color work

A hex list is the rare palette object that fits Microsoft's history rules: it is text, it is tiny, and it can be pinned so it survives restart. Ten swatch PNGs fight the 25-item cap and the 4 MB cap and still cannot be grepped.

If someone copies a full-page palette poster from the brand PDF, the bitmap may never appear in Win+V. That is expected. Leave the poster in the brand folder. Brand Guidelines PDFs Do Not Belong in History.

Related reading

• Exporting @1x and @2x Without Losing the Pair
• Working With Print Shops: PDF First, Clipboard Never
• Best Clipboard Setup for Photoshop Users
• Best Clipboard Habits for Developers in 2026

Sources

• Using the clipboard (Microsoft Support) — text versus bitmap in history; 25 / 4 MB / restart.
• Creative Cloud libraries overview (Adobe) — official reusable colors across Adobe apps.
• Guide to components in Figma — libraries for reusable design attributes.
• Sample colors with the eyedropper tool (Figma) — Windows desktop/browser cannot sample outside the app; do not invent that feature.
• How to use clipboard history in Windows 11 (Microsoft) — pinning a text list, optional text sync.

Copy. Stack. Drop.

Transform your clipboard into an interactive edge shelf. Stack, pin, and drag assets into any app with zero friction.

Download for Windows Get from Microsoft Store

How to Install Guide · First 10 Minutes Guide · Drag & Drop Guide · Edge-Drop vs Win+V · Support