Menu
Log in

FROM WEBSITE FILES TO A LIVE URL

Publish a website made with ChatGPT.

The files are the website. Put the complete browser-ready site on a web host, then test its public address.

Start with a complete website folder.

Ask for a finished static website and save every file its pages reference. A typical folder has index.html, other HTML pages, CSS, JavaScript, and an assets folder for images or fonts. Keep its directory structure so links work. A screenshot or single component is not a deployable site.

A simple site can be written directly as HTML, CSS, and JavaScript. A framework project may need a build command to convert source components into browser files, often in a folder named dist or build. Upload that built output unless your host is configured to run the build.

Static pages do not provide server code, a database, secure login, or form processing. Connect a separate service for those features and review its data handling.

Deploy the files with Netlify Drop.

  1. Check the folder.

    Put index.html at the folder root and open it locally. Follow the navigation and check images and links. Keep passwords, API keys, and private configuration files out of public website files.

  2. Upload it to the host.

    Open Netlify Drop and drag in the website folder or a ZIP. The folder receives a netlify.app address. Check visibility: unsigned uploads are password protected until claimed, and account settings can keep a claimed site private. Upload built output, or sign in for a framework build.

  3. Review the live version.

    Open the returned URL on a phone and computer. Test every page, link, image, contact route, and form. To update a manual deploy, upload the revised folder under Production deploys in the project dashboard. Confirm that the result is publicly visible before sharing it.

Read the Netlify Drop instructions and deployment options for current interface steps.

Connect a domain after the host works.

First publish and test the host-provided address. Then add the custom domain in the host’s settings and follow its exact DNS values at the company managing your DNS. An apex address such as example.com commonly uses A or ALIAS records; www.example.com commonly uses a CNAME. Keep a copy of current DNS records before edits, and verify the site and HTTPS after changes propagate.

DNS changes do not transfer a domain registration. If you use email at the domain, preserve its mail records while changing only the website records. See how to move a website and keep email.

A separate route: use Benchlight.

The Benchlight assistant connector can prepare a private draft from static HTML, CSS, JavaScript, and assets, up to 100 files and 3 MB per request. A draft is not public: publication requires the website UI and a Benchlight hosting plan. The assistant connector cannot buy hosting, publish, or change DNS. You can publish files directly with Netlify without using Benchlight.

See hosting and imports.