Vercel CLI deploys static HTML and Markdown artifacts in under a second

Vercel CLI now ships instant static deployments

Vercel has added sub-second deployments for static artifacts to its command-line tool. According to the Vercel blog, running vercel deploy against an eligible directory of HTML or Markdown files skips the build step altogether and returns a live URL almost immediately — the company's sample output shows a deployment reported ready in 802 milliseconds.

The feature targets the fast end of the sharing workflow: pushing out a quick prototype, publishing an HTML report, or putting a page that a coding agent just generated somewhere a human can actually look at it. Notably, Vercel describes the capability as something "you and your agents" can do, an acknowledgment that deployment commands are increasingly invoked by automated coding assistants rather than typed by hand.

How the fast path works

There is no separate command or flag to learn. The CLI detects eligible artifacts automatically, and when a deployment qualifies, the build phase is skipped and the tool hands back a production URL, an aliased project URL, and a link to inspect the deployment in the Vercel dashboard. In the example Vercel published, a directory deployed with vercel deploy ./my-static-site --prod goes from creation to "Ready" in 802ms.

The constraints

The instant lane is deliberately narrow. Per the Vercel blog, a directory qualifies only if it contains no more than 10 files, totals 5 MB or less, and sticks to the .html, .htm and .md file extensions. Artifacts that fall outside those bounds will not skip the build step and go through the conventional deployment process instead.

To use the feature, developers need Vercel CLI version 59.16.0 or later. The full set of options is listed via vercel deploy --help.

Why it matters

Round-trip time shapes how tooling gets used. A deployment that completes in under a second turns publishing into something closer to a function call than a pipeline: an agent can generate a page, deploy it, and return a URL in the same breath, while a human reviewing that agent's output can click through to a rendered result instead of reading raw markup. That tight feedback loop matters more as coding agents take on larger portions of the build-and-ship workflow, and Vercel is explicitly positioning this feature for that audience.

The 10-file and 5 MB ceilings make clear this is not a replacement for full site builds — it is a fast lane for small, static output. But for exactly that category, such as HTML reports, single-page prototypes, and agent-generated previews, the build step was mostly ceremony. Cutting it removes one of the last gaps between "file written" and "URL shareable," which is a meaningful convenience for humans and a bigger one for automated workflows that deploy repeatedly.