Convert Utf16 To Utf8

Report an Issue

Help us improve by telling us what went wrong.

Embed this Tool

Customize and copy the embed code for your website.

Convert UTF-16 to UTF-8: Bridge Two Unicode Worlds

UTF-16 and UTF-8 are the two most widely deployed Unicode encoding formats, and they dominate different ecosystems. Windows internals, Java strings, JavaScript engines, and .NET frameworks all use UTF-16 as their native string encoding. Meanwhile, the web, Linux, modern APIs, JSON, and file storage have standardised on UTF-8. When data crosses between these ecosystems, you need to convert UTF-16 to UTF-8, and our tool does this conversion instantly in your browser.

How UTF-16 Differs from UTF-8

UTF-16 encodes each Unicode code point as either one or two 16-bit units (two or four bytes). Characters in the Basic Multilingual Plane (U+0000 to U+FFFF), which covers virtually all commonly used characters, are stored as a single 16-bit unit. Characters outside this range, such as emoji and some historic scripts, are stored as surrogate pairs: two 16-bit units that together specify the code point.

UTF-8 uses a variable-length encoding of one to four bytes per character. ASCII characters use one byte, making UTF-8 backward-compatible with ASCII. Most European characters use two bytes, CJK characters use three, and supplementary characters use four. For English-heavy text, UTF-8 is roughly half the size of UTF-16. For CJK-heavy text, the size difference is smaller and sometimes favours UTF-16.

When This Conversion Is Essential

Web development is the primary scenario. JavaScript uses UTF-16 internally for all string operations, but when sending data to servers via fetch or XMLHttpRequest, the transmission encoding is UTF-8. The browser handles this conversion automatically for standard text, but when working with binary data, file contents, or WebSocket messages at a low level, you may need to handle the encoding conversion explicitly.

File format interop is another common need. Windows Notepad saves files as UTF-16LE by default when you choose "Unicode" encoding. Many Unix tools and web servers expect UTF-8. Opening a UTF-16 file in a tool expecting UTF-8 produces garbled text or error messages. Converting the encoding resolves the issue immediately, and our Convert UTF-16 To UTF-8 tool lets you perform this conversion without installing any software.

Database operations sometimes involve encoding mismatches. SQL Server uses UTF-16 (NVARCHAR) for Unicode text, while PostgreSQL and MySQL commonly use UTF-8. When migrating data between these systems or when an application reads from one and writes to the other, encoding conversion happens either automatically at the driver level or manually in the data pipeline. Understanding and being able to verify this conversion is essential for preventing data corruption.

Surrogate Pairs: The Tricky Part

The most technically interesting aspect of UTF-16 to UTF-8 conversion is handling surrogate pairs correctly. In UTF-16, code points above U+FFFF are represented by a pair of 16-bit values: a high surrogate (0xD800-0xDBFF) followed by a low surrogate (0xDC00-0xDFFF). The converter must recognise these pairs, combine them into the original code point, and then encode that code point in UTF-8's four-byte format.

Lone surrogates, a high surrogate without a following low surrogate or vice versa, are technically invalid. Real-world data sometimes contains them due to bugs in string manipulation code that splits strings in the middle of surrogate pairs. Our tool handles these edge cases gracefully, either flagging them as errors or using replacement characters, rather than producing silently corrupted output.

Byte Order Marks and Endianness

UTF-16 comes in two byte orders: big-endian (UTF-16BE) and little-endian (UTF-16LE). The byte order mark (BOM), the character U+FEFF at the start of the data, indicates which order is used. If the first two bytes are FF FE, it is little-endian. If they are FE FF, it is big-endian. Windows systems typically produce UTF-16LE. The tool detects the BOM automatically and handles both byte orders correctly.

UTF-8 does not have byte-order issues, but some tools prepend a UTF-8 BOM (EF BB BF) to the output. Our tool gives you the option to include or exclude the BOM in the UTF-8 output, since some consumers expect it while others treat it as unwanted garbage at the start of the file.

Verification and Debugging

When debugging encoding issues, being able to see the exact bytes of both the input and output is invaluable. The tool displays the hexadecimal representation alongside the decoded text, making it easy to verify that the conversion is correct at the byte level. This is particularly useful when troubleshooting mojibake (garbled text caused by encoding mismatches) or when validating that a data pipeline preserves encoding integrity.

Private and Instantaneous

The Convert UTF-16 To UTF-8 tool processes all data locally in your browser. Text that might contain personal information, proprietary content, or sensitive communications is never transmitted to any server. The conversion runs in milliseconds regardless of input size, and results are immediately available for copying or downloading. A reliable, private encoding converter that is always just a browser tab away.