Text Encoding Converter

No. It recognizes UTF-8, UTF-16 and UTF-32 BOMs, checking four-byte BOMs before two-byte prefixes. Without a BOM it uses strict UTF-8. You must select a known legacy or endian encoding when appropriate.

Malformed UTF-8, unpaired UTF-16 surrogates, invalid UTF-32 scalar values, incomplete code units and unsupported Latin-1 characters cause an error. No replacement characters are silently inserted.

An initial Unicode signature/byte-order mark. You can remove a recognized matching initial BOM on decode and optionally add a new one during encoding. Retaining an existing leading U+FEFF and adding a BOM creates both; the tool reports that situation. A conflicting source BOM raises an error.

This tool implements ISO-8859-1 as the direct U+0000–U+00FF mapping, including C1 controls. It is not Windows-1252 and does not map bytes 80–9F to Windows punctuation. It rejects characters outside Latin-1 and does not add a Unicode BOM.

Unedited decoded source text retains its original CR, LF and CRLF sequences internally. Editing/pasting uses the browser text field, which can normalize line endings to LF. Select explicit LF or CRLF output normalization when needed.

Yes. It produces an empty file, or just the selected Unicode BOM. Files are limited to 1 MiB and text to 200,000 UTF-16 units; output is also limited to 1 MiB.

It shows only the first 512 bytes, in 16-byte rows. The file download contains every encoded byte. The JSON report includes counts and encoding settings without including the text itself.

Only if you know and select the correct original encoding. If incorrect decoding has already changed or replaced characters, this tool cannot reconstruct missing original bytes.

Files are read and encoded in this browser with no processing upload or saved text/file history. Website ads and analytics follow the privacy information.