Skip to main content
Tool Factory

Encoding & Number Bases

Encoding Brute Force for Text Data Converter

Transform data with Text Encoding Brute Force and the selected encoding settings. Enter the data, choose the input and output formats, then copy the result.

Tool workspace

Your input stays in this browser.

Add the required input to continue.

Needs input

You can run the tool again after any change.

Options

Your result appears here

Transform data with Text Encoding Brute Force and the selected encoding settings. Enter the data, choose the input and output formats, then copy the result.

This tool runs open-source code from CyberChef by GCHQ (Apache License 2.0). See open-source credits.

Encoding Brute Force for Text Data Converter: This tool applies every supported text encoding and returns named candidate results. Encode converts characters into each encoding's byte string. Decode interprets the supplied byte string using each encoding. It does not rank candidates, identify the original encoding automatically, or recover an encryption key.

The result displays a table of encoding names and candidate strings. The preview replaces control characters with display symbols. A failed candidate displays Could not decode.

  • Compare how different encodings represent a known character.
  • Investigate unreadable text when the original byte sequence is available.
  • Build a small compatibility sample for an encoding-specific import.

Instructions

  1. Start with A in the text input and select Encode under Mode.
  2. Run the tool. Inspect UTF-8 (65001), which returns A, and UTF-16LE (1200), which adds a null byte after A.
  3. For Decode, supply the original byte string and compare candidate results with known source text. Do not treat readable output as proof.

Example

Input: café

Settings: Mode Decode

Result: A table with one row per code page. The UTF-8 (65001) row shows café.

é appears when the UTF-8 bytes of é are read as Windows-1252 text.

Limits

  • Some encodings cannot represent every character. Conversion can replace or lose unsupported characters.
  • The input is a string, not an automatic hex or Base64 decoder. Literal 41 is not automatically the byte 0x41.
  • Multiple encodings can produce identical readable results. Use source metadata or known text to select the correct encoding.

Questions

What input does Encoding Brute Force for Text Data Converter accept?

Encoding Brute Force for Text Data Converter accepts text.

Which settings does Encoding Brute Force for Text Data Converter provide?

Encoding Brute Force for Text Data Converter provides controls for Mode.

What does Encoding Brute Force for Text Data Converter return?

The tool displays a table of encoding names and candidate results. The preview replaces control characters with display symbols. It does not rank candidates or identify the correct encoding automatically.