Update, October 13, 2026: Active and recent deployments have retention exceptions. Vercel also documents a limited recovery period for successfully built deployments, so automatic deletion and permanent removal are distinct stages.
Update, October 11, 2026: Vercel’s retention change also reaches existing Pro teams. Opt out before October 23 to preserve older deployments.
Vercel’s October 9 announcement extends 30-day deployment retention to existing Pro teams. Deployments older than 30 days will be deleted starting October 23 unless you opt out in retention settings first. Retention means how long Vercel keeps saved copies of your app from each release.
Settings already at 30 days or shorter remain unchanged. The new-team default is part of the same shift.
An older release can become unavailable for rollback, which means switching your live site back to an earlier working version.
Keeping older releases adds storage charges
Vercel’s stated reason is that coding agents have increased how often people deploy, which grows the amount of stored history. A shorter default keeps recent history while limiting older history and its storage costs. Deployment Storage and Functions Storage billing will begin for all Pro teams at $0.10 per gigabyte of stored data each month. Vercel says your team’s email gives its billing start date.
Review retention for pre-production, production, canceled, and errored deployments. A shorter history reduces storage charges but can remove older rollback options.
The retention policy exempts deployments with a production alias, the address pointing visitors to the live release. It also preserves certain recent deployments and active branch previews. An app you rarely update does not automatically lose its currently aliased production release after 30 days.
A bug discovered late may need an older release
If your agent ships several times a day, 30 days of history can hold many rollback points. But a bug that sits unnoticed for six weeks may need a release outside that window. If the last good deployment has been permanently removed, you must rebuild it from source code instead of using instant rollback.
Keep the source code, dependency versions, and required settings for releases you may need to rebuild. Stored deployment history does not replace a separate backup of application data.
Review retention before October 23
Vercel’s Deployment Retention Policy describes a 30-day recovery period for successfully built deployments marked for deletion. Unsuccessful builds may be removed sooner. The October 9 announcement warns that deleted deployments cannot be restored or used for rollback, so opt out before the deadline rather than relying on recovery.
- Open your team’s retention settings and review the period for each deployment category.
- Decide how far back you would realistically want to roll back for your slowest-moving app.
- If 30 days is too short, opt out before October 23 and choose a longer period, allowing for the storage charge.
End of article