Vercel Blob examples

Vercel Blob supports range requests for partial downloads. This means you can download only a portion of a blob, here are examples:

You can track the upload progress when uploading blobs with the callback:

is available on and methods.

Every Vercel Blob operation can be canceled, just like a fetch call. This is useful when you want to abort an ongoing operation, for example, when a user navigates away from a page or when the request takes too long.

If you want to delete all the blobs in your store you can use the following code snippet to delete them in batches. This is useful if you have a lot of blobs and you want to avoid hitting the rate limits.

Either execute this code in a Vercel Cron Job, as a serverless function or on your local machine.

While there's no native backup system for Vercel Blob, here are two ways to backup your blobs:

1. Continuous backup: When using Client Uploads you can leverage the callback from the server-side function to save every Blob upload to another storage.
2. Periodic backup: Using Cron Jobs and the Vercel Blob SDK you can periodically list all blobs and save them.

Here's an example implementation of a periodic backup as a Cron Job:

This script optimizes the process by streaming the content directly from Vercel Blob to the backup storage, avoiding buffering all the content into memory.

You can split your backup process into smaller chunks if you're hitting an execution limit. In this case you would save the to a database and resume the backup process from where it left off.