Skip to main content
Tool Factory

Encoding & Number Bases

Text Encoder

Encode text with the selected format and options. 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

Encode text with the selected format and options. 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.

Text Encoder converts data between formats in your browser. For a correct result, confirm the destination byte order.

encoded bytes represented in the selected format Processing runs in the browser.

Instructions

  1. Provide text or data for this tool.
  2. Select the target character encoding.
  3. Compare the output with a known Text Encoder sample.
  4. Keep the original value until the receiving system accepts the result.

Example

Input: Hello

Settings: Text Encoder: select the target character encoding

Result: encoded bytes represented in the selected format

Limits

  • Text Encoder: encoding does not provide confidentiality
  • Text Encoder: The operation does not detect a different input format automatically.
  • Text Encoder: Processing stays in the browser.

Questions

How do I convert text to UTF-8 or a legacy code page?

Enter the text and choose the required Encoding. The operation produces encoded bytes, which the interface presents as a binary result. Choose the encoding that the receiving application expects, rather than the encoding with the smallest output.

Why can a character change during legacy text encoding?

Many legacy code pages cannot represent every Unicode character. A conversion can substitute unsupported characters. Decode the output with the same encoding and compare it with the original before you use the file.

Does selecting UTF-16 also select a byte order?

The available UTF-16LE and UTF-16BE choices specify different byte orders. Match that choice to the destination format. A correct character set with the wrong byte order can still produce unreadable text.