Does it break words that are longer than the line width?

By default no — overlong words extend past the column limit rather than being split mid-word. Enable break-on-hyphen to allow splitting at hyphen characters.

What column widths are typical?

72 for git commit messages, 80 for older source code conventions, 100–120 for modern style guides. The width is configurable to any positive integer.

Are existing line breaks preserved?

Existing hard breaks are kept; the wrapper only adds new breaks where lines exceed the target width.

Where is the wrapping done?

Locally in your browser. The text is not uploaded.

60 · 72 · 80 · 100 · 120 cols

Wrap text to a target column width

Hard-wrap text to fixed columns (60, 72, 80, etc.). Optionally break extra-long words.

Word Wrap Workspace

Lines in

123 B

Lines out

max 78 cols

Width

target

Break long

off

policy

input · long lines

output · 80-col wrap

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor
incididunt ut labore et dolore magna aliqua.

Quick Start

How to word-wrap text

Hard-wrap to common column widths — 72 (email RFC), 80 (terminal), 100/120 (modern code). Word-aware so words stay whole unless 'Break long' is enabled.

01
Paste text
Long prose or code comments.
Tokenisation is Unicode-aware via \p{L}\p{N} property classes — so accented letters, ideographs, and emoji code points all count correctly.
textUTF-8Unicodecode pointslive
input · textlong · UTF-8
```
Lorem ipsum…
```
loaded · UTF-8UTF-8 · ready
02
Set width
Quick presets 60/72/80/100/120 or custom.
Live re-counts run on every keystroke through a memoised reducer, so even multi-megabyte inputs stay smooth in the editor.
80 colslivememoisedoptionssnappy
width · options80 · live
```
80-col wrap
```
options applied · livelive
03
Word-aware
Wraps at last space before width. Toggle 'Break long' for hard-break on very long words.
Output preserves the original line endings (\n vs \r\n) and trailing whitespace is reported separately so you can spot diff-only changes.
word-awareline endingswhitespacediff-cleanreproducible
policy · countedword · ready
```
words stay whole
```
counted · livecounted
04
Copy or download
One click.
Copy writes via the Async Clipboard API; downloads ship as text/plain; charset=utf-8 — nothing leaves your tab.
copyclipboardtext/plainblobclient-side
export · copiedready · done
```
✓ Copied
```
shipped · ready to shipsuccess

Pro tips

Text-processing fundamentals worth knowing

Tokenise with Unicode classes

Use \p{L}\p{N} with the u flag so accents, ideographs, and emoji count properly.

Normalise line endings

Convert \r\n to \n before diffing or hashing — Windows-vs-Unix endings produce phantom changes.

Mind invisible characters

Zero-width joiners, BOMs, and non-breaking spaces look identical to ASCII space. Strip them before comparison or storage.

Stream don’t slurp

For multi-megabyte text, iterate line-by-line rather than loading everything to memory — keeps the tab responsive.

Choose collation deliberately

Default JS sort is code-point order, not human alphabetical. Use Intl.Collator for locale-aware sorting.

Re-run after normalisation

NFC vs NFD changes byte length but not visible glyphs. String.prototype.normalize() before counts and comparisons.

Use Cases

When to wrap

Anywhere width matters.

Email body (RFC 2822)

72 chars for plain-text email per RFC. Tokenisation uses Unicode property classes (\p{L}, \p{N}) with the u flag so accents, ideographs, and emoji code points all count correctly. Surrogate-pair-aware counts mean 🚀 weighs 1, not 2.

Unicode-correct

Code comments

80 or 100 cols matching project style. Result updates as you type — paste and watch totals settle in milliseconds even on multi-megabyte inputs. Heavy work runs through a memoised reducer so the editor never janks.

diff-clean

Terminal output

80-col is the classic terminal width. Output normalises line endings to LF for clean diffs across platforms. Windows-vs-Unix CRLF mismatches disappear, which keeps git blame honest and review comments focused on real changes.

instant counts

PR descriptions

Markdown bodies that read well in narrow viewports. Code-point counts are stable across NFC/NFD normalisation. Pair with the Reading Time Calculator to layer scan-time on top of raw counts, useful for editorial budgets and SEO meta-description limits.

platform-aware

Plain-text reports

Fixed-width reports for legacy systems. All processing runs client-side — paste sensitive or pre-publish copy without it leaving the tab. The clipboard API writes UTF-8 text/plain so it survives transit to any editor or CMS.

code-point-accurate

ASCII art

Maintain consistent width across art. Same input plus same options always produces identical output, so the tool is safe to embed in CI scripts or doc-generation pipelines without race conditions.

lossless

FAQ

Frequently asked questions

Does it preserve word boundaries?

Yes by default — words stay whole. Enable 'Break long' to hard-break words longer than width.

What about existing line breaks?

Preserved — each input line is wrapped independently.

Common width choices?

72 = email; 80 = terminal/code classic; 100 = modern code (Prettier default); 120 = wide code.

Tabs?

Counted at literal width (1 char). Convert tabs to spaces first if you need accurate visual width.

Is anything sent to a server?

No. All processing runs locally.

Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

47 in queue·8 shipped this month

Request queued. Thanks!