Why ChatGPT Formatting Breaks When You Copy and Paste

A response can look perfectly formatted in ChatGPT or Claude and still fall apart when you paste it into Word, Google Docs, Slack, or another editor.

You may lose headings, get strange spacing, break numbered lists, or see raw Markdown symbols such as ## and **.

The important point is that the screen, the clipboard, and the destination application are three separate layers.

Once you separate those layers, copy-and-paste problems become much easier to diagnose.

If you have only one destination, use that application's native features first. Yomu is mainly useful when one reviewed Markdown source needs to travel to several destinations.

The short answer: the text is the same, but the representation changes

An AI interface renders content for display.

When you copy that content, the clipboard may carry more than one representation—commonly plain text and HTML.

The destination application then decides which representation to use.

The W3C Clipboard API describes clipboard items as capable of containing multiple representations, such as text/plain, text/html, or image formats.

That means the same copy operation can behave differently depending on where you paste it.

The three layers that change pasted formatting

Layer 1: what you see on screen is a rendered result

Suppose the underlying structure is:

## Conclusion

- Check A
- Check B

**Important:** Check C last.

The AI interface may render that as a heading, bullet list, and bold text.

Seeing a heading on screen does not guarantee the clipboard contains a portable "H2" structure that every destination will understand.

Layer 2: the clipboard can carry multiple formats

A clipboard item can expose the same content in multiple MIME types.

Typical examples include:

• text/plain
• text/html
• images

A document application may prefer the HTML representation because it can preserve more formatting. A simpler chat field may use plain text.

That difference alone can explain why the same copied answer looks correct in Word but simplified in Slack.

Layer 3: the destination decides what it supports

Even if the clipboard contains rich structure, the destination application may not have an equivalent concept.

A word processor supports headings, styles, tables, and list structures. A chat app may support only a smaller set of message formatting.

So complete visual reproduction is not always possible.

Plain text, Markdown, and rich text carry different information

Plain text

Plain text carries characters, not document styling.

Pasting as plain text is useful when unwanted styles are the problem, but it can also remove:

• bold text
• heading structure
• list formatting
• tables
• links with display text

It is a good cleanup tool, not a universal preservation method.

Markdown

Markdown stores document structure with lightweight syntax:

## Heading
**Bold**
- List item

If the destination understands Markdown, that structure can be converted.

If it does not, the symbols remain ordinary text.

HTML or rich text

HTML can carry more direct structural and styling information.

That often preserves visual formatting better, but it can also import unwanted fonts, spacing, colors, or source styles into the destination document.

Google Docs: use Paste from Markdown when Markdown is the source

Google Docs provides Markdown support, including Paste from Markdown.

This is different from ordinary paste.

If your source is raw Markdown, explicitly asking Google Docs to interpret it as Markdown is more predictable than hoping regular paste chooses the right clipboard representation.

A practical workflow is:

1. enable Markdown support in Google Docs settings
2. copy the Markdown source
3. use Paste from Markdown
4. review the converted headings, numbered lists, links, and any complex structure

For ordinary rich-text copying, regular paste may still be simpler.

Conversion is not perfect layout reproduction

Markdown does not encode every feature of a word-processing document.

Page numbers, advanced tables, exact typography, headers, footers, and complex layout still require final work in Google Docs.

In June 2026, a Google Docs Editors Community report also described unexpected numbering after using Paste from Markdown with nested numbered lists. A community report is not an official specification, but it is a useful reminder that Markdown support does not mean every nested structure will convert perfectly.

Reference: Google Docs Editors Community: Paste from Markdown not correctly enumerating nested list

Word: choose what you want to preserve

Microsoft Word offers paste modes that reflect the same tradeoff.

Typical choices include:

• Keep Source Formatting
• Merge Formatting
• Keep Text Only

Use source formatting when the copied result already looks right and you want to preserve it.

Use merge formatting when you want the destination document's styles to take priority.

Use text only when source formatting is causing problems and you are willing to rebuild structure.

There is no single best option. The correct choice depends on whether you care more about preserving source appearance or matching the target document.

The destination's document model sets the limit

A destination can only preserve structures it actually supports.

Slack and Discord are chat applications, not word processors. Even if the source contains a real document heading or complex table, the destination may not have an equivalent structure.

Gmail and Outlook also center on email formats rather than raw Markdown conversion. Gmail provides formatted mail and plain-text mode. New Outlook uses HTML by default and can also use plain text.

OneNote exposes paste behavior such as keeping source formatting, merging formatting, or keeping text only. That is still different from treating arbitrary raw Markdown as a native document format.

So the same principle applies across chat, email, and notes: having structure in the source is not enough if the destination has no matching document model.

References:

• Gmail Help: Format your messages
• Microsoft Support: Change the message format in Outlook
• Microsoft Support: OneNote options — Advanced

Diagnose by symptom

Run a small reproduction test

Use a short test instead of a full article:

# Heading 1

## Heading 2

**Bold** and *italic*

- Item A
- Item B

| Item | Value |
| --- | --- |
| A | 1 |

Try the same source through different paths:

1. regular paste into Google Docs
2. Paste from Markdown in Google Docs
3. Keep Source Formatting in Word
4. Merge Formatting in Word
5. Keep Text Only in Word
6. paste into a chat app

The differences show you which layer is changing the structure.

If you want to verify that the Markdown itself is valid before testing the destination, Markdown Viewer provides a browser preview.

For repeated publishing, separate the source from the destination

If you only paste into one application, use that application's native import or paste features.

If the same AI-generated draft needs to go to several destinations, keeping one Markdown source is easier to maintain.

Yomu is designed for that intermediate step: edit the Markdown once, then prepare it for different output formats instead of asking the AI to regenerate the article for every destination.

Summary

Copy-and-paste formatting usually breaks because the representation being transferred does not match what the destination understands.

The useful mental model is:

rendered AI screen → clipboard representation → destination document model

Choose the transfer method based on the destination. Use Markdown-aware paste when the source is Markdown, rich-text paste when visual formatting matters, plain text when styles are the problem, and destination-specific conversion when the same draft must travel across several platforms.

References

• W3C: Clipboard API and events
• Google Docs Editors Help: Use Markdown in Google Docs
• Google Workspace Updates: Import and export Markdown in Google Docs
• Microsoft Support: Control the formatting when you paste text