vercel-storage

Guides selection, configuration, and migration of Vercel Blob, Global Config, and Marketplace storage services.

Updated Aug 21, 2025
One-click install
npx skills add https://github.com/Adithiya-S/AI-Study-Companion --skill vercel-storage-adithiya-s
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-storage
Source: https://github.com/Adithiya-S/AI-Study-Companion/tree/main/.agents/skills/vercel-storage
Command: npx skills add https://github.com/Adithiya-S/AI-Study-Companion --skill vercel-storage-adithiya-s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing and configuring the right data storage for a Vercel application is confusing, especially since @vercel/postgres and @vercel/kv are sunset and Edge Config was renamed to Global Config. This Skill provides expert guidance on which storage product to use, how to provision it, and how to migrate away from deprecated packages. ## Core Features & Use Cases - Storage Selection Guidance: Decision matrix mapping needs (file uploads, feature flags, relational data, caching) to the correct product: Vercel Blob, Global Config, Neon Postgres, Upstash Redis, Supabase, Prisma, MongoDB Atlas, Convex, or Turso. - Deprecation Detection & Migration: Detects usage of sunset packages (@vercel/postgres, @vercel/kv, @vercel/edge-config) and provides drop-in migration paths to @neondatabase/serverless, @upstash/redis, and @vercel/global-config. - Provisioning Workflows: Covers Vercel Marketplace installation via vercel integration add, automatic environment variable provisioning, and fallback manual setup with vercel env pull. - Use Case: You are building a Next.js app that needs file uploads and a Postgres database. The Skill directs you to install @vercel/blob for media and provision Neon Postgres through the Marketplace with lazy initialization to avoid build-time crashes. ## Quick Start Ask the assistant to help you choose and set up the right Vercel storage option for your project, such as adding Neon Postgres or migrating off @vercel/kv.

Frequently Asked Questions about vercel-storage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate from @vercel/postgres to Neon?

Replace @vercel/postgres with @neondatabase/serverless by importing neon() and initializing it with DATABASE_URL. For minimal changes, use @neondatabase/vercel-postgres-compat, which provides API-compatible wrappers for existing @vercel/postgres imports.

What replaces @vercel/kv for Redis on Vercel?

@upstash/redis replaces the sunset @vercel/kv package. Install it via the Vercel Marketplace with `vercel integration add upstash`, then use Redis.fromEnv() which reads the auto-provisioned UPSTASH_REDIS_REST_URL and TOKEN environment variables.

Which Vercel storage should I use for file uploads?

Use Vercel Blob (@vercel/blob) for file uploads, media, and documents. It supports public and private access modes, client-side uploads up to 5 TB, and automatic routing between latency-optimized and volume-optimized delivery.

Why does my Neon database connection crash during next build?

The neon() call throws when DATABASE_URL is unset, and Next.js evaluates top-level module code at build time. Use lazy initialization with a getDb() function that creates the connection on first call instead of at module load.

Is @vercel/edge-config still supported?

Edge Config was renamed to Global Config, and @vercel/global-config is a drop-in replacement that reads both GLOBAL_CONFIG and EDGE_CONFIG environment variables. The legacy package cannot read newly connected stores, so upgrade before connecting a new store.

When should I not use Vercel Global Config?

Do not use Global Config for user data, session state, or frequently written data. It is a read-optimized key-value store for configuration like feature flags and A/B test settings that must be read at the edge with near-zero latency.