\n 👉 \n \n Quickstart\n — \n \n SDK Reference\n \n 👈\n \n
\n\n---\n\n## Installation\n\n```sh\nnpm install @vercel/blob\n```\n\n## Quickstart\n\nWe have examples on the vercel.com documentation, there are two ways to upload files to Vercel Blob:\n\n1. [Server uploads](https://vercel.com/docs/vercel-blob/server-upload): This is the most common way to upload files. The file is first sent to your server and then to Vercel Blob. It's straightforward to implement, but you are limited to the request body your server can handle. Which in case of a Vercel-hosted website is 4.5 MB. **This means you can't upload files larger than 4.5 MB on Vercel when using this method.**\n2. [Client uploads](https://vercel.com/docs/vercel-blob/client-upload): This is a more advanced solution for when you need to upload larger files. The file is securely sent directly from the client (a browser for example) to Vercel Blob. This requires a bit more work to implement, but it allows you to upload files up to 5 TB.\n\n## Releasing\n\nMake sure to include a changeset in your PR. You can do this by running:\n\n```sh\npnpm changeset\ngit commit -am \"changeset\"\ngit push\n```\n\nOnce 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.\n\n## A note for Vite users\n\n`@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.`\n\nYou can fix this in **one** of following two ways:\n\n1. You can populate `process.env` yourself using something like `dotenv-expand`:\n\n```shell\npnpm install --save-dev dotenv dotenv-expand\n```\n\n```js\n// vite.config.js\nimport dotenvExpand from 'dotenv-expand';\nimport { loadEnv, defineConfig } from 'vite';\n\nexport default defineConfig(({ mode }) => {\n // This check is important!\n if (mode === 'development') {\n const env = loadEnv(mode, process.cwd(), '');\n dotenvExpand.expand({ parsed: env });\n }\n\n return {\n ...\n };\n});\n```\n\n2. You can provide the credentials explicitly, instead of relying on a zero-config setup. For example, this is how you could create a client in SvelteKit, which makes private environment variables available via `$env/static/private`:\n\n```diff\nimport { put } from '@vercel/blob';\n+ import { BLOB_TOKEN } from '$env/static/private';\n\nconst blob = await head(\"filepath\", {\n- token: '