ANSI truecolor generator

Enter a short or full hexadecimal value, or an rgb() color, and choose foreground or background output. The result includes the real escape character for direct use, a visibly escaped form that is convenient in source code and configuration, normalized channel values, and the standard reset sequence. It is deterministic, fast, and useful for shell tools, build scripts, logging systems, and command-line interfaces.

Choose a color and the part of the terminal to change

Start with a color in one of the accepted forms: three-digit hexadecimal such as <code>#3af</code>, six-digit hexadecimal such as <code>#33AAFF</code>, the same six digits without a hash, or an RGB function such as <code>rgb(51, 170, 255)</code>. Hexadecimal letters are case-insensitive, and whitespace inside the RGB function is allowed. Every RGB channel must be a whole number from zero through 255. Then select whether the color applies to the foreground, which normally means text, or the background behind the text. The default is foreground because that is the most common need for command output. The generator expands shorthand hexadecimal values, normalizes the final color to uppercase six-digit hexadecimal, and returns the decimal red, green, and blue channels. This makes the result easy to audit before inserting it into a script. It deliberately rejects alpha channels, CSS color names, percentages, and out-of-range channels because ANSI truecolor sequences encode exactly three eight-bit color channels and have no alpha component. Clear validation keeps an accidental CSS value from silently becoming an unexpected terminal color.

Use the generated escape sequence safely

A twenty-four-bit ANSI color uses an escape character followed by an SGR parameter list. Foreground colors begin with <code>38;2</code>, while background colors begin with <code>48;2</code>; the three decimal channels follow in red, green, blue order and the sequence ends with <code>m</code>. The response provides two representations of the same instruction. The <code>sequence</code> field contains the actual ESC control character, so a program can concatenate it directly with text. The <code>escaped</code> field begins with the visible characters <code>\x1b</code>, which is often easier to copy into JavaScript, shell, JSON templates, or documentation where a literal control character would be confusing. How an escaped string is interpreted depends on its host language, so use the representation appropriate for that environment. Append the returned reset after the colored span so later prompts and log lines do not inherit the style. For example, construct output conceptually as color sequence, message, then reset. Avoid applying color codes to machine-readable output unless consumers explicitly support them, since invisible control characters can break comparisons, parsers, and snapshots.

Understand terminal support and production behavior

Truecolor is widely supported by modern terminal emulators, but the ANSI protocol does not force every output destination to render twenty-four-bit color. A redirected file, a basic terminal, a continuous-integration log viewer, or an application configured to strip styling may show no color or expose control characters. Treat color as presentation rather than information: labels, severity names, and status messages should remain understandable when styling is removed. Many command-line programs enable color only when standard output is attached to an interactive terminal and provide a flag or environment setting to force or disable it. This generator does not inspect the caller's terminal, because doing so would make a pure API result depend on an unrelated runtime. It simply creates the correct byte sequence for the requested color. The algorithm performs no network requests, uses no randomness, and preserves no input. Identical inputs therefore return identical JSON. API use costs $0.002 per request, while the browser execution path uses the same pure conversion logic. For logging systems, consider inserting sequences only at the final human-facing renderer rather than storing them in structured events; that keeps searches and downstream exports clean while preserving attractive console output.