Visualize Notion Databases with Conditional Colors | Full Guide & Tutorial

Notion’s new conditional colors let database cards change color automatically based on property values—turning dense tables into at-a-glance dashboards for overdue items, progress states, and numeric “heat map” trends. The tutorial walks through how to set them up: create a database (e.g., tasks), add properties like Due date and Status, then open the database’s settings and add “Conditional color” rules. A common first rule is date-based urgency: if Due date is before today, cards turn red; tasks with no due date or due dates in the future stay uncolored (or default). The payoff is immediate visual triage—especially for users who want to spot overdue work without scanning dates.

From there, the guide shows how to refine date logic into multiple urgency bands. For client projects, one conditional color rule marks deadlines that are before today as red (overdue), while another marks deadlines relative to today—specifically “next week”—as orange. Projects with deadlines further out remain white, creating a simple gradient of urgency that helps people prioritize what needs attention now versus what can wait.

Conditional colors also work for categorical properties. Instead of coloring by dates, the tutorial demonstrates switching the rule to Status (e.g., In progress becomes blue and Done becomes green). It then extends the same idea to categories/tags: when conditional coloring is set to Tag, the card background can match the color already assigned to each tag option, making a task board visually encode what kind of work each card represents (new feature, bug fix, documentation) without relying on small tag pills.

A third major use case is numeric ranges for “heat map”-style tracking. Using a sleep tracker example, the guide sets conditional colors on a number property (hours slept). If hours are greater than or equal to 8, cards turn green; if hours are less than or equal to 5, they turn red; and intermediate thresholds (like 6) map to orange. With multiple range rules, the database becomes a month-long visual summary of performance—highlighting good days versus poor ones. The same approach can apply to other metrics such as reading minutes per day.

Two limitations are called out. First, conditional colors can’t be applied to formula properties, even if a formula returns a number—so habit-tracker-style computed counts can’t be color-coded the way raw numeric fields can. Second, rules are evaluated top-to-bottom, meaning they can’t express complex combined conditions (an “AND” across multiple properties). If a card matches the first applicable rule, later rules won’t be considered, which restricts advanced logic like “hours >= 8 AND date equals X.” Overall, conditional colors are positioned as a practical way to make Notion databases more readable and actionable, with clear constraints around formulas and multi-condition logic.