Chrome notification permissions are one of the most aggressively abused browser features. Sites present the permission prompt when you first visit — sometimes disguised as a necessary step to view content — and once you click “Allow,” they can send desktop pop-ups indefinitely. Most people’s notification allowed list is full of sites they don’t remember approving. For the bigger picture, our Chrome How-To Guides pulls everything together.
Five-second fix: chrome://settings/content/notifications → scroll through “Allowed to send notifications” → click the three dots (⋮) next to each site you don’t want → Remove. Done. No restart needed, notifications from removed sites stop immediately.
The global notification setting
Instead of revoking site by site, you can stop all notification prompts from appearing in the future. chrome://settings/content/notifications → Default behaviour → select “Don’t allow sites to send notifications.” This prevents any site from prompting you, and removes the permission from being grantable without you going into settings to add an exception.
This is the right choice for most users. Genuine notifications you actually want — from a web-based project tool, a messaging service, a calendar app — can be added manually to the “Allowed” list at any time. The default “sites can ask” setting lets sites prompt you, which is the mechanism that fills the allowed list with things you didn’t consciously choose.
What the notification prompt actually looks like
The standard Chrome notification prompt appears just below the address bar: “[Site name] wants to: Show notifications — Block / Allow.” Some sites replace or obscure this with a fake dialog overlay, making it look like clicking “Allow” does something site-specific rather than granting browser notification permission.
Common disguises: “Enable notifications to continue,” “Allow notifications to download your file,” “Click Allow to prove you’re not a robot.” These are manipulative design patterns — the underlying permission being granted is still Chrome’s notification permission, regardless of what the fake dialog claims it does. If you’ve clicked “Allow” on any of these and now receive unwanted notifications: that’s why.
Blocking notifications site-by-site while visiting
When a notification prompt appears on a site you’re visiting: click the X in the prompt, click “Block,” or click “No thanks” (the exact text varies). Clicking X or Block adds the site to your blocked list — it can’t prompt you again on future visits. Dismissing by pressing Escape or clicking elsewhere typically dismisses for the session but doesn’t permanently block; the prompt may reappear on your next visit.
For a site that’s already in your allowed list and sending notifications: lock icon in the address bar → Notifications → change from “Allow” to “Block.” This revokes access immediately. The site will receive an error when it next tries to send a notification and will stop sending them.
Quiet notification requests — Chrome’s anti-spam feature
Chrome automatically reduces intrusive notification prompts through “Quieter notification prompts.” This is enabled by default when Chrome detects a site that frequently gets denied by users. Instead of a full prompt, Chrome shows a small notification icon in the address bar that you can actively choose to expand. This significantly reduces how often you’re interrupted by prompts from sites Chrome has identified as likely to be unwanted.
chrome://settings/content/notifications → “Use quieter messaging (blocks notification prompts from interrupting you)” → can be enabled manually for all sites if Chrome’s automatic detection isn’t catching everything. With this on: all notification requests appear as a small icon rather than an intrusive dialog.
Desktop notifications vs in-browser alerts
Chrome notifications appear as desktop notifications (outside the browser window) — they show in Windows’ notification area or macOS’s notification centre. They’re different from in-browser alerts (JavaScript alert boxes that appear inside the page). You can dismiss in-browser alert boxes, but desktop notifications from Chrome appear even when you’re in another application.
To manage Chrome notifications in Windows: Settings → System → Notifications → scroll to the “Notifications from apps and other senders” section → find Google Chrome → turn off “Notifications” or adjust notification settings (sound, banner, lock screen visibility). This is the Windows-level override — it stops Chrome notifications from appearing in the Windows notification area even if Chrome has granted permission to sites.
On macOS: System Preferences → Notifications → Google Chrome → set to “Off” or change the alert style. This is your override if you want to mute Chrome notifications at the OS level rather than managing them site by site in Chrome.
Our guide on Chrome site permissions management covers all permission types in one place, and our Chrome privacy guide covers the broader data management picture. For understanding Chrome’s notification architecture and how push notifications differ from regular browser notifications, Chrome’s developer documentation explains the Web Push notification standard and how sites implement it.
Web push notifications vs Chrome alerts — the technical distinction
Chrome notifications include two types that behave differently:
- Web push notifications: sent from a server to your browser even when you’re not on the site. These are the ones that appear while you’re doing something else entirely. They use a background service worker and don’t require the site to be open.
- Notification API alerts: sent only while the page is open in a tab. These disappear when you close the tab.
Most intrusive notifications — the spam, the fake alerts, the marketing messages — are web push notifications. Revoking the notification permission stops both types. From the user’s perspective this distinction doesn’t change what you need to do (revoke permission in Chrome’s settings), but it explains why notifications appear even when you haven’t had the site open for days.
| Action | Method | Effect |
| Stop all notification prompts from new sites | chrome://settings/content/notifications → Don’t allow | No more permission prompts |
| Remove specific site from allowed list | Settings → Notifications → Allowed → click ⋮ → Remove | Site loses permission immediately |
| Block a site while visiting it | Lock icon → Notifications → Block | Site blocked; can’t prompt again |
| Mute Chrome notifications OS-wide | Windows: Settings → Notifications → Chrome → Off | No Chrome notifications reach OS tray |
| Reset all notification permissions | chrome://settings/content/notifications → Reset permissions | All sites must re-request permission |
Notifications are one of those permission types where “Allow” once means “allow forever” unless you specifically revoke it. The combination of setting the default to “Don’t allow” and clearing the existing allowed list is the most efficient clean-up: it takes about two minutes and permanently eliminates notification spam from sites you never deliberately wanted to receive alerts from.
Identifying the source of specific notifications
When a Chrome notification appears: look at the small text below the notification title. It shows either the site’s URL or “Chrome” as the sender. If the notification itself doesn’t show the source clearly: right-click the notification (on Windows) → “Settings” → this opens Chrome’s notification settings for that specific site, making it easy to revoke access in one step from the notification itself.
On Windows, all Chrome notifications are also visible in the Action Center (Win+A → see notification history). Even notifications you dismissed are retained there temporarily. If you missed a notification but want to know which site sent it: the Action Center shows recent Chrome notifications grouped by site.
Notifications and Chrome profiles
Chrome profiles each have their own separate notification permission lists. If you use a Work profile and a Personal profile: the allowed sites in your Work profile don’t carry over to Personal, and vice versa. Notification spam in one profile doesn’t affect the other.
When reviewing and cleaning up notification permissions: check each profile separately. A site that’s blocked in your Work profile is only blocked for that profile — it can still send notifications if you’ve allowed it in another profile. Open the profile selector (click your profile avatar) → switch to each profile → visit chrome://settings/content/notifications for each one.
Sites that keep re-requesting permission
A site that’s been blocked can’t re-prompt you — Chrome returns “permission denied” silently without showing a dialog. However, some sites use aggressive popups or overlays outside the permission system to encourage you to manually visit settings and grant permission. These are not Chrome permission prompts; they’re the site’s own HTML/CSS design pressuring you to grant access.
The correct response: ignore the in-page overlay. If the site is blocked in Chrome’s settings, it cannot send notifications regardless of what any in-page element tells you. Sites that pressure users to manually enable notifications are typically doing so for advertising or spam purposes, not for any user benefit. Keeping them blocked is the right call.
Allowed notification sites you actually want
After blocking notifications globally, you might want to add back legitimate services. To manually add a site to the allowed list: chrome://settings/content/notifications → under “Allowed to send notifications” → “Add” → enter the site’s URL. The site can then send push notifications again.
Services that genuinely benefit from notification permission: calendar applications (Google Calendar, Outlook Web), project management tools (Asana, Notion, Linear when used in browser), messaging services used in the browser (Slack web, WhatsApp Web), and perhaps a news site for breaking news alerts if you specifically want that. For most people, the list of services where browser notifications are actually useful is three to five sites, not the thirty that might be in an unreviewed allowed list.
The notification request timing pattern
Sites with good UX practice show the notification permission prompt after you’ve interacted with their service and have a reason to want updates. Sites with poor (or manipulative) UX show it immediately on first page load, before you’ve even determined whether you want to continue using the site.
Chrome’s quieter notification prompts feature specifically targets this: sites that request permission immediately on first load often get classified as likely-to-be-unwanted, so Chrome shows only the small icon rather than the intrusive dialog. This makes early-request sites significantly less likely to get permission from new visitors, which is one of the better anti-spam measures Chrome has introduced in recent years.
The practical outcome of managing Chrome notifications well: desktop pop-ups only come from services you’ve deliberately added, the browser runs with fewer background service workers, and you recover control over the notification channel that websites have increasingly treated as an advertising delivery mechanism. The five minutes it takes to review and clean up the notification allowed list is one of the better browser maintenance tasks available.
Mobile Chrome notification management
Chrome for Android handles notifications through the Android notification system. Sites that have notification permission can send alerts through Chrome’s Android notification channel. Managing these:
- In Chrome: chrome://settings/content/notifications — same as desktop, shows which sites have permission on this device. Revoke here to stop Chrome from delivering the notification.
- At OS level: Android Settings → Apps → Chrome → Notifications — lets you control all Chrome notifications, including silencing them, changing their priority, or turning them off entirely. You can also control individual notification channels within Chrome (Chrome has separate channels for different notification types).
On Android, swiping left on a Chrome notification and tapping the gear icon takes you directly to Chrome’s notification settings for that specific app or site, which is a faster route than navigating through multiple settings menus.
For Chrome on iOS: notifications behave similarly, controlled via iOS Settings → Chrome → Notifications. The per-site permission management happens within Chrome at chrome://settings/content/notifications, while iOS Settings provides the system-level override. Sites you’ve allowed in Chrome can only send notifications if iOS also allows Chrome to display notifications. Our guide on Disable Chrome Password Manager covers an adjacent issue.
Both mobile platforms have this two-layer permission system (Chrome grants permission to the site, OS grants Chrome the ability to show notifications), which gives you two levels of control. If notifications are appearing despite revoking permissions in Chrome: check the OS-level setting. If the OS setting is off but Chrome still shows the site as allowed: the site can’t actually send notifications because the OS is blocking Chrome’s notification channel. See also Disable Chrome Auto Sign for a related case.
One more note on the enterprise side: organisations that use Chrome for internal web tools sometimes send genuine work notifications through Chrome — ticket updates, alert system messages, calendar reminders. If your organisation uses browser-based tools: check before revoking notification permissions for those domains, as they may be delivering legitimate work alerts rather than marketing spam. The URL structure of internal tools (usually intranet.company.com or app.companyname.com patterns) typically distinguishes them from the consumer sites that abuse the notification permission. You might also run into Disable Chrome Microphone and Camera.
