Where
Dashboard → Deploy a zip (in the sidebar under Apps and websites, the All tools menu, or a project's Actions menu). It works on Static website plans, and on PHP plans for plain HTML sites. It is not offered for WordPress (a zip would replace WordPress) or for Node.js, Python and Java apps.
1. Make the zip
Your home page must be index.html, at the top of the zip or inside a single top folder. The zip can be up to 100 MB. A .war of plain files, .tar.gz, .tgz and .tar work too.
2. Upload
Choose the project and the website, then drop the file on the upload area or click it to choose the file. You see the upload progress, then how many files went live.
What happens
- The zip is unpacked into a new folder next to the site, as your own user
- It is checked: an
index.htmlmust be there; links (symlinks) and macOS__MACOSXfiles are removed - Then the new folder replaces
public_htmlin one step, so visitors never see a half-copied site - The version it replaced is kept
Undo
The Versions table lists the live version and the 3 before it. Press Make live next to an earlier one to switch back. The one you leave is kept too, so you can switch again.
When it refuses
- "There is no index.html": your home page is missing or inside a folder that holds other files too. Move
index.htmlto the top - "This is a Java web app": the WAR holds servlets or JSP pages. Run it on a Java plan, which uses Apache Tomcat (see Run a WAR, JSP or servlet app on Tomcat)
- "This website deploys from Git": push to your repository instead, or disconnect Git first
- Storage full: delete files you no longer need, or upgrade the plan
Changing one file
For a small change (one page, one image), use the File manager instead: open public_html, edit or upload the file.
Stuck? Our engineers answer support tickets around the clock. Contact us, or create an account and open a ticket from the dashboard — the same guides are there too.