3 ms·

In an announcement[0] earlier this year, Cloudflare essentially put Cloudflare Pages on life support and began advising potential CFP users to build sites on th

In an announcement[0] earlier this year, Cloudflare essentially put Cloudflare Pages on life support and began advising potential CFP users to build sites on the newly enhanced Cloudflare Workers platform instead. I later wrote about this, particularly as it related to Hugo users.[1][2] [0]: https://blog.cloudflare.com/full-stack-development-on-cloudflare-workers/ https://blog.cloudflare.com/full-stack-development-on-cloudf... [1]: https://www.brycewray.com/posts/2025/05/pages-workers-again/ https://www.brycewray.com/posts/2025/05/pages-workers-again/ [2]: https://www.brycewray.com/posts/2025/07/hugo-sites-cloudflare-workers-or-not/ https://www.brycewray.com/posts/2025/07/hugo-sites-cloudflar...

kentonv 11mo ago
This is a bit of a misunderstanding. We are not sunsetting Pages. We are taking all the Pages-specific features and turning them into general Workers features -- which we should have done in the first place. At some point -- when we can do it with zero chance of breakage -- we will auto-migrate all Pages projects to this new implementation, essentially merging the platforms. We're not ready to auto-migrate yet, but if you're willing to do a little work you can manually migrate most Pages projects to Workers today. If you'd rather not, that's fine, you can keep using Pages and wait for the auto-migration later.
- brycewray 11mo ago
  Thank you for the clarification, sir. I wish that they had run that original Cloudflare blog post by you, especially this particular paragraph: > Now that Workers supports both serving static assets and server-side rendering, you should *start with Workers*. Cloudflare Pages will continue to be supported, but, going forward, all of our investment, optimizations, and feature work will be dedicated to improving Workers. We aim to make Workers the best platform for building full-stack apps, building upon your feedback of what went well with Pages and what we could improve. ... which sounds (at least to me) more like an “either/or” situation, and a “Pages-is-going-into-maintenance mode” situation, than your answer suggests. But perhaps that’s just how I took it.
  - kentonv 11mo ago
    You aren't the only one who was confused! We bungled the messaging there.
- basch 11mo ago
  And when they move to workers we lose access to generic pages urls? Everything I generate going forward has my username in it? It would be nice to leave the first come first serve anonymous urls as an option.
- rcarmo 11mo ago
  I have a site generator that won’t run on workers. Can I just use a storage bucket in Pages and be sure it will survive that migration?

kentonv 11mo ago

This is a bit of a misunderstanding. We are not sunsetting Pages. We are taking all the Pages-specific features and turning them into general Workers features -- which we should have done in the first place. At some point -- when we can do it with zero chance of breakage -- we will auto-migrate all Pages projects to this new implementation, essentially merging the platforms. We're not ready to auto-migrate yet, but if you're willing to do a little work you can manually migrate most Pages projects to Workers today. If you'd rather not, that's fine, you can keep using Pages and wait for the auto-migration later.

brycewray 11mo ago
Thank you for the clarification, sir. I wish that they had run that original Cloudflare blog post by you, especially this particular paragraph: > Now that Workers supports both serving static assets and server-side rendering, you should *start with Workers*. Cloudflare Pages will continue to be supported, but, going forward, all of our investment, optimizations, and feature work will be dedicated to improving Workers. We aim to make Workers the best platform for building full-stack apps, building upon your feedback of what went well with Pages and what we could improve. ... which sounds (at least to me) more like an “either/or” situation, and a “Pages-is-going-into-maintenance mode” situation, than your answer suggests. But perhaps that’s just how I took it.
- kentonv 11mo ago
  You aren't the only one who was confused! We bungled the messaging there.
basch 11mo ago
And when they move to workers we lose access to generic pages urls? Everything I generate going forward has my username in it? It would be nice to leave the first come first serve anonymous urls as an option.
rcarmo 11mo ago
I have a site generator that won’t run on workers. Can I just use a storage bucket in Pages and be sure it will survive that migration?