Workspace Guide: Save Your Design Tokens Across Tools (2026)
Every design tool you use has a memory problem. You pick a color in one tool, move to another, and have to pick it again. You configure a font pairing in the typography tool, open the button generator, and it starts from defaults. The Workspace feature is the fix: a persistent set of design tokens (colors, fonts, spacing, shadows) that travels with you across every tool on UDT and is saved locally in your browser. This guide covers what Workspace does, why it's built the way it is, and how to make the most of it.
- My Workspace saves your colors, fonts, and design tokens locally and syncs them across every tool on the site.
- What Workspace Does.
- Covers getting started with workspace.
- When Workspace Earns Its Keep.
- What Workspace Doesn't Do.
What Workspace Does
Workspace is a lightweight token store. You save colors, fonts, spacing values, radii, shadows, and brand assets into it, and every compatible tool on the site can read from and write to it. Pick a primary color in the palette generator, open the button generator, and your primary color is the default. Choose a font pair in the typography tool, open the heading generator, those fonts are applied. Nothing has to be re-entered tool-to-tool.
The tokens live in your browser's local storage. They don't go to any server, they aren't tied to an account, and they persist across sessions on the same device. Open the site a week later and your workspace is still there. Clear your browser storage and it's gone — which is the intended behavior, not a bug. No cloud means no data risk, and no data risk means no privacy policy for workspace data.
Workspace is also exportable. Any saved token set can be downloaded as a JSON file you can share with teammates, commit to a repository, or import on another device. That sidesteps the "no cloud means no cross-device sync" limitation for anyone who wants one.
Getting Started with Workspace
Open the My Workspace tool. On first visit it's empty. Add tokens one of three ways: import from the AI Design Assistant (start with AI-generated tokens and refine them), import from a JSON file (if a teammate shared theirs), or add tokens manually by hand from any compatible tool.
-webkit-backdrop-filter alongside backdrop-filter for Safari support. Without the prefix, the effect is invisible to roughly 25% of mobile users.Most users start via the AI Design Assistant — generate tokens from a brand description, click "save to workspace," and your colors, fonts, and spacing are all instantly available in every compatible tool. From there, refine individual tokens as needed. The Design System Builder is the best place to edit saved tokens in a structured way, preview changes against a live component set, and export to production-ready CSS or Tailwind config.
Once tokens are saved, they auto-populate in every compatible tool. The gradient builder, button generator, shadow generator, typography scale, and most other design tools will use your workspace tokens as defaults. You can override them per tool if needed — workspace is a set of defaults, not a lock.
When Workspace Earns Its Keep
Building a brand from scratch. Start with the AI Design Assistant, save the output to workspace, then iterate through the component generators (buttons, cards, forms, headings) and see every component styled consistently with your brand. Without workspace, you'd be manually matching colors and fonts tool by tool.
backdrop-filter inside a position: fixed element can cause severe scroll performance issues. Test thoroughly on real iOS devices.Matching an existing brand. You have a brand you're designing for — copy the brand's primary color, accent, and font pairing into workspace, and every tool reflects the brand when you use it. Generate a palette variation, design a new component, prototype a new section, all consistently themed without reconfiguring per-tool.
Teaching or handoff. Hand someone a workspace JSON and they can design in context — open any tool and see the client's brand, not the site's defaults. This is especially useful when walking juniors through how the tools work against real brand constraints rather than blank slates.
Multi-brand workflows. Save different workspaces for different clients or projects (export each as JSON). Swap by re-importing when context changes. Less elegant than account-based multi-brand support would be, but no-cloud means the trade-off is worth it for most users.
What Workspace Doesn't Do
No cloud sync. If you want your workspace on your phone and laptop, you have to export and import manually. For most solo users this is fine; for teams, the export-to-JSON-and-share model works but adds friction compared to auto-sync platforms.
No history. Workspace holds your current tokens; it doesn't track changes over time. If you want version history for design tokens, export snapshots periodically or commit the JSON to Git. The tool itself stays simple because simplicity is the feature.
No team permissions. Since there are no accounts, there's no "read-only for juniors" or "lock these tokens" capability. A shared workspace JSON is a shared starting point, not a shared live document. Teams that need collaborative live editing should use a dedicated design token platform (Tokens Studio, Specify, etc.) alongside UDT rather than as a replacement for those tools.