How to Copy from Claude Without Losing Formatting

Every time you copy from Claude and paste into Google Docs, Word, or email, something breaks. The headings vanish. The tables collapse into pipe characters. The code blocks lose their formatting. Claude is the most structured AI writer available right now, with clean heading hierarchies, well-formed tables, proper code blocks, nested lists, and (as of March 2026) inline charts. That precision is also what makes the paste problem worse.

When you copy from Claude, all of that careful structure breaks on arrival. Because Claude's output is more structured than what ChatGPT or Gemini produce, there is more to break. A simple paragraph with some bold text might survive the paste. A structured report with H2s, H3s, a comparison table, code examples, and a Mermaid diagram will not.

This post explains why the formatting breaks, what happens in each destination app, and how to fix it.

Why Claude's formatting breaks when you paste

Claude writes in markdown. Every response is composed of markdown syntax: # for headings, **text** for bold, | pipes for tables, triple backticks for code blocks, and so on. Inside Claude's interface, this markdown gets rendered into nicely formatted HTML so it looks great on screen.

The problem is the clipboard. According to the W3C Clipboard API specification, the text/html MIME type is required for formatted paste to work correctly. When you copy Claude's response (using the copy button), you get raw markdown as text/plain. When you select and copy from the rendered view, you get HTML styled specifically for Claude's web interface. Neither of these is what your destination app expects.

Google Docs, Word, Slack, OneNote, and email clients each have their own internal format for representing rich text. They expect clipboard content to arrive in a specific flavor of HTML with specific metadata. Raw markdown gives them literal symbols. Claude-styled HTML gives them formatting that does not map to native styles.

The result: broken formatting every time.

What breaks in each app

Claude to Google Docs

Google Docs is a rich text editor that expects HTML with specific structure. When you paste Claude's output, here is what typically goes wrong:

• Headings either appear as bold text (losing the actual heading level) or display with Claude's font styling instead of Google Docs heading styles. Your document outline stays empty.
• Tables are the biggest casualty. Simple tables might paste as a visual grid, but the cells carry Claude's CSS padding, borders, and widths. Complex tables (5+ columns, long cell content) frequently collapse into a jumbled block of text.
• Code blocks lose their monospace font and syntax highlighting. You get a gray background from Claude's styling, but the text itself is in the document's default font.
• Nested lists flatten. A three-level nested list becomes a single-level list, or worse, a sequence of unrelated bullet points.
• Math equations (LaTeX) render as raw LaTeX syntax: $\sum_{i=1}^{n}$ instead of the actual equation.

Google Docs does have a markdown detection feature (Tools > Preferences), but it only handles basic bold and italic. Tables, headings, code blocks, and nested lists are not detected.

Claude to Word

Word handles pasted HTML differently than Google Docs, and the results are slightly better for some elements and worse for others:

• Headings sometimes map to Word heading styles, sometimes to styled body text. It depends on the HTML structure Claude's interface generates, which is inconsistent.
• Tables paste more reliably than in Google Docs, but they carry over Claude's exact pixel widths and CSS styling. They do not adapt to your document's page width or theme.
• Font inconsistencies are the main issue. Pasted content arrives in whatever font Claude's web interface uses, not in your document's default font. You end up with mixed fonts throughout the document.
• Code blocks lose syntax coloring and may not preserve the monospace font.

Claude to Slack

Slack uses its own formatting syntax called mrkdwn, which is not standard markdown. The differences are subtle but important:

• Slack uses *bold* (single asterisks), while markdown uses **bold** (double asterisks)
• Slack uses _italic_ (underscores), while markdown also supports *italic* (single asterisks)
• Slack does not support headings at all. There is no heading syntax in mrkdwn.
• Slack tables do not exist in mrkdwn. Pipe-delimited tables paste as literal pipe characters.
• Code blocks work similarly, but inline code formatting differs

When you paste Claude's markdown into Slack, bold text shows literal asterisks, tables become unreadable pipe characters, and headings are just lines starting with hash marks.

Claude to email

Email is the most unpredictable destination. Every email client renders HTML differently:

• Gmail is relatively forgiving but strips many CSS properties, so table styling and code block backgrounds may disappear.
• Outlook uses Word's HTML rendering engine, which has notoriously poor CSS support. Tables that look fine in Gmail can break entirely in Outlook.
• Apple Mail handles most HTML well but has its own quirks with list indentation and code block rendering.

When you paste Claude's output into an email compose window, you get the HTML from Claude's interface. It might look acceptable in your email client, but recipients using a different client may see something completely different. There is no way to preview this before sending.

Claude Artifacts

Artifacts are Claude's side panel for standalone documents, code, and visualizations. They give you a cleaner rendering than the chat view, and the copy experience is slightly better:

• The Artifact viewer uses simpler CSS than the main chat interface
• Headings are more consistently formatted
• You can download as .docx, which handles basic structure

