package
The Vercel Blob JavaScript API client
npm install @vercel/blobGitHub-flavored package documentation.
Across all versions.
Download trend unavailable.
Runtime metadata.
The Vercel Blob JavaScript API client.
👉 Quickstart — SDK Reference 👈
npm install @vercel/blobWe have examples on the vercel.com documentation, there are two ways to upload files to Vercel Blob:
Make sure to include a changeset in your PR. You can do this by running:
pnpm changeset
git commit -am "changeset"
git pushOnce such a commit gets merged in main, then GitHub will open a versioning PR you can merge. And the package will be automatically published to npm.
@vercel/blob reads the token from the environment variables on process.env. In general, process.env is automatically populated from your .env file during development, which is created when you run vc env pull. However, Vite does not expose the .env variables on process.env.
You can fix this in one of following two ways:
process.env yourself using something like dotenv-expand:pnpm install --save-dev dotenv dotenv-expand// vite.config.js
import dotenvExpand from 'dotenv-expand';
import { loadEnv, defineConfig } from 'vite';
export default defineConfig(({ mode }) => {
// This check is important!
if (mode === 'development') {
const env = loadEnv(mode, process.cwd(), '');
dotenvExpand.expand({ parsed: env });
}
return {
...
};
});$env/static/private:import { put } from '@vercel/blob';
+ import { BLOB_TOKEN } from '$env/static/private';
const blob = await head("filepath", {
- token: '<token>',
+ token: BLOB_TOKEN,
});Latest published Nov 9, 2026
latest
snapshot
matt.straka
matt.j.straka@gmail.com
Estimated unpacked size across 14 packages.
10.1 MB
Includes dependencies.
6 direct · 3 outdated
^6.23.0
8.12.4
^2.0.5
2.0.5
^2.1.0
3.0.0
^1.3.3
1.3.3
^3.6.1
4.0.9
^1.2.0
1.2.0