Anthropic changes model output format — switches from Markdown to HTML for developer workflows
- Anthropic said on May 20 that members of its Claude Code team are increasingly using HTML instead of Markdown for model outputs. - Claude Code engineer Thariq Shihipar wrote that he now prefers HTML because Markdown has become “an increasingly restrictive format” for larger outputs. - Anthropic’s post links HTML templates for common use cases on Claude’s site, where developers can follow the workflow.
Anthropic said on May 20 that members of its Claude Code team are increasingly using HTML instead of Markdown to present model outputs in developer workflows. The change surfaced more widely on Friday, May 22, in posts on X from developers and users who shared examples and raised concerns about how the switch could affect downstream parsing. Anthropic framed the change as a workflow choice inside Claude Code rather than a formal deprecation of Markdown. The company’s public post said HTML can produce richer, more readable and more easily shareable outputs. ### Where did this change come from? Anthropic published a Claude blog post on May 20 titled “Using Claude Code: The unreasonable effectiveness of HTML.” In that post, Claude Code engineer Thariq Shihipar wrote that Markdown had become the dominant format used by agents to communicate with humans, but said he had “started preferring HTML as an output format instead of Markdown” and was “increasingly” seeing that pattern used by others on the Claude Code team. (claude.com) The Claude post said the team was using HTML for plans, specs and other files that people review rather than edit directly. Shihipar wrote that Markdown remained simple and portable, but said larger agent outputs had made it “an increasingly restrictive format.” ### Why does Anthropic say HTML works better? Anthropic’s explanation centered on information density and presentation. (claude.com) The May 20 post said HTML can represent tables, CSS-based design elements, SVG illustrations, code snippets, interactions with JavaScript and CSS, workflows, spatial layouts and images in a single file. Shihipar also wrote that he found Markdown files longer than 100 lines difficult to read and harder to get others in an organization to review. (claude.com) The post said HTML gave the model a better way to present in-depth information and reduced workarounds such as ASCII diagrams and Unicode-based approximations. ### Why are developers worried about code blocks and parsing? (claude.com) Developers on X said the move could create problems for workflows that treat model responses as predictable Markdown, especially when code blocks are extracted programmatically. The social discussion cited in the briefing described HTML output as potentially prettier and more universal, but warned that code sections may become more fragile when developers parse responses automatically. (claude.com) Anthropic’s post itself did not present the change as a machine-readable output standard. Instead, it described HTML as a better format for human review, sharing and interaction inside Claude Code workflows. That distinction matters for developers who depend on stable delimiters, fenced code blocks or Markdown-first post-processing pipelines. This is an inference from Anthropic’s description of the workflow and the developer reaction reported in social posts. (claude.com) ### Is Anthropic dropping Markdown altogether? Anthropic did not say it was eliminating Markdown. The May 20 post described a preference for HTML in certain Claude Code use cases and said Markdown was still simple, portable and easy to edit. The post also offered HTML templates for common use cases, which suggests Anthropic is trying to steer developers toward a new pattern rather than announcing a hard platform-wide format change. (claude.com) Anthropic’s public developer materials still include broader guidance on APIs, JSON outputs and agent control for builders who need structured responses. ### What should developers watch next? Anthropic’s next public signal is likely to come through Claude Code documentation, templates and product updates rather than a standalone policy notice. The company is already pointing users from the May 20 post to HTML templates and to Claude Code documentation, and it has a recurring “What We Shipped” webinar for feature updates from the Claude Code team. (claude.com) Friday’s developer reaction means the practical next step will be whether Anthropic adds clearer guidance for teams that need human-friendly HTML outputs on one hand and stable programmatic extraction on the other. For now, the named participants to watch are Shihipar and the Claude Code team, which Anthropic has put at the center of this workflow change. (claude.com)