But Artifacts still write markdown internally. Downloading as .docx gives you a plain, unstyled document with default formatting. There is no way to choose a template, match your company's branding, or control the output style. And if your Artifact includes a chart, Mermaid diagram, or LaTeX equation, those elements are lost in the .docx export.

Claude's new charts and visualizations make this harder

In March 2026, Claude gained the ability to generate inline charts and data visualizations directly in responses. This is a significant capability for analysts, product managers, and anyone who works with data.

But it makes the paste problem significantly worse. Charts rendered in Claude's interface are SVG elements or Canvas-based visualizations. When you copy the response:

• The copy button gives you markdown with a code block containing the chart specification. The actual visual is gone.
• Select-and-copy from the rendered view captures an image of the chart, but it arrives in your destination app as a bitmap with no editability.
• Neither approach preserves the chart in a useful format for documents.

If you need Claude's charts in a Google Doc or Word document, you currently have to screenshot them and insert the images manually. This is one more piece of structure that breaks on paste.

How to fix it

There are three approaches, ranging from manual and tedious to automated and clean.

Option 1: Paste without formatting, then reformat manually

Every rich text editor supports "paste without formatting" (Cmd+Shift+V on Mac, Ctrl+Shift+V on Windows). This strips all formatting and gives you plain text.

From there, you manually:

1. Apply heading styles to each heading
2. Recreate tables from scratch
3. Format code blocks with a monospace font and background
4. Re-nest your lists
5. Re-apply bold and italic throughout

This works for short responses. For a 2,000-word structured document with tables and code blocks, you are looking at 15 to 30 minutes of reformatting work. Multiply that by however many Claude responses you paste per week.

Option 2: Browser extensions

Several browser extensions attempt to bridge the gap between markdown and rich text. Markdown Here and similar tools can convert markdown in a text field to rendered HTML.

The limitations:

• Most extensions work in the opposite direction (writing markdown, not pasting it)
• They do not account for destination-specific formatting differences
• Table and code block rendering is generic, not optimized for any specific app
• They cannot handle Claude's charts or visualizations

Extensions are a partial fix for simple content. For anything with tables, code, or complex structure, they fall short.

Option 3: Unmarkdown

Unmarkdown™ is purpose-built for this exact problem. The workflow:

1. Copy the markdown from Claude using the copy button (clipboard icon)
2. Paste into Unmarkdown™
3. Choose your destination: Google Docs, Word, Slack, OneNote, Email, or Plain Text
4. Pick a template from 62 options to style the output
5. Copy the formatted output to your clipboard
6. Paste into your destination app

The key difference is that Unmarkdown™ generates output specifically formatted for each destination. Google Docs gets HTML structured for Google Docs' rendering engine. Word gets Word-compatible HTML with proper heading styles. Slack gets mrkdwn, not markdown. Email gets inline-styled HTML that renders consistently across Gmail, Outlook, and Apple Mail.

Tables, code blocks, nested lists, headings, math equations, and Mermaid diagrams all transfer correctly because the conversion accounts for each destination's specific requirements.

For Claude users who do this frequently, there is also an MCP integration that lets Claude create, style, and export documents through Unmarkdown™ directly from the conversation. No tab switching or copy-paste needed.

A quick comparison

Here is what a typical Claude response looks like across each approach:

Tips for the best results

Always use the copy button. Selecting and copying from Claude's rendered view gives you HTML with Claude's interface styling baked in. The copy button gives you clean markdown, which is a much better starting point for conversion.

Use Artifacts for long documents. Ask Claude to create your document as an Artifact. This keeps the full content in one place and makes copying easier than scrolling through a long chat response.

Check your destination's quirks. Google Docs handles pasted tables differently than Word. Slack does not support headings at all. Knowing what your destination can and cannot render helps you set expectations.

For recurring workflows, use MCP. If you regularly move Claude's output into documents, the MCP integration eliminates the copy-paste cycle entirely. Claude can create, style, and publish through Unmarkdown™ in a single conversation.

The formatting gap is growing

Claude keeps getting better at generating structured content. Heading hierarchies, comparison tables, code with syntax highlighting, LaTeX equations, Mermaid diagrams, and now charts. Every new capability adds more structure to the output, and more structure means more that breaks when you paste.

The destination apps are not keeping up. Google Docs' markdown detection still only handles bold and italic. Word still mangles pasted HTML. Slack still uses its own formatting syntax that differs from standard markdown.

Until these apps natively understand markdown (which may never happen), the gap needs a bridge. For simple text with some bold, you can get by with manual reformatting. For anything with tables, code, headings, or charts, you need a dedicated conversion step.

Try Unmarkdown™ free and see how your Claude output should look.

Related reading

• Claude Compacting Explained: What Happens When Claude Forgets
• The AI Formatting Problem Nobody Talks About
• Why ChatGPT Output Looks Terrible When You Paste It
• Claude Artifacts to Google Docs: The Complete Formatting Guide
• Markdown vs Slack mrkdwn: Why Your Formatting Breaks
• 5 Things That Break When You Paste AI Output