Google Calendar Per-Calendar Default Event Length Spotted

Google Calendar currently forces every calendar in an account to share one default event length. That might not last. A teardown of the Android app's code points to Google testing a per-calendar default event length setting, one that would let each calendar hold its own typical duration instead of borrowing a single number for the whole account, according to Android Authority.

The find comes from version 2026.38.0-989268529-release of Calendar for Android. Nothing about it shows up in Google's own release notes yet, and Android Authority frames it conditionally: Google "appears" to be prepping the change, and the setting "looks like" it's headed toward per-calendar defaults rather than staying one global rule.

How Google Calendar's default event duration works today

Google Calendar already lets users speed up event creation by picking a default length for new events, instead of dragging an end time into place every time one gets added. Someone who schedules a lot of quick 15-minute meetings can set that as the default, while someone who prefers longer blocks can choose an hour or more.

That default syncs across devices and platforms, so a choice made on one device applies everywhere else signed into the same account. The convenience is also the catch: the number covers every calendar tied to the login, not just one.

A work calendar built around short standups and a personal calendar built around longer appointments currently share that single number, whether it fits either one well or not. Switching calendars inside Calendar's event settings doesn't change which default length applies to a new event.

Where Google Calendar's individual calendar settings could hold the new control

Google looks like it's getting ready to move the default-duration option out of one global settings menu and into the settings for individual calendars instead. If Google follows through, the per-calendar option would become the only way to set default event lengths, and the global toggle would disappear.

That's a structural swap, not an added feature sitting beside the old one. Nothing in the code points to the two settings coexisting; the per-calendar version reads as a replacement.

A few things stay unanswered. The teardown doesn't show final interface wording, a timeline, or how an account's existing global preference would carry over if the feature ships. It also doesn't say whether the new option would apply to every calendar a person has access to, including ones they've subscribed to or that have been shared with them, or only to calendars they personally own, and whether Calendar on the web or iOS would get a matching control at all.

Who benefits, and who picks up extra setup

The likely winners are people who already keep separate calendars for different parts of their life. Pair a work calendar full of 15-minute check-ins with a personal or client calendar built around hour-long appointments, and each one could finally carry a default that fits instead of forcing both to compromise on one shared number. That's a reasonable read of what the change would enable, though it's still a projection built on code in an unreleased build, not a feature anyone has used.

The trade-off runs the other way for anyone who wants the same default everywhere. If the per-calendar setting really does replace the global one, someone who prefers a uniform 30-minute default across every calendar would need to set that number on each calendar separately instead of changing it once in a shared menu. That's extra setup for multi-calendar users who liked having one dial that controlled everything.

Worth weighing before anyone starts reorganizing how their calendars are split up, since none of this is confirmed behavior yet.

Why one teardown isn't a release date

Code sitting inside an app build shows what a company may be preparing, not what it will actually ship. A 2024 Android Authority teardown makes that distinction concrete: it found a Birthday chip buried in Calendar for Android that wasn't live in the tested build, and the outlet said at the time the feature "may or may not roll out."

That chip was designed to simplify adding recurring birthday events by stripping out fields people normally adjust by hand, like time duration and recurrence settings, according to the earlier report. Android Authority managed to activate it inside version 2024.21.0-637471596 of the app. Being able to switch on dormant code in a build is not the same as Google shipping that code to everyone. In this case, Google later did launch the Birthday event feature, announcing it for Android in September 2024.

The same caution applies to the per-calendar default-duration discovery. A feature spotted in code is worth tracking. It isn't confirmation of a shipping date, a finished design, or even a final decision to release it.

What to do now

No official Google release information is attached to this find, and there's no new control to enable inside any current version of Calendar. The per-calendar default-duration option is still an Android code discovery, not an announced update.

Keep using the existing account-wide setting for now, and don't restructure calendars around a feature that hasn't shipped. Watch Google's own Workspace and Calendar release notes, rather than this teardown, for the actual confirmation if and when it comes.