Notion pages can run HTML now. Here is the plain reading.
Notion 3.6 adds an HTML block: ask an agent and it builds an interactive calculator, quiz, explainer, or diagram right on the page. It is the fifth major product this year to render agent-made HTML inside its own walls, and it leaves the same question the other four left: what happens when the person who needs it is not in your workspace?
No card · 3 pages free · about a minute
What is the Notion HTML block?
A block type announced July 1, 2026 in Notion 3.6 that renders HTML interactively, in a sandboxed iframe, on a Notion page: ROI calculators, quizzes, interactive explainers, org charts from a people database. Notion AI can build one, you can type /html or upload an .html file, and agents can create one through Notion MCP. It is scoped to the page it lives on: no standalone URL, and access follows the page's sharing, not the block's.
What Notion shipped
The announcement is one sentence long and carries a lot: "New block in Notion: HTML. Build interactive HTML right on your Notion page. Ask AI to turn your content into interactive explainers, prototypes, or diagrams. Share with your team to use and tinker together." The release notes for Notion 3.6 add the worked examples: Notion Agents can build a custom ROI calculator for a client presentation, a quiz with questions drawn from your content, or an org-chart visualization generated from your people database.
The mechanics, as documented, run through Notion Agents rather than a code editor. You describe what you want, the agent writes the HTML against your page's content, and the block renders it in place, interactive, not a screenshot. The same release also shipped External Agents, which lets Claude and Cursor work inside Notion, and wider file support for Office formats. Taken together, the 3.6 release is Notion positioning its pages as a surface agents write to, not just a place humans type.
Update, 13 October 2026: Notion's developer docs now spell out the mechanics. The HTML block is an embed backed by an uploaded .html or .htm file, and the app renders the file's contents interactively in a sandboxed iframe instead of linking out to it. It is the same block the /html command creates, and agents create it through Notion MCP. So the block is not agent-only: you can bring a file you or another tool wrote.
Why this existed as a hack first
One reason to take the feature seriously: people were already doing this the hard way. Rendering real HTML in a Notion page previously meant third-party workarounds, code blocks with magic captions rendered by external site builders, embed services, converter libraries. A workaround ecosystem is the strongest demand signal a feature can have. Users wanted interactive things inside their docs badly enough to duct-tape them in; Notion just made it native and put an agent on the authoring side.
The fifth container this year, and counting
Zoom out and this is a pattern, not a feature. In the last year: Claude ships artifacts and then Live Artifacts, dashboards that re-query your apps. OpenAI ships Codex Sites, full apps on a workspace URL. Shopify ships Quick, an internal hosting surface. Slack starts rendering HTML attachments inline. And now Notion renders agent-built HTML as a first-class block. Five major products, one identical move: let the agent's HTML output render inside our own walls. The two weeks after this post proved the count was not done: Cloudflare shipped Drop on July 8, and Anthropic shipped public artifact sharing on July 13.
The shared premise is worth stating plainly, because it is the most important thing happening in this corner of software: HTML has won as the output format of AI. When an agent needs to hand a human something interactive, a calculator, a dashboard, a prototype, a report, it writes HTML, and every platform is now racing to be the place where that HTML lands. Each of them scopes it to their own container, because the container is the product they are defending. That is rational for them, and it is also exactly why the same gap keeps reappearing.
What is documented now, and what is not
At launch the material was a tweet and a release-notes entry. We re-checked Notion's help center and developer docs on 13 October 2026. Three of the original open questions now have answers:
- Bring-your-own HTML: yes. Type
/html, or upload an.htmlfile. The block is an embed backed by that file. - API and external agents: yes. Agents create HTML blocks through Notion MCP, and any integration can upload a file with the File Upload API and attach it to an embed block.
- The sandbox: partly. Notion says the block renders in a sandboxed iframe. It does not publish the exact rules. Independent testing reports that scripts run, that calls out to the network are blocked, and that state such as a drawing or a counter stays in the browser on that device rather than syncing.
Still not documented:
- Public-page behavior. Whether an HTML block renders for anonymous visitors on a page shared to the web or published with Notion Sites.
- Plans for /html and uploads. Notion AI, which can generate a block, is on Business and Enterprise. Whether typing /html or uploading a file is limited by plan is not stated.
- Mobile. How the block behaves in the iOS and Android apps.
Check these before you rely on the block for anything beyond a team page. We will keep updating this post as Notion documents them.
The gap: a block is not a link
Full disclosure: we build Stacktree, a host for agent-made HTML, so read this section as us describing where we sit in the pattern rather than neutral advice.
The HTML block is scoped to a Notion page, and Notion's own framing is honest about it: share with your team. Who can see the block is whoever can see the page. That is the right shape for an internal calculator or a team quiz, and the wrong shape the moment the person who needs the thing is not in your workspace: a client who should not be invited into your Notion, a stakeholder who just needs a link, a report that should expire after the engagement, a page that needs a password rather than a workspace membership.
That job needs the HTML to exist as its own artifact, on its own URL, with its own access rules. Stacktree does that one thing: an agent publishes the HTML over MCP and gets back a private, unguessable link the viewer opens with no account, gateable by password or email domain, with an expiry if the page should clean itself up. The block and the link are complements, not competitors. Inside the workspace, the block is better; the moment the audience is outside it, the block has no answer and the link is the answer.
How to share a Notion HTML block outside Notion
The block goes wherever the page goes, so sharing it means choosing how to share the page, or taking the HTML out of the page. Three routes:
- Invite them to the page. Add the person as a guest from the Share menu. They need a Notion account, and they get the whole page, not just the block. Fine for a collaborator, awkward for a client.
- Publish the page to the web. Notion Sites, or "Anyone on the web with link" in the Share menu. Anyone with the address can open it, and Notion has no password option for published pages: its help answers "Can I password protect a page?" with "Unfortunately, not at the moment." Whether the HTML block renders for those visitors is not documented, so open the link in a private browser window before you send it.
- Give the HTML its own link. If you uploaded the .html file, you already have it; if Notion AI wrote it, ask Claude or ChatGPT for the same thing as one self-contained HTML file. Publish that file to Stacktree and send the link: it is private and unguessable, it opens in any browser with no account, it carries a passcode on every plan (Free included), and you can add an email check or an expiry. Change the file and the same link shows the new version.
The first two keep the block inside Notion's rules. The third is the one that works for a client who should not be in your workspace, or a page that needs a password. More on which hosts can put a password on a site.
What to watch
- The documentation filling in. Public-page rendering and the full sandbox rules decide how far the block can stretch beyond team pages.
- What agents do with write access. Any agent can now write HTML blocks through Notion MCP or the API, so Notion pages are a render target for the whole agent ecosystem. Watch whether that shows up in templates and integrations.
- Whether the pattern keeps repeating. Five containers now render agent HTML. Each new one strengthens the same conclusion: the output format is settled, and the remaining competition is over where it lives and who gets to see it.
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.
Frequent questions
Can Notion render HTML? +
What is the Notion HTML block? +
How do you create an HTML block in Notion? +
Do Notion HTML blocks work on publicly published pages? +
Can external agents like Claude create Notion HTML blocks? +
Is the Notion HTML block a website? +
How do I share a Notion HTML block with someone outside Notion? +
Related guides
- What are Claude Live Artifacts? The Anthropic version of the same move: agent-built dashboards, personal and local at launch.
- Private HTML hosting For HTML that outgrows the block: unguessable URLs, gates, your own domain.
- What is Codex Sites? The OpenAI version: full apps deployed to a workspace-only URL.
- Slack renders HTML attachments The Slack version: agent-made HTML rendered inline in the channel.
- What Shopify Quick proves The Shopify version, and what the container pattern keeps proving.
- Share with clients The job the containers leave open: agent-made HTML on a private link for someone outside the workspace.
Sources and further reading
- Notion on X, the HTML block announcement ↗ The July 1, 2026 announcement: interactive HTML on the page, built by asking AI, shared with your team.
- Notion, What's new (3.6 release notes) ↗ The release entry: agents building interactive HTML blocks, External Agents, and Office file support.
- Notion, Code blocks ↗ The prior state: code blocks displayed HTML as text, and rendering it required third-party workarounds.
- Notion Developers, Block reference ↗ HTML blocks: an embed backed by an uploaded .html file, rendered in a sandboxed iframe, created by /html or through Notion MCP.
- Notion Help, publish a website with Notion Sites ↗ Published pages are open to anyone on the web, and password protection is "not at the moment".
- Notion Help, Notion AI FAQs ↗ Which plans include Notion AI, the route that generates a block for you.
Need the agent's HTML outside the workspace?
Stacktree publishes agent-made HTML to a private, unguessable link the viewer opens with no account. Passcodes are on every plan; email checks and permanent pages start on Solo, $19 a month.
Sign up free →