> For the complete documentation index, see [llms.txt](https://fluid-crm.gitbook.io/fluid-crm-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fluid-crm.gitbook.io/fluid-crm-docs/features/themes.md).

# Themes

Themes are purely visual. Changing the theme does not affect data, workflows, performance or features. They exist to make Fluid feel comfortable for the way you work.

### The nine themes

All nine themes use dark tones. Themes set the color palette you work in. A full dark mode across every screen is a separate feature and it is on the roadmap.

* **Graphite**: Pure dark grey for focus
* **Obsidian**: Near-black, maximum contrast
* **Midnight**: Deep blue, easy on the eyes
* **Ocean**: Lighter blue with a calmer feel
* **Forest**: Dark green, nature-inspired
* **Moss**: Muted olive, softer than Forest
* **Sunset**: Warm orange and brown tones
* **Merlot**: Deep red, warm and low glare
* **Amethyst**: Dark purple with a creative feel

You can switch between any of them at any time. The change applies instantly across the entire app.

### When to change themes

Different themes suit different situations.

* **For long work sessions or low-light environments**: any of the dark themes work well, with Graphite being the most neutral
* **For higher contrast and focus**: Graphite or Midnight
* **For softer visual fatigue reduction**: Forest, Sunset or Amethyst
* **For matching your personal aesthetic**: pick whatever feels right

There is no recommended default. Choose what feels best for your daily workflow.

### How to change your theme

To switch themes:

* Go to Settings
* Open the Themes and appearance section
* Click the theme you want
* The change applies immediately

You can switch as often as you want. Some users prefer different themes for different times of day or different work modes.

### What themes affect

Theme settings control:

* Background colors across all pages
* Surface and panel styling
* Accent colors for buttons, links and highlights
* Color of stage cards on the Deals board
* Reminder badge colors (red, green, gray stay consistent across themes)

Themes do not change:

* Layout or page structure
* Feature availability
* Keyboard shortcuts
* Deal, contact or pipeline behavior
* Data or workflows

### Themes are per-user

Themes are selected per user account. Your theme choice:

* Only affects your own view
* Does not change what teammates see
* Does not affect workspace settings
* Syncs across devices when you log into the same account

Each teammate can pick their own preferred theme without affecting anyone else.

### What themes are not

Themes are not:<br>

* A dark mode. Themes set colors. Full dark mode across the app is on the roadmap
* Shared workspace settings

If you need a specific color match for client-facing work or screenshots, the closest match is to pick the theme whose accent color is closest to your brand.

### Why themes matter

Most CRMs offer one default theme, usually a generic light mode that strains your eyes during long work sessions. Some offer a dark mode toggle but no real variety.

Fluid includes nine dark-toned themes because the CRM is where you spend hours every day. The right one matches your environment and makes daily work feel less draining.

It is not the most important feature. But over thousands of hours of CRM use, it adds up.

### What to read next

* Customize deal cards, control which fields show up on cards regardless of theme
* Keyboard shortcuts, the navigation that works the same across all themes
* Dashboard, see how the home screen looks in your selected theme


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://fluid-crm.gitbook.io/fluid-crm-docs/features/themes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.