Upload a ready-made site
Have HTML, CSS, and images ready? Use Pages Direct Upload to publish your finished files. This guide walks you through it.
Follow the upload guide →Go from “where do I start?” to a live website on Cloudflare. One page, a few simple steps, and a link you can share.
A little corner of the internet, made by you.
This is just the beginning ↗Same destination. A different way to get there.
Have HTML, CSS, and images ready? Use Pages Direct Upload to publish your finished files. This guide walks you through it.
Follow the upload guide →Keep your code in GitHub or GitLab and let Pages deploy changes when you push. A useful path for ongoing development.
Explore Git integration ↗Download the starter above. It’s a complete HTML page. Put index.html in a folder and open it in your browser. Edit the text in a text editor to make it yours.
Sign in to Cloudflare. Go to Workers & Pages, create an application, and choose the Pages Direct Upload flow. Dashboard wording may vary.
Give your project a name. Upload the folder or ZIP containing your finished site, with index.html at its root, then select Deploy site.
Open the provided pages.dev address. Check your links and mobile layout, then share it. To update the site, upload a new deployment in the same project.
No. You can start with the pages.dev address Cloudflare gives your project. Add your own domain later from the project’s Custom domains section. Follow Cloudflare’s custom domain instructions for DNS setup.
Build the project first and upload its generated static output, often a folder named dist or build. Uploading your source code alone does not build the site. Apps that need server-side code require an appropriate Workers or Pages Functions setup.
Yes, but this starter is a static page. For server logic, explore Cloudflare Workers. A contact form, account system, or database needs additional implementation; uploading HTML does not create those services.
Check that index.html is at the top level of the uploaded output, rather than inside an extra nested folder. Also check that your image and stylesheet paths match the filenames, including capitalization.
Yours can start right here.