Static site deployments
Publish a folder of HTML pages, styles, scripts and assets. Keep the project structure you already work with locally.
Deploy HTML, CSS, JavaScript and assets from a folder, the CLI or an AI agent through MCP. Keep your project structure, share a live URL and pull published changes back to your machine.
Free to start. You can export your files.

Ask Chat to change the button accent in the shared stylesheet, then inspect the result.
Recorded in the htmlhost editor using a sample project. AI processing time shortened.
Open a template or upload your HTML files. Keep Edit Mode on.
Open Chat, choose Execute and send: “Change the button accent to green #2d8f72 in styles.css. Keep the rest of the design.”
Wait for the edit to finish and review the changed page. AI processing time is shortened in this recording.
Choose Phone preview to check the result before publishing.
Publish a folder of HTML pages, styles, scripts and assets. Keep the project structure you already work with locally.
Publish a working website for a client to test. Update it after each round of feedback, with password protection available on Pro.
Connect a compatible AI assistant through the MCP server, or use the CLI in your workflow to deploy and pull your site files.
Preview a template, open it in the editor, then replace its text and images with your own. To use a template marked Pro, you need a Pro plan.
A warm, light one-page site for a web studio, with services, work and a contact form.
A near-black one-page landing page lit by a pointer-following flame.
A dark landing page for a type animation tool, where letters and words move.
Use your HTML project or build your frontend into static files. Check that page links and asset paths work together.
Upload the folder in the browser, sign in with the CLI and deploy it, or connect your AI assistant to the MCP server.
Edit locally or in the web editor. Pull published changes before editing your local copy to avoid overwriting them.
Deploy folders, list your sites and pull their files with the htmlhost CLI. Link a local project to its hosted site.
How it worksConnect a compatible AI assistant to the MCP server to deploy, update and pull your hosted projects.
How it worksExport the project or use CLI pull to download its pages, CSS, JavaScript and other files.
How it worksKeep the HTML pages and their linked styles, scripts and assets in one project folder. Upload that folder through the browser or sign in with the CLI and run htmlhost deploy . from it. Check the published site to confirm nested page links and relative asset paths resolve correctly.
Yes, when its build produces static HTML, CSS, JavaScript and assets. Deploy that output folder. Server rendering, server functions and databases need to run on a separate service.
Yes. The editor works with the project files. Use the CLI's pull or sync workflow to bring published changes back to your local copy before making further edits.
Pro includes version history with preview, comparison and restore. You can restore through the dashboard, CLI, API or supported MCP tools, then pull the restored files into your local project.
Upload your files or choose a template. Edit your pages in htmlhost, preview them and click Publish.