Why does ChatGPT text paste weirdly into Word and Google Docs?
Because the chat window copies more than words: ChatGPT, Claude, and Gemini put styled HTML plus markdown remnants on your clipboard, and hidden characters ride along inside the text itself. Your destination app then picks its poison — a rich paste imports the chat's fonts, colors, and heading styles; a plain paste surfaces the raw markdown markers (**bold**, ### headers, backticks, hyphen bullets) that the chat UI was rendering for you.
Meanwhile the character-level layer travels with either mode. Chat interfaces are HTML, so copied answers routinely contain non-breaking spaces (U+00A0), curly quotes (U+201C, U+201D, U+2018, U+2019), em dashes (U+2014), and sometimes invisible characters like zero-width spaces (U+200B). Originality.ai's testing found that invisible characters mostly enter documents through exactly these Word, Google Docs, and HTML copy pipelines rather than from the models themselves — though models have emitted them too: in April 2025, ChatGPT's o3 and o4-mini briefly inserted narrow no-break spaces (U+202F) into long answers, as documented by Rumi and covered on our ChatGPT watermark page. Either way, the artifacts end up in your document — the same mechanism behind why text pastes weird from any source, not just chatbots.
What survives paste-without-formatting (and what doesn't)?
Ctrl+Shift+V strips formatting, not characters — so it solves exactly half the problem. Here's the breakdown:
| Artifact | Survives Ctrl+Shift+V? | What fixes it |
|---|---|---|
| Chat styling (fonts, colors, headings) | No — this is what plain paste removes | Ctrl+Shift+V alone |
| Markdown markers (**, ###, backticks) | Yes — they're literal text | The Strip Markdown toggle (off in every preset) |
| Curly quotes (U+2018, U+2019, U+201C, U+201D) | Yes | Typography normalization |
| Special spaces (U+00A0, U+202F) | Yes | Whitespace normalization |
| Invisible characters (U+200B, U+2060, U+FEFF) | Yes | Invisible-character removal |
Curly quotes as an AI habit are documented in Wikipedia's "Signs of AI writing" guide — one more thing that follows the text into every app you paste it into.
Per-app fixes: Word, Google Docs, Notion, email & CMS
Microsoft Word
Paste with Ctrl+Shift+V (text-only paste in current versions of Word) or use Paste Special (Ctrl+Alt+V) → Unformatted Text. Then press Ctrl+Shift+8 (the ¶ button) to show formatting marks: a normal space appears as a raised dot (·) while a non-breaking space appears as a small ring (°) — an instant visual audit of leftover NBSPs. Find and Replace with ^s converts them. Watch out: Word's AutoFormat may re-curl straight quotes as you type afterwards.
Google Docs
Paste with Ctrl+Shift+V (Cmd+Shift+V on Mac). For text you already pasted, select it and use Format → Clear formatting (Ctrl+\). Both only affect styling — markdown markers, curly quotes, and special spaces stay in the text, which is why pasted AI answers still show stray asterisks even after clearing formatting. Fix those before pasting, or with per-character find-and-replace. Docs also has no equivalent of Word's formatting-marks view, so the quickest way to see what is actually in the text is the AI watermark checker, which counts every hidden character by code point.
Notion
Ctrl+Shift+V pastes plain — and Notion helpfully parses markdown on plain-text paste, turning ### into a real heading and **bold** into bold. That's often what you want. When a block lands as the wrong type, select it and type /turn-into (or use the drag-handle menu → Turn into) to convert it. Rich pastes from chat UIs can double-format, so plain paste is the safer default.
Email (Gmail & Outlook)
In Gmail's composer, Ctrl+Shift+V pastes as plain text; Outlook offers paste options → Keep Text Only. Email is where markdown residue looks worst — "**Next steps:**" in a client email reads as carelessness — and where non-breaking spaces cause those odd mid-sentence line breaks. Clean first, with Strip Markdown switched on; the recipient sees only normal prose.
CMS (WordPress, Webflow & friends)
WordPress's block editor converts some pasted markdown and lets the rest through as literal characters; Webflow's rich-text element keeps whatever characters arrive. NBSPs are the silent killer here — they break responsive line wrapping so two words wrap as one glued unit, the exact problem covered in fix weird spacing and remove non-breaking spaces. Paste clean text and none of it reaches your published page.
The one-step alternative: clean it before you paste
Instead of memorizing a fix per app, run the text through the AI text cleaner at the top of this page first. The default AI Clean preset normalizes quotes and dashes, converts special spaces, and removes hidden characters in one pass — and the "What Changed" report names every change, so you know exactly what was in the text. Markdown markers are deliberately left alone by every preset, because Notion and other markdown-aware editors turn them into real formatting on paste; when you want them gone, switch on Strip Markdown in Advanced Controls. Then every destination gets the same clean input.
What you copied
### Q3 Summary **Revenue** rose 12%[U+00A0]YoY — “ahead of plan,” per the CFO. Kickoff: 9:30[U+202F]AM
After the default AI Clean preset
### Q3 Summary **Revenue** rose 12% YoY - "ahead of plan," per the CFO. Kickoff: 9:30 AM
Same text with Strip Markdown switched on
Q3 Summary Revenue rose 12% YoY - "ahead of plan," per the CFO. Kickoff: 9:30 AM
The bracketed tags [U+00A0] (non-breaking space) and [U+202F] (narrow no-break space) stand in for characters that are invisible in real text — that's the point. The default preset reports five changes here: both special spaces become regular spaces, and the em dash and curly quotes are normalized (see how typography normalization works). The ### and ** markers survive that pass on purpose — turn on Strip Markdown in Advanced Controls for the second version. Everything runs in your browser, free, with zero visible words changed.