Treating delimiter extraction as a spreadsheet engine
The parser handles quoted fields and escaped quotes, but formulas, workbook types, locale-specific numbers, and spreadsheet display rules require the actual spreadsheet application.
Text Cleanup Workbench | Clean Lists, Logs, and Paragraphs
TextRuns in Your Browser (No Uploads)
Clean lists, logs, copied tables, and paragraphs through twelve bounded local operations without uploading the text. Preview every change before copying or downloading the result.
What to do next
Continue with a related workflow or open the next tool that usually follows this task.
Workflow guide
Rename identifiers safely across code, data, and routes
Use a case converter to draft names, then treat every rename as a contract change: inventory consumers, define acronym rules, review invalid identifiers, compare a diff, and verify the destination.
OpenRelated toolLine Ending Detector for CRLF, LF, and Mixed Text Files
Count original CRLF, LF, CR, and Unicode line separators in a local file.
OpenRelated toolRemove Duplicate Lines | Keep First Occurrences
Keep first occurrences, compare case or trimmed keys, and optionally sort unique lines locally.
OpenRelated toolRemove Empty Lines | Remove or Collapse Blank Rows
Remove every blank row or collapse repeated gaps, with exact counts and line-ending diagnostics.
OpenHow to Use This Tool
Choose the operation that matches the next change you need and paste only the text required for that task.
Set the visible options. Column extraction uses strict 1-based selections and quote-aware delimiter parsing; regex filtering uses RE2 syntax rather than unrestricted JavaScript backtracking.
Run the operation and review changed status, line counts, affected lines, line-ending notices, and any warnings before accepting the result.
Use the result as the next input when another cleanup step is needed. The pipeline records applied operation names and Undo restores the previous workspace snapshot.
Copy or download the exact displayed UTF-8 result, then validate it in the destination editor, parser, spreadsheet, source repository, or publishing workflow.
When to Use This Tool
Reduce a noisy log to reviewable evidence
Keep matching lines with a bounded literal or RE2 expression, remove adjacent repeats, sort the remaining events, and preserve the resulting text for an incident note.
Prepare a copied list for configuration
Trim surrounding whitespace, remove blank rows, wrap each line with escaped quotes, and merge or download the exact result for a configuration file.
Repair repository line and indentation style
Inspect mixed line-ending warnings, normalize to LF or CRLF, and convert only leading indentation between tabs and spaces without changing tabs inside content.
Extract fields from a pasted delimited table
Select strict 1-based column ranges from comma, tab, semicolon, pipe, or one-character custom-delimited text while preserving quoted delimiter characters.
Common Mistakes
Using a regex when a literal filter is enough
RE2 prevents catastrophic backtracking but intentionally excludes lookbehind and backreferences. Literal matching is clearer when no pattern syntax is needed.
Removing all whitespace unintentionally
The explicit remove-all option also removes line breaks. Leading, trailing, and horizontal-collapse controls preserve line structure and are safer for most documents.
Assuming visual width equals grapheme count
Wrapping counts user-perceived grapheme clusters, not terminal columns or rendered pixels. Wide CJK characters, tabs, emoji, and proportional fonts can occupy different display widths.
Pasting secrets because processing is local
Normal transformation stays in the browser, but clipboard history, downloaded files, browser extensions, screenshots, and the destination system can still expose private text.
Examples
Filter and deduplicate repeated errors
Include lines containing ERROR, promote the result, then remove only adjacent duplicates.
Input
INFO ready
ERROR timeout
ERROR timeout
ERROR retryOutput
ERROR timeout
ERROR retryExtract quoted CSV columns
Select columns 1-2 with comma input and output. The quoted comma remains part of the note cell.
Input
name,note,count
Jane,"red, green",2Output
name,note
Jane,"red, green"Normalize and indent a source fragment
Normalize mixed endings to LF, promote the result, then add a two-space leading indentation unit.
Input
first
second
thirdOutput
first
second
thirdWrap a paragraph at a review width
Existing soft line breaks inside a paragraph are reflowed while blank lines continue to separate paragraphs.
Input
A long paragraph copied from a narrow support system can be reflowed for a plain text note.Output
Lines no wider than the selected grapheme width, with paragraph separators retainedBounded local transformations with explicit text semantics
Every task starts with the same validation contract: valid Unicode, no NUL characters, bounded code points, UTF-8 bytes, line count, line length, and result size. Consistent CRLF or CR endings are retained by operations that do not explicitly change them; mixed endings are normalized with a warning.
Column extraction uses Papa Parse for quoted delimiter-aware rows, validates a strict 1-based column grammar, pads missing cells in ragged rows with an explicit warning, and serializes fields with the selected output delimiter.
Regex filtering compiles with RE2JS and rejects unsupported syntax or excessive program size before scanning lines. Literal matching avoids regex interpretation. Indentation conversion changes only leading whitespace, preventing tabs or aligned spaces inside content from being rewritten.
Sorting is stable for equal values, supports locale-aware alphabetical comparison, numeric values embedded in lines, grapheme length, and an unbiased browser-crypto shuffle when available. Character splitting and wrapping use grapheme segmentation where the runtime supports Intl.Segmenter.
Each run is tied to a generation token, so an older asynchronous parse or regex result cannot replace a newer edit. Output is considered current only when it belongs to the exact input shown. Copy and download use that exact result.
Pipeline history stores workspace text only in page memory for Undo. Analytics excludes the text and custom token values. Closing or refreshing the page clears the in-memory pipeline.
Frequently Asked Questions
Does the workbench upload my text?
The twelve transformations run in the browser. Consent-aware analytics can record fixed operation names, safe option names, timing, byte and line counts, changed status, diagnostic count, and fixed error codes, but not source or result text.
Can I apply several operations in sequence?
Yes. Run one operation, choose Use result as next input, then select another tab. The pipeline lists applied operations and Undo restores the prior text and pipeline state.
What regular expressions are supported?
Regex filtering uses RE2 syntax with a 512-byte pattern and bounded program size. Common groups, classes, anchors, and repetitions work; lookbehind and backreferences are intentionally unsupported.
Will column extraction preserve quoted commas?
Yes for supported one-character delimiters. The parser recognizes quoted fields and doubled quote escapes. It does not evaluate formulas or reproduce spreadsheet formatting.
What are the processing limits?
Input is limited to 1,000,000 Unicode code points, 2 MiB of UTF-8, 250,000 lines, and 262,144 code points per line. Output is capped at 4 MiB. NULs and unmatched UTF-16 surrogates are rejected with a location.
How This Tool Was Verified
Maintained and tested by SimpleWebUtilsReviewed
Method: To check “Prepare a repeated deployment log list for a review ticket”, we used Text Cleanup Workbench with the guide's exact source data and applied “Normalize boundaries with one narrow operation”. The output had to match the documented result; evidence for “Running many transformations without checking intermediate output” and “Treating all duplicate removal as the same operation” was reviewed before recording the check.
Expected result: The staged cleanup preserved timestamps and quoted comma-containing service names, removed only the selected health-check and duplicate rows, and retained a reviewable intermediate result after each operation.
Open the tested workflowRelated workflow guides
Use these focused guides when you need a practical workflow before opening the tool.
Workflow guide
Rename identifiers safely across code, data, and routes
Use a case converter to draft names, then treat every rename as a contract change: inventory consumers, define acronym rules, review invalid identifiers, compare a diff, and verify the destination.
Workflow guideCompare text revisions and verify a unified diff
A useful diff workflow starts with exact input, not filters. Preserve the source files, compare line structure and final newlines, explain every raw addition and removal, use equivalence options only as a diagnostic view, and validate any exported patch against a disposable copy before it reaches a repository or deployment.
Workflow guideConvert CRLF to LF for Git and shell scripts safely
Use this incident workflow when a Windows-edited script fails on Linux, Git shows a whole-file line-ending diff, or generated text mixes CRLF and LF. Inspect first, normalize only confirmed text, then enforce the decision with repository settings.
Workflow guidePreview Markdown safely before publishing a README or article
A Markdown preview is most useful as a review stage, not as a promise that every destination will render the same document. This workflow keeps the working text in the browser, checks common extended syntax and sanitized raw HTML, treats remote images as an explicit privacy decision, and separates content markup from destination styling. It finishes by testing the exported HTML fragment or original Markdown in the system that will actually publish it.
Workflow guideClean lists, logs, and copied text with a repeatable pipeline
Text cleanup is safest when it is treated as a sequence of explicit, reversible transformations. Preserve the source, identify line and delimiter boundaries, make one structural change at a time, promote only reviewed output to the next step, and compare the final text with the destination contract before publishing, importing, or sharing it.
Workflow guideAdd fixed labels and delimiters to copied lines safely
Use this workflow for a plain list copied from a spreadsheet, report, log, or editor when every row needs the same label, marker, wrapper, or delimiter. It keeps line boundaries exact and separates bulk text insertion from JSON, CSV, SQL, shell, or HTML validation.
Related Tools
Continue with another maintained workflow
Line Ending Detector for CRLF, LF, and Mixed Text Files
Count original CRLF, LF, CR, and Unicode line separators in a local file.
Text
Remove Duplicate Lines | Keep First Occurrences
Keep first occurrences, compare case or trimmed keys, and optionally sort unique lines locally.
Text
Remove Empty Lines | Remove or Collapse Blank Rows
Remove every blank row or collapse repeated gaps, with exact counts and line-ending diagnostics.
Text
Find and Replace Text | Literal and Regex Replacement
Replace literal or regex matches with Unicode boundaries, capture tokens, exact counts, and Worker limits.
Text
Add Prefix or Suffix to Every Line | Preserve Line Endings
Add literal text before or after each line while preserving its original line endings.
Text