Reflow words into lines with a grapheme-aware width check and an optional long-word breaking mode.
Text cleanup runs locally in your browser. These tools operate on plain text lines; structured CSV/JSON/XML and regex workflows remain in their dedicated tools.
Compare line count and trailing-newline state before reusing the wrapped output. Long-word breaking is destructive when enabled.
Use output as input only when the preview is what you intended. Restore returns to the page-load sample, and the before/after audit remains local to your browser.
A wrap width can mean code points, grapheme clusters, display columns, or bytes depending on the target system. This tool is for text-oriented wrapping; terminal width and proportional-font layout can differ. If the output feeds a strict protocol or fixed-column file, verify the receiving system’s width definition before relying on the line count.
Preserving existing line breaks and collapsing whitespace are different transformations. Decide whether the source formatting is meaningful before wrapping. For prose, word-boundary wrapping is usually easier to read; for identifiers, URLs, or unbroken strings, forcing a break can change copy/paste behavior or make the result unsuitable for downstream parsing.
After wrapping, scan for lines that exceed the requested width because of an indivisible token. A single long URL or hash can defeat a word-boundary rule. If strict width is required, choose an explicit hard-break policy and document that it may split tokens that were contiguous in the source.
Wrapping changes line boundaries even when the visible words stay the same. Keep the source text if later systems compare exact line positions, generate patches, or use digital signatures. A practical verification is to join wrapped lines using the intended whitespace rule and confirm the semantic text still matches the source.
WebToolArc