A reproducible color-palette record contains the input HEX, the selected harmony scheme, every output swatch in HEX, RGB, and HSL, and the application context.
That definition makes the record useful to another designer, developer, or project stakeholder. It shows how the palette was generated, preserves the exact output values, and explains where the colors are intended to be used. A phrase such as “the blue palette” is not enough because it leaves the base value, color relationships, and final assignments unclear.
Use the Color Palette Generator to choose a base with the color picker or type a HEX value, select one supported scheme, and then read or copy the results. The documented copy action places one swatch's HEX on the clipboard, while RGB and HSL are displayed for reading. Do not treat that click as a palette file or an activity log: keep the documentation in your own project record.

Capture the inputs that determine the palette
Begin with the two controls that determine the generated set: the base color and the selected scheme. Record the base as an exact HEX value, including the number sign, whether you chose it with the picker or typed it. If the starting color came from a brand guideline, an existing component, or another source, add that source to your notes. It gives future readers important context without changing the input you supplied to the generator.
| Scheme | Defined color relationship | Typical use |
|---|---|---|
| Complementary | Hue rotated 180° | Strong, high-contrast pair or call-to-action accent |
| Analogous | Hues shifted ±30° | Calm, cohesive combinations |
| Triadic | Three hues 120° apart | Balanced, vibrant sets |
| Tetradic | Four points 90° apart | Varied two-pair schemes |
| Split-complementary | Two hues 30° either side of the direct complement | Contrast with less tension than a direct pairing |
| Monochromatic | One hue with stepped lightness | Tonal scales, shadows, borders, hover states, and depth |
These six choices implement familiar color theory relationships, but your record needs the exact scheme name selected in the tool. Write “triadic” rather than “three-color scheme,” and write “split-complementary” rather than “soft colors.” The base and scheme determine the generated relationships, so they are the essential starting point for reproducing the work.
Document the generator actions in order
- Set the application context. Name the project, screen, component, or asset where the palette will be used. For example, record “checkout page” or “brand guide,” not merely “web design.” This tells a later reader what the palette must accomplish and which decisions still need to be made.
- Choose and record the base color. Use the color picker or enter a HEX value such as #3b82f6. Write the final base HEX in the record exactly as shown. If it came from a brand token or another approved source, note that source separately.
- Select the scheme and record its name. Choose complementary, analogous, triadic, tetradic, split-complementary, or monochromatic. Include the exact name because changing the scheme changes the relationships even when the base HEX remains unchanged.
- Label and transcribe every output swatch. Give the visible swatches temporary IDs such as A, B, and C. For each swatch, record its HEX, RGB, and HSL values as displayed. Keeping the three representations separate prevents a copied code from being mistaken for the complete specification.
- Use the clipboard without treating it as the record. Click a swatch when you need its HEX on the clipboard. The verified action copies an individual swatch's HEX only; RGB and HSL are for reading, and no all-format or scheme-history copy is documented. Place those values into your own notes.
- Assign purpose labels yourself. Decide which swatch is the primary color, accent, background, text color, border, hover state, or another role. The generator produces a color set from the base; it does not determine how those colors should function in a page, component, or brand system.
- Write the reasoning and destination. Add a short explanation of why the base and scheme fit the application. Then record where the final values will live, such as CSS variables, design-tool styles, or a brand guide. The same color can have a different purpose in another project.
- Validate and finalize. Test the values in their intended application, run text and background pairs through a WCAG contrast check, and record the result. If a color changes, update the recorded values. Finally, paste the copied HEX into the target stylesheet or design file and compare it with the documented value.
Build a reusable palette record
A practical record separates generation facts from design decisions. The first group explains what the tool produced; the second explains what you decided to do with it. This separation makes the document easier to audit and prevents an assumed purpose from being mistaken for an automatic generator label.
- Application: Project, screen, component, or asset receiving the palette
- Record details: Owner, date, and design or documentation version
- Tool: Name of the generator used for the palette
- Base input: Exact HEX entered or selected
- Scheme: Exact name of the selected harmony relationship
- Outputs: Swatch ID, HEX, RGB, HSL, and assigned role for every color
- Rationale: Why the base, scheme, and roles fit the application
- Validation: Contrast-check results and the final implementation location
For example, a checkout-page record might start with the base #3b82f6 and the triadic scheme. A corresponding swatch entry could read: “Swatch A — HEX [copied value], RGB [shown value], HSL [shown value], role: page background.” Replace each bracketed field with the actual value from the generator. Do not guess RGB or HSL values or fill them with unverified conversions.
The generator runs entirely in your browser, and nothing is uploaded, stored, or sent to a server. Keep the notes in your project file or design documentation as the durable record.
Choose the format that fits each handoff
Record all three formats when collaborators need more than a copy-ready color code. Each representation supports a different kind of review while describing the same generated color.
| Format | Information shown | Best documentation use |
|---|---|---|
| HEX | Hexadecimal color value | Primary value to paste into CSS or a design tool |
| RGB | Red, green, and blue channel values | Handoff where a tool or specification expects RGB |
| HSL | Hue, saturation, and lightness values | Reviewing hue relationships or fine-tuning saturation and lightness |
HEX and RGB can be used directly in CSS or design applications such as Figma, while HSL makes manual adjustments to saturation and lightness easier. Keeping the values together also lets another person compare formats without regenerating the palette. For implementation handoff, the guide on dropping Palette Generator colors straight into CSS or Figma explains how copied colors move into working files.
Keep purpose and accessibility checks in the record
Do not assume that the base color must become the primary design token or that any particular swatch is suitable as text or a background. Those are design decisions. Record the intended role for each color, including any distinctions among a default state, hover state, border, surface, or text color. If you generate a monochromatic palette for shadows and borders, for example, label those roles separately rather than listing the colors without purpose.
Color harmony and accessible contrast answer different questions. A harmonious palette is not automatically readable, so check every important text and background pair with the Color Contrast Checker and assess the result against WCAG guidance. In the record, include the foreground color, background color, result, and any replacement values. If a replacement changes the final palette, revisit the associated HEX, RGB, and HSL entries before sign-off.
Version the record before final handoff
Create a new version or dated revision whenever the base color, selected scheme, swatch values, or color roles change. Keep the previous version when a design decision is reversed, and note what changed. Do not overwrite earlier values without recording the revision, because the latest screenshot or stylesheet may no longer represent the original generation process.
- Base HEX is present and matches the final input
- Scheme name is exact and recorded
- Every final swatch has HEX, RGB, HSL, and a stable ID
- Each color has a documented design role
- Implementation location is identified
- Text and background contrast results are recorded
- Date and version identify the final state
The documentation is complete when another person can identify the original input, understand the selected color relationship, recover every output value, and find where the palette is used without needing to reconstruct the process from memory.
Related reading: How to Fix a Color Palette That Looks Wrong.