NETLIFY

Publish a static site on Netlify without using the wrong project

Manual deployment is simple when you know which folder is the finished site and which Netlify project owns the live domain.

A static site is a folder of finished files such as HTML, CSS, JavaScript and images. With a manual Netlify deployment, the safe habit is to update locally, test locally, then upload that complete folder to the existing project for the site.

Important: do not change DNS, domain settings or the project name just to publish a page update. Those are separate tasks and can affect whether visitors reach the site.

1. Find the correct project first

Open the Netlify project that shows your live domain. If you upload from the general Projects page, Netlify may create a separate project instead. A new project does not automatically update the website people already visit.

2. Check the folder before uploading

Open the folder locally. It should contain the homepage file—usually index.html—plus the folders and files it needs, such as articles, CSS files, JavaScript files and images. Upload the whole site folder, not one file from inside it.

3. Test the local version

Open the local index.html and check the changed page, navigation and important links. If the site includes a form, make sure its form markup is still present. This makes the live deployment a confirmation rather than a surprise.

4. Deploy from the existing project

In the project’s Deploys area, use the manual deploy drop zone or folder picker. Choose the updated site folder. Wait for the deployment to complete and confirm that it is published to the intended production site.

5. Verify the public result

Open the live domain in a private browser window. Check the new page, one older guide and the contact form if it changed. A private window helps you see the current version rather than an older cached copy.

6. Keep the deploy history useful

Deploy after a meaningful batch of checked changes. A tidy history makes it easier to identify when an issue appeared and to return to a previous working version if needed.

If something looks wrong: stop before changing DNS. First check whether the right project received the right folder, then inspect the newest deploy and compare it with the previous one.