Common symptoms
- A web app cannot work offline
- Install or push features are missing
- Service Worker works in one browser but not an embedded in-app view
Possible causes
- The page is not served through HTTPS
- An older browser or restricted embedded browser lacks support
- Private mode or an enterprise policy limits registration
- The website's own Service Worker file or scope is misconfigured
How to diagnose it
- Run Browser Feature Test in a full current browser
- Confirm the address uses HTTPS
- Compare normal and private browsing contexts
- If you own the site, inspect registration errors in developer tools
Solutions to try
- Open the link in a full supported browser
- Use HTTPS for every production page and asset
- Update the browser and operating system
- Site owners should correct scope, MIME type, caching, and registration errors
Frequently asked questions
Is missing Service Worker a device hardware problem?
No. It is a browser-context or site-delivery capability, not a CPU, memory, or GPU fault.
Does every website need a Service Worker?
No. It is useful for offline, caching, push, and installable experiences, but many ordinary websites work correctly without one.