A Google Calendar color coding system you can still read at a glance a month later

Color coding a calendar is easy to start and easy to ruin. The first version has four colors and a clear meaning for each. Three months later there are eleven colors, two of them mean something nobody remembers, and the week reads as a pile of confetti. The scheme stopped being useful the moment it stopped being readable at a glance, which was long before anyone noticed.

A scheme that lasts is built around two decisions: what the colors are for, and where the color lives. Everything else, including the exact shades, follows from those.

Decide what the colors answer

A color is a one-bit question answered without reading. Before assigning anything, settle which question the week should answer from across the room.

The question	What the colors should separate	Typical scheme size
Whose time is this?	Work, personal, family, a client	3 to 5
What kind of work is this?	Deep work, meetings, admin, travel	3 to 4
How firm is this?	Confirmed, tentative, optional	3
Where does this happen?	Office, home, on site	3

Choosing more than one of these at the same time is the usual failure. A calendar that tries to encode both the client and the type of work needs a dozen colors, and a dozen colors is a legend, not a glance.

Choose where the color lives: the calendar or the event

Google offers two places to set color, and they behave differently.

A calendar's color applies to everything on that calendar and is set from the calendar list on the left, through the options next to the calendar's name. Google's page on creating a new calendar describes the same menu, which also offers Add custom color when the preset palette is not enough. The strength is that it is automatic: once a calendar has a color, nothing has to be remembered per event.

An event's color overrides the calendar color for that one entry, set when editing the event. The strength is precision. The weakness is that it depends on someone choosing it every time, which is exactly the habit that lapses in a busy week.

The durable pattern is to let calendars carry the scheme and reserve event colors for a single, rare exception. For example: every calendar has its color, and one event color, used sparingly, means this cannot move. Two systems, each with a job, and neither requiring a decision on every event.

When a separate calendar beats an event color

If a category needs to be hidden, shared, or counted separately, it deserves its own calendar rather than a color. Calendars can be shown and hidden with a checkbox, shared with different people, and subscribed to individually. A color can do none of that. Travel, a side project, or a partner's schedule are all better as calendars.

There is a practical limit to remember before creating a calendar per client. Google's page on subscribing to calendars notes that subscribing to more than 400 calendars can cause performance issues when browsing calendars. Few people approach that, but teams that create a calendar for every project do.

Make the scheme readable, not decorative

A scheme is readable when the colors differ in more than hue.

Use light and dark, not just color. Two mid-tone colors of similar brightness read as one blur in Month view, especially on a laptop screen in daylight. Pairing a dark color with a pale one for the two categories that matter most does more for legibility than picking prettier hues.

Do not rely on red and green together. Color vision deficiency is common enough that a scheme built on that contrast will fail for some of the people a shared calendar is meant to serve. Blue against orange, or dark against pale, survives.

Limit the scheme to what fits in working memory. Three colors are read instantly. Five require a moment. Eight require a legend, and a legend that has to be recalled is not a glance.

Keep one color meaning nothing. A neutral default for ordinary events makes the coded ones stand out. When every event is colored, none of them are.

The settings that change how colors look

Google has two appearance settings that affect legibility more than the palette does. The event color set and density page describes both, available only on a computer. The color set offers Modern with white text or Classic with black text, and Google notes that the background must be set to Light to change it. Density offers Responsive, which scales events up to fill larger monitors, Comfortable, which keeps standard spacing regardless of screen size, and Compact, which shows more events at once with tighter spacing.

Anyone finding that a scheme is hard to read should try Classic with black text before repainting every calendar. Dark text on pale blocks stays legible at small sizes in a way that white text on mid-tones does not.

What color does not do

Two limits are worth knowing before any effort goes into a scheme.

Colors are not a report. A week that looks balanced by color may not be. For anything that needs counting rather than glancing, Google offers labels: up to 200 labels can be created and assigned to calendar entries on a work or school account, then tracked in Time Insights. Labels answer how many hours, colors answer what kind of day this is. Trying to make color do the counting is what pushes a scheme past readability.

