Vercel CLI dry-run: check a deploy before you ship it

The Vercel CLI dry-run deployment feature lets you preview exactly what the CLI would upload before it actually creates a deployment. You run vercel deploy --dry from a linked project, and instead of shipping code, the CLI tells you which files it picked up, which it ignored, and which framework it detected. Nothing leaves your machine.

I read about it in for exactly that: paste the manifest, expand the tree, find the file that shouldn't be there.

Warning: A dry run tells you what Vercel would upload, not whether your app works. It's a packaging check, not a test suite. Keep your linting, type-checks, and builds in the pipeline too.

💡 The bigger shift: deployments you can inspect

For years the deploy step was a black box. You typed a command, files went somewhere, and you found out what actually shipped by reading logs after the fact. Making the manifest inspectable before upload moves the deploy from something you trigger to something you can reason about.

That fits a pattern I like: tools that let you look before you leap. Content hashes mean you can diff two manifests and see precisely what changed between deploys. File-mode reporting means a security-conscious team can assert that nothing ships with the wrong permissions. None of this is glamorous, but it's the kind of detail that saves a bad afternoon.

To get it, the changelog says to update the Vercel CLI to v54.17.2 or later. If you're on an older version, vercel deploy --dry simply won't be there.

What this means for you

If you deploy to Vercel, add one habit: run the dry run before an important ship, especially your first deploy of a new project when framework detection and ignore rules are least certain.

• 
  Solo builders and students: save upload time and data by catching bloat before it goes over the wire.


• 
  Small teams: wire vercel deploy --dry --json into CI as a cheap pre-flight gate that never creates a deployment.


• 
  Anyone on a slow line: stop paying the upload cost just to learn what you packaged.

It's a small feature with a clear payoff. Look at the manifest, fix your ignore rules, deploy once. On the connections most of us actually work on, deploying right the first time is worth more than deploying fast.