Only show working hours in Google Calendar and shorten the grid

Nobody works at three in the morning, and yet a quarter of the week view is given to it. The search for a way to only show working hours in Google Calendar almost always starts there, with a grid where the part that matters is squeezed into the middle and the rest is scrolled past all day.

There is a complication worth knowing before hunting through settings. Two different requests share this wording. One is about the grid on your own screen. The other is about what other people see when they try to book you. Google has a feature for the second and no setting for the first, which is why the search results are so contradictory. This article separates them, describes what the Working hours feature actually does, and covers where the vertical trim exists.

The two requests inside one search

Request one is visual. The day view runs from midnight to midnight, and shortening it to something like eight in the morning until seven in the evening would make the whole working day fit without scrolling. This is a display preference, and it has nothing to do with colleagues.

Request two is social. Invitations keep arriving at seven in the evening or at lunchtime, and the goal is to make the people sending them stop. This is about availability signalling, and the display of your own grid is irrelevant to it.

Google Calendar addresses request two. The Working hours feature exists, it is well documented, and it does a specific job. Request one has no equivalent setting in the web interface, and knowing that saves an hour of looking. What Google offers for the shape of the view is horizontal, through custom day counts and density, rather than vertical. The hours axis stays the same length.

Sorting the request first also changes what the answer looks like. If the goal is fewer badly timed invitations, no display change will help. If the goal is a grid that fits, no availability setting will help.

What Working hours actually does

Working hours lives in Google Calendar on the web under Settings, then General. It was substantially rebuilt in 2019, and the launch note is precise about where the hours become visible:

Working hours now show in grid view: When you schedule a meeting with other Calendar users, their working hours will be shown in the calendar grid. Source: workspaceupdates.googleblog.com

The word "their" is doing the work in that sentence. The grid shading is a courtesy extended to whoever is scheduling, not a view preference for the owner of the calendar. The same release added a warning shown to an event creator who picks a time outside a guest's working hours, and turned the feature on by default for all users.

A second release in 2021 made the hours more expressive. Working hours can be split into several blocks per day, so a long break in the middle of the day can be marked as outside hours rather than folded into a single continuous stretch. That release also confirms where the shading appears: working hours are visible on your calendar when someone schedules a meeting with you.

Two limits follow from this design. Working hours is a signal, not a rule. Somebody can read the warning, decide the meeting matters more, and book anyway. And because the feature is attached to work and school accounts, a calendar running on a personal account has no working hours for anyone to respect, which is why freelancers often see this whole feature as absent.

Why your own working hours stay invisible

Having set the hours, most people go looking for the grey bands on their own calendar and find nothing. This is deliberate rather than broken. The 2021 release that added segmented hours states where the shading lives:

Working hours are visible on your calendar when someone schedules a meeting with you. Source: workspaceupdates.googleblog.com

That has a practical consequence for checking your own work. Since the shading is drawn for whoever is scheduling rather than for the owner, the reliable way to confirm a change is to reopen Settings, then General, then Working hours, and read back the row for each day. There is no view of your own calendar that will show it to you.

Two platform limits are worth knowing before hunting for the setting on a phone. Google's help page for the feature states that working hours can only be turned on from a computer. The 2021 release adds that working hour segments are available on the web only, so a day split into two blocks on a laptop cannot be edited from the mobile apps even though it keeps working.

Checking is worth the ten seconds, because working hours have a quiet failure mode. The hours are stored per day of the week, and editing them in a hurry on one day leaves the rest as they were. A Friday that still ends at six when everything else ends at four will keep collecting late invitations, and nothing on the screen will point at it.

Check the time zone at the same time

Working hours are hours of the day, and an hour of the day only means something against a time zone. If the calendar's zone is still set to a city that was left behind, colleagues reading the availability are reading the wrong window, and the settings themselves will look perfectly correct. The primary time zone sits in the same General settings page, which makes confirming it part of setting the hours rather than a separate job.

