Why Wrap Text?
- Terminal output typically 80 columns wide
- Email plain text usually 72 columns
- Git commit messages: 72 char line limit
- Code comments: 80 char convention
- Some CMS fields have character limits per line
Wrap long lines of text to a fixed column width — useful for plain-text email (72 columns), git commit message bodies (72), terminal output (80), and code comments (80–99). Set any width between 20 and 1000 columns and the result updates live.
Soft wrap (the default for prose) breaks only at word boundaries, so lines never end mid-word and may sit slightly under the target. Hard wrap breaks at the exact column position even inside long words — essential when the output must fit a strict column budget like a fixed-width terminal pane. Blank lines and existing paragraph breaks are preserved.
80 for terminal output and code comments (the classic VT100 default), 72 for email plain-text and git commit message bodies (per Linux kernel convention), and 100–120 for modern source code. Most documentation is wrapped at 80–90.
Soft wrap breaks at word boundaries — lines may be slightly under the target width but never end mid-word. Hard wrap breaks at the exact column even inside a word, useful when output must fit a strict column budget (e.g. fixed-width terminals or text-only emails).
Yes — blank lines between paragraphs are kept. Each paragraph is re-flowed independently, so wrapping doesn’t merge them or lose visual separation.
No — the wrap runs entirely in your browser using a single JavaScript pass over each paragraph.
Explore the full suite of TEXT tools and 290+ other free utilities at Chunky Munster.