Remove ANSI escape codes from terminal text and logs

Those instructions are useful in an interactive shell but become distracting characters when logs are copied into tickets, reports, search indexes, or datasets. This tool removes ANSI color and formatting escape codes while preserving the actual message, spaces, and line breaks. Paste output for a quick browser-side cleanup, or send it through the API when plain-text normalization belongs in an automated workflow.

Turn styled terminal output into useful plain text

Command-line programs frequently detect a terminal and decorate their output with color, emphasis, cursor controls, hyperlinks, or title-setting instructions. The display interprets those bytes, so a person sees a neat status message rather than the underlying control syntax. Problems appear when that same output is redirected, copied from a build system, stored in a database, or pasted into a support case. Escape sequences may surface as bracketed fragments, interfere with searches, inflate diffs, and make machine processing unreliable. This remover scans the supplied text and discards recognized ANSI control sequences while retaining ordinary Unicode characters, whitespace, and line structure. It handles common Select Graphic Rendition color codes as well as broader Control Sequence Introducer commands, Operating System Command strings, and related terminal control forms. The result is suitable for reading, copying, indexing, comparing, or passing to a downstream parser without display instructions mixed into the content.

How the deterministic scanner treats escape sequences

The cleaner reads the text from beginning to end once. When it encounters an ESC introducer or an equivalent single-byte C1 control, it checks the byte ranges defined for terminal control syntax and consumes the complete sequence. CSI commands are recognized through their parameter, intermediate, and final bytes, which covers familiar forms such as color changes, resets, erased lines, and cursor movement without maintaining a fragile list of individual commands. String controls such as OSC, DCS, SOS, PM, and APC are removed through their BEL or String Terminator boundary; an unterminated string control is treated as control data through the end of the input. Ordinary text is copied exactly, including emoji, non-Latin scripts, tabs, carriage returns, and newlines. The response also reports how many control sequences were removed and whether any change occurred, making it easy for an automated pipeline to record cleanup without comparing two potentially large strings. No terminal is emulated, so cursor movement does not rearrange visible characters; the tool removes instructions and preserves the textual payload order.

Use clean output safely in logs and automation

Use this capability immediately after capturing output from a process that may force color or formatting, especially when you cannot change that process to emit plain text. The cleaned value can go into a log aggregator, full-text index, incident report, snapshot test, notification, or structured extraction step. Because the algorithm is deterministic, identical input always produces identical output, which is important for build artifacts and regression comparisons. It performs no network requests, does not execute the supplied text, and does not interpret shell commands embedded in it. Remember that removing ANSI sequences is normalization, not security sanitization for every destination: HTML, SQL, CSV, and shell contexts each have their own escaping requirements. Also note that terminal applications can overwrite lines with carriage returns or backspaces; those ordinary control characters are preserved because they are not ANSI escape sequences. If you need a rendered transcript that reconstructs cursor positioning, use a terminal emulator before exporting plain text. For routine colorized logs, this focused cleanup keeps meaningful words and layout while removing presentation noise.