Website Hosting
Publish standalone HTML or a multi-file static website, prepare build output, and troubleshoot paths and routing.
Choose a website format
| Format | Plan | Best for |
|---|---|---|
| One standalone HTML file | Free, Pro, Enterprise | Simple pages with content and inline styling |
| ZIP containing a multi-file static site | Pro, Enterprise | Sites with CSS, JavaScript, images, fonts, or framework build output |
Free standalone HTML is intentionally constrained: custom JavaScript, forms or active embeds, arbitrary external resources, and links to unapproved external destinations may be removed. Pro hosts browser-ready standalone HTML and website ZIPs with their JavaScript assets.
Linkyhost is a static host. It does not run PHP, Python, Node servers, API routes, server actions, SSR, build commands, or databases.
Prepare a standalone HTML page
- Save the page as
.htmlor.htm. - For a genuinely single-file page, keep its CSS inline and embed any required images or fonts.
- Open it locally and check that it renders without files that exist only on your computer.
- Upload it from Create Link.
Use Pro if the page needs its own JavaScript or broader external resources. Password protection for an existing HTML link is also a Pro feature.
Prepare a website ZIP
Upload generated, browser-ready output—not an unbuilt project folder.
- Put
index.htmlat the archive root whenever possible. - Include every relative asset the page needs.
- Keep file paths relative and preserve their letter case.
- ZIP the contents of the output folder for the cleanest result.
- If the ZIP has one enclosing folder, Linkyhost can unwrap it.
- Common generated folders such as
dist,out,build, or framework-specific public output may be detected automatically.
If source markers are found but no supported output containing a usable index.html exists, the deployment is rejected. Run the framework's static build or export command locally, then ZIP the generated output.
Archive limits
In addition to the plan's compressed upload-size limit, a website ZIP can contain at most 5,000 entries and may declare no more than 200 MB after extraction. A usable .html page is required. See Limits.
Production and preview deployments
The ZIP-to-website uploader offers two modes:
| Mode | Address | Lifetime | Custom domain |
|---|---|---|---|
| Production | Chosen or generated address | Persistent until deleted or expired | Supported on Pro |
| 7-day preview | Isolated generated address | Deletes automatically after 7 days | Not supported |
A preview does not reserve your production address. Deploy the ZIP again as Production when it is ready.
Routes, redirects, and headers
Single-page apps receive an entry-page fallback when the build is detected as an SPA. A site can also include small static-host control files:
_redirectsfor redirects and internal rewrites; and_headersfor supported response headers on matching paths.
For example:
/old-page /new-page 301
/* /index.html 200
Redirect status codes 301, 302, 307, and 308 are supported. A 200 rule is an internal rewrite. Unsafe, malformed, excessive, or unsupported rules are ignored and reported in deployment diagnostics.
Asset and route checklist
- A usable
index.htmlexists in the published output. - Asset URLs use
/, not local filesystem paths. - File-name case matches every HTML, CSS, and JavaScript reference.
- No browser request depends on a local development server.
- SPA routes work after a direct refresh.
- Reserved platform paths such as
/apiand/pdfjsare not used for site assets. - The production site has been tested in a private window.
If the entry page works but assets do not, open Troubleshooting and check the ZIP root, output directory, and relative paths first.