# Vercel Pro teams face October 23 deletion of old deployments as storage billing expands Vercel is extending Deployment Storage and Functions Storage billing to existing Pro teams at $0.10 per GB-month, while changing deployment retention to 30 days. Unless teams opt out, deployments older than 30 days can be deleted from October 23 and cannot be recovered for rollback. Existing Vercel Pro customers have a concrete October 23 deadline to preserve older deployment history, plus new storage charges that begin on team-specific dates. - Status: Active - Published: 2026-10-13T21:14:54+13:00 - Updated: 2026-10-13T21:14:54+13:00 - Categories: SaaS, Cloud & Infrastructure, Hosting, Pricing & Billing, Deployment & DevOps - Tags: Cloud pricing, deployment retention, Deployment Storage, Vercel - Canonical HTML: https://beyondthe.news/dossiers/vercel-pro-storage-billing-30-day-retention-october-23-2026 ## What changed Vercel announced on October 9, 2026 that Deployment Storage and Functions Storage charges of $0.10 per GB-month will apply to existing Pro teams, not just newly created Pro teams. Billing starts on the date Vercel communicates to each team by email; the announcement does not establish a universal billing start date. Separately, Vercel is reducing the default deployment retention window to 30 days. From October 23, deployments older than 30 days will be deleted unless the team opts out or changes its retention settings before then. New Pro teams already default to 30 days. This is distinct from the September Hobby-plan change that immediately deletes non-exempt deployments when a free team exceeds its 10GB limit. ## Why it matters Older deployments are often the fastest way to reproduce a production regression, investigate a release, or roll back to a known build. An automatic retention change can silently remove those options. At the same time, AI coding agents and CI pipelines are creating more builds and larger stored histories; two metered storage categories create a new ongoing cost for Pro teams. Teams need to make a deliberate choice between keeping rollback history and paying to store it, rather than discover the trade-off after October 23. ## The October 23 deadline is about retention, not a universal invoice date Vercel's October 9 changelog says deployments older than 30 days will be deleted starting October 23 unless a team opts out in its retention settings beforehand. Teams already configured for 30 days or less are unchanged. In contrast, Vercel says the billing start date for existing Pro teams is communicated by email, so it should not be assumed to be October 23. These are two separate operational clocks. ## Deployment Storage and Functions Storage are two billable categories Vercel lists $0.10 per GB-month for each category. Deployment Storage covers stored deployment outputs; Functions Storage is a separate meter for function bundles. The project Usage page shows both. A team with many builds, large static outputs or functions deployed to multiple regions should inspect its own usage rather than infer a likely monthly charge from another team's experience. ## Longer retention remains configurable New Pro teams default to 30 days, but Vercel says they can select longer periods in team settings. Existing Pro teams should review retention separately for Pre-Production, Production, Canceled and Errored deployments. Shortening the window reduces storage use; retaining more history can protect incident response and rollbacks but may cost more. Vercel warns that deleted deployments cannot be restored or used for rollback. ## This is not the same rule as Hobby's September storage cap BTN previously covered Vercel's September 16 change to free Hobby accounts: a shared 10GB allowance, fewer protected deployments, and immediate cleanup of non-exempt history when over the cap. The new Pro change is a paid-plan billing expansion and time-based retention default, with a specific October 23 action deadline. Builders comparing plans must not confuse the two failure modes. ## A practical check before the deadline Review the team's email for the applicable billing start date; check Deployment Storage and Functions Storage by project in Usage; identify old deployments needed for rollback, compliance or debugging; set a retention period explicitly before October 23; and reduce future build outputs, large static assets and function bundles where possible. If a release must remain reproducible indefinitely, preserve its artifacts independently of deployment retention. ## Key details - Announcement: October 9, 2026. - Existing Pro teams will be charged $0.10 per GB-month for Deployment Storage and $0.10 per GB-month for Functions Storage. - Billing start dates are communicated per team by email, not as one universal October 23 start. - Deployment retention defaults to 30 days for new Pro teams and changes to 30 days for existing Pro teams unless opted out. - Starting October 23, 2026, deployments older than 30 days can be deleted under the new default. - Retention settings already at 30 days or shorter remain unchanged. - Deleted deployments cannot be restored or used for rollback. - Separate September 2026 Hobby-plan rules remain in force. ## Builder takeaways - Open Vercel's retention settings before October 23; do not rely on default rollback history. - Check the team-specific billing email instead of assuming charges begin on October 23. - Use the Usage page to inspect Deployment Storage and Functions Storage separately by project. - Decide which older production and preview deployments are genuinely worth paying to retain. - Archive critical release artifacts and build information outside Vercel if long-term reproducibility matters. - Reduce unnecessary build files and function bundle sizes to control future storage charges. ## What to watch - Whether Vercel changes the October 23 retention cutoff or grants any further transition period. - How team-specific billing dates and usage reports translate into real invoices. - Whether Vercel adds clearer pre-deletion warnings, storage budgets or easier long-term artifact exports. ## Uncertainties - The October 9 notice does not specify a single billing commencement date for all existing Pro teams. - Exact monthly charges depend on actual stored GB-months and account-specific usage. - The retention documentation contains exceptions; teams must inspect their own policy rather than assume every deployment older than 30 days is necessarily removed. ## Sources - [Deployment Storage billing begins for existing Pro teams](https://vercel.com/changelog/deployment-storage-pricing-expands-to-existing-teams) — Vercel · primary · 2026-10-09T00:00:00+13:00. Official $0.10/GB-month pricing, team-specific billing date and October 23 deletion/opt-out deadline. - [New Pro teams now default to 30-day deployment retention](https://vercel.com/changelog/new-pro-teams-now-default-to-30-day-deployment-retention) — Vercel · primary · 2026-10-09T00:00:00+13:00. New team default, storage rationale and longer-retention option. - [Vercel starts billing existing Pro teams for deployment storage](https://azeemhassni.com/blog/wire-vercel-deployment-storage-billing-pro-teams/) — Azeem Hassni · independent analysis · 2026-10-09T00:00:00+13:00. Independent operational explanation distinguishing billing date and retention deadline.