Vercel CLI Introduces Sub-Second Deployments by Bypassing Build Step for Static Artifacts

Vercel has announced support for sub-second artifact deployments when deploying static assets via the Vercel CLI. When running the deployment command, the platform now automatically detects eligible static directories and skips the build phase entirely, generating live preview URLs almost instantaneously. This optimization triggers specifically when the target deployment directory consists solely of valid static files with supported extensions. The platform currently recognizes and supports three file extensions for this fast-path deployment route, which are HTML, HTM, and Markdown. Previously, even basic static assets often had to route through Vercel's standard build pipelines, which introduced avoidable deployment latency. The new deployment path is designed to accelerate modern automated workflows, such as previews generated by AI coding agents, HTML test report publishing, and rapid prototyping. However, projects that include dynamic server-side logic, API routes, or complex framework configurations will continue to trigger the traditional build process as usual.