# Asked your AI for it in HTML? How to open, keep and share it · Stacktree
Source: https://stacktr.ee/blog/ask-your-ai-for-html
[Skip to content](#main) [stacktr.ee](/) [Examples](/#proof) [How it works](/#how) [Pricing](/pricing) [Security](/security) [Log in](https://app.stacktr.ee) [Publish one](https://app.stacktr.ee/?join=1) By [Steve Smith](/about) · Founder, Stacktree Last updated October 2, 2026 how-to
# Asked your AI for it in HTML? Here is how to open, keep and share it.
Asking ChatGPT, Claude or Codex to answer in HTML turns a wall of text into a page you can scan: a summary up top, a table, a chart. On 2 October Andrej Karpathy put it simply: ask for output "in HTML" to get a beautiful, interactive webpage. Getting the page is the easy part now. This guide covers what comes after it: opening it, keeping it, and sending it to someone privately so you know it was read.
[ Get started free ](https://app.stacktr.ee/?join=1&from=seo_blog_ask_your_ai_for_html) install npx stacktree-install
Copy
No card · 3 pages free · about a minute
## How do I share an HTML file my AI made?
Open it yourself by saving it as a `.html` file and double-clicking it, or in the preview your AI shows. To send it, put it on a private link instead of attaching the file: publish it to Stacktree, or ask your agent to, add a passcode, and send a link with the person's name on it. They open it in any browser with no account, and on a paid plan you see when they did.
Explain our Q3 numbers for Dana. Answer in HTML.q3-summary.htmlonly on your computerstacktr.ee/p/7Kq2mVx…Passcode onQ3 at a glanceHTMLREVENUE£291k +18%ORDERS2,140 +9%Publish privatelyLink for Dana copiedDana opened itjust nowAsk for HTML, publish it privately, and see when the person you sent it to opens it.
## On this page
- 01 [ Why ask for HTML at all ](#why-html)
- 02 [ Step 1: ask for it well ](#ask)
- 03 [ Step 2: open it ](#open)
- 04 [ Step 3: keep it ](#keep)
- 05 [ Step 4: send it privately ](#send)
- 06 [ Step 5: change it at the same link ](#update)
- 07 [ Do it from your agent in one line ](#agent)
- 08 [ Throwaway or keep? ](#throwaway)
## Why ask for HTML at all
A long answer in a chat is a wall you read top to bottom. The same answer as a page has structure: the conclusion on the first screen, the figures in a table, a chart where a chart helps, sections you can skip. Nothing about the content changes. It is just easier to take in.
That is the point Karpathy was making. As models do more of the work, more of our time goes on understanding what they made, and the format decides how hard that is. He ranks the options roughly in order: tightly written text, then diagrams, then web pages, then made-to-order explainer videos. Web pages are the step most people can use today, with nothing but a sentence added to the prompt.
## Step 1: ask for it well
"In HTML" alone works. A few more words make the page hold up when you move it, open it on a phone, or send it on:
```
`Answer in HTML. One self-contained file: inline CSS and JavaScript,
no external fonts or images. Put the answer on the first screen,
then the detail. It must read well on a phone. Write in plain
English: short sentences, one point each. It is for Dana, our client.`
```
- Self-contained means it still works after you move it or send it. A page that pulls fonts or scripts from elsewhere can break when it leaves your machine.
- The answer first stops the page burying the one number the reader came for.
- Phone-friendly, because a link you send is often opened on a phone.
- Plain English is Karpathy's other tip. He asks for writing close to [ASD-STE100](https://www.asd-ste100.org/), the controlled language written for aircraft maintenance manuals, and finds it easier to read. When the full spec is too strict he asks for "80% of the way to ASD-STE100".
- Who it is for changes the tone: a page for a client reads differently from a page for you.
## Step 2: open it
Where the page appears depends on the tool, but opening it never needs anything special:
- ChatGPT can preview the page in the chat or give you a file to download.
- Claude shows it as an artifact beside the chat.
- Codex and Claude Code write the file into your project folder.
In every case you can save it as `something.html` and double-click it. Any browser opens it, offline, with no server and no account. For reading it yourself, that is all you need.
## Step 3: keep it
The trouble starts the day after. The file sits somewhere in Downloads with a name like `index (3).html`. The artifact lives inside one chat, in one account. If the page mattered, you want it at an address you can find again, in the state you left it.
Publishing it gives it that address. On Stacktree each update keeps the earlier version, so you can go back, and the address does not change when the page does.
## Step 4: send it privately
Most pages people ask their AI for are meant for someone else: a client, a manager, a team. Sending the file as an attachment works until someone opens it on a phone, forwards it, or asks for the latest version. A link is better, and a private one should mean four things:
- Nobody can guess it. The link itself is the key, so it cannot be found by searching or by trying addresses.
- A passcode when it matters. Stacktree includes passcodes on every plan, Free included.
- A link per person. Choose who it is for when you publish, and the link you copy carries their name. On Solo and up you see when that person opened it, and you get an email the first time they do.
- No account to open it. The reader taps the link and the page opens.
The tools that made the page mostly do not do all four. [ChatGPT Sites](/blog/share-chatgpt-site-with-client) asks viewers to sign in with a ChatGPT account. [Claude's artifacts](/blog/claude-artifacts-public-sharing) are shared publicly or inside your organisation, without a passcode or a per-person link. A file posted in [Slack](/blog/slack-renders-html-attachments) stays inside the workspace.
## Step 5: change it at the same link
Pages go stale: the figures move, the client asks for a change. Ask your AI for the new version and update the page in place. The link the reader already has keeps working, and they see the new page the next time they open it. If you publish something that looks like a new version of a page you have already sent, Stacktree names that page and offers to update it instead, so you do not end up sending a second link.
If you need a decision rather than a read, turn on sign-off for the page. Each person you send it to can approve it, or go section by section, and every answer is recorded against the version they saw.
## Do it from your agent in one line
If your AI is connected to Stacktree you never touch the file. In ChatGPT, Claude, Cursor, Codex or Claude Code, ask in the same breath as the page:
```
`Make it a page, publish it privately with a passcode,
and give me a link for Dana.`
```
Connecting takes a minute: see [publishing over MCP](/mcp-publish-html), or the guides for [Claude Code](/claude-code) and [Codex](/codex). From a terminal, one request does it, and works without an account:
```
`curl -X POST https://api.stacktr.ee/sites -F file=@q3-summary.html`
```
A page published without an account stays up for 24 hours and comes with a link to keep it.
## Throwaway or keep?
Karpathy calls these discardable artifacts, and most of them are: you read the page once, it did its job, and nobody needs it next week. Stacktree's Free plan is built for that: 3 pages, each up for 7 days, passcodes included. The pages worth keeping are usually the ones someone else reads. Solo keeps 25 pages with no expiry, on your own branding, and shows you who opened what.
Full disclosure: we build Stacktree, so read the last few sections as us describing where we fit. The first three steps work whatever you use to share the page.
Fix it now
You've read why the public link is a problem. Paste the artifact here and get a
private one, no account, and a passcode if you want it.
Paste HTMLDrop a fileno account · 24 h linkHTML to publishAdd a passwordPublish private link Getting the page is easy now. Sending it well is the job.
Publish the HTML your AI made to a private link with a passcode, send each person a link with their name on it, and see when they open it. From the dashboard, from your agent, or with one request.
[ Get a private link →
](https://app.stacktr.ee/?from=blog_cta_ask_your_ai_for_html&join=1) Free to try: 3 pages, each live for 7 days. Own domain from $19/mo.
FAQ
## Frequent questions
How do I get ChatGPT or Claude to answer in HTML? + Say so at the end of your request: "Answer in HTML, as one self-contained file with inline CSS and JavaScript." Add who it is for and that it must read well on a phone. ChatGPT, Claude, Codex and Claude Code all follow this, and you get back a single file you can open anywhere. How do I open an HTML file my AI made? + Save it with a .html ending and double-click it: any browser opens it, with no server and no account. ChatGPT and Claude can also preview the page in the chat, and Codex or Claude Code write the file into your project, where you open it the same way. How do I share an HTML file privately? + Put it on a private link rather than attaching the file. Publish it to Stacktree from the dashboard, from your agent, or with one curl request, and you get a link nobody can guess. Add a passcode, which every plan includes, and send each person a link with their name on it. Can someone open the page without an account? + Yes. A Stacktree link opens in any browser for anyone you send it to, with no sign-up and no app. That is the difference from ChatGPT Sites, which asks viewers to sign in with a ChatGPT account, and from a file in Slack, which stays inside your workspace. Will I know when they open it? + Send them a link with their name on it. On Solo and up you see when that person opened it, and you get an email the first time they do. Pages that nobody has opened an hour after you sent them are flagged on your home screen. How do I change the page without sending a new link? + Update it in place. Ask your AI for the new version and replace the page: the link the reader already has keeps working, and the earlier version is kept. If you publish something that looks like a new version of a page you already sent, Stacktree offers to update that page instead.
Keep reading
## Related guides
- [ Share agent-made HTML Put a page an assistant built on a private link the viewer opens without an account. ](/share-claude-artifacts)
- [ Password-protect an HTML page How passcodes work on a published page, and when to use one. ](/password-protect-html-page)
- [ Share a ChatGPT site with a client What ChatGPT Sites asks of a viewer, and the alternatives. ](/blog/share-chatgpt-site-with-client)
- [ Publish HTML from Claude Code From a file in your project to a private link, in one step. ](/deploy-html-from-claude-code)
- [ Publish HTML over MCP The cross-agent publish flow behind a private, unguessable URL. ](/mcp-publish-html)
- [ Private HTML hosting The access model: unguessable URLs, plus passcode, email and expiry gates. ](/private-html-hosting)
References
## Sources and further reading
- [ Andrej Karpathy on X, understanding the outputs of language models ↗ The 2 October 2026 post ranking output formats for understanding: controlled writing, diagrams, HTML pages and explainer videos. ](https://x.com/karpathy/status/2105819303471976479)
- [ ASD-STE100 Simplified Technical English ↗ The controlled language specification from aerospace maintenance writing that Karpathy suggests asking for. ](https://www.asd-ste100.org/)
- [ Model Context Protocol ↗ The open protocol agents use to publish a page to Stacktree directly. ](https://modelcontextprotocol.io)
## Your AI made the page. Send it on a link that tells you it was read.
A private, unguessable link with a passcode, opened without an account. Free tier, no card.
[ Sign up free → ](https://app.stacktr.ee/?join=1&from=cta_blog_ask_your_ai_for_html) install npx stacktree-install
Copy
stacktr.ee [Page video](/page-video) [Ask this page](/ask-this-page) [Client feedback](/client-feedback-loop) [Client spaces](/client-spaces) [Templates](/templates) [Use cases](/use-cases) [Integrations](/agents) [Alternatives](/alternatives) [About](/about) [Blog](/blog) [Changelog](/changelog) [Pricing](/pricing) [Security](/security) [FAQ](/faq) [Made with Stacktree](/made-with) Building with AI agents? See the [developer docs →](/developers)
---
Full markdown summary of the Stacktree marketing surface: https://stacktr.ee/llms-full.txt