Missed the action at the 2018 Chrome Dev Summit? Catch up with our playlist on the Google Chrome Developers channel on YouTube. Watch now.

Workbox Strategies

What are Workbox Strategies?

When service workers were first introduced, a set of common caching strategies emerged. A caching strategy is a pattern that determines how a service worker generates a response after receiving a fetch event.

workbox-strategies provides the most common caching strategies so it’s easy to apply them in your service worker.

We won’t go into much detail outside of the strategies supported by Workbox, but you can learn more in the Offline Cookbook.

Using Strategies

In the following examples we’ll show you how to use the Workbox caching strategies with workbox-routing. There are some options you can define with each strategy that is covered in the Configuring Strategies section of this doc.

In the Advanced Usage section we’ll cover how you can use the caching strategies directly without workbox-routing.


Stale While Revalidate Diagram

The stale-while-revalidate pattern allows you to respond the request as quickly as possible with a cached response if available, falling back to the network request if it’s not cached. The network request is then used to update the cache.

This is a fairly common strategy where having the most up-to-date resource is not vital to the application.

  new RegExp('/images/avatars/'),

Cache First (Cache Falling Back to Network)

Cache First Diagram

Offline web apps will rely heavily on the cache, but for assets that are non-critical and can be gradually cached, a cache first is the best option.

If there is a Response in the cache, the Request will be fulfilled using the cached response, the network will not be used at all. If there isn't a cached response, the Request will be fulfilled by a a network request and the response will be cached so that the next request is served directly from the cache.

  new RegExp('/styles/'),

Network First (Network Falling Back to Cache)

Network First Diagram

For requests that are updating frequently, the network first strategy is the ideal solution. By default it will try and fetch the latest request from the network. If the request is successful, it’ll put the response in the cache. If the network fails to return a response, the caches response will be used.

  new RegExp('/social-timeline/'),

Network Only

Network Only Diagram

If you require specific requests to be fulfilled from the network, the network first is the strategy to use.

  new RegExp('/admin/'),

Cache Only

Cache Only Diagram

The cache only strategy ensures that requests are obtained from a cache. This is less common in workbox, but can be useful if you have your own precaching step.

  new RegExp('/app/v2/'),

Configuring Strategies

All of the strategies allow you to configure:

  • The name of the cache to use in the strategy.
  • Cache expiration restrictions to use in the strategy.
  • An array of plugins that will have their lifecycle methods called when fetching and caching a request.

Changing the Cache Used by a Strategy

You can change the cache a strategy used by supplying a cache name. This is useful if you want to separate out your assets to help with debugging.

  new RegExp('/images/'),
    cacheName: 'image-cache',

Using Plugins

Workbox comes with a set of plugins that can be used with these strategies.

  • workbox.expiration.Plugin
  • workbox.cacheableResponse.Plugin
  • workbox.broadcastUpdate.Plugin
  • workbox.backgroundSync.Plugin

To use any of these plugins (or a custom plugin), you just need to pass in instances to the plugins option.

  new RegExp('/images/'),
    cacheName: 'image-cache',
    plugins: [
      new workbox.expiration.Plugin({
        // Only cache requests for a week
        maxAgeSeconds: 7 * 24 * 60 * 60,
        // Only cache 10 requests.
        maxEntries: 10,

Advanced Usage

If you want to use the strategies in your own fetch event logic you can use use the strategy classes to run a request through a specific strategy.

For example, to implement the stale-while-revalidate class you can do the following:

self.addEventListener('fetch', (event) => {
  if (event.request.url === '/') {
    const staleWhileRevalidate = new workbox.strategies.StaleWhileRevalidate();

You can find the list of available classes in the workbox-strategies reference docs.