Upload your HTML. Share the link.

1. Prepare the website files

For a single-page site, save the page as index.html. Include any stylesheets, scripts, images or fonts that the page references. A file that opens on your computer may still depend on files elsewhere on your disk; those dependencies need to be included too.

my-site/
  index.html
  about.html
  styles.css
  assets/
    cover.webp

Use relative paths such as assets/cover.webp, not paths beginning with file:// or a folder on your computer. Keep the file names and their capitalization consistent. For a ZIP, put index.html and its assets at the archive root. Upload only files intended to be public.

2. Choose a mode and upload

Open the hobing homepage and use the upload box to choose an HTML file, a ZIP or a folder. Choose anonymous publishing for a temporary link, or log in to save the project and use your account's limits.

Anonymous publishing supports 100 files and 25 MiB per site; its links normally last 24 hours. A Free account supports 300 files per site and one always-online slot. See all plan limits.

Wait for the successful publish result. Copy the public website URL for your visitors; keep management credentials and claim links private. A preview on your own computer is not the published website.

3. Check the link on another device

Open the returned URL on your phone or in a separate browser window. Check images, navigation, fonts and interactive buttons. Visitors can open the public site without a hobing account.

For a saved site, Dashboard lets you replace the full set of files while keeping its current link and expiry. Updating files does not renew a temporary link. Use the available always-online slot if the site should stay online.

Fix common publishing problems

Missing entry page

Include a root index.html. Upload the website contents, not an unrelated parent folder.

Missing images or CSS

Check relative paths and capitalization, and include all referenced files. References to localhost only work on the original computer.

Framework source

Build React, Vue or another frontend project in your development environment and upload its static output, not node_modules or the source project.

Client-side routes

Enable the single-page app option when your built app uses browser routing and needs index.html for extensionless page paths.

Quota reached

Read the returned limit and reset time. Account usage is visible from the account menu. Avoid repeating failed uploads without addressing the error.

What this hosting does and does not run

Static HTML, CSS, browser JavaScript and assets are supported, including multi-page sites. PHP, server-side Node.js processes, databases and private API keys need a separate backend. Forms that collect submissions also need a backend or form service.

Hosted sites currently send a noindex directive. They are suitable for direct sharing and previews; they are not currently offered as search-indexable business websites. See the product documentation for the complete hosting rules.