Cloudflare Pages exits beta with production-ready features
What began as a beta in December has quickly matured. Cloudflare Pages is now generally available, and the company is using the launch to roll out a wave of additions aimed at making the platform viable not just for static sites, but for the fuller life cycle of a web project.
The platform, which hooks into Git repositories to automate builds and deploys, has already seen thousands of developers push more than ten thousand projects through it. Those projects will now run on Cloudflare’s network across data centers in over 100 countries, with the same security and performance guarantees the company applies to its other products.
A single workflow from commit to production
Cloudflare Pages is built around the idea that deployment should not interrupt a developer’s flow. Connect a repository, pick a framework, and set build commands - after that, a git push is all it takes to publish changes. Each commit also generates a unique preview URL that gets attached to the associated pull request, giving reviewers a way to test code or content before it goes live.
That workflow has been extended with two collaboration features. First, protected previews are now available through Cloudflare Access integration. The Zero Trust service acts as a gatekeeper for preview URLs, prompting visitors with a one-time PIN sent to their email before granting access. Policies can be customized to work with an existing SSO provider, and the free tier includes 50 seats. Second, live previews leverage Cloudflare Tunnel to expose a localhost environment through a secure, shareable URL, which is useful for real-time feedback sessions before the final commit.
Post-launch tools baked into the platform
The launch-day questions - how many views, where traffic originates, whether core web vitals are healthy - can now be answered without leaving the Pages dashboard. Cloudflare’s privacy-first Web Analytics will be enabled with a single click later this week, tracking traffic and performance metrics without requiring any client-side script changes.
URLs change as sites evolve, and Cloudflare has added support for _redirects files to prevent dead links. Adding the file to the build output directory allows a developer to map old paths to new destinations in the browser-ready format:
[source] [destination] [http code]
That means URL changes and the corresponding redirects can be introduced in the same commit, rather than coordinated across separate steps.
Performance tuning through compression and resizing
Page speed improvements are also part of the GA release. Asset compression is now handled at build time rather than on the fly, which Cloudflare says produces stronger results. Images are processed through Cloudflare Polish, which reduces their size and serves WebP versions when the browser supports it; AVIF support is planned. HTML and JavaScript assets are served with gzip or Brotli compression, whichever the client accepts. In addition, a device-based resizing feature will deliver smaller images to mobile devices so that large files are not wasted on small screens.
Those additions come on top of the network-level performance the platform inherited from Cloudflare’s decade of edge optimization work.
Next steps: GitLab, webhooks, and gradual rollouts
Cloudflare has already mapped out the next round of features. GitHub integration is the first connection, but GitLab and Bitbucket support are in the pipeline. Webhooks will give teams that manage content in a CMS a way to trigger deployments without a commit. And for managing risk, the company plans to offer A/B testing capabilities so changes can be rolled out to a percentage of traffic before reaching 100 percent.
Toward full-stack applications
Static site hosting is just the starting point. The _redirects file is already a small step toward dynamic behavior, but the larger goal is to make Pages the deployment target for APIs as well as assets. Workers can soon be deployed by dropping a function into an /api or /functions directory. Durable Objects and KV namespaces will follow the same path, bringing frontend, API, storage, and data all under a single commit-and-deploy workflow.
The platform is available now, and documentation is already live for developers who want to explore the new features or migrate existing projects.
