About this text separator
A text separator replaces boundaries between pieces of text with a delimiter of your choice. It can turn a whitespace-separated series into a comma list, join a line-based list with semicolons, or place a marker between individual characters. Choose the split mode first, then enter the output separator and inspect the result before copying it.
Whitespace mode groups together consecutive spaces, tabs and line breaks, leaving only the nonempty tokens. Line mode uses explicit line breaks and preserves blank entries. Character mode uses grapheme segmentation when supported by the browser, keeping combined accents and joined emoji together. Custom mode splits on an exact literal delimiter; it does not interpret the delimiter as a regular expression.
Both custom and output delimiters recognize backslash-n for a newline and backslash-t for a tab. A doubled backslash represents a literal backslash. An empty output separator joins pieces without anything between them, while an empty custom input delimiter is rejected. The tool does not implement CSV quoting or escaping. If values contain the delimiter or embedded quoted line breaks, review them carefully or use a dedicated structured-data parser.
Which controls should I check first?
The Text Separator form labels its controls as Your text; Split on; Custom input delimiter; Output separator (\n = newline, \t = tab); Result. Its selectable values include Whitespace; Lines; Characters; Custom delimiter. Use those labels to keep the source and settings separate. A sample argument that selects a mode is not additional source text. Choose the setting matching your intended operation before copying a result, and change it explicitly when comparing another mode. The labels describe what this form accepts; the worked examples below demonstrate only the stated supplied values.
How should I interpret this specific operation?
The input boundary and output delimiter are two separate controls. A literal custom separator is not a regular-expression pattern. Whitespace mode groups consecutive separators, while line mode can retain empty entries. A requested newline delimiter creates actual line boundaries rather than the printed backslash and letter n. Start with three short tokens to confirm both controls before joining a full list.
Worked helper values
These values come from the reproducible calculation examples supplied with this tool. Each row identifies the complete supplied arguments and the returned value. A visible ↵ denotes a line break and ⇥ denotes a tab in text examples. Settings appear alongside source data so that a different mode is not mistaken for an identical input. These are helper calculations, not observations of a live device, fetched target, image decoder, browser preview or downloaded file. Use the stated method above to relate the returned fields to the actual operation.
| Supplied values | Calculated return value |
|---|---|
| a b ↵ c; words; ; , | a, b, c |
| a|b|c; custom; |; \n | a ↵ b ↵ c |
What counts as one text element?
Text can be handled as visible graphemes, Unicode code points, bytes, words or complete lines. These units differ. A joined family emoji may look like one character while containing several code points; an accented character may use more than one encoded byte. Use the unit stated in this tool's method before comparing results with an editor or database. Line tools should receive one entry per line, while word tools use their documented whitespace boundaries. A transformation that preserves every visible word can still change separators, and a transformation that preserves every byte does not necessarily operate on complete visible characters.
How should I prepare a representative sample?
Start with a short excerpt containing the features that matter to your job: an accented letter, a number, punctuation, a repeated item, or a blank line. Choose the relevant options and inspect the result before processing the full text. Keep a separate source copy so that you can compare exact spaces and case. If duplicate labels refer to different records, attach identifiers before applying a list operation that could remove them. Text processing cannot infer whether two identical-looking names belong to the same record. A small sample makes delimiter mistakes easier to see than a long unstructured paste.
Which differences should I inspect after conversion?
Compare the first and last entries, any blank entries, and text around punctuation. Check whether the intended operation preserves line endings, joins tokens with spaces, or substitutes a custom delimiter. These are distinct behaviors: reversing words does not preserve the original layout, while reversing lines keeps each line's internal content together. A normalized comparison can intentionally ignore case or accents, whereas an exact comparison retains them. Read the stated method instead of assuming that all text tools share one normalization policy. If another application reports a different count, compare the boundary rules before treating either number as incorrect.
Why can copied text behave differently elsewhere?
A destination can apply its own normalization, line-ending rules, font substitution or length limits. Fancy Unicode letters are different characters from ordinary ASCII letters even when they look like a font change. Some destinations cannot display those glyphs, and searching plain text may not match them. Likewise a byte count changes with encoding, while a visual count may remain unchanged. Test a small converted sample in the receiving application before replacing a large document. Retain ordinary text when accessibility, searching or exact identifiers matter. A local text result is data rather than proof that the destination interprets it the same way.
Can I use a newline as the separator?
Yes. Type \n, or use \t for a tab. Use \\ to produce a literal backslash.
Are custom delimiters regular expressions?
No. They are matched literally after the supported escape sequences are decoded.
Does this handle quoted CSV fields?
No. It splits text boundaries without implementing CSV quoting rules.