Guide
Text cleanup workflows: word count, diff, case, then slugs
Suggests an efficient order for word metrics, comparisons, case normalization, and slug or line utilities when preparing content for publishing.
Start with metrics: word counter
When you inherit messy copy, measure first: counts, reading time, and rough structure inform what to normalize next.
Word counter is cheap signal before you invest in heavy manual editing.
See what changed: text diff
Use the diff tool when you have two versions of the same document and need line-level understanding before merging.
Diff highlights disagreement between inputs; it does not choose the “right” wording for you.
Normalize surface form: case converter
Use case conversion when naming conventions, titles, or code style require consistent casing.
Title case rules vary by style guide; treat the tool as practical, not legalistic typography.
Ship-ready strings: slug and line utilities
Use slug tools when you need URL-safe identifiers from headlines or lists.
Duplicate-line removal and sorting help clean imports from spreadsheets or logs before downstream steps.
Text tools
FAQ
Should I diff before or after case changes?
Diff first on the raw inputs if you need to audit editorial changes; run case passes after you agree on content to avoid noisy comparisons.
Does the slug tool enforce global uniqueness?
No. It produces a candidate string; collision checks belong to your CMS or router.
Can diff handle huge files?
Browser tools are best for practical pasted sizes. Split very large inputs for responsiveness.
Will title case match Chicago Manual?
No. It applies straightforward rules; consult a human editor for publication-grade headings.
When is word counter insufficient?
When you need tokenization for billing, localization quality, or compliance—you need language-aware tooling beyond heuristics.