入力テキスト 出力

使い方

1. 入力エリアにテキストを貼り付けます。
2. 希望のクリーンアップオプションを選択します(デフォルトですべてチェック済み)。
3. テキストをクリーンをクリックして処理します。
4. クリーンな結果をコピーまたはダウンロードします。

よくある質問

スペースとして何がカウントされますか?

スペース、タブ、改行不可のスペース、その他のUnicodeスペース文字。改行は「空白行」と「改行を折りたたむ」オプションを介して個別に処理されます。

このツールはコンテンツを変更しますか?

いいえ。スペース文字のみを削除または折りたたみます。単語、句読点、その他のコンテンツはそのまま残ります。

コードに使用できますか?

可能ですが、注意が必要です · 先頭スペースを削除するとコードのインデントが破壊されます。クリーンアップ対象を正確に制御するには、個別のチェックボックスを使用してください。

What "whitespace" actually means

A whitespace character is one that produces blank space when text is rendered, instead of a visible glyph, used to separate words, indent lines, and break paragraphs. The Unicode Character Database assigns the formal White_Space property to exactly 25 code points. The familiar suspects (space, tab, line feed, carriage return) cover most of what you'll ever paste, but the full list also includes the no-break space (U+00A0), narrow no-break space (U+202F), 11 typographic spaces in the U+2000-U+200A range, the line and paragraph separators (U+2028, U+2029), the medium mathematical space (U+205F), and the full-width ideographic space (U+3000) used after CJK punctuation.

A separate group looks invisible but is not classified as whitespace by Unicode: the byte-order mark (U+FEFF), zero-width space (U+200B), zero-width joiner and non-joiner (U+200D, U+200C), word joiner (U+2060), and soft hyphen (U+00AD). These are formatting controls, not spaces, most "I cleaned my text but something's still wrong" reports trace back to one of them.

What this tool does, option by option

