Storage APIs: Downloading Files for Offline Access

In my ongoing adventure to build a personal media web app I keep finding new web APIs to make it more awesome. I’ve adopted the Internationalization API for natural sorting and relative dates and the Media Session API for native integration.

Next I’m improving my use of file storage APIs to download and cache audio files for offline playback. A feature that has long been a pain to implement.

Turtle is a little demo project I built to understand the new APIs.

Turtle UI screenshot

Keep reading to learn more!

Safari is back!

Previously my media app was using IndexedDB to store files. IndexedDB is not really designed for that nor it is a pleasant API to use. It was however the best method I found. Except for the time Safari 14 broke IndexedDB.

I use an iPhone so I’m stuck with Safari (WebKit) which has historically lagged behind on web standards support. Well not long after I had implemented an IndexedDB store, Safari 15.2 added some support for the StorageManager API. Now Safari 17 has improved support and removed the 1 GB limit:

Now, the origin quota is calculated based on total disk space. This means an origin generally gets a much higher limit, and users will no longer receive permission prompts in Safari.

The Storage APIs and OPFS (origin private file system) give websites access to file storage. This is perfect for my app to download and store audio (usually MP3 between 100–1000 MB). Safari on my iPhone reports over 38 GB quota via Safari 17 on macOS gives me over 76 GB. Firefox limits me to 10 GB.

Getting a list of files is as simple as:

const dir = await;
for await (const [key, value] of dir.entries()) {
  // Do something...

No more IndexedDB transactions and events! You will not be missed.

Stream Download Progress

Reading and writing files is almost as easy. You can even stream a file directly to storage and track download progress. I’ve whipped up a demo project. Find it at GitHub, CodePen, and deployed at

Safari doesn’t support createWritable for a writable stream (streams are seriously cool). It does support createSyncAccessHandle which is only available inside a Web Worker context (to avoid blocking the main thread). I created a worker that accepts a URL message and posts back download progress.

A reduced example of the worker code:

self.addEventListener('message', async (ev) => {

const download = async (url) => {
  const response = await fetch(url);
  // Get a readable stream and content length
  const reader = response.body.getReader();
  const length = Number.parseInt(response.headers.get('content-length'));

  // Create a new writable file handle
  const root = await;
  const handle = await root.getFileHandle('example', {create: true});
  const writer = await handle.createSyncAccessHandle();

  // Track read bytes as chunks are streamed
  let read = 0;
  while (true) {
    const {done, value} = await;
    if (done) break;
    read += value.length;
    self.postMessage({url, read, length});

  self.postMessage({url, length});

This was possible with IndexedDB before but you have to temporary store the chunks in memory before writing a Blob to the database.

My example code is missing all the error handling. One lazy approach would be to wrap the entire download function in a try/catch statement and post back an error message.

A neat trick is to use an AbortController that allows you to cancel the download.

try {
  const controller = new AbortController();
  const response = await fetch(url, {signal: controller.signal});
} catch (err) {
  // When abort() is called, the fetch() promise rejects with
  // an Error of type DOMException, with name AbortError.
// Cancel the download

Good stuff!

The only bad thing about these APIs is their names. There is the “Web Storage API”, aka “Storage”, which is the key/value local & session storage. The “Storage API” and the “File System API” which seem to overlap. The “Storage Standard” which attempts to consolidates them all into one API to rule them all, including the IndexedDB and Cache APIs, I think.

Check out my demo at to see it in action.

You can find my media player meSonic² on GitHub (beware: work in progress!)