Publish v1 while signed in
Upload HTML or a static ZIP, or let the Skill API create the first project. Guest 1-hour previews cannot be replaced later.
Same-URL HTML updates · Updated September 21, 2026
Keep One URL While Your AI Keeps Updating the Page
Share the link once. When Claude Code, Cursor, Codex, or another AI tool revises the HTML, update the page while keeping the same review URL. Same-URL updates require Pro or Max; Free and Guest previews cannot be replaced. HTMLShare is not a Git history system.
How to update HTML without changing the link
The URL is the artifact. Filenames such as report_final_v2_fixed.html are not.
Share the project URL once
Send the HTTPS preview to Slack, Notion, email, or a client. That address is the artifact identity, not the filename.
Keep projectId, slug, or URL
The first publish returns projectId, deploymentId, and url. Store them with the agent run so the next session can find the same project.
Replace content, not the link
Pass replace with the existing project ID, slug, or preview URL on /api/skill/publish, /api/skill/publish-files, or the CLI --replace flag.
Same URL shows v2
HTMLShare writes a new deployment, points the project at it, and keeps the public URL. Recipients refresh the original link.
Pro and Max projects can be replaced; Free projects and Guest uploads cannot. Pro and Max allow 5 MB for one HTML file and 20 MB for the whole project. Guest uploads are 1 MB HTML and 3 MB ZIP. Replace updates an existing project, so it does not consume a new project slot.
Why changing URLs breaks AI review workflows
The first publish is easy. The second revision is where teams lose the thread: v1 URL, v2 URL, v3 URL, final URL, final-final URL.
Where the old URL livesWhat breaks
Slack
The thread still points at v1 while the team is discussing v3.
The client’s original message never updates, so they reopen an old snapshot.
Notion
The spec page embeds yesterday’s URL unless someone remembers to edit the block.
Bookmarks
Stakeholders keep the first link and never receive the “final-final” one.
PM / QA
Feedback lands on the wrong revision because nobody knows which file is current.
Same URL for Claude Code, Cursor, and Codex
HTMLShare does not import from those tools. It hosts the static HTML they export, then lets an authenticated Pro or Max account update that same project.
Claude Code
Fix review comments in the generated page, then republish the same HTMLShare project instead of a new share link.
Cursor
Revise a prototype in the editor and replace the existing preview so the design-review URL does not churn.
Codex
Regenerate a report or dashboard and send the update to the same Skill-published project identity.
Other agents
Any authenticated HTMLShare Skill or CLI session can pass replace. Use a new project only when the artifact is intentionally separate.
Persistent URL vs version history
Several new hosts now sell “same URL” and “versioned links” as the product. Those are two different jobs. HTMLShare offers same-URL updates on Pro and Max.
CapabilityHTMLShareNotes
Persistent / stable URL
Yes, with replace
One project URL keeps serving the latest signed-in deployment.
Same-URL update
Yes, authenticated
Skill API and CLI --replace. Guest and ordinary /new uploads create a new project.
Version history browser
No
You get a new deploymentId. HTMLShare does not list, diff, or restore older files in the product UI.
Rollback
Not built in
Replaced files are removed. Keep the previous export locally or in Git if you may need it again.
Permanent link
Plan-dependent
Free currently lasts 1 day, Pro 30 days, Max is described as permanent. Guest previews last one hour.
One URL for client review
Prototype v1 → client feedback → AI revision → v2 at the same URL. Recipients do not need Claude, Cursor, Git, or a new bookmark.
Share a review snapshot
Send one question with the link: copy, layout, flow, or mobile. Later Design or agent edits do not change the URL unless you replace the files.
Replace after feedback
Keep the same project identity. Ask the agent to publish with replace rather than creating spec-v2 and spec-v3 projects.
Do not treat noindex as privacy
HTMLShare preview links are noindex. That is not a password, expiry gate, or workspace permission. Anyone with the URL can open a live preview.
Stable URLs as agent memory
A stable preview URL is a cross-session reference. The next Claude Code, Cursor, or Codex run can keep using the same address instead of hunting for a local file named final-v3.
- Store projectId and url in the agent run notes, not only in chat.
- Pass replace only for a revision of the same artifact.
- Create a new project when the audience, experiment, or page is actually new.
- Keep secrets out of the published HTML. The token belongs in the Skill runtime, not in page JavaScript.
Common same-URL problems
Browser upload created a second URL
The publisher at /new creates a new project. To keep the first link, publish through the Skill API or CLI with replace.
Publish HTML via APIGuest preview cannot be updated
Temporary previews expire after one hour and reject replace. Sign in and publish an account-owned project first.
Private HTML hostingNeed Git-style history
Same-URL replace is not source control. Keep the HTML in Git if you need blame, diffs, pull requests, or rollback.
HTMLShare vs GitHub PagesLink expired after a few days
Free previews currently last 1 day and Pro 30 days. Replace refreshes expiry from the current plan. Max is the long-retention option.
PricingFAQ
Common questions
Can I update HTML without changing the URL?
Yes, for a Pro or Max HTMLShare project. Publish the first version, keep the project ID, slug, or preview URL, then send the next HTML or file list with replace. The project URL stays the same. Free and Guest previews cannot be replaced; the ordinary browser upload creates a new project instead.
How do I keep the same URL after editing an HTML file?
Do not upload a new file in the publisher and expect the old link to move. On a Pro or Max account, use the HTMLShare Skill or CLI with --replace pointing at the existing project. The next deployment is served from that same URL.
Can Claude Code update an existing HTML link?
Yes, when the session uses a Pro or Max account and the agent passes replace with the previous project ID, slug, or preview URL. The same path works for Cursor and Codex through the Skill API. A new unauthenticated publish still creates a new URL.
How do I version AI-generated HTML?
Keep one stable review URL for the current page, and record deploymentId, timestamp, and a short change note yourself. HTMLShare replace updates the live files; it is not a Git-style history, diff, or rollback UI.
What is a persistent artifact URL?
It is one human-facing address tied to a project identity rather than to a filename such as report_final_v2.html. Later revisions publish to that identity so Slack, Notion, email, and bookmarks keep working.
Can one prototype URL always show the latest version?
Yes, after you replace a Pro or Max project. Recipients who already have the link see the new HTML on refresh. They do not get a second URL unless you create a new project on purpose.
Can I roll back an HTML artifact?
HTMLShare does not expose a restore button for earlier deployments. Replace writes a new deployment, points the project at it, and removes replaced files. Keep your own source export if you may need an older snapshot.
Can clients keep using the original link?
Yes, that is the point of replace. The original review URL continues to resolve to the current files for as long as the project remains live under the plan’s retention rules.
Do I need GitHub to version an HTML prototype?
No. Pro and Max same-URL updates do not require a repository, GitHub Pages, or CI. Use Git when you want source history, pull requests, and rollback. Use HTMLShare replace when reviewers should keep one browser link.
What is the difference between a stable URL and version history?
A stable URL is the address that always shows the current revision. Version history is the ability to browse, compare, or restore v1, v2, and v3. HTMLShare provides the first for Pro and Max projects. It does not provide a public version-history browser.
Does a stable URL mean the page is permanent?
No. Stable means the path does not change when you replace the files. Guest previews expire after one hour. Free links currently last 1 day, Pro 30 days, and Max is described as permanent. Replace also refreshes the project’s expiry from the current plan.
Can I replace a guest preview?
No. Temporary previews and Free projects cannot be replaced. Use a Pro or Max account to publish a project, then use replace on that account-owned project.
Have a v2 of the same prototype?
Publish the first project with Pro or Max, keep that URL, and replace the files instead of sending another link. Free users need to upgrade before updating the same URL.