⌘ K
per-line · left / right / both

Trim whitespace from every line

Strip leading, trailing, or both-sides whitespace from every line. Preserves line count and structure.

Trim Whitespace Workspace
Input size
65 B
4 lines
Output size
50 B
4 lines
Bytes removed
15 B
whitespace
Side
both
.trim()
Trim
input · with whitespace
output · trimmed
hello world
another line
tabbed line
spaced   line
Quick Start

How to trim whitespace from text

Each line is processed independently. Both = String.prototype.trim(), Left = trimStart(), Right = trimEnd().

  1. 01

    Paste text

    Each line is processed separately. Tabs and spaces both count as whitespace.

    Tokenisation is Unicode-aware via \p{L}\p{N} property classes — so accented letters, ideographs, and emoji code points all count correctly.

    per-lineUTF-8Unicodecode pointslive
    input · textraw · UTF-8
       hello
    loaded · UTF-8UTF-8 · ready
  2. 02

    Choose side

    Both / Left / Right. Both is most common.

    bothleftright
    sideboth
    hello
    trimmed
  3. 03

    Line structure preserved

    Number of lines doesn't change — only the whitespace on each.

    Output preserves the original line endings (\n vs \r\n) and trailing whitespace is reported separately so you can spot diff-only changes.

    preserveline endingswhitespacediff-cleanreproducible
    lines · countedkept · ready
    line A
line B
    counted · livecounted
  4. 04

    Copy or download

    One-click copy or download as plain text.

    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.

Related toolsRemove WhitespaceRemove Empty LinesTabs ↔ SpacesIndent TextPad TextRemove Line Breaks
Use Cases

When to trim text

Anywhere stray whitespace causes problems.

Email lists

Trim before validating email addresses. 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

CSV cleanup

Cells often arrive with extra padding from spreadsheets. 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

Config lines

Strip indentation before parsing key=value configs. 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

Log triage

Normalize indented log lines for diff/sort. 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

Code paste

Clean up code copied from PDFs or emails. 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

Form input

Trim before comparing usernames or slugs. 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

Spaces, tabs, newlines, and other Unicode whitespace (\s in JavaScript regex).
No — only trims each line. Use Remove Empty Lines to drop blanks entirely.
Yes — trimming doesn't add or remove lines, only the whitespace on each.
Both = JavaScript's String.prototype.trim(). Left = trimStart(). Right = trimEnd().
No. All processing runs locally.
Suggest a tool

Something missing?

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

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!