15 Common Copy-Paste Formatting Problems and How to Fix Them

Most copy-paste formatting problems have one of three causes: the source broke its lines for layout instead of meaning, it used characters that look ordinary but are not, or formatting and markup travelled along with the words. The fifteen problems below are grouped that way, each with its cause and its fix.

Where a fix names a setting, it is an option in the Text Cleaner or a mode in Remove Line Breaks. In the examples, ⏎ stands for a line break, and a bracketed label such as [NBSP] stands for a character you cannot normally see.

Line breaks and spacing

1. Lines broken in the middle of sentences

Text copied from a PDF or a plain-text email has a line break at the end of every visual line, because the source recorded lines, not paragraphs. In a column of a different width the breaks land mid-sentence.

Fix: In Remove Line Breaks, choose Keep paragraph breaks. In the Text Cleaner, choose Join wrapped lines but preserve paragraphs. Both treat a blank line as a paragraph boundary, so check that the pasted text has them, and both keep list items on their own lines. Fixing text copied from a PDF covers the awkward cases.

2. Words split by end-of-line hyphens

Typeset text hyphenates long words at line ends. Once the lines are joined, infor-⏎mation becomes infor- mation.

Fix: Tick Rejoin words hyphenated across lines, which is in both tools and off by default. It works only while lines are being joined, and it merges only when both halves are lowercase. It cannot tell a layout hyphen from a real one: well-⏎known comes out as wellknown. Read the result.

3. Double and multiple spaces

Two spaces after a full stop, gaps left by justified type, columns lined up with the space bar. A web page hides the extras, because browsers collapse runs of spaces when they render. A plain-text field or a data file shows every one.

Fix: Collapse multiple spaces, part of the default General Clean preset. Indentation at the start of a line is left alone. More in removing extra spaces and tabs.

4. Trailing spaces at the ends of lines

You cannot see them, but software can. They stop two values from matching, add noise to file comparisons, and in Markdown two or more spaces at the end of a line force a line break.

Fix: Trim line endings, also part of General Clean, removes spaces and tabs at the end of every line. Trim each line removes them at the start as well, which you do not want for indented text.

5. Tabs where spaces were expected

Copying cells from a spreadsheet or a table puts a tab between the values, and word processors use tabs for alignment. In a plain field a tab appears as a gap of unpredictable width, and a search for a space will not find it.

Fix: Tabs → spaces replaces each tab with one space. Leave it off when the text is going into a spreadsheet, where the tabs are what place each value in its own cell.

6. Too many blank lines

Three or four empty lines sit between paragraphs, often because spacing the source drew around each block became real empty lines in the copy.

Fix: Collapse multiple blank lines to one, in General Clean, keeps a single blank line between paragraphs. Remove empty lines deletes all of them: right for a list, wrong for prose.

7. Mixed line endings

Windows marks the end of a line with two characters, CR and LF. Unix systems and macOS use LF alone. Text assembled from several places can contain both, and the signs are indirect: a file comparison that flags every line as changed, or a program that rejects a file that looks fine.

Fix: The Text Cleaner converts every line ending to LF before it does anything else, so one pass makes them consistent. Its output is always LF. If the destination needs CRLF, set that when you save the file in your editor. CRLF, LF and CR compared has the background.

Lookalike and invisible characters

8. Non-breaking spaces

A non-breaking space (U+00A0) looks exactly like a space and is a different character. Word processors and web pages, where it is written  , use it to keep two words on one line. A search for 10 kg can miss 10[NBSP]kg, and Excel’s TRIM function does not remove it.

Fix: Normalize non-breaking spaces, on in General Clean, converts U+00A0 and two related spaces (U+202F and U+2007) to an ordinary space. See the non-breaking space explained.

9. Zero-width and other invisible characters

The zero-width space (U+200B), the byte order mark (U+FEFF) and the soft hyphen (U+00AD) take up no visible room. The clues are indirect: a word that search cannot find, or a character count higher than the text you can see.

Fix: Remove zero-width spaces, Remove byte order marks and Remove soft hyphens. The Word / Docs preset turns on all three. Leave Remove ZWJ / ZWNJ off unless you are sure, because emoji sequences and scripts such as Persian and Arabic depend on those characters. Invisible Unicode characters describes each one.