Travel produces the same mismatch without anything being misconfigured. A fortnight in another region leaves the bands describing a working day that finished before the local morning started, and the people booking have no way to tell. Either move the calendar's zone for the trip or accept that the signal is wrong until it ends.

The layer that actually declines things

If the aim is for badly timed invitations to be refused rather than merely flagged, working hours is the wrong tool. The enforcement lives in the event types that carry an automatic decline setting. Google's Calendar API documents out of office and focus time as distinct event types, each holding an autoDeclineMode with three options: declineNone, declineAllConflictingInvitations and declineOnlyNewConflictingInvitations, alongside a declineMessage sent to whoever tried to book the time.

That difference is the practical heart of this topic. Working hours tells people when you would rather not be booked. A focus time or out of office block actually refuses the invitation and replies with a sentence. The two are often described interchangeably, and they are not the same thing at all.

The everyday version of this is simple. Put a recurring focus time block over the hours that keep getting eaten, set it to decline only new conflicting invitations so that existing commitments survive, and write a decline message that names an alternative. Working hours then does what it is good at, which is stopping the invitation from being created in the first place, and the block handles the ones sent anyway.

Focus time availability depends on the Google Workspace edition in use, so a calendar on a personal account will not show the option. On personal accounts the equivalent is an ordinary busy event, which blocks the slot in a free and busy lookup but declines nothing by itself.

Where the vertical trim does exist

The request to shorten the grid is a real setting, just not in a browser. The Calendar app on macOS has held it for years, and Apple's guide describes the range:

You can customize Day and Week views so that the Calendar window shows from 6 to 24 hours of events per day, and you can mark when your day starts and ends. Source: support.apple.com

Three separate controls sit in Calendar settings under General, and they are easy to confuse with each other.

Control	What it changes	Range
Day starts at	The hour your day is marked as beginning	Between midnight and noon
Day ends at	The hour your day is marked as ending	Between noon and midnight
Show hours at a time	How much of the day the window displays at once	Between 6 and 24 hours
Days per week	Whether Week view holds the working week or all seven days	5 days, Monday to Friday, or 7

The first two shade the hours outside your day rather than deleting them, so a late event is still reachable by scrolling. The third is the one that removes the scroll, because setting it to eleven hours fills the window with eleven hours and nothing else. Setting Days per week to five completes the trim by dropping the weekend columns.

Because these are per app rather than per account, they apply to every calendar in the window, including Google accounts signed into the app. The events stay in Google, and only the framing changes. This is the closest thing to what the original search asked for, and it works the same whether the underlying accounts are Google, iCloud or Exchange.

What a shortened grid costs

Trimming has a downside that shows up in week two. Events genuinely outside the window stop being visible without scrolling, and early flights, evening classes and calls with another time zone are exactly the events that hurt most when forgotten. A grid clipped to office hours quietly teaches you that the day begins at nine.

Two habits keep that in check. Set Day starts at an hour earlier than the earliest thing you ever do, rather than at the time work begins, so an unusual morning still appears in the shaded zone. And keep a week view rather than a day view as the default, since a clipped week still reveals the shape of the coming days.

The other cost applies to anyone booking across regions. A day clipped to local office hours makes overlap with another time zone hard to judge, and the calendar will look empty at exactly the hours a colleague is awake. In that case the wider window is worth the scrolling, and the shading from Day starts at and Day ends at gives most of the benefit without the loss.

Entry habits matter more than the grid here. An event recorded at the wrong hour is worse than an event you had to scroll to, and the friction of a six field form is what produces wrong hours. The Entering events page covers turning a plain sentence into an entry with the time already parsed, which is the part of this problem no display setting reaches.

What to change first

Decide which of the two requests applies. If invitations are the problem, set working hours per day of the week in Google Calendar on the web, confirm the cross hatching by opening a new event, then add a recurring focus time block over the hours you keep losing. If the grid is the problem, the setting is in a desktop app rather than a browser, and a native Mac calendar such as Caltimate holds the same Google accounts while letting the window show as little as six hours at a time.