Markdown is fine. HTML is better.
I’ve been writing in Markdown for sometime now. It’s portable, easy to edit, agents love it.
But at some point it started feeling like a limitation.
You can’t show color. Can’t really do diagrams. Can’t make something someone else actually wants to read. Past 100 lines, I check out, its a lot of text overload and most of the times visuals are better.
So I switched to HTML after seeing this post on X.
What HTML actually does that Markdown can’t
HTML isn’t just “fancier text.” It’s a completely different surface.
Tables. SVGs. Color. Sliders. Clickable elements. Layouts that breathe. Diagrams that don’t look like they were drawn by a drunk robot.
Basically anything you’d want to show or explain someone — you can do it properly, cos just reading large text is daunting, and sometimes not the best way to understand things.
Yes you can create agentic workflows now but to be able to review, understand and course-correct what Claude produces, HTML makes that review actually happen.
How I use it
Product specs - Instead of a 200-line markdown doc nobody reads - ask for an HTML spec. Add mockups, data flow diagrams, key decisions with tradeoffs. Share the link. People will actually open it.
Content planning - Drop your goals, audience, and a few reference pieces. Ask Claude to build a content plan as an HTML dashboard — calendar view, content pillars, distribution breakdown. Way easier to review than a table in Markdown.
Slide decks - Stop wrestling with Slides for your weekly update or meeting prep. Describe what you want — metrics, decisions needed, what shipped - and ask Claude to build it as an HTML slide deck. It pulls in your actual numbers, adds charts, keeps it tight.
Exploring directions before you commit - Ask Claude to generate 4-5 different approaches to something — positioning, onboarding flow, pricing structure — side by side in one HTML file. Label the tradeoffs. Pick the direction. Move fast.
Custom editors - This one’s underrated. Need to reprioritize your roadmap? Ask Claude to make a drag-and-drop kanban in HTML. Tweaking a prompt? Ask for a side-by-side live preview editor. The trick: always add a “copy as JSON” or “copy as prompt” button so you can pipe it back into the next step.
It’s not just about looks
You don’t need a fancy prompt or a special setup for this.
Just ask for “an HTML file” instead of a doc.
The real shift is realizing that the format you use changes how you think about the output — and how much you actually use it.
Markdown is for agents talking to agents.
HTML is for agents talking to humans.
(And you’re still human. For now :P)