Character Encoding Converter

Transcode hexadecimal byte sequences between UTF-8, ASCII, Latin-1, and UTF-16 encodings.

▲ Client-side only● No data sent to server✓ Free forever
Source bytes (hex)
Target bytes (hex)
Ready

Converter guide

About Character Encoding Converter

Character encoding defines how text characters are represented as bytes. This converter transcodes between UTF-8, ASCII, Latin-1, and UTF-16, which can help move text between older software and modern systems. Encoding names matter because the same byte sequence can mean different characters under different rules.

How to use this converter

  1. 1Choose the source encoding that matches the bytes or text you have.
  2. 2Choose the target encoding required by the receiving application, then enter or provide the input in the format the tool accepts.
  3. 3Convert and inspect accented letters, punctuation, and symbols. If a character becomes a replacement mark or disappears, the source may not support it.

Conversion method and technical details

Transcoding decodes the input according to its source character set, then encodes those characters in the destination set. UTF-8 and UTF-16 can represent Unicode broadly; ASCII and Latin-1 cover smaller character ranges. Conversion between byte encodings is not merely changing a label.

Worked real-world example

The letter `é` can be represented in UTF-8 by more than one byte, while Latin-1 uses a single byte. If the original bytes are decoded using the wrong source encoding, text can appear corrupted.

Common scenarios and use cases

Repair text imports, inspect legacy files, and prepare content for software that expects a particular encoding.

For a dependable comparison, confirm both unit labels, keep the original measurement with the converted value, and use the precision required by the task. The converter changes the representation of a value; it does not measure the item or decide which standard your project requires.

Important details and limitations

ASCII cannot represent most non-English characters, and Latin-1 cannot represent all Unicode text. Some conversions are lossy when a target set lacks a character. Keep the source data and verify the chosen input/output convention before overwriting a file.

Check the output unit as well as the number. If the result will be reused in another calculation, retain full precision where possible and round only at the end. For measurements governed by a technical specification, use the standard and tolerance required by that document.

Frequently asked questions

Is UTF-8 the same as ASCII?

UTF-8 preserves ASCII byte values for basic characters but also represents a much larger Unicode range.

Why do accents turn into question marks?

The target encoding may not contain that character, or the source bytes may have been decoded with the wrong encoding.

Does changing the encoding recover already corrupted text?

Only if the original byte sequence is still available and the correct source encoding is known.

Why can the converted number look much larger or smaller?

Different units use different scales. A measurement can have a larger number in a smaller unit and still describe the same quantity. Check the source and target unit labels before comparing values.

How many decimal places should I keep?

Keep enough precision for the job and avoid rounding values between steps. Round the final displayed answer to match the specification, document, or measuring tool you are using.