A worker is an object created using a constructor (e.g.,Worker()) that runs a named JavaScript file — this file contains the code that will run in the worker thread.

In addition to the standardJavaScript set of functions (such asString,Array,Object,JSON, etc.), you can run almost any code you like inside a worker thread. There are some exceptions: for example, you can't directly manipulate the DOM from inside a worker, or use some default methods and properties of theWindow object. For information about the code that youcan run seesupported functions, andsupported Web APIs.

Data is sent between workers and the main thread via a system of messages — both sides send their messages using thepostMessage() method, and respond to messages via theonmessage event handler (the message is contained within themessage event'sdata property). The data is copied rather than shared.

Workers may in turn spawn new workers, as long as those workers are hosted within the sameorigin as the parent page.

In addition, workers can make network requests using thefetch() orXMLHttpRequest APIs (although note that theresponseXML attribute ofXMLHttpRequest will always benull).

There are a number of different types of workers:

• Dedicated workers are workers that are utilized by a single script. This context is represented by aDedicatedWorkerGlobalScope object.
• Shared workers are workers that can be utilized by multiple scripts running in different windows, IFrames, etc., as long as they are in the same domain as the worker. They are a little more complex than dedicated workers — scripts must communicate via an active port.
• Service Workers essentially act as proxy servers that sit between web applications, the browser, and the network (when available). They are intended, among other things, to enable the creation of effective offline experiences, intercept network requests and take appropriate action based on whether the network is available, and update assets residing on the server. They will also allow access to push notifications and background sync APIs.

WhileWindow is not directly available to workers, many of the same methods are defined in a shared mixin (WindowOrWorkerGlobalScope), and made available to workers through their ownWorkerGlobalScope-derived contexts:

• DedicatedWorkerGlobalScope for dedicated workers
• SharedWorkerGlobalScope for shared workers
• ServiceWorkerGlobalScope forservice workers

Worker

Represents a running worker thread, allowing you to pass messages to the running worker code.

WorkerLocation

Defines the absolute location of the script executed by theWorker.

SharedWorker

Represents a specific kind of worker that can be accessed from severalbrowsing contexts (i.e., windows, tabs, or iframes) or even other workers.

WorkerGlobalScope

Represents the generic scope of any worker (doing the same job asWindow does for normal web content). Different types of worker have scope objects that inherit from this interface and add more specific features.

DedicatedWorkerGlobalScope

Represents the scope of a dedicated worker, inheriting fromWorkerGlobalScope and adding some dedicated features.

SharedWorkerGlobalScope

Represents the scope of a shared worker, inheriting fromWorkerGlobalScope and adding some dedicated features.

WorkerNavigator

Represents the identity and state of the user agent (the client).

We have created a couple of demos to show web worker usage:

• Basic dedicated worker example (run dedicated worker).
• Basic shared worker example (run shared worker).
• OffscreenCanvas worker example (run OffscreenCanvas worker).

You can find out more information on how these demos work inUsing Web Workers.

• Using Web Workers
• Worker interface
• SharedWorker interface
• Service Worker API