Does it truncate by characters or words?

Both modes are available. Character mode cuts at a fixed character count; word mode cuts at a fixed word count. Pick whichever matches your downstream limit.

Will it cut a word in half?

Only if you ask it to. Enable "break on whitespace" to fall back to the nearest earlier space, which produces clean word boundaries.

Is the ellipsis configurable?

Yes. The default appended marker is …, but any string works — "...", " [more]", or none at all.

Where does truncation happen?

In your browser. The text is processed locally and not transmitted.

chars · words · word-boundary aware

Truncate text to a max length

Cut text at N chars or N words, optionally snapping to the nearest word boundary. Configurable ellipsis.

Truncate Text Workspace

Input size

123 B

19 words

Output size

57 B

truncated

Limit

chars

Boundary

word

snap

input · text

output · truncated

Lorem ipsum dolor sit amet, consectetur adipiscing elit,…

Quick Start

How to truncate text

Cap text at a character or word limit, optionally snapping to the nearest word boundary so you don't cut mid-word.

01
Paste text
Long prose, descriptions, post bodies.
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 dolor…
```
loaded · UTF-8UTF-8 · ready
02
Set limit
Chars (280, 160, 155) or words (50, 100).
Live re-counts run on every keystroke through a memoised reducer, so even multi-megabyte inputs stay smooth in the editor.
charswordslivememoisedoptions
limit · options60 chars · live
```
Lorem ipsum…
```
options applied · livelive
03
Word boundary
Avoid cutting mid-word. Falls back to char-exact if no boundary nearby.
Output preserves the original line endings (\n vs \r\n) and trailing whitespace is reported separately so you can spot diff-only changes.
snapline endingswhitespacediff-cleanreproducible
snap · countedboundary · ready
```
Lorem ipsum dolor…
```
counted · livecounted
04
Copy or download
Per-line option for table cells.
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 truncate

Anywhere there's a length limit.

Meta descriptions

Keep under ~155 chars for Google search snippets. 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

Card previews

Truncate body text in card components. 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

Tweet thread split

Cut at 280 chars for individual tweets. 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

Excerpts

Generate consistent-length excerpts for archive pages. 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

Table cells

Per-line truncation for tabular display. 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

Push notifications

Mobile push titles have ~178 char limits. 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 the ellipsis count toward the limit?

Yes — output is at most the configured limit including the ellipsis.

What happens if the input is shorter than the limit?

It's returned as-is with no ellipsis.

Word boundary — how is it found?

Last space before the cut. Snaps only if found in the last half of the cut window (avoids cutting too short).

Per-line vs whole-text?

Per-line truncates each line individually (table-cell style). Off = treats input as a single string.

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!