Netlify Blobs

This is Netlify's zero-config object storage for files and assets like images, documents, uploads, and cached artifacts. It's available across all Netlify compute contexts without provisioning. The skill covers getStore(), CRUD operations, metadata handling, and the important distinction between site-scoped and deploy-scoped stores. The most useful bit here is the clear guidance on what Blobs is not for: if you need to store queryable records or application state, you want Netlify Database instead. Reach for this when you're dealing with actual file blobs, not structured data. Includes local development setup and the common "environment not configured" error fix.

skills.sh installs: 3.3K
GitHub stars: 51
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add netlify/context-and-tools --skill netlify-blobs --agent claude-code

Installs into .claude/skills of the current project.

Files

Netlify Blobs

Modern syntax: import from @netlify/blobs, open a store, then call methods on the handle.

import { getStore, getDeployStore, listStores } from "@netlify/blobs";
import type { Context } from "@netlify/functions"; // or "@netlify/edge-functions"

In Functions, Edge Functions, and Build Plugins, siteID, deployID, token (and region for getDeployStore) are injected automatically. Install with npm install @netlify/blobs.

Not a database. For dynamic, per-user, transactional, or relational data, use Netlify DB. Blobs is for objects, files, and cache-like state. It is optimized for frequent reads and infrequent writes.

Store scope is a footgun. Read this first. getStore opens a site-wide store shared across ALL deploy contexts. Code on a deploy preview reads, overwrites, and deletes production data. Never run destructive tests or seed throwaway data from a preview against a site-wide store. Use getDeployStore() or a context-specific store name for isolation.