Wrap text to a fixed width locally - hard line breaks at a column you choose. Nothing is uploaded.
Running locally on your device ...
Running locally on your device ...
0%
Your files never left your device
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
Wrapping text inserts hard line breaks so that no line is longer than a width you choose. This is useful for plain-text emails, code comments, README files, commit messages, or any context with a fixed column limit (often 72 or 80). The tool breaks lines at word boundaries where possible, so words are not split.
Set the maximum width in characters. Each line is rewrapped to fit; a word longer than the width is kept whole and allowed to overflow rather than being cut in the middle. Existing paragraph breaks are preserved.
Everything runs entirely locally in your browser (no upload, even offline) - your text never leaves your device. Wrapping changes only where the line breaks fall, never the words themselves.
One important point about the width: it counts characters, not pixels. The wrapping therefore matches fixed-width (monospace) environments exactly - plain-text email, terminals and source code, where every column is the same width. In variable-width fonts the character count is only an approximation of the visible length.
| Input formats | Text input |
|---|---|
| Output format | TXT |
| Batch processing | No |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: Inserts hard line breaks at word boundaries so no line exceeds the chosen width (default 80). A word longer than the width overflows rather than being split. Pure text math; the words are unchanged.
No. The wrapping runs entirely locally in your browser - even offline. Your text never leaves your device.
No. A word longer than the width is kept whole and overflows the line, rather than being cut in the middle.
80 characters, a common limit; you can set any width you like.
Yes. Existing blank lines and paragraph breaks are preserved; only over-long lines are rewrapped.
Yes. LF, CRLF and the old Mac CR line ending are all recognized; the output uses plain line breaks (LF) uniformly.