Gmail notifications on a Mac: one badge instead of three

Two complaints about Gmail notifications on a Mac arrive in roughly equal numbers, and they point in opposite directions. One group gets nothing: the browser is open, mail is arriving, and the screen stays silent. The other group gets everything three times over, once from a browser tab, once from a pinned window, once from a phone sitting next to the keyboard. Both symptoms come from the same place. A Gmail notification has to clear three independent layers before it lands on screen, and each layer can be set without regard for the other two.

Checking those layers in a fixed order turns a guessing game into a two-minute job. What follows is that order, then the separate question of how many places should be allowed to alert at all.

Three layers decide whether a notification arrives

The first layer is Gmail itself. Gmail has a desktop notification setting of its own, stored per account, and nothing reaches the operating system if that setting is off.

The second layer is the browser. Chrome, Safari and Firefox each hold a per site notification permission, and the answer given to a permission prompt months ago is still in force. A browser that has blocked mail.google.com will silently discard every alert Gmail tries to raise, no matter what the Gmail setting says.

The third layer is macOS. System Settings has a Notifications pane where every app and website is listed separately, with its own switch for whether alerts appear, where they appear, and how long they stay.

The layers are independent, which is the part that makes troubleshooting feel random. Fixing one of three changes nothing observable, so the natural response is to change it back and try something else. Working top to bottom, Gmail first and macOS last, avoids that loop.

One structural fact sits underneath all three. Browser based Gmail notifications only exist while Gmail is open in a tab or window. Close the tab and the source of the alert is gone, which is a different failure from a blocked permission and needs a different fix. Anyone who wants alerts with no Gmail window open has to move to a mail client or to a pinned web app that stays running.

Layer one: the setting inside Gmail

Open Gmail on a computer, click the settings icon at the top right, and choose See all settings. Scroll down to Desktop notifications. Three mutually exclusive options appear: new mail notifications on, important mail notifications on, and mail notifications off. Pick one, then scroll to the bottom of the page and click Save changes. Skipping that last click is the single most common reason the setting appears not to stick.

The same block holds the notification sound. With notifications switched on, a dropdown next to Mail notification sounds offers a set of tones, and selecting None keeps the alert visual only. This sound is separate from the system sound set in macOS later, and having both active can produce a double chime for a single message.

One behavior here catches people out regularly: if inbox categories are in use and new mail notifications are on, only messages landing in the Primary category raise a notification. A client email that Google has filed under Promotions arrives normally, sits in the inbox, and never announces itself. When specific senders seem to be silently skipped while everything else works, the category assignment is the thing to check, not the notification setting.

Choosing important mail notifications narrows things further, since it depends on Gmail's own importance markers, which shift as the account is used. For a work inbox where nothing can be missed, new mail notifications is the safer of the two.

Layer two: the browser permission

Chrome asks before any site may show notifications, and that prompt only appears once. A refusal given in passing is stored indefinitely. To review it, open Chrome settings, then Privacy and security, then Site settings, then Notifications. That page lists sites allowed to send notifications and sites not allowed, and entries can be added to either list by hand.

A faster route works from Gmail itself. With Gmail open, click the view site information control at the left of the address bar and switch Notifications on for that site.

Chrome also revokes permissions on its own. If Chrome decides a site's notifications are intrusive, it can remove that site's permission automatically, after which the site has to ask again. Notifications that worked yesterday and stopped today, with no setting changed, usually trace back to this. The same page in settings restores them.

For anyone who wants notifications without the interruption of permission prompts, the notifications page offers quieter messaging. Sites can still request permission, but the request appears as a bell icon beside the address instead of a dialog over the page.

Two smaller points close out this layer. Incognito windows do not show notifications at all, so a Gmail window opened privately will never alert. And on Safari the permission lives in Safari's own website settings rather than in a Chrome style list, which matters for anyone who keeps mail in one browser and everything else in another.

Layer three: the macOS notification settings

Open the Apple menu, choose System Settings, and click Notifications in the sidebar. Scrolling is usually required, since the item sits well down the list.

Under Application notifications, each app and website appears separately. Allow notifications is the master switch; with it off, every option below turns grey and nothing else on the page has any effect. That switch is the first thing to read.

Alert style covers both where an alert appears and how long it stays. The destinations are Desktop, Notification Center and Lock Screen. The duration choice is between temporary, which fades after a few seconds, and persistent, which stays until dismissed. Missed messages call for persistent. Broken concentration calls for temporary. Very few inboxes need both.

