Google Calendar is finally moving beyond its tiny 11-colour comfort zone. The service now offers up to 24 default event colours, plus a full RGB colour picker that gives users around 200 custom shades for events they want to separate at a glance.
That sounds cosmetic, because it is. But in a calendar app, cosmetic is functional: if your work trips, doctor visits, holidays, and team meetings all blur together, the whole point of colour-coding gets lost. Google has been slow to fix one of Calendar’s simplest annoyances, especially while rivals such as Outlook have long offered more flexible visual sorting.
What the new Google Calendar colours include
The update expands the default palette to 24 options and adds a colour picker for custom event colours. Google says the expanded set will be available on the web and in mobile apps, and it also lands in the Calendar API, which matters for people and tools that automate scheduling.
- Up to 24 default event colours
- A full RGB colour picker
- About 200 custom colours
- Available on web, mobile apps, and the Calendar API
Who gets the Google Calendar colour update
Google says the new colours are rolling out to personal account owners, Workspace customers, and Individual subscribers. That is a broad enough rollout to make this feel less like a niche tweak and more like a long-overdue cleanup of one of Google’s most-used productivity tools.
There’s no hardware angle, no AI pitch, and no dramatic redesign here. Just a rare case of a company admitting that people really do care about the little things, especially when those little things are the only thing standing between a usable calendar and a sea of beige meetings.
Why this Google Calendar update will probably stick
If Google keeps the picker easy to access, the new colours should become one of those updates people stop thinking about only because it quietly makes the app better every day. The bigger question is whether Google will keep polishing the basics of Calendar, or leave users waiting another long stretch for the next obvious fix.

