Turning on Gmail desktop notifications and making them reliable

Gmail has a switch for desktop notifications, and flipping it is not usually the hard part. The hard part is that the switch is one of three independent permissions, each owned by something different, and any one of them can silently veto the other two. Gmail can be set to notify. The browser can be set to block. macOS can be set to deliver quietly. Nothing in any of those three places tells you about the other two.

What follows is the order those layers sit in, what each one actually controls, and the specific configurations that produce the most common complaint: notifications that worked for a while and then stopped, with no setting visibly changed.

Layer one: the setting inside Gmail

Google's documentation for computers puts the control in one place. Open Gmail, click Settings at the top right, then See all settings, then scroll to the section headed Desktop notifications. Three options are listed there, and they are mutually exclusive:

• New mail notifications on
• Important mail notifications on
• Mail notifications off

Changes here do not take effect until Save Changes is clicked at the bottom of the settings page, which is a genuine cause of "it did not work" reports. The settings page is long, the save button is at the very bottom, and navigating away discards the change.

The same section holds the sound control. Next to Mail notification sounds, a sound can be picked from the list, or None can be selected to turn the audio off while keeping the visible notification. That is a useful middle setting and it is worth knowing it exists before concluding that notifications are broken because they are silent.

Google states the supported browsers plainly: notifications work in Google Chrome, Firefox or Safari after signing in to Gmail and opening it in the browser. Everything below assumes one of those three.

What the middle option actually does

New mail notifications on and Important mail notifications on are not two intensities of the same thing. The second one hands the filtering decision to Gmail's own importance marking, which means the volume of notifications depends on how Gmail has learned to classify mail on that account. On a busy account this is the difference between a notification every few minutes and a handful a day. On an account where importance markers have never been corrected, it can be the difference between useful and arbitrary.

Layer two: the category filter nobody expects

This is the single most common reason Gmail notifications appear to work badly rather than not at all, and Google states it directly: if inbox categories are in use and notifications for new mail are turned on, notifications only arrive for messages in the Primary category.

Read that against how most inboxes are actually configured. Anything Gmail files under Promotions, Social, Updates or Forums produces no desktop notification, regardless of the setting. For a personal account that is mostly the desired behaviour. For a working account it is a trap, because a large amount of genuinely operational mail gets categorised as Updates: receipts, shipping notices, service alerts, password resets and anything sent from an automated system.

The practical consequences are worth stating in full.

Symptom	Likely cause	What to change
No notifications at all	Setting not saved, or browser permission blocked	Re-check Save Changes, then the browser's site permission
Notifications for some mail only	Inbox categories are on and only Primary notifies	Turn off categories, or move senders to Primary
Notifications appear with no sound	Mail notification sounds set to None, or macOS per-app sound off	Gmail's sound list, then macOS Notifications settings
Notifications stopped after a while	Browser permission reset, or the tab is no longer open	Site settings, then whether Gmail is still loaded

Moving a sender to Primary is done from the message itself and persists, which makes it the lower effort fix when only a handful of senders matter. Turning categories off entirely is the blunt version and changes how the whole inbox looks.

Layer three: the browser holds the permission, not Gmail

Gmail's setting is a request. The actual permission to display a notification belongs to the browser, and it is granted per site. Google's own documentation is unambiguous about the failure mode: notifications will not arrive if notifications are turned off for the browser as a whole.

In Chrome, the path runs through Privacy and security, then Site settings, then Notifications. A site that has been blocked appears in the blocked list, and mail.google.com can be added to the allowed list directly by choosing Add next to the allowed entry and entering the address. The permission can also be restored from the page itself when the address bar shows that notifications are blocked.

Two things about this layer cause repeat problems.

The permission is per browser profile. A second Chrome profile, created for a second Google account, starts with no permission granted. The Gmail setting inside that account may well be on, because it is stored with the account, while the browser profile that renders it has never been asked.

A blocked permission is sticky. Dismissing the browser's permission prompt once, in a hurry, can record a decision that then persists indefinitely and is never mentioned again. Nothing in Gmail's settings page reflects it.

Layer four: macOS decides what a granted notification looks like

Once the browser is allowed to notify, macOS controls the result. In System Settings, Notifications lists the app that will display the alert, and for Gmail in a tab that app is the browser, not Gmail.

