UTF-16 Decoder
UTF-16 Decoder
Decode hexadecimal byte input using UTF-16LE encoding.
Result size
0chars
Live update on input changes.
File input
Choose a file
Click, drop, or paste from clipboard.
Options
0 option(s)
No additional options required.
More actions
Input: manual
Input: manualInputsText/FileManual input • Auto-updateWaiting
Your input is processed locally in your browser whenever possible. We do not store your data.
Flow
- Parse hexadecimal bytes into binary values.
- Interpret bytes as UTF-16 code units (typically little-endian in this tool).
- Resolve surrogate pairs when needed and return decoded Unicode text.
Example
Worked example: 48 00 69 00
- 1 Bytes 48 00 69 00 are UTF-16LE code units for H and i.
- 2 Decoder reads little-endian pairs.
- 3 Output text is Hi.
48 00 69 00 decodes to "Hi" in UTF-16LE.
How
- Paste UTF-16 hex bytes in the input panel.
- Run decode and check the text output and warnings.
- If output is garbled, switch byte order assumptions in your source data.
Cases
- Troubleshoot BOM/endian issues in legacy exports.
- Decode Windows-origin text payloads stored as UTF-16 bytes.
- Validate migration steps when converting old systems to UTF-8.
Avoid
- Feeding UTF-8 bytes into a UTF-16 decoder.
- Ignoring byte-order differences between LE and BE data.
- Supplying an odd number of bytes that cannot form full code units.
FAQ
Does utf-16 decoder send my input to a server?
No. UTF-16 Decoder handles the input in your browser whenever possible, so routine conversions, previews, and copy actions stay on your device instead of being sent to Calctrove servers.
Why does output look like random symbols?
Most often the byte order is wrong or the input is not actually UTF-16 encoded.
Does this decode surrogate pairs?
Yes, valid surrogate pairs are combined into the correct Unicode code points.
Switch
Switch12
No match.