Text Wrapper

What this tool does

Text Wrapper inserts line breaks so that no line exceeds the width you choose, breaking only between words. It can re-flow paragraphs that were wrapped at a different width, indent every line, add a prefix such as “> ” or “// ”, and optionally split words that are longer than the limit.

Many places that show text never wrap it for you: terminals, plain-text email, git commit messages, code comments and fixed-width printouts. Long lines either scroll off to the side or get chopped at awkward points. Conventions grew up to avoid this; RFC 5322 recommends email lines of no more than 78 characters, and git tooling expects commit bodies around 72.

This wrapper uses a greedy algorithm: it adds words to the current line until the next one would cross the limit, then starts a new line. Widths are measured in user-perceived characters, so an emoji or an accented letter counts once. With re-flow on, existing line breaks inside a paragraph are joined first, which lets you rewrap text from one width to another; blank lines keep paragraphs apart. The prefix and indent are included in the width. It all happens in your browser.

How to use Text Wrapper

1. Paste the text you want to wrap, or click Sample.
2. Pick a “Line width” preset such as 72 for email, or choose Custom and enter your own value.
3. Keep “Re-flow paragraphs” on to rewrap already wrapped text; turn it off to treat every existing line separately.
4. Decide whether to “Break words longer than the width”; leave it off to keep URLs whole.
5. Add an Indent or a “Line prefix” like “> ” for quoted replies or “# ” for comments.
6. Choose line endings, check “Longest line” in the statistics, and copy or download the result.

Tips for better results

• For git commits, keep the subject line at 50 characters and wrap the body at 72.
• Wrapping with a “// ” prefix turns a paragraph into a neatly formatted code comment block.
• Turn re-flow off for lists and addresses so each existing line stays on its own.
• Wide characters such as Chinese ideographs take two columns in most terminals, so use a smaller width for CJK text.

Common use cases

• Formatting a plain-text email or newsletter so it reads well in any mail client.
• Rewrapping a README section that was edited and now has uneven line lengths.
• Preparing text for a receipt printer or a fixed-width display with a strict column limit.
• Quoting a message with “> ” prefixes when replying in a mailing list.

Common mistakes to avoid

• Hard-wrapping text that will be shown in a web page or word processor, which then wraps it again and creates ragged lines.
• Forgetting that the prefix and indent use part of the width, so the text itself gets fewer characters.
• Re-flowing Markdown lists or code, which joins separate items into one paragraph.