New Vercel CLI Feature: Automatically Set Project Expiration on Deploy

Vercel recently introduced a practical new feature to its CLI tool: developers can now set an expiration time directly when deploying a new project, and the project will be automatically deleted upon expiry without manual cleanup. This update aims to simplify temporary resource management for prototypes, demos, and test apps, reducing the clutter caused by leftover projects.

How to Set Project Expiration

Using the latest version of the Vercel CLI, simply add the --delete-project-after parameter with a duration when running the vercel deploy command. For example, the following command creates a new project that will be automatically deleted after one day:

vercel deploy --delete-project-after 1d

The CLI supports durations including 1h, 1d, 1w, 2w, and 30d, covering common temporary needs ranging from hours to months. After a successful deployment, the command line prints the project's specific expiration date and time for easy confirmation.

This feature only applies to newly created projects. If you use the parameter on an existing project, the project's expiration time will not change, and the CLI will output a warning. This design avoids accidentally modifying the lifecycle of production projects.

Vercel CLI (command-line interface) is a development tool provided by Vercel that allows developers to deploy, manage projects, and view logs directly from the terminal without relying on the web console. It is commonly used in local development and CI/CD workflows, and vercel deploy is one of its core commands, responsible for uploading local code and building it into an accessible online project. Understanding where the CLI fits in the Vercel workflow helps clarify why moving project lifecycle management earlier into the deploy command can significantly reduce manual operations.

Managing Project Expiration Status

If you need to cancel a project's expiration setting, you can use the vercel project keep command. For example:

vercel project keep my-project

This command marks the project as permanently retained, removing the scheduled automatic deletion. This gives developers flexible control, allowing them to adjust promptly when a project transitions from a prototype to formal use.

Use Cases and Version Requirements

This feature is particularly well-suited for fast-iterating development workflows. Prototype validation, temporary demo environments, and automated test apps often only need to exist for a short time, and manual cleanup is not only tedious but also easy to overlook. By presetting an expiration time at deploy time, teams can ensure resources are released on schedule and reduce management burden.

To use this feature, you need to update the Vercel CLI to v65.12.0 or higher. For more details, refer to the official documentation for vercel deploy.

This update from Vercel reflects its continued optimization of developer workflows by moving resource lifecycle management earlier into the deployment step, and it is expected to become a standard practice for temporary project management.

In Vercel, a "Project" is the basic unit of code deployment, associated with resources such as Git repositories, build configurations, environment variables, and domains. Each project can contain multiple deployments, representing the output of a particular build. The project itself continues to consume storage and configuration resources and may be bound to a domain, so long-abandoned projects can accumulate management burden. Automatic expiration deletion targets the project level rather than individual deployments, which also explains why this parameter only takes effect for newly created projects—once a project exists, its lifecycle may already be referenced by other deployments or domains, and modifying it rashly carries risk.