Apple's documentation for this panel describes the controls that matter here. Alert Style chooses where the notification appears, with Desktop showing it on screen and Notification Center listing recent ones, and chooses whether it is Temporary, meaning it disappears after a while, or Persistent, meaning it stays until dismissed. Play sound for notification controls audio separately from everything else. Show previews controls whether the content is visible, with Always, When Unlocked and Never as the options, and Apple notes that the top-level preview setting is used as the default for individual apps.

Notification grouping is the setting that changes how a busy inbox feels. Apple describes Automatic grouping as grouping by app or website, and adds that in some cases an app's notifications may be stacked into multiple groups, giving Mail messages grouped by email account as the example.

The per-browser granularity is the real limitation. Setting Chrome to Persistent affects every site that notifies through Chrome, and turning Chrome's notification sound off silences all of them together. There is no way in this panel to treat mail differently from a calendar reminder or a chat message if all three arrive through the same browser. That constraint is why mail often gets pulled out of a general browser tab and into something that holds it in its own window with its own notification behaviour.

Where Notification Center fits

Notifications that are not seen when they arrive do not vanish. Apple describes Notification Center as the place to catch up on notifications that were missed, opened by clicking the date and time in the menu bar or by swiping left with two fingers from the right edge of the trackpad. Notifications from an app can be expanded from a stack, acted on directly, or cleared individually or as a whole stack.

That matters for mail specifically, because a banner set to Temporary disappears after a few seconds. If the pattern is that notifications are known to be arriving but keep being missed, the change worth making is Alert Style rather than anything in Gmail. Setting the browser to Persistent means the notification waits until it is dismissed.

Apple also notes that an app's notification settings can be reached from Notification Center itself: when an arrow is shown to the right of the app name, clicking it gives the option to mute or turn off notifications, or to open notification settings. That is a faster route than System Settings when a single noisy source needs quieting on the spot, and it is also an easy way to turn something off by accident and forget about it.

The reliability problem: notifications come from a loaded page

Google's phrasing for how this works is that notifications arrive after signing in to Gmail and opening it in the browser. That is the mechanism, not a convenience note. The notification is produced by the running Gmail page.

Everything that ends the page's life ends notifications with it, and most of those things are routine. Closing the tab. Quitting the browser at the end of the day and not reopening that tab. A browser that discards background tabs to reclaim memory. A session that expires and leaves a sign-in screen where the inbox was.

None of these announce themselves. The tab is still in the tab strip, apparently fine, and no alert has arrived for two hours. This is also why Gmail notifications tend to be described as unreliable rather than broken: they work, then they stop, then they work again after the tab is touched.

The structural answer is to stop depending on a tab that competes with several dozen others. That can mean pinning the tab so it survives ordinary tab closing, or keeping mail in a window that is not part of the general browsing pile at all, which is the shape multi-account setups for macOS take. For several Gmail accounts at once it becomes the deciding factor, because the browser's per-origin permission model was never designed to distinguish one signed-in Google account from another on the same site.

Focus will override all four layers

One more thing sits above everything described so far. A Focus, including Do Not Disturb, silences notifications by design, and Apple's documentation describes Focus as a way to pause and silence all notifications or allow only certain ones.

Focus is easy to leave on without noticing. Apple lists several ways to turn Do Not Disturb on, including Control Center and holding the Option key while clicking the date and time in the menu bar, and states that when Focus is kept up to date across Apple devices, turning it on or off on one device does the same on the others. A Focus switched on from a phone in a meeting arrives on the Mac.

If mail genuinely has to come through while a Focus is running, Focus settings include an Allowed Apps list, where choosing Allow Some Apps and adding the browser permits it while the rest stay quiet. Apple's Focus settings also include Focus Filters, one of which applies to Mail and limits which email accounts are shown while that Focus is active.

What to change first

Check the browser's site permission before touching anything in Gmail. It is the layer most likely to be silently blocking and the one least likely to have been set deliberately. Then confirm Save Changes was actually clicked on the Gmail settings page, and only after that consider inbox categories, which explain almost every case of notifications arriving for some mail and not others. If several Gmail accounts have to notify independently rather than sharing one browser's permission, SpaceDeck is built around giving each account its own window and its own alerts.