Cleaning Tools
Cleaning tools exist because pasted text almost never arrives in the shape you actually want it in. Copy a paragraph out of a PDF and you get sentences broken mid-thought by hard line wraps. Copy from Word or Google Docs and you get curly quotes, non-breaking spaces, and stray HTML formatting. Six tools in this category each target one specific, genuinely different mess, because 'clean up my text' is really several separate problems wearing one name.
The single most important distinction across this whole category is the one between an intentional blank line (a real paragraph break) and an unintentional one (formatting noise) — and correspondingly, between an intentional single line break (poetry, a list) and an unintentional one (a PDF's mid-sentence wrap). Several of these tools exist specifically to make that distinction correctly, which is exactly why running the wrong cleaning tool on the wrong kind of text can do real damage, like destroying a poem's line structure.
None of these tools guess at your intent beyond the specific pattern they're built to detect — they apply a consistent, explainable rule, which means understanding what each tool actually does (rather than treating all of them as interchangeable 'fix my text' buttons) matters more here than in almost any other category on the site.
Three genuinely different source problems drive most of the traffic to this category. The first is PDF extraction, which introduces hard mid-sentence line wraps and sometimes hyphenated words split across a line break. The second is rich-text paste from Word or Google Docs, which introduces curly quotes, non-breaking spaces, and autocorrected em dashes that look fine on screen but can break code, search, or plain-text rendering elsewhere. The third is compiled or scraped lists — emails, keywords, URLs — accumulated from multiple sources, which introduces duplicate entries and inconsistent blank-line spacing rather than sentence-level formatting problems. Recognizing which of these three you're actually dealing with points you to the right one or two tools immediately instead of running your text through all six in sequence.
The tools in this category
Specifically targets PDF-style hard-wrapped lines — the kind that break a sentence mid-thought because the source document wrapped a line visually — while carefully preserving genuine blank-line paragraph breaks, even rejoining hyphenated words that got split across a line wrap. Not safe to use on poetry or lyrics, where every line break is intentional rather than a wrapping artifact; running that kind of text through this tool will flatten its structure.
Tightens up doubled spaces and stray leading/trailing whitespace in one pass, and catches a genuinely sneaky culprit most people never think to check for: the invisible non-breaking-space character that Word and Google Docs quietly insert, which looks identical to a normal space but can throw off a word count or make an exact search silently fail.
Removes exact or case-insensitive repeated lines from a list, keeping the first occurrence — built for cleaning a collected email list or a keyword list compiled from multiple overlapping sources, with the case-sensitivity trade-off explained honestly. Case-insensitive mode is the more practically useful default for most human-entered lists, since real-world email systems treat capitalization as irrelevant even though the technical spec technically allows it to matter.
A narrower, more surgical job than removing line breaks entirely: strips genuinely blank lines while preserving the paragraph-separating role of the ones you actually want, with a toggle to collapse excess blank lines down to exactly one rather than removing every trace of spacing. Useful on code and config files with inconsistent blank-line spacing between sections, not just prose.
Strips HTML tags, converts curly 'smart' quotes back to straight ones (which matters because curly quotes break code string literals), and normalizes the em dashes and non-breaking spaces that Word and Google Docs insert automatically during autoformatting. Also strips invisible zero-width Unicode characters that some web pages insert for internal line-wrap hinting, which can otherwise silently break an exact-text search.
Batch-fixes a misspelled name or swaps one term for another across an entire document in one action, with an optional regex mode for the rarer cases plain search can't handle — like matching any run of digits, or rearranging a 'Last, First' name list into 'First Last' order across dozens of lines using a single capture-group pattern.
A typical two-step cleanup for text extracted from a PDF or scraped off a web page: run /remove-line-breaks/ first to rejoin sentences broken by hard wraps, then /remove-empty-lines/ or /remove-extra-spaces/ to tidy up whatever blank-line or spacing noise is left over. Running them in the wrong order, or skipping the line-break step on genuinely line-structured content like poetry, is the most common mistake in this category.
/text-cleaner/ and /find-and-replace/ sit slightly apart from the other four tools here: rather than solving one narrow, specific mess, they're more general-purpose instruments — text-cleaner handles a bundle of common rich-text artifacts in one pass, and find-and-replace handles anything you can describe as a pattern, including problems none of the other five tools were built to catch.
For list-cleaning specifically (email lists, keyword lists, URL lists), the two relevant tools here are /remove-duplicate-lines/ and /remove-empty-lines/, and they're often better paired with /sort-lines/ in the /category/converting/ hub, which has its own dedicated dedupe-while-sorting mode that combines deduplication with alphabetizing in a single pass — worth knowing about if you're cleaning and organizing a list at the same time rather than just deduplicating it in isolation.
It's worth being honest about the limits of automated cleaning, too: none of these six tools attempt to correct spelling, grammar, or factual content — they only remove structural and formatting noise (unwanted breaks, spacing, duplicates, markup) while leaving the substance of what you wrote completely untouched. A document that's grammatically messy going in will still be grammatically messy after any combination of these tools, just with the formatting artifacts removed around it. That's a deliberate scope boundary, not a missing feature — cleaning tools clean formatting, they don't edit prose.
A second honest limitation worth naming: several of these tools rely on pattern-based heuristics rather than a full understanding of your document's meaning, which means edge cases exist for every one of them. Remove-line-breaks can't tell poetry from PDF-wrapped prose on its own; remove-duplicate-lines can't tell a legitimately repeated entry from an accidental one; text-cleaner's dash-normalization can occasionally flatten an intentional em dash along with the autoformatted ones it's meant to catch. None of this makes the tools unreliable for their intended purpose — it just means a quick visual check of the output, rather than blind trust, is worth doing on anything important.
FAQ
- Which cleaning tool should I use first on text copied from a PDF?
- Start with /remove-line-breaks/, since PDF text almost always arrives with sentences broken mid-thought by hard line wraps — fixing that first makes any subsequent cleaning (removing extra spaces, empty lines) work on properly-joined sentences rather than fragments.
- Is remove-line-breaks the same as remove-empty-lines?
- No — they solve different problems. Remove-line-breaks rejoins single, non-blank line breaks that broke a sentence mid-thought (the PDF-wrap problem), while remove-empty-lines strips genuinely blank lines that add unwanted spacing between otherwise correctly-formatted blocks. They're often used together but target different symptoms.
- Will any of these tools destroy intentional formatting, like a poem's line breaks?
- Yes, if used incorrectly — /remove-line-breaks/ in particular assumes every single line break is an unwanted wrapping artifact, which is true for prose extracted from a PDF but false for poetry, where every line break is meaningful. Don't run poetry or lyric text through that specific tool.
- I just need to fix curly quotes before pasting text into code — which tool do I need?
- /text-cleaner/ — it converts Word and Google Docs' automatically-substituted curly 'smart' quotes back to plain straight quotes, which is the specific fix needed since curly quotes are a different Unicode character than the ASCII quote mark most programming languages expect in a string literal, and will otherwise cause a syntax error.
- Can I run more than one cleaning tool on the same text without losing earlier fixes?
- Yes — each tool's output is safe to feed directly into the next tool's input, since none of them re-introduce the specific mess the previous tool just removed. Running remove-line-breaks, then remove-extra-spaces, then remove-empty-lines in sequence on a messy PDF extraction is a normal and safe three-step cleanup, each step targeting a distinct remaining problem.
- Is there one single tool that fixes everything wrong with messy pasted text?
- No, deliberately — this category is split into six narrow tools rather than one broad 'fix everything' button precisely because a single automated pass trying to guess at multiple different kinds of formatting problems at once is more likely to make an incorrect guess on any individual one. Diagnosing which specific mess you're actually dealing with (PDF wraps, rich-text artifacts, or list duplicates) and picking the matching tool gets a more reliable result than hoping one tool handles all three.
- Do any of these six tools require installing a browser extension or desktop app?
- No — every one runs directly on the page in your browser's own JavaScript engine, the same as every other tool on this site. There's nothing to install, and nothing you paste in is ever sent anywhere for processing.