How to Strip ANSI Color and Escape Codes from CLI & CI/CD Logs
Modern CLI tools, Docker containers, Jest test runners, and GitHub Actions pipelines emit ANSI escape sequences to colorize terminal output. When redirected to a file or copied into a text editor, those colors turn into noisy garbage like [31m and [39m.
Why does this problem happen?
Terminals interpret ESC (\x1b or \u001b) sequences as foreground colors, bold text, or cursor movements. Plain text editors, Markdown documents, and log search tools display the raw bracketed codes instead.
Those stray escape sequences break regex searches, bloat ticket descriptions, and confuse LLM context windows when debugging build failures.
How to solve it?
Paste your raw terminal or CI output into the editor above. DataPurge strips all ANSI SGR color codes, cursor sequences, and trailing whitespace while preserving your actual log lines and timestamps.
Copy or download the clean plain-text log in one click.
Why use 100% Client-Side (Zero-Telemetry)?
CI/CD and build logs frequently expose internal package names, repository paths, and environment metadata.
DataPurge processes every byte locally in your browser with zero server uploads or telemetry.