Chrome notifications that keep showing up on your desktop — even when the browser is closed — are using the operating system’s notification system, not the browser’s pop-up system. This is an important distinction because it means ad blockers don’t stop them. You can have every extension active and every browser setting configured properly and still see these notifications, because they’re being delivered through the same channel Windows uses for its own system notifications. The only way to stop them is to revoke the permission that allows those websites to send them in the first place. We go deeper on the whole subject in our Google Chrome Errors.
The fix is almost always in one place: Chrome’s notification permissions list. Most of these notifications come from sites you accidentally granted permission to — often by clicking “Allow” on a prompt that looked like a cookie consent or age verification form rather than a notification permission request.
Find the Source and Revoke the Permission
Before changing anything, look at the next notification that appears. In the bottom-right corner of the notification, there’s usually a small URL or site name — that’s the source. Write it down. It’s often something generic-sounding like “news-update.net” or “securealert.co” rather than a site you’d recognise.
Now go to: Chrome Settings → Privacy and security → Site settings → Notifications. This page lists every website that has permission to send you notifications. Scroll through it carefully. Any site you don’t explicitly recognise or use — remove it. Click the three dots next to the entry → Remove (or Block). Be thorough: some adware notification operations run through multiple domains simultaneously.
If you want to block all website notifications entirely (which is a perfectly reasonable choice if you don’t rely on any), click the toggle next to “Sites can ask to send notifications” to disable it. From that point, no website can request notification permission. You can still manually grant permission to specific trusted sites by clicking the padlock icon in Chrome’s address bar on those sites.
Why Standard Ad Blockers Can’t Stop This
Push notifications that arrive via the OS notification system bypass Chrome’s rendering engine entirely once permission is granted. Ad blockers work by intercepting requests as pages load — but a push notification that’s already been sent doesn’t go through the browser’s page loading process. It goes directly to Windows Notification Service (WNS), which is why you see them even when Chrome is in the background or completely closed.
Some specialised privacy extensions (uBlock Origin with specific filter lists, or Consent-O-Matic) do prevent notification permission prompts from appearing in the first place — they block the permission request dialog before it shows up. But they can’t retroactively remove permissions that were already granted before those extensions were installed. Only removing the permission from Chrome’s settings does that.
Check for Suspicious Extensions
Some adware extensions work specifically by redirecting users to notification permission pages without making it obvious what’s happening. If you were recently prompted to allow notifications on a site you don’t remember visiting, an extension may have opened that page in the background. Go to chrome://extensions and look for anything you don’t remember installing — particularly anything with vague names like “Browser Helper,” “Shopping Assistant,” “Video Player Pro,” or any extension you can’t attribute to a specific intentional installation.
Remove anything suspicious. Don’t just disable — remove. Some adware extensions reinstall themselves when re-enabled, and the background process that opens notification permission pages continues running even when the extension appears disabled.
Stop Chrome Running in the Background
Notifications arriving when Chrome is completely closed are coming from Chrome’s background process. Even after all windows are closed, Chrome keeps running to serve push notifications and Chrome apps. Settings → System → toggle off “Continue running background apps when Google Chrome is closed.” After making this change, closing Chrome actually stops all Chrome processes, and no further notifications can arrive until Chrome is reopened.
Adjust Windows Notification Settings
Windows itself has a layer of notification control independent of Chrome. Settings → System → Notifications → scroll to the list of apps and find Google Chrome. You can toggle Chrome notifications off entirely here, limit how many Chrome notifications appear, or change their behaviour (banner only, with no sound). This is a useful belt-and-suspenders approach — even if a site retains Chrome permission, Windows won’t display the notification if Chrome notifications are disabled at the OS level.
Focus Assist (Windows 10) or Do Not Disturb (Windows 11) suppresses all notifications during set times or activities. Settings → System → Focus (Windows 11) or Focus Assist (Windows 10) → configure rules to automatically suppress notifications during work hours or specific activities. This doesn’t remove the underlying permissions but prevents notification interruptions during productive periods.
Scan for Adware
If notifications continue appearing from multiple domains even after removing permissions — or if removed permissions reappear — adware is likely present at the system level and is automatically re-granting notification permissions through Chrome’s policy system. Chrome Settings → Reset and clean up → Clean up computer → Find. Run this scan, then also run Malwarebytes (free tier) for a broader adware sweep. System-level adware that grants Chrome permissions through registry or group policy entries won’t be visible in the extensions list but will be found by these tools.
Reset Chrome Notification Settings
If the notification permissions list is very long and removing entries individually is impractical, a Chrome settings reset clears all notification permissions at once alongside other browser settings: Settings → Reset settings → Restore settings to their original defaults. Bookmarks and synced passwords are preserved. All notification permissions are cleared. After the reset, only grant notifications to sites you specifically and deliberately want to hear from.
After resetting, enabling Chrome’s “Quieter notification requests” setting prevents most abusive sites from even showing the permission dialog: Settings → Privacy and security → Site settings → Notifications → toggle “Use quieter messaging (blocks notification prompts on sites known to send spammy notifications).” This Chrome feature is specifically designed to identify and suppress notification requests from sites with high permission-grant-to-report ratios.
Creating a New Profile
If notification problems persist through settings reset — which is rare — the Chrome profile data itself may have stored notification permissions in a way that resists the UI-level reset. Creating a new profile starts with completely clean permission sets. Profile icon → Add → Continue without signing in → test. If no spurious notifications appear in the new profile, the old profile’s data was the issue. Sign into your Google account in the new profile to restore sync data, and don’t import old cookies or site data from the old profile.
Our guide on Chrome opening new tabs automatically covers the closely related problem of tab hijacking, which often occurs alongside notification spam from the same adware sources. For Chrome extensions specifically related to this issue, the Chrome extensions guide covers how to audit and remove problematic extensions comprehensively. The Google Chrome security documentation includes a dedicated section on notification abuse with instructions for reporting sites that exploit the push notification system.
One practical tip that prevents this from happening again: when any website shows a notification permission prompt, there’s now a keyboard shortcut to dismiss it without granting permission. Press Escape rather than clicking the X button — Escape always dismisses the prompt and denies permission, while clicking the X sometimes counts as “dismiss but maybe ask again later” depending on the site’s implementation. Getting into the habit of pressing Escape on permission prompts from sites you didn’t intentionally set up for notifications prevents the permission list from growing in the first place.
Chrome’s notification permission system has a “Previously denied” list as well as a “Permitted” list — and this is worth checking when sites that you thought you blocked keep appearing in your notification tray. Sites with a “Block” permission entry should never be able to send notifications, but if a site appears in both the block list and continues generating notifications, the site may be accessing your Chrome instance through a different domain that doesn’t have a block entry. Many ad notification operations run through rotating subdomains — blocking “news.spam-site.com” doesn’t block “alerts.spam-site.com” if that’s a different entry in Chrome’s permissions list. Searching through the full permissions list for partial domain matches is the thorough way to ensure a specific operator is fully blocked across all their notification domains.
Enterprise Chrome deployments add a complicating layer to notification management. On domain-joined machines, Chrome policies set by IT can force-allow notifications from specific sites, and user-level notification settings may not be able to override those policies. If you’re seeing persistent notifications on a work machine and the Chrome settings show notification permissions you can’t remove (they appear greyed out or reappear after removal), they may be policy-set rather than user-granted. Check chrome://policy to see what notification-related policies are active. In enterprise contexts, the fix belongs with IT rather than with Chrome settings changes.
Website notifications that appear as Windows toast notifications (the rectangular popups in the bottom-right) versus notifications that appear as browser-internal alerts look similar but behave differently. True Windows toast notifications from Chrome — coming through the OS notification system — appear in the Windows Notification Center (the bell icon in the taskbar or swipe from the right edge on touchscreens). Browser-internal pop-up alerts (generated by JavaScript’s alert() or confirm() functions) appear only while the browser window is in focus and don’t persist in the Notification Center. If you can’t find a notification source in Chrome’s permissions list and the alerts appear only while actively using Chrome on specific sites, they may be JavaScript dialog alerts rather than push notifications — which are controlled differently. Chrome Settings → Privacy and security → Site settings → Intrusive ads can help suppress sites that use invasive dialog-based notifications alongside banner ads.
The “Notify after first visit” behavior Chrome uses for notification prompts is a significant contributor to accidental permission grants. Chrome sometimes shows notification permission prompts after a single visit to a new site, before the user has enough context about whether the site is trustworthy. Many users reflexively click “Allow” on any dialog that appears — a habit cultivated by years of GDPR cookie consent dialogs — and accidentally grant notification permissions as a result. Awareness of what the notification permission dialog looks like (it has a bell icon and explicitly says “wants to send notifications” in most browsers) helps distinguish it from cookie consent and other prompts. If you notice this prompt on an unfamiliar site, clicking “Block” or pressing Escape is always the safe choice until you’ve determined the site is legitimately useful and its notifications would be welcome.
Mobile Chrome notification management follows the same principle but the settings location differs. On Android Chrome: three-dot menu → Settings → Site settings → Notifications → review and remove permissions. On iOS Chrome: the notification permission is managed at the OS level (iOS Settings → Chrome → Notifications) rather than within Chrome itself, because iOS handles push notification permissions differently from Android and desktop systems. If you’re troubleshooting Chrome notification spam across multiple devices with Chrome Sync enabled, note that notification permissions are not synced between devices — permissions granted on desktop Chrome do not carry to mobile Chrome. Each device maintains its own permission list and requires its own cleanup.
Scheduled notification delivery is a feature that some legitimate sites (news sites, sports apps, calendar services) use genuinely, and these are worth distinguishing from spam-source notifications before removing all permissions indiscriminately. Before removing a notification permission for a site you do actually use, click through one of its notifications to see where it goes — legitimate sites like BBC News, ESPN, or Google Calendar send notifications that navigate to relevant content. Spam notification sites send notifications that navigate to ad pages, redirect chains, or fake security warnings. If clicking a notification opens useful content relevant to what you’d want from that site, it’s a legitimate notification you may want to keep. If it opens something unexpected, the site was abusing the permission and should be removed from the allowed list.
Service Worker registration is the underlying technology that enables web push notifications and explains why they persist even after clearing cookies. Service Workers are small JavaScript programs that continue running in the browser background even when a site’s page is closed. When a site registers a Service Worker for push notifications, the Worker persists until explicitly unregistered — clearing cookies doesn’t remove it. To fully remove a site’s notification capability including its Service Worker, go to Chrome Settings → Privacy and security → Site settings → Notifications, remove the site’s permission, and then also go to Settings → Privacy and security → Site settings → All sites, find the site, click on it, and click “Clear data and reset permissions” to remove the Service Worker registration. This two-step approach ensures the site can’t continue sending notifications through a previously registered Service Worker even after you’ve removed its listed notification permission. You might also run into Stop Chrome Tabs From Reloading.
