HTML Deployer — User Guide

Click the HTML Deployer icon in the Chrome toolbar.

On the sign-in screen, click Continue with Google and approve the Google account prompt.

After sign-in, the Deploy, History, and Settings tabs unlock. Your email is used for license and quota on our server only.

Ask the AI for a full HTML page (landing page, email template, etc.) and wait until the code block appears.

Use the Deploy button the extension adds near the HTML/code block (or artifact toolbar on Claude).

The popup opens with a preview. If detection fails, use the pencil icon to paste HTML manually.

Review the preview. Set Page name (used as the file name, e.g. my-page.html).

Pick Download (ZIP), Cloud (Netlify / Vercel / GitHub), FTP, or Host Agent. Connect the provider in the popup or in Extension options if prompted.

Click Deploy To Host or Download ZIP. When finished, copy the live URL, open it, or view it in the History tab.

In the popup, choose the Download card (ZIP file).

Enter a name without .zip — the extension adds the extension automatically.

Click the download button. Upload the HTML inside the ZIP to any host manually if you prefer.

On Netlify → Personal access tokens, add a description, set expiration, and click Generate token.

Copy the token immediately and store it safely — Netlify shows it only once.

In Extension options → Netlify, paste the token and click Connect. Then return to your AI chat and deploy from the popup.

In the popup, select Cloud, then the Netlify provider pill.

Select an existing site or create a new one from the Deploy to site dropdown.

Click Deploy To Host and use the success link when deployment completes.

On Vercel → Account tokens, set name, scope, and expiration, then click Create.

Copy the token right away — it is shown only once.

Extension options → Vercel → paste token → Connect.

Select team (if any) and project, or choose to create a new project.

For a new project, the page name is used as the project name.

Click Deploy To Host and open the deployment URL from the success panel.

On GitHub → New token (classic), enable the repo scope, then generate and copy the token.

Extension options → GitHub → paste token → Connect.

Create a repo on GitHub (empty is fine). In repo Settings → Pages, set Deploy from a branch, branch main, folder / (root).

Search and select your owner/repo from the list.

Pick the branch (usually main) and confirm the HTML file name (e.g. index.html).

Click Deploy To Host. GitHub Pages may take a few minutes to go live on first publish.

Extension options → Host Agent → Download agent script. Upload backrun.php to your host via FTP or cPanel.

Edit the file on the server: replace CHANGE-THIS-TO-RANDOM-32-CHAR-STRING with your own long random secret.

In options, Add Endpoint with profile name, public URL (e.g. https://yourdomain.com/backrun.php), and the same secret. Use Test Connection, save, then choose Host Agent in the popup and deploy.

Extension options → FTP Profiles → enter your Relay Server URL → Test Relay Connection.

Click Add Profile, fill host, port, username, password, remote path, and preview URL pattern ({filename} placeholder).

Click Test Connection, then Save Profile. In the popup, choose FTP, select the profile, and deploy.

Use the product key from your purchase email (format BACKRUN-…) or stay on FREE_LICENSE for the free tier.

Open the popup → Settings tab → License key field → Save.

Options → General → same license field → Save. To remove a paid key, use Remove in the popup to return to free.

In the popup, click the History tab.

Filter by Cloud, FTP, or Host Agent. Click a URL to open, or copy it from the row actions.

To wipe local history: Extension options → General → Danger Zone → Clear History.