Colors do not travel everywhere. A scheme is tied to Google Calendar's own notion of color, and other applications map it in their own way or not at all. Microsoft's known issues list states that Categories are not supported for Google accounts in Outlook for Mac, which means Outlook's category colors and a Google color scheme are separate systems that will not agree. Anyone maintaining a scheme across two applications should check that the colors survive before building habits on them. On a Mac calendar that syncs with Google, the thing to verify is whether calendar and event colors carry over exactly or get approximated, because an approximated palette quietly destroys the distinctions the scheme was built on. The compare page sets out how different desktop calendars handle that.

Four schemes that work, with their trade-offs

Rather than inventing a scheme, it is usually faster to take one that fits the week and adjust it.

Whose time is this. Work in a dark blue, personal in a warm pale tone, family or household in a mid green, and one client or project in something distinct. This is the scheme for anyone whose main risk is booking over a personal commitment. It reads correctly on a phone and it needs no maintenance, because each category is already a separate calendar. The trade-off is that it says nothing about the kind of work inside the blue.

What kind of work is this. Meetings in one color, focused work in another, admin in a pale neutral, travel in something loud. This is the scheme that supports a decision, because a month that is mostly meeting-colored is an argument for changing something. The cost is that it has to be applied per event unless separate calendars are created for the categories, which many people find heavy.

How firm is this. Confirmed in a strong color, tentative in a pale one, and optional in the neutral default. Useful for anyone whose week regularly gets rearranged, and it makes the moveable slots obvious when a conflict arrives. The weakness is that the state changes, so events have to be recolored as things firm up.

Where does this happen. Office, home, and on site. Worth it for anyone who splits days across locations, because the travel cost of a badly ordered day becomes visible in the grid. It matters less for anyone working from one place.

Mixing two of these in one calendar is what produces a twelve-color mess. If two questions genuinely both need answering, the second one belongs in labels or in separate calendars, not in more colors.

A scheme that survives three months

Two rules keep a scheme alive.

Add a color only by removing one. A fixed number of colors, decided once, forces each new category to justify itself against an existing one. Schemes die by accretion, not by bad initial choices.

Write the legend down somewhere the calendar can show it. A recurring all-day event once a month, titled with the legend, is enough. It costs nothing and it settles the argument about what orange meant.

Decide what happens to shared calendars. A color set on a calendar someone else owns applies to the view, not to the calendar itself, so teammates see their own colors. That is fine, until a team tries to agree on a scheme and discovers each person has to set it separately. Where a shared scheme matters, agree it in writing and let each person apply it once.

Reviewing what the colors show

The review is quick. Open Month view, stand back from the screen, and ask what the month looks like. If the answer is a clear impression, the scheme is working. If the answer requires reading titles, the scheme has too many colors or too little contrast, and the fix is to remove a category rather than to adjust a shade.

It is also worth checking the scheme on a phone, where blocks are smaller and colors are the only signal that survives. A distinction that disappears at that size is not doing any work.

The part that actually takes time

Setting up colors takes an afternoon at most. Keeping them costs a few seconds per event forever, which is where schemes quietly fail: the color gets skipped when an event is created in a hurry, and a month later half the calendar is default-colored.

The two ways out are to push the work onto calendars rather than events, as above, or to make setting an event's color fast enough that it survives a busy day. On a desktop calendar, that means an event's color is reachable while creating it rather than after, and duplicating an existing event carries its color forward so recurring kinds of work keep their identity without a decision. The features list covers the editing side, and the guide shows how events get created in one pass rather than in a form.

What to change first

Pick one question for the colors to answer, cut the scheme to four colors with real contrast between them, and let the calendars carry the color instead of individual events. Then check the result in Month view from a distance, and if the colors still look muddy, switch the color set to Classic before touching the palette again. The Caltimate features show how the same scheme looks in a desktop calendar that keeps Google's colors intact.