Vercel · v0
Vercel · source page ↗ · last checked Jul 6, 2026, 12:00 AM
Current pricing
captured Jul 6, 2026, 12:00 AM- Deploy apps to Vercel
- Edit visually with Design Mode
- Sync with GitHub
- $5 of included monthly credits
- 7 messages/day limit
- Purchase additional credits shared across your team
- Centralized billing
- Share chats and collaborate with your team
- $30 of included monthly credits per user
- $2 of free daily credits on login per user
- Training opt-out by default
- Centralized billing
- Share chats and collaborate with your team
- $30 of included monthly credits per user
- $2 of free daily credits on login per user
- Your data is never used for training
- SAML SSO
- Role-based access control
- Priority access for better performance and no queues
- Guaranteed customer support SLAs
| Model / item | Input | Output |
|---|---|---|
| v0 Mini | $1 / 1M tokens | $5 / 1M tokens · Cache write $1.25 / 1M tokens; cache read $0.10 / 1M tokens |
| v0 Pro | $3 / 1M tokens | $15 / 1M tokens · Cache write $3.75 / 1M tokens; cache read $0.30 / 1M tokens |
| v0 Max | $5 / 1M tokens | $25 / 1M tokens · Cache write $6.25 / 1M tokens; cache read $0.50 / 1M tokens |
| v0 Max Fast | $10 / 1M tokens | $50 / 1M tokens · Cache write $12.50 / 1M tokens; cache read $1 / 1M tokens |
v0 by Vercel. Page is mixed: subscription tiers (Free, Team, Business, Enterprise) plus usage-based token pricing per v0 model. Plan credits are denominated in dollar credits consumed against the per-model token rates. No separate individual "Premium/Pro" subscription tier exists. No explicit tax or "prices subject to change" caveat shown on the page. Verified against r.jina.ai mirror — both sources agree.
Curated snapshot · as of 2026-06-15. Live diffs are recorded in the change history below.
Change history
- Deprecation Mar 12, 2026, 1:00 PM
Deprecating the DHE cipher suite for TLS connections
On June 30th, 2026, Vercel will remove support for the legacy cipher suite.DHE-RSA-AES256-GCM-SHA384 This cipher may still be used by automated systems, security scanners, and HTTP clients with non-standard TLS configurations. After this date, clients using TLS 1.2 will only be able to connect to the Vercel network with:our six remaining cipher suites Modern clients and TLS 1.3 connections are unaffected. If you operate integrations or automated systems that connect to a domain hosted on Vercel
- Deprecation Feb 23, 2026, 1:00 PM
Support for now.json will be removed on March 31, 2026
Support for the legacy config file will be officially removed on. Migrate existing files by renaming them to no other content changes are required.now.jsonnow.jsonvercel.json,March 31st, 2026 For more advanced use cases, try for programmatic project configuration.vercel.ts Learn more about configuring projects with in the.vercel.jsondocumentation Read more
- Deprecation Aug 8, 2025, 1:00 PM
Bulk upgrade deprecated Node.js versions
Team owners and members can now upgrade all projects using Node.js 18 or earlier to Node.js 22 with one click in the Vercel Dashboard. This updates the. If your project also defines a version in, you'll need to update it manually. Existing deployments are not affected.Node.js version in project settingspackage.json View and upgrade deprecated Node.js projects now. Read more
- Deprecation Apr 10, 2025, 1:00 PM
Legacy build image is being deprecated on September 1, 2025
Node.js 18 (LTS support ends April 30, 2025) and the Vercel legacy build image will be deprecated on September 1, 2025. If you are still using the legacy build image on this date, new builds will display an error. What changes between the legacy build image and latest build image? How do I know if I am still using the legacy build image? Will my existing deployments be affected? Existing deployments However, the Node.js version will need to be updated on your next deployment.will not be affected
- Deprecation Jan 16, 2025, 1:00 PM
Node.js 18 is being deprecated on September 1, 2025
Following the Node.js 18 end of life on April 30, 2025, we are deprecating Node.js 18 for Builds and Functions on September 1, 2025. Will my existing deployments be affected? No, existing deployments with Serverless Functions will not be affected. When will I no longer be able to use Node.js 18? On September 1, 2025, Node.js 18 will be disabled in. Existing projects using 18 as the version for Functions will display an error when a new deployment is created.project settings How can I upgrade my
- Deprecation Nov 29, 2023, 1:00 PM
Node.js 16 is being deprecated on January 31, 2025
Following the Node.js 16 end of life on September 11, 2023, we are deprecating Node.js 16 for Builds and Functions on January 31, 2025. Will my existing deployments be affected? No, existing deployments with Serverless Functions will not be affected. When will I no longer be able to use Node.js 16? On January 31, 2025, Node.js 16 will be disabled in. Existing projects using 16 as the version for Functions will display an error when a new deployment is created.project settings How can I upgrade
- Deprecation Aug 3, 2022, 1:00 PM
Enhanced geolocation information for Vercel Functions
This changelog entry is historical. Edge Functions are deprecated for new projects. Use with the Node.js runtime and. Use for request-time routing before a response completes.Note:Vercel FunctionsFluid computeRouting Middleware Requests received by Vercel Functions are now enriched with headers containing information about the timezone of the visitor: As an example, a request from Tokyo is now enriched with the following headers: This header is now automatically activated for all new and existi
- Deprecation Nov 12, 2021, 1:00 PM
IP Geolocation now available for all plans
This changelog entry is historical. Edge Functions are deprecated for new projects. Use with the Node.js runtime and. Use for request-time routing before a response completes.Note:Vercel FunctionsFluid computeRouting Middleware IP Geolocation is now available on all plans,, for requests received by Vercel Functions. Check out to learn more.Hobby, Pro and Enterprise teamsour documentation Read more