PICK A WAY TO PUT THE FILES ONLINE
Compare hosts for a one-page business website.
For a small business page, compare how you deploy and update, how a domain connects, and whether the service permits the site’s purpose.
Netlify Drop: quick manual file upload.
Use this with a finished browser-files folder when you want to avoid setting up Git. Drag the folder or ZIP to Netlify Drop for a netlify.app URL. Claim unsigned uploads and check visibility settings before sharing. Upload revised output under Production deploys to update it. Signed-in users can also submit a project for an available build step.
Review Netlify’s terms, account ownership, usage limits, and custom-domain setup. See the Drop quickstart and deployment methods.
GitHub Pages: publish from Git.
This fits suitable project or documentation sites if you are comfortable storing files in a repository and publishing through Pages settings or GitHub Actions. A custom domain needs repository configuration and DNS records. Updates go through the repository workflow.
Business-use restriction: GitHub says Pages is not intended or allowed as free hosting for online businesses, e-commerce, commercial SaaS, or sites primarily facilitating transactions. Do not use it for a business site covered by that policy. See GitHub’s Pages limits and use policy. For valid use cases, follow GitHub’s custom domain setup.
Benchlight: preview, then publish.
Use this when you want a private review draft made from static HTML, CSS, JavaScript, images, and fonts before publishing through Benchlight’s website workflow. The assistant connector accepts up to 100 files and 3 MB per request. Publishing requires the website UI and a Benchlight hosting plan. The assistant connector cannot buy hosting, publish the site, or change DNS. A draft alone does not create a public website.
Benchlight can be a useful step for reviewing files, but it is not a prerequisite: the same files can go directly to a host such as Netlify Drop. Static browser files also do not provide server code, a database, login, or form processing; confirm those needs before choosing any of these routes.
Choose based on the finished files.
For a built site and few setup steps, use a manual file deploy. For versioned source, use a repository workflow whose terms permit the intended use. For private review, add a draft stage before choosing a host. Always test the public page and contact path on phone and desktop, connect the domain with the host’s exact DNS values, and preserve email records.
See domain setup and email-safe website moves.