Deploy static HTML sites
from a folder
Drop in a finished HTML, CSS, and JavaScript project and get a real URL with HTTPS, edge delivery, previews, and custom domains ready when you need them.
Plain HTML is simple. Publishing it should stay simple.
Static does not mean throwaway
A hand-coded page, course project, prototype, resume, export, or AI-generated HTML site still needs the basics done correctly: the right root file, clean asset paths, HTTPS, caching, compression, and a URL you can share without explaining the setup.
No framework ceremony
If the project already has an index.html file, CSS, JavaScript, images, and assets, you should not need to create a Git repo or learn a build pipeline just to show it online.
Built for finished folders
Upload the folder you would normally serve locally: index.html at the root, relative asset paths intact, and subfolders preserved.
Production details included
DeployPages handles HTTPS, edge delivery, compression, stable URLs, and custom-domain setup so the static site does not feel like a temporary file share.
Best fit for finished static projects
Use this path when the site is already built and only needs to be published cleanly.
Hand-coded pages
Landing pages, class assignments, small business pages, personal homepages, and experiments written directly in HTML, CSS, and JavaScript.
Exported site folders
Static exports from design tools, documentation generators, AI site builders, no-code tools, or build pipelines that already produce HTML files.
Shareable previews
Client reviews, portfolio pieces, demos, resume links, and one-off pages where sending a live URL is better than sending a zip file.
Before you upload
Most broken static deployments come from folder structure, not hosting.
Keep index.html at the root
The root document should be named index.html so the site can resolve at the main URL without an extra filename.
Upload the output folder
Choose the folder that contains the final HTML, CSS, JS, images, fonts, and assets. For build tools, that is often dist, build, out, or public.
Use relative asset paths
References such as ./styles.css, /assets/logo.png, or assets/app.js should match the folder structure you upload.
Check subpages locally
If your site has about/index.html or docs/getting-started.html, open those paths locally before upload so missing files are caught early.
Deploy an HTML project in three steps
Prepare the public folder
Put the final HTML, CSS, JavaScript, images, fonts, and assets in one folder. Make sure index.html sits at the root.
Upload the whole site
Drag the folder into DeployPages. Keep subfolders intact so styles, scripts, images, and pages resolve with the same paths.
Share or connect a domain
Use the preview URL immediately, then attach a custom domain and HTTPS when the page is ready for public traffic.
What happens after the upload
The file tree becomes the URL structure, then the site can grow into a proper domain when it is ready.
Instant preview URL
Use the generated URL to test the page in a real browser, send it to a teammate, or review the static export before attaching a domain.
Subfolders stay reachable
A folder like /docs/index.html becomes a clean /docs path, while files such as /assets/app.js stay available to the pages that reference them.
Custom domain when ready
Add your own domain later, point DNS to the provided target, and let HTTPS provisioning happen as part of the setup.
If the deployed page looks broken
The homepage returns 404
Check that index.html is in the uploaded folder root, not one directory deeper.
CSS or images do not load
Inspect the asset paths. A site that works from a local file path can still break online if links point to the wrong directory.
Only one page works
Make sure subpage folders and linked HTML files were included in the upload along with the homepage.
JavaScript behaves differently
Check browser console errors, mixed-content warnings, module paths, and any code that assumes a local file:// environment.
HTML hosting FAQ
Q:Is there a free plan for static HTML sites?
Yes. Static HTML projects can start on the free tier, which is enough for lightweight personal sites, resumes, simple landing pages, and prototypes.
Q:Does the homepage file need to be named index.html?
Yes. Using index.html keeps the project compatible with how static hosts resolve the default document at the site root.
Q:Can I use nested folders and subpages?
Yes. If your project contains routes such as about/index.html, DeployPages preserves that structure so the matching URL path remains available.
Q:Do I need GitHub to deploy a plain HTML site?
No. Git-based publishing is useful for ongoing development, but a finished static folder can be uploaded directly when you only need to publish the files.
Q:Can I deploy a site generated by an AI builder?
Yes, as long as the output is static HTML, CSS, JavaScript, and assets. Upload the generated folder the same way you would upload a hand-coded project.
Q:Can I host PHP, WordPress, or a database-backed app this way?
No. This page is for static files that can be served directly by a browser. Server-rendered apps, PHP, databases, and backend APIs need a different runtime.
Q:Can I automate deployments with a CLI or API?
Yes. DeployPages supports scripted deployments, so teams can connect static publishing to CI workflows when they do not want to drag and drop manually.
Q:Can I attach my own domain later?
Yes. After deployment, add the domain in the console and point DNS to the provided target. HTTPS is provisioned automatically once the record resolves.