Gmail pop up notifications: keeping new mail from taking over

A Gmail pop-up either arrives when nothing needed interrupting, or fails to arrive on the one morning it mattered. Both symptoms come from the same place: on a Mac, a Gmail alert has to pass through three independent switches before it reaches the screen, and each of the three is set somewhere different. Nothing in the interface tells you which one is closed. The fix is to stop guessing at the Gmail settings page and instead walk the chain in order.

The three switches a Gmail alert has to pass

The first switch is inside Gmail itself. Under Settings, in the section labelled Desktop notifications, the choice is between new mail notifications on, important mail notifications on, and mail notifications off. This setting is stored per account, not per browser, so it follows the account to any machine.

The second switch belongs to the browser. A web page cannot raise a system notification on macOS without being granted permission, and that grant is recorded per site, per browser profile. Chrome documents the default behaviour plainly:

By default, Chrome alerts you whenever a website, app, or extension wants to send you notifications. Source: support.google.com

That prompt is easy to dismiss by reflex, and once dismissed it does not come back on its own. It lives afterwards in Settings, under Privacy and security, Site settings, Notifications, as an entry in the not-allowed list.

The third switch is macOS. Every app that raises notifications has its own row in System Settings, and a browser is just another app in that list. If the browser's row is off, or if a Focus is running, the notification is created and then silently dropped before it is drawn.

Gmail's own requirement sits on top of all three. Google states that email notifications arrive in Chrome, Firefox, or Safari after you sign in to Gmail and open it in your browser. Open is the operative word. A closed tab produces no alerts at all, because there is no page running to raise them.

Turning them on in the order that works

Work outward from the account to the operating system. Reversing the order wastes time, because a change at the outer layer has no visible effect while an inner layer is still closed.

Start in Gmail. Open Settings, then See all settings, scroll to Desktop notifications, choose new mail notifications on, and click Save Changes at the bottom of the page. The save button is the step most often missed, because the radio button appears to have taken effect immediately.

Next, deal with the browser permission. Reload Gmail. If no prompt appears and no alerts follow, the site has already been denied. In Chrome, check the notifications list under Site settings and remove mail.google.com from the blocked entries. Chrome also offers a quieter mode that suppresses the prompt entirely and leaves only a bell icon in the address bar, which explains a case where nothing seems to be asking for permission.

Finally, confirm the browser's own row in System Settings under Notifications, and check whether a Focus is active. Do Not Disturb can be toggled by holding the Option key and clicking the date and time in the menu bar, which makes it very easy to leave on by accident.

One more setting is worth knowing while you are there. If inbox categories are switched on and notifications are set to new mail, alerts are limited to messages in the Primary category. That behaviour is a feature when it matches your habits and a bug when it does not.

Why the alerts go quiet again a week later

Notification setups rarely break loudly. They stop working after some unrelated change, and the timing makes the cause hard to see.

Private browsing is the cleanest example. Chrome does not deliver notifications from an incognito window at all, so a habit of opening a second Gmail in a private window guarantees silence from that account. The same applies to any profile that was set up fresh, because site permissions do not travel between profiles.

A restarted browser is the second common cause. If Gmail is not in the set of tabs restored on launch, there is no page to raise an alert, and the first clue is usually a reply that arrives hours late. Pinning the tab helps only if the browser is configured to reopen pinned tabs.

The third cause is Chrome's automatic protection. Chrome blocks notifications from sites it judges to be intrusive or misleading and recommends keeping them blocked. This is aimed at advertising, but the outcome is the same list of blocked origins that a legitimate site can end up on.

Focus is the fourth. A Focus scheduled for working hours, or one synced across devices from an iPhone, silences the browser without changing anything on the Mac that you would think to check.

The part no setting solves: which account

The switches above control whether an alert appears. They do nothing about whose mail it is. A Mac notification from a browser is labelled with the browser, not with the account, so three signed-in Gmail addresses produce three visually identical banners.

