Every answer is on the page. Nothing is hidden behind a control you have to click, and where the honest answer is no, it says no.
What BinHTML is, what it takes as input, and what you get back.
It takes one complete HTML document and turns it into a managed share link. The document renders in a sandboxed viewer, the link has visibility and expiry settings you control, the original source stays downloadable, and new versions can be published against the same URL.
A complete document: it must include a doctype or an <html> tag. Styles, scripts, and data should be inline or embedded, because BinHTML publishes a single file rather than a directory of assets. A fragment of body markup will publish but will render unstyled.
No. You can publish from the dashboard by uploading or pasting a document. The API and MCP surfaces exist for people who want the publish step inside a script or an agent, but they are optional.
No. An unlisted share link opens in any browser with no account. A private artifact is the exception: it only opens for the account that owns it.
One request. The response contains the share URL, the management URL, and the source download URL, so the link is usable immediately.
How artifacts, versions, and projects behave over time.
Yes, and this is the main reason to use artifacts rather than uploads. Publishing a new version against an existing artifact id replaces the content behind the same share URL. Anyone already holding the link sees the new version on their next load.
A project groups related artifacts, and a project link is one URL that indexes the whole group. It suits a release packet, a multi-part client deliverable, or a recurring report series where someone wants to see every run.
Yes, through a project link. Builder allows 10 active project links with up to 25 artifacts in each. Pro allows 500 with up to 250 artifacts each.
Yes. The source download is available from the dashboard for as long as the artifact exists, so the published link is never the only copy of what you sent.
Versions are retained per artifact up to the plan limit: 25 on Builder and 200 on Pro. The share URL always resolves to the current version.
No. Custom domains are not supported, and links are always on binhtml.com. If the delivery has to be on your domain, a deployment platform is the right tool.
Published limits, so you find out here rather than at publish time.
10 MB per document on Builder and 50 MB on Pro. Embedded base64 images are the usual reason a document gets close to the cap.
250 active artifacts and 2 GB of active storage on Builder; 5,000 artifacts and 100 GB on Pro.
Yes: 10 per minute on Builder and 60 per minute on Pro. Exceeding it returns a rate limit error with headers describing the window, so a well-behaved script can back off and retry.
Builder artifacts expire after three days, and that is the free plan working as designed rather than a trial. Pro artifacts can be permanent or given a custom expiry.
The API returns an explicit error naming the limit and the plan it belongs to, rather than failing silently or truncating your document.
How the rendering sandbox works, and what unlisted does and does not mean.
No, and this distinction matters. Unlisted means the URL is unguessable and the page is noindex, so it will not appear in search. Anyone who receives the URL can open it. If the content must be restricted to specific people, unlisted is not sufficient.
A private artifact only opens for the account that owns it. It is available on Pro. There is no way to grant private access to a named list of other people; BinHTML does not have teams or per-viewer permissions.
Artifacts render in a sandboxed context separated from the application, which is the right default for a document produced by a model and not read line by line. The sandboxing page describes the model in detail.
No. Artifact and project share pages are noindex by default. Public marketing and documentation pages are indexable; the things you publish are not.
Yes. Disabling the share link stops access immediately, and expiry does the same on a schedule. Both are actions you take yourself from the dashboard or the API.
Revoke the link straight away, then treat it as disclosed. Anyone who already opened the URL may have a copy. Redacting before publishing is the only reliable protection.
Using BinHTML from CI, scripts, and MCP-capable agents.
Yes. Connect the remote MCP endpoint at https://binhtml.com/mcp and the agent gains a publish tool. It can then return a share URL in its response instead of pasting a large HTML document into the conversation.
Any MCP-capable client. There are published walkthroughs for Claude Code, Codex, Cursor, Cline, Windsurf, Gemini CLI, GitHub Copilot agent mode, and n8n, and the same endpoint works for a custom client.
REST for deterministic pipelines where you control the call, such as CI jobs and scheduled scripts. MCP when an agent should decide to publish and hand the URL back as part of its own answer. Both create the same artifacts.
Store the artifact id after the first publish and have later runs post a version against it. Without an id, every run creates a new artifact. Publishing into a named project at least keeps the set organised.
In a secret store: CI secrets, your shell environment, or the agent's credential configuration. Never in a prompt, a committed file, or the HTML you are publishing.
Plans, payment, cancellation, and what happens after.
Yes. Builder includes dashboard, REST API, and MCP publishing, plus temporary artifact and project links. No payment details are required to start.
Yes. Builder includes up to 10 active project links with up to 25 artifacts in each link. Builder project links and their artifacts remain subject to the three-day retention window.
Upgrade when a link must remain available, an artifact must be private, a file exceeds Builder limits, or a recurring workflow needs higher publishing, storage, version, project, or project-link capacity.
Builder artifacts expire after three days and are removed by the retention cleanup process. Use Pro when a handoff needs a permanent artifact or project link.
You can manage or cancel Pro through the billing portal. After paid access ends, the workspace returns to Builder limits and BinHTML provides a warning window before older Pro artifacts become eligible for cleanup.
You pay once and keep permanent artifacts and private sharing for good, with no renewal and nothing to cancel. Lifetime is not a swap for Pro: it carries the same features but lower limits on file size, storage, artifact count, publish rate, and monthly traffic. Every one of those is in the comparison table above.
Take Lifetime if you want to pay once and your usage fits its limits, which suits most people. Take Pro if you need the higher ceilings: larger files, more artifacts and storage, a faster publish rate, or more monthly traffic. You can start on Lifetime and subscribe to Pro later if you outgrow it.
For as long as BinHTML runs. You get the publishing features you bought plus fixes and improvements to them, at no extra cost. If we ever launch a separate product, that would be priced on its own.
Go to binhtml.com/redeem, create an account or sign in, and enter your code. Access is switched on straight away.
Every time someone opens a shared artifact, it uses bandwidth. Each plan includes a monthly amount, from 5 GB on Builder to 50 GB on Pro, and it resets on the first of the month. For context, 10 GB is roughly 80,000 views of a typical artifact, so you are unlikely to notice it.
No. BinHTML publishes generated HTML as managed private or unlisted artifacts. Use a deployment platform when you need a public website, custom domain, server-side application, or public search indexing.
Email help.binhtml@outlook.com. If the answer turns out to be useful to other people, it ends up on this page.