01 / HTML HOSTING
Host AI-generated HTML with its resources intact.
A working HTML file is already a deliverable. You can host an interactive prototype, a product proposal or a report without rebuilding it as an application. The first step is making sure the file also works outside the computer where it was generated.
Choose one HTML file or a ZIP package
Upload a single .html or .htm file when its styles, scripts and images are embedded, or when it needs no additional files. If it depends on a stylesheet, a JavaScript file or local images, package those resources with the HTML in a ZIP. Uploading only the entry file cannot restore missing dependencies.
For a ZIP, place index.html at the package root. A package with only one HTML entry file can also be accepted. Keep filenames consistent with the references inside your code, including letter case. Do not include credentials, hidden files, development dependencies or backend source files.
project.zip
├── index.html
├── styles.css
├── app.js
└── assets/
└── cover.pngUse relative paths and test the complete package
Reference resources with paths such as ./styles.css and ./assets/cover.png. An absolute path on your computer cannot work for visitors. A path beginning with / refers to the hosting origin and may miss the project’s own directory, so prefer paths relative to the page.
Extract the ZIP into a fresh folder and open its entry page. Check navigation, image loading, controls and narrow screens. For pages that rely on browser module loading or fetch, also test through a local static server: opening a file directly may behave differently from serving it over HTTP.
Stay inside the static hosting limits
6HL serves static HTML, CSS, JavaScript and supported resource files. It does not run Python, PHP, Node.js servers or a project database. A generated interface that depends on an unavailable API will not become a working backend simply because its page is hosted.
By default, a project loads resources from its own package. The optional CDN setting allows a defined set of common providers, including Tailwind, jsDelivr, unpkg, cdnjs and Google Fonts. Visitors then connect to those providers. Include resources in the package when you want to avoid that dependency.
- One upload: up to 50 MB.
- ZIP after extraction: up to 100 MB and 2,000 files.
- Account storage and project-count quotas: check Space settings.
- Unsafe paths, unsupported file types and excessive compression ratios are rejected.
Upload, preview and replace an existing project
Sign in to your creator workspace, choose the HTML or ZIP and enter a project name. After validation, 6HL creates a random project address. The project is private and is not automatically added to existing grants. Preview the hosted page before sharing it.
An updated ZIP must still contain the complete project, not only the changed stylesheet or image: replacement applies to the whole package. If you need to test an unfinished layout, upload a separate test project before replacing content that existing recipients can already access.
To publish a revised file, update the existing project instead of creating a duplicate. Updating replaces its current content while retaining its address and access grants. Keep your source files locally: replacement is not a version-history service. Public registration is not yet open; these steps currently apply to existing creator accounts.