10. Curly quotes in code or data

Word processors replace " with “ and ”, and ' with ’. That is right for prose and wrong for code, JSON, CSV and command lines, where only the straight characters count as syntax.

Fix: Smart quotes → straight quotes and Smart apostrophes → straight apostrophes. Both are off in every preset, because in prose the curly forms are usually wanted. Smart quotes versus straight quotes helps you decide.

11. Dashes and ellipsis characters in ASCII-only fields

The en dash, the em dash and the single-character ellipsis are not ASCII. A field or system limited to ASCII cannot store them, so they are rejected or replaced with something else.

Fix: En dash → hyphen, Em dash → hyphen and Ellipsis character → three periods. Each dash becomes a single hyphen with no spaces added, so rain—again turns into rain-again and reads like a compound word. Adjust those by hand.

Leftover formatting, markup and repeated lines

When you copy from a web page or a document, the clipboard usually holds plain text and at least one formatted version of the selection. A rich editor takes the formatted one, so the source’s font, size, colour and links arrive with the words.

Fix: Paste as plain text. Google Docs calls it “Paste without formatting” and puts it on Ctrl+Shift+V (Cmd+Shift+V on a Mac), and other rich editors generally have an equivalent command. Pasting into the Text Cleaner has the same effect, because its input box holds plain text only. Plain text versus rich text explains the mechanism. Cleaning text from Word and Google Docs covers what those two leave behind even after the styling has gone.

13. Raw HTML tags and entities

Text taken from a page’s source, a CMS’s code view or a data export arrives with its markup showing.

Before

<p>Fish &amp; chips &mdash; <strong>large</strong> portion</p>

After

Fish & chips — large portion

Fix: Strip HTML tags and Decode HTML entities, both included in the Plain Text preset, which produced the result above. Paragraphs and <br> become line breaks, and the contents of <script> and <style> are dropped. Converting HTML to plain text explains the pitfalls.

14. Markdown symbols showing as literal characters

## Heading, **bold** and backticks appear exactly as typed when Markdown, often from a chatbot answer, is pasted into a field that does not render it.

Fix: The AI Formatting preset removes heading markers, bold and italic markers, code fences and the backticks around inline code, without changing any words. Tick Remove Markdown list markers if the -, *, + or number at the start of each item should go too. Links, tables and blockquote markers are not rewritten, so fix those by hand. See removing Markdown formatting.

15. Duplicate lines in a list

Merging lists from several places leaves repeats. They often differ by a capital letter or a trailing space, so software does not see them as identical.

Fix: Remove duplicate lines, comparing by Exact match, Ignore case or Ignore surrounding whitespace. The first occurrence is kept and the original order is preserved. Lines are compared after the whitespace cleanup, so a trailing space no longer hides a repeat. Removing duplicate lines explains which comparison to pick.

Fixing several at once

The Text Cleaner’s presets group these fixes by where the text came from.

Preset Problems covered
General Clean (default) 3, 4, 6, 7, 8
PDF Copy General Clean plus 1, and the soft hyphens and zero-width spaces from 9
Word / Docs General Clean plus 9
Plain Text General Clean plus 13 and 14, and the zero-width spaces and byte order marks from 9
AI Formatting General Clean plus 14

No preset fixes problems 2, 5, 10, 11 or 15. Each needs a box ticked, because each fix can damage text that was fine. Problem 12 is solved at the moment of pasting, not by cleaning.

Start with General Clean, read the summary of what changed, and add options one at a time. What a text cleaner is sets out what a tool of this kind will and will not touch.

Sources

  1. CommonMark Spec, Version 0.31.2 — CommonMark
  2. white-space CSS property — MDN Web Docs
  3. The Unicode Standard 16.0, Chapter 5: Implementation Guidelines — Unicode Consortium
  4. TRIM function — Microsoft Support
  5. Keyboard shortcuts for Google Docs — Google Docs Editors Help

This guide was drafted with AI assistance and reviewed by the publisher. See the editorial policy for how guides are written and corrected.