Line separators
PARAGRAPH SEPARATOR (U+2029)
Unicode’s paragraph break — the counterpart of U+2028, one level up.
- Codepoint
U+2029- Category
- Line separators
- Removed by default
- No
- Governing option
- Line endings
-n - Can be load-bearing
- No
Where it comes from
Word processors and layout tools when a real paragraph ends, and from PDF and RTF extraction.
Why it matters
Like U+2028 it is a break that most line-oriented tools ignore, so a document can appear to be one enormous line. It shares the same JavaScript string-literal history.
Before and after
Two paragraphs that most tools will read as one line.
The character is shown as a labelled chip so you can see where it sits. In your text it draws nothing at all.
When it is legitimate
Between paragraphs, in software that understands it. Plain text conventionally uses a blank line instead.
How to remove it
Turn on Line endings (`-n`); it is folded to a plain LF.
Is it an AI watermark?
Not a watermark
No. A structural character from document software. It says nothing about who wrote the paragraphs.
No connection to machine-generated text. It comes from software, from a keyboard, or from a person.
Questions
What is the difference from U+2028?
U+2028 ends a line within a paragraph; U+2029 ends the paragraph. Ghostchars folds both to a line feed under `-n`.
Should plain text use it?
No. The convention in plain text is a blank line, which every tool understands.
Check your own text
Paste anything into the cleaner to see every hidden character it contains, with position, codepoint and what happens to each one. Nothing is uploaded.