ChatGPT paste looks different in Google Docs because the clipboard often carries more than the glyphs you saw in the chat. Docs then interprets no-break spaces, zero-width code points, and leftover HTML the way a word processor should: it refuses to wrap where a no-break space sits, it treats a zero-width space as part of the word, and it can keep rich-text residue from a select-and-copy.
The words did not change. The code points around them did.
What Docs does with a no-break space
A normal space (U+0020) is a wrap opportunity. A no-break space (U+00A0) is a glue. Chat UIs and many editors insert U+00A0 when they want "100 km" or "Mr. Smith" to stay on one line. When that character is scattered through a paragraph, Docs will not break the line where you expect. On a narrow column, or in a comment, the line overflows or leaves an awkward hole.
The narrow no-break space (U+202F) is the same idea with a thinner glyph. In April 2025 it showed up in longer o3 and o4-mini pastes. OpenAI called it a training quirk. It looks identical to a space in Docs until you put the cursor in the middle of a "word" that will not hyphenate.
What a zero-width space does to search inside the doc
U+200B has no width. Docs will still store it. Find in document can miss marketing if the file contains market[U+200B]ing. Word count can drift by a few characters. Collaborators who copy a heading into a URL slug get a character they cannot see and a link that does not match the heading they typed later.
This is why "it looks fine in ChatGPT and weird in Docs" is usually a clipboard story, not a font story.
Select-all versus the Copy button
If you drag-select the reply, the browser may put an HTML fragment on the clipboard. ChatGPT's UI has used data-message-* attributes to track the bubble. Docs then has to decide whether to keep any of that markup. The Copy control on the message has more often produced a plainer payload.
When a paste into Docs brings unexpected bold, extra spans, or a style that will not clear with "paste without formatting," try the Copy button first, then paste again. Ctrl+Shift+V (or Cmd+Shift+V) strips a lot of rich formatting. It does not always strip valid Unicode spaces, because those are still plain text.
A 30-second check in Docs
Paste the ChatGPT output into a new Doc.
Put the cursor where wrapping looks wrong and use the right-arrow key. If the cursor hesitates on an empty column, you likely have U+00A0 or U+202F.
Search for a word you can see. If Docs finds nothing, try pasting that word from the chat again, or inspect code points in a text editor.
If you need a clean copy, run a Unicode cleaner, then paste the result with paste-without-formatting.
GPT CLEAN UP will scan the draft on the homepage, show what it found, and let you copy a character-clean version without a plan. Phrase suggestions and humanization are paid. The Docs problem is almost always the free layer: hidden spaces and paste HTML.
Does this mean Docs is detecting AI?
No. Docs is laying out characters. It has no idea who wrote the paragraph. AI detectors that people worry about in school or publishing score writing patterns: predictability, burstiness, vocabulary. Originality.ai's own test of adding or removing invisible characters did not move those scores. Cleaning the paste so Docs wraps correctly is a formatting fix.
OpenAI has not shipped a text watermark in ChatGPT. Image and audio files can carry C2PA and SynthID. A Google Doc is neither.
When the paste is still ugly after a clean
Then the remaining issues are visible: smart quotes, long dashes, markdown bold that never rendered, extra blank lines from the chat column. Those are optional. Strip hidden characters first so you can see the real layout, then decide whether you want ASCII punctuation. Mixing those two jobs in one panic pass is how people delete meaning they meant to keep.
Docs-specific moves that actually help
Paste without formatting as the default. In Docs, Ctrl+Shift+V (Cmd+Shift+V on Mac) is the gesture that avoids inheriting chat-bubble styles. Pair it with a Unicode strip so you are not keeping U+00A0.
Clear direct formatting after a bad paste. Select the paragraph, then Format → Clear formatting. This drops local overrides. It will not delete U+200B.
Watch comments and suggestions. A no-break space inside a suggested edit is painful to select. If a comment thread looks like the text is "stuck" to the next word, inspect that join.
Tables. Docs tables already fight wrapping. A single U+00A0 in a cell is enough to force horizontal scroll on a laptop. Clean the source, then paste into the cell.
Add-ons and "markdown in Docs." Some add-ons re-parse the paste and reintroduce spans. If a clean paste becomes dirty after an add-on runs, the add-on is the second clipboard. Turn it off for the paste step.
A small QA checklist before you share the Doc
Search for a distinctive word from the ChatGPT output. If Docs cannot find a word you can see, suspect zero-width characters.
Shrink the browser window. If a paragraph overflows instead of wrapping, suspect no-break spaces.
Copy a heading into the document outline or a link. If the URL looks identical to a later typed heading and the two do not match in a script, print code points.
Keep the original chat until a second person can open the Doc on their machine. Clipboard bugs are local until they are in the file.
That is the whole Docs problem: the file stored different characters than the screen showed. Once you believe that, the cleaner is obvious and the "watermark" story is optional.
Top comments (0)