vercel-blob

Client-side uploads use presigned tokens generated on your server, which you pass to the browser. This approach avoids exposing your BLOB_READ_WRITE_TOKEN. Generate a token via a server action, send it to the client, then upload directly from the browser using @vercel/blob's client methods.

Use path prefixes to organize files logically—for example, avatars/ for user profile images and uploads/ for general user content. Prefixes make it easier to list, manage, and apply consistent access policies to groups of related files.

Yes. Validate both file size and content-type on the server before calling put() or issuing a client token. This prevents invalid uploads, reduces wasted storage and bandwidth, and enforces security boundaries.

Vercel Blob automatically caches uploaded files on Vercel's CDN. Files are delivered with caching headers, so repeated requests serve from edge locations near users instead of origin, reducing latency and load.

No. Never expose BLOB_READ_WRITE_TOKEN to the browser. Instead, generate short-lived presigned tokens on the server and send only those to the client for uploads, maintaining security and access control.

Vercel Blob supports listing files in storage, downloading files, deleting files, and multipart uploads for large files. These operations integrate with the same storage backend and CDN delivery system.