Chrome Extension Service Worker vs Background Page

Chrome extension service worker vs background page

Short answer

A Manifest V2 background page can stay loaded persistently. A Manifest V3 service worker is event-driven and can be stopped when idle, then restarted when an event arrives. Both can coordinate extension behavior and make network requests, so the privacy review focuses on what they do, not only on the lifecycle model.

Lifecycle and state

A persistent background page keeps in-memory state for the life of the browser session. A service worker is suspended when idle, so extensions must persist important state in storage and reinitialize on wake.

The service worker model reduces idle resource use. It does not inherently reduce access to APIs, pages or network endpoints.

Background execution models
Aspect	Background page (V2)	Service worker (V3)
Lifecycle	Can remain loaded	Event-driven, may stop
State	In-memory state persists	State must be persisted separately
Network access	Available	Available
Manifest field	background.page or scripts	background.service_worker
Browser direction	Legacy	Current Chromium model

What to inspect in either model

Read the background script or worker for network calls, storage access, message handling and remote code references. Check whether it registers event listeners that observe tabs, history, web requests or cookies.

The analyzer reports the background type, service worker or script paths, and static findings from the referenced files. It also shows the update URL and CSP, which affect what can change later.

Privacy does not follow the manifest version

A service worker can be just as invasive as a background page if it has broad permissions and sends data to third parties. A legacy background page can be carefully scoped and transparent.

Use the lifecycle as context, not as a safety label. Pay attention to what data the background context can reach and where it sends it.

Frequently asked questions

Is a service worker more secure than a background page?

The service worker model is newer and aligns with Manifest V3 restrictions, but security depends on permissions, code and data handling. The lifecycle alone does not determine safety.

Can a service worker make network requests?

Yes. It can use fetch and related APIs subject to permissions, CSP and host access. Network access is available in both models.

Why does a V3 extension still have background scripts?

Firefox and cross-browser manifests can declare background scripts. Chromium primarily uses service_worker, but manifests may include compatibility entries.

Last reviewed: October 31, 2026