> For the complete documentation index, see [llms.txt](https://help.usejimo.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usejimo.com/docs/build/theme.md).

# Theme

What a theme applies to an experience, what it overwrites, and in which order themes and builder styling take effect.

A theme is a saved set of colours, fonts and spacing that you apply to experiences so they all look like your product. Applying a theme rewrites the look of the whole experience, so knowing what it overwrites saves you from losing styling you did by hand.

## Create a theme

You create and manage your themes in [Settings > Themes](https://i.usejimo.com/settings/themes). Click **New Theme**, name the theme, then set every property of every element your experiences use.

{% hint style="info" %}
You can also [save a theme on the fly](#use-a-theme-in-the-builder) from any experience, from its builder.
{% endhint %}

### Theme dashboard

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2Fuif7tCQJRiY0pmORCtQf%2FC-s04b-themes-dashboard.png?alt=media&amp;token=71c8a906-4a22-4eb8-9364-a60b1ac3bdd3" alt="Settings, Themes, with four markers: A on the New Theme button, B on the theme cards, C on the menu of a card open on Edit, Duplicate, Make default and Delete, D on the Smart Theme button"><figcaption></figcaption></figure>

* **A (New Theme)**: opens the theme editor on a new theme. Name it and define its design, so your experiences look the same across your product.
* **B (Theme overview)**: every theme you have, as a card with its main colours and fonts, so you can tell them apart at a glance. The theme with the **Default** badge is the one every new experience starts in, whether you create it in the dashboard or through an AI assistant.
* **C (Theme menu)**: the menu of each card lets you:
  * **Edit** the theme in the [theme editor](#theme-editor).
  * **Duplicate** it to start a variant.
  * **Make default**, so every new experience starts in it.
  * **Delete** a theme you no longer need.
* **D (Smart Theme)**: generates a theme from the colours of a website, to match your product or your brand in a few seconds. See [Smart theme](#smart-theme).

{% hint style="warning" %}
**Editing a theme does not update the experiences that already use it.** An experience keeps the styles written on it when the theme was applied. To bring your changes to an experience, apply the theme again from its builder.
{% endhint %}

### Theme editor

The theme editor sets the visual standard that you then apply to any experience. Here is how it is laid out:

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2Fg0WcAZBEsJCDZ5L7KDdm%2FC-s07b-theme-editor.png?alt=media&amp;token=efa4125e-4959-463d-a904-387d47540079" alt="Theme editor of the Purple Theme with five markers: A on the back arrow and the name, B on the list of elements, C on the open Step settings, D on the Preview dropdown set to Hotspot, E on the live preview"><figcaption></figcaption></figure>

* **A (Back and theme name)**: go back to the list of themes, or rename the theme. Pick a clear, descriptive name: it is how you find the theme in the builder.
* **B (Element list)**: every element a theme styles, in the order of the experiences that use them:
  * Step, Dismiss, Cursor and Hotspot.
  * Text and buttons: Heading, Paragraph, Label, Image/Video, Primary CTA, Secondary CTA and Stepper.
  * Survey blocks: Multiple Choice, Slider, NPS, Opinion Scale, Open Question and Concept Test.
  * Checklist: its base, header, progress, tasks and buttons.
  * Resource Center: its base, header, Launch Agent and Send message CTAs, groups, actions, embedded checklist and trigger.
* **C (Element settings)**: open an element to set its colours, border, radius, padding, gap, shadow and overlay. This is where you match the theme to your brand.
* **D (Preview type)**: pick the type of experience to preview, for example a hotspot, a tooltip or a modal, to see each element in its context.
* **E (Live preview)**: shows the theme as you change it, so you can check it before you apply it anywhere.

### Smart theme

A smart theme is generated from the colours of an existing website, for example your marketing site. Click **Smart Theme**, name the theme, give the website in **Generate theme from**, then **Create theme**.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FSB8dp8nkARp2CtedgHDr%2FC-s05-smart-theme-dialog.png?alt=media&amp;token=bfe6e3d2-633d-460a-94ab-3d3391f45eb6" alt="Generate a smart theme dialog: Name set to Brand theme, Generate theme from set to https://b2b.usejimo.com, and the Cancel and Create theme buttons"><figcaption></figcaption></figure>

The theme is generated and added to your list. It works like any other theme: open it with **Edit** to adjust it.

{% hint style="warning" %}
**The Smart Theme only works with public websites.** If the address is a private page or a page with restricted access, the theme may not generate properly.
{% endhint %}

## Use a theme in the builder

To apply a theme to an experience, open its builder and click the **Theme** icon (the brush) in the side menu.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FaVisPudKQyyGsjrSvIue%2FC-s08-builder-theme-panel.png?alt=media&amp;token=09e0d5b7-3b69-444f-aba7-13793282050d" alt="Builder of a modal with the Theme panel open, with two markers: A on Save as new theme, B on the list of saved themes, next to the modal in the canvas"><figcaption></figcaption></figure>

* **A (Save as new theme)**: once an experience looks the way you want, save its design as a new theme, to reuse it on other experiences.
* **B (Your themes)**: every saved theme, with its colours and fonts. Click one to see it on the experience.

Click the theme you want: the design of the experience changes to match its settings.

{% hint style="warning" %}
**It is only a preview.** Apply the theme to save it: it then applies to every step of the experience.
{% endhint %}

After you change the design of an experience by hand, a pop-up offers to update the theme with these changes, or to apply them to all steps.

The builder panel does not generate smart themes: create them from [Settings > Themes](#smart-theme), then apply them here.

## What applying a theme changes

Applying a theme writes its colours, fonts and spacing onto the experience, onto every step and onto every block. It is not a layer on top: the styles are copied into the experience.

{% hint style="warning" %}
**Applying a theme replaces the styling you set in the builder.** Colours, fonts or spacing you changed by hand on that experience are overwritten, on every step. This is true whether you apply the theme in the builder or ask an AI assistant to do it.
{% endhint %}

#### Every step, never one

A theme always applies to the whole experience. You cannot apply a theme to one step only. To style a single step differently, apply the theme first, then change that step in the builder.

#### Position is separate

Where an experience appears on screen (a corner for a snippet or a checklist, a side for a Resource Center, the placement of a tooltip around its element) is not part of the theme. A modal is always centered. See [Positioning](https://help.usejimo.com/docs/build/positioning.md).

## Order of priority

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2F9EO4Ha30UJFpL0ZxnwAb%2FC-01-theme-priority.png?alt=media" alt="Four stages in order: the default theme at creation, a theme applied on every step, builder edits on one element, then a theme applied again on every step. Dashed arrows show that each theme application overwrites what came before it, so the last write wins."><figcaption></figcaption></figure>

What your users see is the last style written on the experience:

| Order                  | What happens                                           | What it overwrites                        |
| ---------------------- | ------------------------------------------------------ | ----------------------------------------- |
| 1. Creation            | The experience starts in the default theme             | Nothing                                   |
| 2. Apply a theme       | The theme's styles are written on every step and block | The default theme and any builder styling |
| 3. Edit in the builder | Your change applies to that element only               | The theme, for that element               |
| 4. Apply a theme again | The theme is written again on every step and block     | Every builder change from step 3          |

The practical rule: **choose the theme first, fine-tune in the builder last.** If you need to switch theme on an experience you already styled by hand, expect to redo those touches.

## When to use what

| You want to                                    | Do this                                             |
| ---------------------------------------------- | --------------------------------------------------- |
| Every new experience to look like your product | **Make default** on that theme in Settings > Themes |
| Bring a theme change to existing experiences   | Apply the theme again from each builder             |
| Match your brand quickly                       | Generate a smart theme from your public website     |
| Reuse a design you built on one experience     | Save it as a new theme from the builder             |
| One step to stand out (an intro, a warning)    | Keep the theme, change that step in the builder     |
| Switch a styled experience to another theme    | Apply it, then redo your builder touches            |

## From your assistant

With the [Jimo MCP](https://help.usejimo.com/docs/integrations/mcp.md) connected, an AI assistant can list your themes and apply one:

> Apply the "Purple Theme" to the tour "Onboarding" and show me what changes before you save.

On a live experience, or on a draft someone already edited in the dashboard, the assistant shows you a preview first, with a warning that builder styling will be replaced, and waits for your confirmation. Once confirmed on a live experience, your users see the new look within minutes. If the experience already uses that theme, nothing is written. More prompts in [What to ask](https://help.usejimo.com/docs/integrations/mcp/what-to-ask.md).

## Verify

Open the experience in [Preview](https://help.usejimo.com/docs/build/preview.md) and go through every step: colours, fonts and buttons should match the theme, and the steps you fine-tuned by hand should still carry your changes.

## Go further

* [Positioning](https://help.usejimo.com/docs/build/positioning.md): where each experience appears, which a theme does not change.
* [Preview](https://help.usejimo.com/docs/build/preview.md): check the look before you publish.
* [Jimo MCP](https://help.usejimo.com/docs/integrations/mcp.md): manage themes and appearance from an AI assistant.

**Next page:** [Multiple Languages](https://help.usejimo.com/docs/build/multiple-languages.md)
