Vercel Pro Teams to Be Charged for Deployment Storage: $0.10 per GB/Month

Vercel has started charging Pro teams for Deployment Storage. According to the official announcement, all Pro teams will now be billed for both Deployment Storage and Functions Storage at $0.10/GB-month. At the same time, the default deployment retention window has been adjusted to 30 days—deployments older than 30 days will be automatically deleted unless you proactively opt out in your retention settings.

This isn't a simple price adjustment—it's a recalibration of CI/CD storage habits.

Billing Rules and Effective Date

Pro teams will begin paying for Deployment Storage and Functions Storage at $0.10 per GB per month. Vercel says it has notified teams of their specific billing start dates via email, and recommends checking your team inbox as soon as possible to confirm your effective date.

From the wording of the announcement, this isn't a restriction targeting new users, but a policy change affecting existing Pro teams. This means that deployment storage space previously used for free will now officially appear on your bill.

Default Retention Window Reduced to 30 Days

Alongside the billing change comes an adjustment to the retention policy: the deployment retention window is now set to 30 days. Vercel explicitly states that starting October 23, deployments older than 30 days will be deleted unless you opt out in your retention settings beforehand.

Teams that have already set a retention period of 30 days or shorter are unaffected. However, there's one key limitation to note: deleted deployments cannot be used for rollback. If you rely on older deployments for quick rollbacks, this change needs to be factored in ahead of time.

Deployment Retention Policy is a retention configuration mechanism provided by Vercel that allows teams to set the retention period for historical deployments by deployment type. It categorizes deployments into four types: Pre-Production (preview environments), Production (production environments), Canceled (canceled builds), and Errored (failed builds). Each category can be configured independently with its own retention period. The longer the retention period, the more historical versions are available for rollback, but the more Deployment Storage is consumed. Note that adjusting retention policy is a two-way street: shortening the period directly reduces storage bills but sacrifices long-term rollback capability. It's recommended to configure these categories based on your team's actual release cadence and compliance requirements, rather than applying a one-size-fits-all reduction.

How to Control Deployment Storage Costs

Vercel offers several concrete paths to control costs:

Review retention policies. Use the Deployment Retention Policy to separately check the retention periods for Pre-Production, Production, Canceled, and Errored deployments. Shorter periods mean less storage history, but rollback capability is correspondingly reduced.

Monitor project usage. The Usage page lets you view Deployment Storage and Functions Storage consumption by project, making it easy to identify high-usage projects.

Reduce deployment size at the source. Vercel recommends removing unnecessary build files, migrating large static assets to Vercel Blob, and compressing Function bundles. The official storage optimization guide is also available for reference.

Vercel Blob is an object storage service provided by Vercel, designed specifically for storing images, videos, fonts, and other static assets, separate from deployment artifacts. The core value of migrating large static assets from the deployment directory to Vercel Blob is this: deployment bundles are fully retained in Deployment Storage, and each new deployment creates a snapshot. If these bundles contain large amounts of static assets, storage costs accumulate rapidly with each deployment. In contrast, assets in Blob are stored independently of the deployment lifecycle, incurring storage costs only when actually needed, and supporting on-demand references—significantly reducing deployment size and the resulting bills.

Practical Impact on Development Teams

The core tension of this change is that deployment history is both a safety net and a cost item. The more you retain, the more comfortable your rollbacks are—but the higher your bill. The 30-day default window is sufficient for most teams that iterate frequently, but for teams that do quarterly version rollbacks or need to retain audit records long-term, proactive adjustments to the policy are necessary.

Another easily overlooked point: Canceled and Errored deployments also consume storage. These "failed artifacts" often go uncleaned but continue to generate costs. Periodically reviewing the retention settings for these categories may be the most effective cost-saving action.

For Pro teams using Vercel as their primary deployment platform, it's recommended to complete three things before the next billing cycle: confirm the billing start date from your email, review retention policies for all four deployment categories, and evaluate whether large assets need to be migrated out of deployment artifacts.

One-line Summary

Vercel charges Pro teams $0.10/GB-month for deployment storage and reduces the default retention window to 30 days.

Paragraph Summary

Vercel has announced that Pro teams will be billed for Deployment Storage and Functions Storage at $0.10/GB-month, with specific effective dates communicated via email. Alongside this, the retention policy is changing: the default deployment retention window is now 30 days, deployments older than 30 days will be automatically deleted unless you opt out in retention settings, and deleted deployments cannot be used for rollback. Vercel offers three cost-control paths: reviewing retention periods for all four deployment categories (Pre-Production, Production, Canceled, Errored), monitoring usage by project on the Usage page, and reducing deployment size at the source (removing build files, migrating large assets to Vercel Blob, compressing Function bundles). The core tension is that deployment history is both a rollback safety net and a cost item. Pro teams are advised to complete three things before the next billing cycle: confirm the effective date, review retention policies, and evaluate asset migration.