• Trim leading/trailing spaces per line: strips whitespace at the start and end of each individual line. Useful for cleaning indented quotes from email, or right-padding accidentally added during copy-paste.
• Collapse multiple spaces to one: runs of two or more spaces become a single space. Handles the typewriter habit of double-spacing after a period (which most modern style guides (Chicago, AP) discourage).
• Remove blank lines: drops any line that's empty or contains only whitespace. Common need after pasting text from PDFs.
• Convert tabs to spaces: replaces every \t with spaces. Be cautious in code: Python and YAML are whitespace-sensitive, and Makefiles actually require tab indentation in recipe lines.
• Trim entire text start/end: strips leading and trailing whitespace from the whole string at once (the equivalent of JavaScript's trim()).
• Collapse multiple newlines to one: runs of consecutive newline characters become a single newline. Useful when "Remove blank lines" is too aggressive and you want to keep a single empty line for paragraph breaks.

All six options are independent toggles (un-check any you want to skip) and each one runs only over the text you paste. Nothing is uploaded; the cleaning happens in your browser via JavaScript regex passes.

When you'd reach for this

• PDFs and Word documents. PDFs insert hard line breaks at the visual end of every line and sometimes preserve hyphenation; pasted Word text often has no-break spaces between numbers and units (10 km), around French punctuation, or after honorifics like Mr. Smith.
• Normalising user input. Trailing spaces in a "Name" or email field cause "Smith" and "Smith " to compare unequal. Stripping them on entry (or before lookup) eliminates a whole class of "user not found" bugs.
• CSV and TSV preparation. Field values with leading or trailing spaces wreck downstream parsers that expect exact-match keys. Excel's UTF-8 CSV export silently prepends a byte-order mark, which a downstream parser that doesn't strip BOM will see as part of the first column header, producing a strange-looking colname.
• Markdown and blog drafts. Multiple consecutive blank lines render as a single block in Markdown but bloat source files and make diffs noisy.
• Email signatures, chat transcripts, and identifiers: quick clean-up before pasting them into another document, or before submitting a promo code or licence key to an API that's strict about whitespace.

Common gotchas

• Removing leading whitespace breaks code. Python and YAML use indentation as syntax. Strip it and the file looks identical to the eye but won't parse.
• Tab conversion breaks Makefiles. GNU make refuses to run if recipe lines are indented with spaces instead of tabs. Same caution applies to Go's gofmt output.
• NBSP looks identical to a space. A user often sees a single "space" between two words and assumes any cleaner will catch it. JavaScript's \s regex does match no-break space in modern browsers, but if you're writing your own regex in another language (or a very old environment) you may need to list NBSP explicitly.
• Trailing whitespace in Markdown is meaningful. Two trailing spaces at the end of a Markdown line create a <br> line break. Trimming per-line trailing whitespace removes those line breaks; if you depend on them, leave the option off.
• Windows line endings. Files copied from a Windows source use CRLF (\r\n). The "remove blank lines" and "collapse newlines" passes need to recognise CR; otherwise a stray \r can survive at the end of every line.
• Zero-width characters survive a whitespace remove. ZWSP (U+200B), ZWJ (U+200D), ZWNJ (U+200C), word joiner (U+2060), and soft hyphen (U+00AD) are not Unicode whitespace, so a generic whitespace cleaner won't touch them. If your text feels off after cleaning, paste it into a hex viewer or a separate "invisible character" inspector.
• Aspect ratio between input and output. Cleaning is irreversible inside this page once you copy or close, there's no undo history. Keep the original somewhere if you might need it.

Brief technical context

This tool runs entirely in your browser using JavaScript's built-in regex engine. String.prototype.trim() in modern engines (every evergreen browser since around 2015) strips both no-break space and the byte-order mark, because the ECMAScript spec defines its trim set as the union of WhiteSpace and LineTerminator productions, a list that covers tabs, plain space, NBSP, BOM, the typographic spaces, and CR / LF / LS / PS line breaks. It excludes only one Unicode whitespace character, U+0085 (NEL), which is a curiosity inherited from EBCDIC and almost never appears in modern text.

For very large inputs, the slow part is rarely the regex pass, it's writing the result back to the textarea and re-rendering the DOM. Inputs up to a few megabytes are typically fine on a modern laptop; beyond that, command-line tools (tr, sed, awk, or a short Python script) are usually faster.

More questions

What's the difference between a regular space and a no-break space?

They render at the same width but the no-break space (NBSP, U+00A0) tells the renderer not to break a line at that point. Word, Google Docs, and many CMSes insert it between honorifics and surnames (Mr. Smith), between numbers and units (10 km), or around currency symbols ($ 5). It's the single most common "weird" character to find in pasted text, and it's why the same-looking gap between two words sometimes resists a regex written for plain spaces.

Will this remove zero-width characters or the byte-order mark?

JavaScript's whitespace handling generally catches the byte-order mark (U+FEFF). It does not catch zero-width space (U+200B), zero-width joiner (U+200D), zero-width non-joiner (U+200C), word joiner (U+2060), or soft hyphen (U+00AD), Unicode does not class those as whitespace, so they survive a whitespace pass by design. If you suspect one of those is in your text, you'll need an invisible-character inspector instead.

Why are blank lines and consecutive newlines two separate options?

"Remove blank lines" deletes every empty line, the result is one continuous block of text with no paragraph breaks. "Collapse multiple newlines to one" keeps a single newline between paragraphs and only removes the extras. If you want readable paragraphs in the output, leave the first option off and use the second.

Is there a length limit?

There's no hard limit, the tool can comfortably handle text in the range of tens of thousands to a few million characters on a modern laptop. The limit is your browser's textarea performance: very large pastes start to lag during typing or copying, not during the cleaning step itself.

Does anything get sent to a server?

No. The text never leaves your browser. The cleaning runs locally in JavaScript, the result is written back into a textarea on the same page, and you can use the page offline once it's loaded. The same applies to every tool on Absolutool.

関連ツール