Do I need to allow notifications globally?

No. Keep the global setting on "Ask" and allow only the sites you trust.

Why do notifications arrive late on macOS?

Focus modes and Low Power Mode can defer delivery. Turn them off for real-time alerts.

Can VPNs or firewalls block push?

Rarely. Web push typically uses HTTPS. If you suspect it, test briefly on another network to isolate the network path.

Fix Browser Notifications Not Working in Chrome, Edge, or Firefox (Run the Notifications Test)

Confirm permission with the Notifications Test

Open the Notifications Test. Click Request permission. You should see a browser prompt and then a sample notification. If the button is greyed out or no prompt appears, keep the tab open, apply each fix, and rerun the test. Real-world symptoms: no alerts from Gmail or Slack, or notifications that only appear after you reopen the tab.

Fix 1: Allow notifications for the site

Click the lock icon in the address bar on the affected site and set Notifications to Allow.
Chrome/Edge: Settings > Privacy and security > Site settings > Notifications → move the site from Blocked to Allowed.
Firefox: Settings > Privacy & Security > Permissions > Notifications → click Settings and allow the site.
Reload and retry the Notifications Test.

Fix 2: Check OS-level notification toggles

The OS can block alerts even when the browser allows them.

Windows 10/11: Settings > System > Notifications → turn Notifications On, then enable them for your browser in the app list.
macOS: System Settings > Notifications → select your browser and enable Allow Notifications. Turn off Deliver quietly.
Linux (GNOME/KDE): ensure Do Not Disturb is off in the notification shade and that the browser is allowed to show popups.

Fix 3: Disable Do Not Disturb / Focus Assist

Focus modes silence notifications silently.

Turn off Do Not Disturb or Focus Assist on Windows/macOS.
On macOS, check scheduled Focus modes under Focus settings and disable them temporarily.
Retest with the Notifications Test.

Fix 4: Keep the site active in the background

Some sites rely on service workers to deliver push while the tab is idle.

Pin the tab or install the site as a PWA so it can run in the background.
Avoid closing the last window of the browser; background notifications stop when the browser fully quits unless the site is installed as an app.

Fix 5: Clear blocked permission state

If you dismissed the prompt before, the browser remembers.

In Chrome/Edge, click the reset option inside Site settings for the domain.
In Firefox, remove the entry from Notifications settings, then reload and allow again.

Fix 6: Check extension conflicts

Notification blockers, privacy filters, or user-agent spoofers can stop web push registrations.

Disable extensions that change headers or block service workers.
Try the site in Incognito/InPrivate (extensions off). If notifications appear, keep the conflicting extension off or add an allowlist rule.

Fix 7: Verify service worker registration

If you are comfortable with DevTools:

Open DevTools > Application > Service Workers on the site.
Ensure a worker is Running and Push is Subscribed.
Click Update if the worker is outdated, then retest.

Fix 8: Battery saver and background restrictions

Battery saver modes may pause background tasks.

Disable Battery saver on Windows or macOS Low Power Mode while expecting alerts.
On laptops, keep the browser allowed to run in the background (Chrome/Edge: System and performance > Continue running background apps when browser is closed).

Verify the fix

Run the Notifications Test again. You should see the prompt and a delivered test notification. Then trigger a notification from your app (send yourself a Slack test message or calendar reminder). If managed device policies block notifications, you will see it in chrome://policy; provide that line to IT for changes.