This is not a cosmetic problem. Signing several Google accounts into one browser profile also makes the accounts share state in ways Google documents openly: when more than one account is signed in, settings from the default account may be applied, and the default account is generally whichever one signed in first during that session. Restarting the browser in a different order changes which account behaves as the default.

The structural fix is to stop putting several accounts in one profile. A separate browser profile per account works and is free, at the cost of a separate window, a separate set of extensions, and a manual hunt for the right window when a notification arrives. A browser built around app windows takes the same isolation and attaches an identity to it, so each account runs in its own workspace with its own cookie container and its own visible label. The comparison of how the products in that category handle per-account sessions is set out in the Wavebox comparison.

Where each approach puts the alert

Approach	Needs a tab open	Tells accounts apart	Survives a browser restart
Gmail in a normal browser tab	Yes	No	Only if the tab is restored
One browser profile per account	Yes	By window, not in the banner	Only if each profile is reopened
Gmail added to the Mail app	No	Yes, by account name	Yes
App windows in an aggregation browser	The app stays loaded	Yes, by named workspace	Yes

The Mail app that ships with macOS is the option people skip because it feels like a step backwards, and it is worth a second look on the narrow question of notifications. It holds accounts from iCloud, Gmail, Exchange, work, school, and other providers in one place, it keeps checking without a browser tab, and its alerts carry the account name. It also sorts incoming messages into Primary, Transactions, Updates, and Promotions, which cuts the volume before the notification stage. What it cannot do is show the Gmail interface, so labels, filters, and search operators stay behind.

A pinned tab, an installed shortcut, and an app window are not the same thing

Once the chain is working, the remaining question is how to keep the page loaded without keeping a browser window in the way. Three answers get recommended interchangeably, and they behave differently.

A pinned tab is the lightest option and the least dependable. It keeps Gmail at the left edge of the tab strip, but it lives inside a normal browser window, so it shares that window's fate. Closing the window closes the tab, and whether pinned tabs return on the next launch depends on the startup setting rather than on pinning. Browsers also reclaim memory from background tabs, and a discarded tab stops raising notifications until it is visited again.

An installed web app shortcut goes further. Chrome and Edge can open a site in a frameless window with its own Dock icon, which means macOS treats it as a distinct target for notifications and for window management. The limitation is identity. The shortcut still uses the profile it was created from, so two Gmail accounts need two profiles, and the Dock ends up with two icons that look identical.

A purpose-built app window in an aggregation browser starts from the opposite end. The app is the unit, the session belongs to the app, and the window is named. Notifications from all of the loaded apps are collected in one place rather than spread across browser windows, which is the practical difference when six services are open. The trade-off is that a second application is now running on the Mac, and the supported app list is worth checking before assuming a given service is covered.

None of the three changes whether Gmail is willing to send an alert. All three change how likely it is that something is loaded and listening when the mail arrives, which in practice is the failure most people are actually hitting.

Cutting the volume, not just the switch

Most people who search for this topic want fewer interruptions rather than more, and the useful levers are not in the on and off pair.

Important mail notifications on is the least used of the three Gmail choices. It leaves the delivery path intact and hands the filtering to Gmail's importance markers, which means the alert rate falls without any per-sender work.

Notification sounds are a separate setting under the same Desktop notifications section, with None available in the list. Silencing the sound while keeping the banner is a reasonable middle position, because a banner can be ignored for a minute and a sound cannot.

Filters do the sharpest work. A filter that skips the inbox for a noisy sender removes that sender from the notification path entirely, since a message that never lands in the inbox produces no new mail alert. This is more durable than muting, because it survives moving to a different Mac.

Where several accounts are in play, the same logic applies one level up. Only one or two accounts usually deserve to interrupt. Running each app in its own persistent window makes that a per-account decision instead of a single global switch, and the full feature list shows how notifications and workspaces relate in that model.

What to change first

Walk the chain once, in order: Gmail's Desktop notifications setting, the browser's permission for mail.google.com, then the browser's row in System Settings and whether a Focus is on. If the chain is clean and the real problem is that three accounts raise three identical banners, the setting is not the thing to change, the container is, and SpaceDeck keeps each account in a window that says whose mail just arrived.