You set a custom background color on a Notion database view, but after switching your workspace theme from light to dark or vice versa, the color resets to the default. This happens because Notion applies a theme-specific color mapping that overrides user-selected view colors. The workspace theme change triggers a refresh of the interface color palette, which can discard custom view colors that are not locked to a specific theme. This article explains the root cause of this behavior and provides steps to prevent your database view colors from resetting when you change the workspace theme.
Key Takeaways: Preventing Database View Color Reset
- View customization > Background color: The color you pick is tied to the current theme; switching themes may discard it.
- Notion theme engine: Light and dark themes use separate color tables; view colors are not automatically migrated.
- Reapply color after theme change: Manually set the view background color again to restore your preferred appearance.
Why Changing the Workspace Theme Resets Database View Colors
Notion uses a theme engine that stores two separate sets of color values for the workspace interface: one for light mode and one for dark mode. When you change the workspace theme, Notion reloads the color palette for the entire interface. Database view background colors are stored as part of the view configuration, but they are not automatically mapped to the corresponding color in the new theme. Instead, Notion reverts the view background to the default color for that theme.
The technical root cause is that view background colors are saved as a single hex value or a named color reference. When the theme switches, the color reference may point to a color that does not exist in the new theme’s palette, or the hex value is replaced with the default. Notion does not maintain a separate color mapping for each theme per view. This means any custom background color you set on a database view is lost when you toggle themes.
This behavior affects all database view types: table, board, gallery, list, calendar, and timeline. The color reset applies only to the view background, not to property colors or status colors. Property colors such as red, blue, green, and yellow are theme-aware and change appearance automatically. Only the view-level background color resets because it is not part of the theme-aware color system.
Steps to Restore and Lock Database View Colors After a Theme Change
Follow these steps to reapply the background color to a database view after changing the workspace theme. You must repeat this for each view that had a custom color.
- Open the database view
Navigate to the page that contains the database. Click the view tab at the top of the database that lost its color. - Click the view name dropdown
Click the name of the view (for example, “Table View” or “Board View”) at the top-left of the database. A menu with view options appears. - Select Customize view
From the dropdown menu, choose the option labeled Customize view. This opens the view customization panel on the right side of the screen. - Set the Background color
In the customization panel, scroll to the Background color section. Click the color swatch to open the color picker. Select the color you want. The view background updates immediately. - Repeat for each affected view
If your database has multiple views, switch to each view tab and repeat steps 2 through 4. Each view stores its own background color setting. - Consider using property colors instead
If you frequently switch themes, use property-level colors for status, tags, or select fields instead of view background colors. Property colors automatically adapt to both light and dark themes without resetting.
If Notion Still Resets Colors After the Main Fix
Theme change resets color again after reapplying
If you change the workspace theme a second time, the view background color will reset again. This is by design. Notion does not offer a way to lock a view background color across themes. The only workaround is to reapply the color each time you switch themes. To avoid this, choose one theme and stick with it, or use property colors that are theme-aware.
Color picker shows limited options after theme change
After switching to dark mode, the color picker may display fewer swatches or different default colors. This is because Notion adjusts the color palette to match the theme. You can still select any color from the full spectrum by clicking the custom color option (the rainbow icon) at the bottom of the color picker. The custom color you pick will be applied to the view, but it will reset again if you change themes.
View background color is not visible on some devices
If you apply a custom background color but it does not appear on mobile or tablet, this is a known limitation. Notion mobile apps do not render database view background colors. The color is stored and visible only on desktop and web versions. Changing the theme on mobile will not affect the view color on desktop, but the color may still reset if you change the theme from the desktop app.
Notion Workspace Theme Change vs View Color Reset: Behavior Comparison
| Item | Light Theme | Dark Theme |
|---|---|---|
| View background color persistence after theme switch | Resets to default white | Resets to default dark gray |
| Property color (red, blue, green, etc.) behavior | Adapts automatically | Adapts automatically |
| Color picker swatches | Light palette shown | Dark palette shown |
| Custom hex color support | Yes, but resets on theme change | Yes, but resets on theme change |
| Mobile view color rendering | Not supported | Not supported |
You can now reapply database view background colors after a workspace theme change and understand why the reset occurs. To avoid repeating this task, use property colors that automatically adapt to both themes. For a permanent solution, consider locking your workspace to one theme. An advanced tip is to create a duplicate view for each theme: one with a light background and one with a dark background, then switch between them manually when you change themes.