Do you build the Hugo site for me?

No. You run hugo yourself and upload the public folder. Nothing is compiled on our side, which is why the site is live seconds after the upload.

Which folder do I upload?

public, or a zip of its contents. What matters is that index.html ends up at the top level of what you upload.

Will my section and taxonomy pages work?

Yes. Hugo writes each one as a folder with an index.html inside, and folder URLs are served as pages here.

What about the sitemap and RSS feed?

They're files in the build like any other, so they're served as-is. Set baseURL to your published address before building so the URLs inside them are right.

Can I keep a build private while a client reviews it?

Yes. Set a password when you publish and visitors are asked for it before they see anything, and the page is kept out of search results.

Is there a size limit?

500 files and 100 MB per site, with 25 MB for any single file. A normal Hugo blog or docs site fits comfortably; a large image gallery may need compressing.

Host your Hugo site at your own address

Hugo builds in milliseconds. Publishing it should take about as long: run hugo, drag the public folder in, and the site is live over HTTPS.

You can host:

index.html/assetsfolder.zip

Drop your public folder here

Any other file works too — up to 25.0 MB, or 100.0 MB for a whole site

Choose a fileor drag it anywhere in this box

Free to use, live at your-name.99helpers.site in about ten seconds.

Why publishing is the slow part

Hugo's whole appeal is speed: a thousand pages render before you've finished reading the terminal output. Then the publishing step arrives and you're back to configuring a pipeline, a host and a domain for a site that took thirty seconds to build.

What a Hugo build gives you

A public folder holding the entire rendered site
Section and taxonomy pages as folders with their own index.html
A 404.html when your theme provides one
sitemap.xml and index.xml, already written out by Hugo

Build it, then upload it

Build command: hugo
Folder to upload: public/
Check baseURL in hugo.toml: Set baseURL to your published address before you build, or pass it on the command line: hugo --baseURL https://your-name.99helpers.site/

The build is instant, the deploy isn't

Hugo finishes before you blink, then you spend twenty minutes on a repository, a workflow file and a hosting project.

baseURL has to match where it lives

Hugo bakes baseURL into canonical links, feeds and sitemaps. Build for one address and publish to another, and those links point at the wrong place.

Previews need somewhere to live

hugo server is for you. Showing a draft to a client means putting it somewhere they can open, without handing them a repo.

Publishing a Hugo site

1
Set baseURL, then build
Pick your address first and put it in hugo.toml as baseURL, or pass it in: hugo --baseURL https://your-name.99helpers.site/. Hugo writes the site into public.
2
Upload the public folder
Drag public in, or a zip of what's inside it, and choose your address. index.html sits at the top level of the build, which is what the site is served from.
3
Share and keep publishing
The link works immediately over HTTPS. Each rebuild goes to the same address, so what you've shared stays current, and earlier versions are kept for a rollback.

Worth knowing

Hugo's ugly URLs setting isn't needed: /docs/ is served from /docs/index.html and /docs redirects to it.
relativeURLs = true in hugo.toml is a safe fallback if you want a build that works at any address.
Hugo Modules and themes run entirely at build time, so nothing extra has to be installed where the site is hosted.
Run hugo --minify before publishing: fewer bytes, and it keeps a big site comfortably inside the 500-file, 100 MB limit.
Drafts stay out of the build unless you pass -D, so a public address won't accidentally show unfinished posts.

Questions

Do you build the Hugo site for me?: No. You run hugo yourself and upload the public folder. Nothing is compiled on our side, which is why the site is live seconds after the upload.
Which folder do I upload?: public, or a zip of its contents. What matters is that index.html ends up at the top level of what you upload.
Will my section and taxonomy pages work?: Yes. Hugo writes each one as a folder with an index.html inside, and folder URLs are served as pages here.
What about the sitemap and RSS feed?: They're files in the build like any other, so they're served as-is. Set baseURL to your published address before building so the URLs inside them are right.
Can I keep a build private while a client reviews it?: Yes. Set a password when you publish and visitors are asked for it before they see anything, and the page is kept out of search results.
Is there a size limit?: 500 files and 100 MB per site, with 25 MB for any single file. A normal Hugo blog or docs site fits comfortably; a large image gallery may need compressing.

Publish the Hugo build you already have

Drop the folder in at the top of this page and see the link for yourself. You only make an account once it's ready to go live.

Back to the top Every generator we cover

Hosting sites from other tools

Hosting guides by file type

Every site gets its own address on 99helpers.site — see static site hosting for every generator, how website hosting works here or free file hosting for any file type.