NOCLAU GUIDE
Em Dashes in AI Writing
When and how to replace Em Dashes in text.
An em dash is punctuation, not evidence of an author or a writing system. If a draft contains more dashes than your publication style allows, edit the sentences for clarity rather than treating punctuation as a detector signal. This guide shows how to decide between keeping a dash, replacing the surrounding construction, and using a mechanical tool for a deliberately narrow transformation. The examples are written for this guide and describe editing choices, not measured differences between human and AI writing.
Scroll the table sideways to see every column.
| Input | Remove | Replace with hyphen |
|---|---|---|
| A—B | AB | A-B |
| A — B | A B (two spaces) | A - B |
| A⸺B | AB | A-B |
| A–B (en dash) | Unchanged | Unchanged |
Identify the mark before changing it
The em dash is U+2014. It differs from a hyphen used inside words, an en dash often used in ranges, and a minus sign used in mathematics. A search-and-replace operation that groups all of them together can change meanings that have nothing to do with prose rhythm. First inspect the character and determine whether the apparent dash is actually one of the variants your chosen tool handles.
noclau's dash rule handles U+2014, U+2E3A, and U+2E3B. It does not replace every horizontal-looking symbol. This is useful when a document mixes ordinary hyphenated terms with em dashes: the terms remain unchanged. It also means that an untouched en dash is not a tool failure. Choose a separate edit only when the destination's style guide calls for it.
Decide what the sentence needs
Read the sentence aloud and identify what the dash does. It may introduce an explanation, separate a parenthetical aside, or interrupt a thought. The right replacement depends on that relationship. A colon may work before an explanation; parentheses may work for an aside; a new sentence may give a dense paragraph room to breathe. Those are editorial decisions rather than character substitutions.
Consider this example: The import failed—one column had a different header. A possible revision is: The import failed because one column had a different header. Removing the dash alone gives failedone when no surrounding spaces exist. Replacing it with a hyphen keeps a separator but does not provide the same grammatical relationship as the revised sentence. The shortest automatic result is not necessarily the clearest prose.
Compare three concrete editing choices
For the sentence The draft — a first attempt — needs review, keeping the dashes preserves the current interruption. An editorial rewrite could be The draft, a first attempt, needs review. A simpler alternative is This first draft needs review. Neither rewrite requires you to argue about whether an AI system might use dashes more often than a human writer.
If a receiving system accepts only a narrow punctuation set, replacing each supported dash with a hyphen may be an explicit technical requirement. In that case, document the requirement and apply the transformation consistently. Do not describe that compatibility step as making the writing human. The output still needs a read-through, especially where the original uses two- or three-em dash symbols for specialized purposes.
Understand the tool's mechanical behavior
The em dash remover starts in Custom mode with dash removal selected and invisible-character removal turned off. It removes the supported dash characters and preserves the surrounding spaces. Therefore A — B becomes A B, with two ordinary spaces, while A—B becomes AB. The tool does not collapse doubled spaces or invent a replacement word boundary.
Choosing Replace dashes with hyphens replaces each supported character with one ASCII hyphen. A single U+2E3A character becomes one hyphen rather than two. Choosing Keep dashes leaves the supported marks unchanged. Conservative cleaning also keeps dashes. If you switch modes while editing, check the visible rule note and run the tool again before copying the result.
Review each transformed sentence
Use the diff to locate proposed changes, then read the full output rather than only the colored markers. The preview can be shortened for long input, so divide a long manuscript into logical sections. Check dialogue, quoted passages, titles, and parenthetical asides particularly carefully. A quoted source should not be silently rewritten just to match a general preference for fewer dashes.
When exact quotation matters, preserve the quotation and follow your publication's rules for indicating editorial changes. For ordinary original prose, review whether both sides of a removed dash remain complete and readable. If a sentence now has an unexplained abrupt transition, restore the dash or rewrite the relationship explicitly. A successful copy operation is not editorial acceptance.
Separate style consistency from detector claims
A document can use dashes consistently and still contain factual mistakes, weak reasoning, or uncredited material. Conversely, a thoughtful human writer may use many dashes. noclau does not measure authorship or predict third-party AI detector results. The practical reason to edit punctuation is to improve readability, meet a house style, or satisfy a format constraint.
If your school, employer, or publication requires disclosure of AI assistance, changing punctuation does not change that requirement. Preserve citations and attribution while revising. Spend the review time on the ideas and evidence in the draft: verify claims, remove repetition, and make the argument your own through substantive work. Those tasks are separate from the mechanical cleanup offered here.
Check the destination and keep a style record
Paste the revised passage into the destination and inspect its final appearance. A publishing system may apply smart punctuation or transform consecutive hyphens, so a textarea preview is not the last word. Check both the saved text and the rendered page when exact characters matter. If the system changes the punctuation again, resolve that setting rather than repeatedly cleaning exports.
For recurring editorial work, record a few accepted examples in your style notes. State when an em dash is appropriate, when an explanation should become a separate sentence, and whether technical fields require ASCII punctuation. This small set of decisions is more useful than a blanket ban. It lets several editors produce consistent work while still choosing punctuation that fits the sentence.