Brave push notifications: why they fail and how to fix it
Brave is privacy-first, and that includes push. On desktop, subscribing to web push usually fails until you turn on one setting that uses Google’s push messaging service. Here’s what it does, the trade-off, and what site owners can do.
- On Brave desktop, PushManager.subscribe() commonly fails with “Registration failed – push service error”.
- Fix: brave://settings/privacy → turn on “Use Google services for push messaging”, then relaunch Brave.
- Brave’s help centre describes it as allowing the browser to send and display push notifications; Brave keeps it off by default.
- Sites can’t change this setting — detect the error and tell Brave users what to do.
Why it fails by default
Chromium-based browsers deliver web push through Google’s push messaging service (the endpoints you see start with fcm.googleapis.com). Brave turns that connection off by default to limit calls to Google services. With it off, a site can show its own prompt and the browser can even grant notification permission, but creating the push subscription fails with an AbortError such as “Registration failed – push service error”. Brave community threads going back to 2019 describe exactly this behaviour.
Turn it on
- Open
brave://settings/privacy(Settings → Privacy and security). - Turn on Use Google services for push messaging.
- Relaunch Brave when prompted — some users report the setting only sticks after a full relaunch.
- Reload the site and subscribe again.
The privacy trade-off
Push messages are end-to-end encrypted between the site and your browser (RFC 8291), so the push service can’t read their content. It does see that a message was delivered to your browser’s endpoint, and the setting lets Brave register with Google’s infrastructure. Whether that’s acceptable is your call; many Brave users enable it only for the handful of sites they rely on and keep other privacy protections on.
Brave on Android and iOS
Behaviour on Android can differ from desktop by version; if subscribing fails, look for the same push messaging option and check Android’s notification settings for Brave. On iPhone and iPad, all browsers use Apple’s WebKit, and web push only works for sites added to the Home Screen on iOS 16.4+ (iPhone steps).
A friendly Brave hint
Show this only after a subscription attempt fails in Brave, never as the first thing a visitor sees. Most Brave users who want notifications are happy to flip the switch once they know why.
Testing in Brave
- Try subscribing with the setting off — confirm your site shows a helpful message rather than failing silently.
- Turn the setting on, relaunch Brave and subscribe again.
- Send a test notification and check OS notification settings for Brave.
For site owners
You can’t flip this setting for visitors, but you can handle it gracefully. Brave exposes navigator.brave, so you can detect it and show a short hint when subscription fails:
try {
await reg.pushManager.subscribe({ userVisibleOnly: true, applicationServerKey: KEY });
} catch (e) {
if (navigator.brave && await navigator.brave.isBrave()) {
showHint('In Brave, enable “Use Google services for push messaging” in brave://settings/privacy, then relaunch.');
}
}With Pusharoo, listen for the pusharoo:permission event and check Pusharoo.state() after an Allow to decide when to show such a hint (JavaScript API).
Questions
Why do push notifications not work in Brave?
On desktop, Brave disables Google’s push messaging service by default, which Chromium uses to deliver web push. Turn on “Use Google services for push messaging” in brave://settings/privacy and relaunch.
Is enabling push messaging in Brave safe?
Message contents stay encrypted end-to-end; the push service only handles delivery. It’s a privacy trade-off rather than a security risk.
Can a website enable it for me?
No. Only you can change the setting; sites can only explain how.
Does Brave block push notifications from all sites?
Brave doesn’t block the permission itself, but on desktop it disables the Google push messaging service that delivers web push in Chromium, so subscriptions usually fail until you turn that setting on.
Do notifications work in Brave private windows?
Like most browsers, Brave doesn’t keep push subscriptions in private windows. Subscribe in a normal window.
Keep reading
Chrome push notifications: a complete guide
How Chrome asks, its quieter permission UI, settings on desktop and Android, background delivery and testing.
Web push notifications not working? Fix it by symptom
Symptom-by-symptom fixes: no prompt, blocked permission, nothing arrives, iPhone issues and worker caching.
The Web Push protocol, explained
RFC 8030 delivery headers, RFC 8291 encryption, RFC 8292 VAPID, status codes and payload size.
How to test web push notifications
A live demo, DevTools push buttons, sending to yourself, iPhone checks and a pre-launch checklist.
More in Browsers & devices: Firefox push notifications: how they work · Safari push notifications on the Mac · Microsoft Edge push notifications · Web push notifications on Android · PWA push notifications on iOS and Android · How to turn off website notifications · Samsung Internet notifications, explained · Push notifications in Opera and Opera GX · Website notifications on a Chromebook · How to get website notifications on your iPhone · All guides
Free for life. No limits.
Unlimited subscribers, campaigns and automations. No badges. About five minutes to install.