Stop Sharing Raw HTML
7 min read
We all use AI chat tools now. ChatGPT, Claude, Gemini, Perplexity — they're normal parts of work and daily life. We use them to draft blog posts, write business plans, summarize research, create reports, outline lessons, and generate polished-looking artifacts.
But there's a strange new problem hiding in plain sight.
AI tools often produce outputs that look useful inside the chat but break the moment you try to share them. The result looks formatted and polished on screen. But when you copy it, paste it into Slack, email it to a colleague, or send it to your family group chat, you end up with something like this:
<div class="container">
<section class="hero">
<h1>Title Goes Here</h1>
<p>This is the introduction...</p>
</section>
</div>
To a developer, that's normal. To almost everyone else, it looks broken.
Why raw HTML is the wrong default
HTML is the language web pages are made of. It's useful for developers and websites. It's not the format most people expect to receive in a text message, email, Slack thread, or Google Doc.
When someone gets a wall of HTML, they don't know whether to copy it, open it, save it, upload it, paste it somewhere, or assume you sent it by mistake. That friction kills the content before it gets read.
A few specific ways it fails:
It gets truncated. Large HTML outputs are long. Paste them into Slack, Teams, iMessage, or email and the message may get cut off, collapsed, or hidden behind "show more." The person receiving it may never see the full thing.
It looks more technical than the idea is. The actual content might be a guide for parents, a business memo, a product comparison, or a neighborhood report — something totally normal. Wrapped in raw HTML, it feels like a software project. Instead of engaging with the idea, people get distracted by the format.
It's hard to edit. Most people know how to edit a Google Doc. They don't know how to edit HTML without breaking the layout. The format prevents collaboration.
It makes good AI work look worse than it is. A useful AI-generated explanation becomes unusable if the packaging is bad. The reader doesn't reject the idea — they reject the format. That matters more now that AI is producing first drafts, summaries, proposals, and reports at scale.
AI output is not finished until it's shareable
A useful AI workflow has two steps:
- Create the content
- Package the content for the audience
Most people stop after step one.
They ask the AI for a report, get something that looks impressive on screen, and assume the job is done. But if the output can't be easily shared, read, printed, or forwarded, it's not really done.
The right question isn't only "did the AI create the answer?" It's "can another human actually use this?" That depends entirely on format.
Do not send people the construction materials. Send them the finished object. HTML is often the construction material.
The fastest cleanup
When you get raw HTML from an AI, don't paste it directly into Slack or email. Use this prompt first:
Convert this raw HTML into a clean, readable blog post in markdown.
Remove all HTML tags, CSS, JavaScript, inline styles, wrappers, and layout code.
Preserve the meaning, structure, headings, bullets, links, and tables.
Rewrite awkward phrasing into clear American English for non-technical readers.
That single prompt turns a messy HTML block into something usable in under a minute.
The fastest practical workflow for most people:
AI output → clean markdown → Google Doc → PDF or share link
Markdown cleans the structure. Google Docs makes it editable and familiar. PDF makes it stable and polished. A share link makes it easy to send. Each step makes the content more usable.
The formats worth knowing
Clean markdown. The best bridge format. Readable as plain text even for people who don't know markdown. Pastes cleanly into Notion, Substack, GitHub, and most AI tools. When in doubt, convert to markdown first.
Google Doc. The universal shareable format. Paste clean text, apply normal styles (Title, Heading 1, Heading 2, body), and share with "Anyone with the link can view." Everyone understands Google Docs.
PDF. For polished, fixed-format sharing. If the HTML renders well in a browser, open it in Chrome and use Command+P → Save as PDF. Or paste clean text into Google Docs and export from there. Best when you don't want the formatting to change.
Email. For friends, family, and colleagues who won't open attachments. Convert to a short email with the main point at the top and key takeaways as a numbered list. Shorter than the blog version. Main point first.
Executive memo. Prompt: "Convert this into a one-page executive memo with BLUF, context, key points, implications, and recommended next steps." Best for business colleagues, investors, and advisors. One of the most useful formats for serious readers.
Substack or Medium. Don't paste raw HTML into either editor. Convert to markdown or plain article text first, paste in, then manually check headings, bullets, and images. Substack is friendly for non-technical readers and easy to forward. Medium handles quotes, bullets, and images well but raw HTML pastes strangely.
LinkedIn. A long article can become one LinkedIn article, a 5-post thread, or a short executive-summary post linking to the full doc. Prompt: "Convert this into a LinkedIn article for non-technical readers. Then create a 5-post series summarizing the key points."
Notion. Best for living documents, team wikis, and lightweight publishing. Convert to markdown, paste into Notion, use headings, toggles, callout boxes, and tables, then share the public Notion link.
Slides. Often better than a long article for meetings. Prompt: "Turn this into a 10-slide presentation outline with one main idea per slide, short bullets, and suggested visuals." Good structure: Problem → Why it matters → What changed → Key insight → Framework → Example → Implications → Recommendation → Risks → Next steps.
One-page brief. For non-technical people who need the idea quickly. Sections: What this is / Why it matters / Who it's for / How it works / Main takeaway / Next step. Better than a full blog post when the audience is busy.
Clean single-file HTML. When you still want a webpage but not a monster. Prompt: "Create a clean single-file HTML page using simple semantic HTML and minimal internal CSS. No JavaScript. No external dependencies. Make it printable." Open in Chrome and print to PDF.
Static webpage. For a public link that anyone can open. Easiest non-developer options: Google Docs public link, Notion public page, Substack post, Medium post.
Best format by audience
| Audience | Best Format |
|---|---|
| Friends and family | Email, PDF, Google Doc |
| Colleagues | Google Doc, memo, PDF, Notion |
| Investors and advisors | One-page memo, PDF |
| Public audience | Substack, Medium, blog post |
| Internal team | Notion, Google Doc |
| Presentation setting | Slides |
| Print handout | |
| Editing over time | Google Doc or Notion |
| Technical archive | Markdown |
A better habit before you ask
The easiest fix is upstream: add one more sentence to your AI request before you get the output.
Instead of: "Make this look nice."
Say: "Make this readable and shareable as a blog post, Google Doc, or PDF. Do not output raw HTML unless I ask for it."
Or: "Write this in clean markdown, not HTML."
Or: "Make this suitable to paste directly into Substack, Google Docs, or an email."
That one instruction prevents most of the cleanup.
The principle
The useful output is not the code. It's the message, the explanation, the plan, the lesson, the argument, the recommendation. The format should disappear into the background.
A good AI-generated artifact should feel like something a person can immediately use — read it, forward it, print it, comment on it, publish it — without needing a developer.
In the AI era, communication isn't just about generating good ideas. It's about packaging those ideas so other people can actually use them.