Badge application icon puts an unread count on the Dock icon, which is the quietest useful signal available: a number that can be read on the way past without any interruption. Play sound for notifications is the system level sound, separate from the one configured in Gmail.

Show previews has three settings: always, when unlocked, or never. Screen sharing makes this consequential. A persistent desktop alert with previews always on will put the first line of an incoming message in front of everyone on the call. When unlocked is the sensible default for anyone who presents regularly.

The top of the same pane governs Notification Center as a whole, with separate switches for showing notifications while the display is asleep, while the screen is locked, and while the display is being mirrored or shared. That last one is worth turning off before a week of demos rather than during one.

Group notifications, on each app's own page, offers automatic, by application, or off. Automatic groups mail notifications by mail account, which is the closest the system gets to separating work mail from personal mail without any extra software.

Why the same message arrives twice

Duplicate alerts are not a bug. They are the predictable result of having more than one thing listening to the same mailbox. On a typical Mac there are four candidates.

Receiver	Alerts when Gmail is closed	Separate macOS settings	Typical reason to keep it
Gmail in a browser tab	No	No, shares the browser's entry	Already open all day
Gmail as a pinned web app	Yes, while the app runs	Yes, its own entry	Wanted a Dock badge
Apple Mail with the account added	Yes	Yes, its own entry	Prefers a native client
iPhone or iPad nearby	Yes	Set on that device	Away from the desk often

Any two of these active at once doubles the interruption count for every message. At forty messages a day that is eighty interruptions instead of forty, for exactly the same information.

The fix is a decision rather than a setting. Pick one receiver and silence the rest. For someone who works inside a browser all day, that is the browser, and Apple Mail's entry in System Settings gets switched off. For someone who prefers a native client, Gmail's own desktop notification setting goes to off and the client keeps the job. A phone stays useful as the away from desk receiver, which is a reason to configure it differently rather than a reason to silence it.

Making the inbox its own app

Once one receiver is chosen, a browser tab is a slightly awkward place to put it, because the browser holds a single notification identity for every site inside it. Promoting Gmail to a web app splits that off.

In Safari, open Gmail, click the share control in the toolbar and choose Add to Dock. Apple's documentation is specific about two things worth knowing in advance: the web app carries over the existing signed in session in most cases, with the same username and password, and a web app can receive notifications just as an app does. The window gets a simplified toolbar, and its settings allow the name, URL, icon, navigation controls and title bar color to be changed afterwards.

In Chrome, open the three dot menu, choose Cast, save and share, then Install page as app. Installed web apps can use notifications and icon badging, and they are managed from chrome://apps, where a right click offers Create shortcut and Open at login.

The practical gain is granularity. Instead of one entry named after the browser, System Settings now lists the inbox as its own item, so persistent alerts, badges and previews can be set for mail alone while every other site in the browser stays quiet. Renaming the web app is worth doing immediately if two accounts are involved, since both will otherwise arrive with the same name and the same icon in the Dock.

Per account, not per browser

Pinning solves the granularity problem and then runs into a harder one. Two Gmail accounts pinned from the same browser profile share one session. Switching the work account switches the personal one, and both windows are the same identity as far as notifications are concerned, so work mail and personal mail cannot be treated differently.

That limit is about where login state is stored, which is why the answer is a tool that stores it per app rather than per browser. A browser that keeps each web app in its own window, with its own cookies and its own session, treats two accounts of the same service as two genuinely separate entries: separate Dock badges, separate sound settings, separate notification rules. The Workspaces page covers how that separation is arranged, and Features sets out what else falls out of it once each app has its own window.

Several tools take this approach with different limits. Wavebox offers a free Basic plan with two groups of two apps each and one extension, with Pro at $8.33 per month billed annually and Teams at $12.50 per user per month, after a seven day trial. Ferdium is community built and free, runs without an account, and allows the same service to be added more than once so that separate accounts can be signed in side by side. Sleeping unused services to save resources is part of its design. Pricing is the place to compare that against a paid option before committing to either.

What to change first

Start by counting the receivers rather than adjusting any settings, since silencing three of four does more for a working day than tuning all four ever will. Then walk the three layers in order, Gmail, browser, macOS, and set the one surviving receiver to persistent alerts with previews limited to when unlocked.

If two accounts of the same service are in play, per account windows are the piece that standard pinning cannot supply, and SpaceDeck is built around that separation.