⌘ K
regex delimiter · numbered segments · local

Split any text by a regex delimiter

Drop in a splitter pattern, paste your text, and read every resulting segment as a numbered list. Runs locally.

Regex Split
Segments
5
produced
Empty
0
blank
Flags
g
1 on
Status
ready
live
Flags
input · delimiter + text
//g
output · numbered segments
  1. "apple"
  2. "banana"
  3. "cherry"
  4. "date"
  5. "elderberry"
Quick Start

How to split with a regex

Use a regex as a delimiter and watch the text break into numbered segments — perfect when commas, spaces, or fixed strings aren't enough.

  1. 01

    Paste pattern

    Type a regex that matches your delimiter. Whitespace around commas? \s*,\s* works.

    Patterns compile through the JavaScript RegExp constructor, so syntax errors surface immediately and engine quirks like Unicode property escapes (\p{L}) work when the u flag is on.

    patternECMAScriptliterallive
    input · literalregex · regex
    \s*,\s*
    loaded · ECMAScriptPCRE · ready
  2. 02

    Drop sample text

    Add the text to split. Each delimiter match becomes a segment break.

    Each flag character mirrors the ECMAScript literal: g enables iteration, i folds case, m anchors per line, s lets . match newlines, u unlocks proper Unicode, y is sticky, and d emits indices.

    flagsoptionsg · i · mlive
    config · optionssample · flags
    apple, banana, cherry
    flags applied · liveECMA · live
  3. 03

    Read segments

    Every piece appears as a numbered row, JSON-quoted so empty strings are visible.

    Watch for catastrophic backtracking on nested quantifiers — a common ReDoS source. The tool caps match counts to keep the page responsive on pathological patterns.

    matchgroupshighlightReDoS-safe
    run · outputsplit · matches
    1 'apple' 2 'banana' 3 'cherry'
    matches · livegroups · live
  4. 04

    Copy or export

    Grab the output as JSON, CSV, or plain text — ready for your editor or pipeline.

    Copy writes via navigator.clipboard.writeText; downloads use a Blob and object URL, so nothing transits the network and the output is byte-identical to what you see on screen.

    copyexportclipboardblob
    export · exportedready · saved
    Copied
    ready to shipsuccess
Pro tips

Regex patterns that don't melt down

Use named groups

(?<year>\d{4}) reads better than $1 and survives reordering. Supported in ECMAScript 2018+.

Anchor strictly

Use ^/$ with the m flag when matching whole lines. Without anchors, partial matches sneak through.

Avoid catastrophic backtracking

Nested quantifiers like (a+)+ can explode. Run patterns through ReDoS Detector first.

Escape every literal

Backslash any meta character you want literally: \.\$\^\*\+\?\(\)\[\]\{\}\|\\.

Test edge cases

Empty string, single character, unicode, the maximum length you expect — write fixtures for each.

Patterns aren&rsquo;t parsers

Don’t parse HTML, JSON, or balanced parens with regex. Use a proper parser when the grammar is recursive.

Related toolsRegex Find AllRegex Extract GroupsRegex Extract To CsvRegex TesterRegex ReplaceRegex Cheatsheet
Use Cases

When a regex split helps

Multi-character or irregular delimiters made simple.

Parse CSV with messy whitespace

Split on \s*,\s* to tolerate spaces around commas. Compiles through the JavaScript RegExp constructor — engine quirks (Unicode property escapes, sticky matching, named groups) work when their flags are on. Error messages cite the exact position of any syntax issue.

ReDoS-safe

Tokenise on any whitespace

Use \s+ as the splitter. Pairs with the ReDoS detector to catch catastrophic backtracking before you deploy. A pattern that handles 1k-character input fine can become a denial-of-service vector on attacker-controlled 1M-character input.

ECMA-compliant

Custom delimiters

Pipes, double-dashes, tab+newline — anything regex can match. Output exports as JavaScript, Python re, Java util.regex, .NET System.Text.RegularExpressions, PCRE, and POSIX — language quirks are highlighted on conversion so you don't ship a JS-only pattern to a Go service.

spec-grade

Test edge cases

Empty segments tell you when delimiters touch. Capture groups (named or numbered) round-trip cleanly into replacement strings, JSON output, or CSV extraction without re-typing. Backreferences ($1, ${name}) preserve semantics across languages.

cross-engine

Pre-process logs

Split lines into fields by a regex pattern. Test against edge cases — empty input, single character, max length, multibyte boundaries — to catch off-by-one and zero-length match bugs before they reach production.

test-ready

Audit a parser

Compare segments with what your code produces. All matching runs client-side so secret patterns never leave the browser. Useful when the pattern itself is sensitive (PII regexes, internal data formats, security filters).

production-ready
FAQ

Frequently asked questions

g is forced for global splitting. Other flags work normally — m and i are useful.
JavaScript split keeps captured groups in the output array. If your pattern has groups, they appear as additional segments.
So you can tell apart "" (empty segment) from a missing one and see whitespace clearly.
It makes . match newlines in your delimiter pattern — useful for multi-line splits.
No. The tool runs entirely in your browser — your pattern and sample text never leave the page.
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!