Saving & Projects

Docs

Getting Started

Overview Your Control Color Understanding Families

Generating Colors

Scale Generation Role System Neutral Engine

Using Your Palette

Exporting Accessibility

Palette Workflow

Saving & Projects

Save your palettes to work on them later, organize multiple projects, and build a library of color systems.

What Saved Palettes Are

WebShades saves palettes locally in your browser's storage. This means:

Your palettes are stored on your device
No account required for basic saving (free tier)
Palettes persist across browser sessions
Each palette includes all settings, colors, and metadata

Save

Saves the current palette, overwriting the existing saved version if one exists. Use this when you've made changes to an existing palette.

Save as New

Creates a new palette entry without overwriting the current one. Use this to create variations or experiment with different settings.

Rename

Changes the name of a saved palette. Useful for organizing and identifying palettes later.

Delete

Permanently removes a saved palette. This action cannot be undone, so use with caution.

How Project Switching Works

The project picker lets you organize palettes into projects or categories. Think of projects as folders for your color systems.

Common use cases:

Separate palettes for different clients or brands
Organize by product or application
Group experimental palettes separately from production ones
Create project-specific color systems

When you switch projects:

The palette list updates to show only palettes in that project
You can create new palettes within the selected project
The current palette (if any) remains loaded until you select a different one

When you select a saved palette, all settings (control color, contrast, saturation, etc.) are restored, and the color scales and semantic roles are regenerated with those settings. Your current unsaved work is preserved when switching projects, so you won't lose any changes.

Accessibility