UTF-16#Code points from U+010000 to U+10FFFF

In the late 1980s, work began on developing a uniform encoding for a "Universal Character Set" (UCS) that would replace earlier language-specific encodings with one coordinated system. The goal was to include all required characters from most of the world's languages, as well as symbols from technical domains such as science, mathematics, and music. The original idea was to replace the typical 256-character encodings, which required 1 byte per character, with an encoding using 65,536 (2¹⁶) values, which would require 2 bytes (16 bits) per character.

Two groups worked on this in parallel, ISO/IEC JTC 1/SC 2 and the Unicode Consortium, the latter representing mostly manufacturers of computing equipment. The two groups attempted to synchronize their character assignments so that the developing encodings would be mutually compatible. The early 2-byte encoding was originally called "Unicode", but is now called "UCS-2".{{cite web|url=https://dev.mysql.com/doc/refman/5.7/en/charset-unicode-ucs2.html|title=MySQL :: MySQL 5.7 Reference Manual :: 10.1.9.4 The ucs2 Character Set (UCS-2 Unicode Encoding)|website=dev.mysql.com}}

When it became increasingly clear that 2¹⁶ characters would not suffice,{{cite web|title=What is UTF-16?|url=https://www.unicode.org/faq/utf_bom.html#utf16-1|website=The Unicode Consortium|publisher=Unicode, Inc.|access-date=29 March 2018}} IEEE introduced a larger 31-bit space and an encoding (UCS-4) that would require 4 bytes per character. This was resisted by the Unicode Consortium, both because 4 bytes per character wasted a lot of memory and disk space, and because some manufacturers were already heavily invested in 2-byte-per-character technology. The UTF-16 encoding scheme was developed as a compromise and introduced with version 2.0 of the Unicode standard in July 1996.{{cite web |url=https://www.unicode.org/faq//utf_bom.html|title=Questions about encoding forms |access-date=2010-11-12}} It is fully specified in RFC 2781, published in 2000 by the IETF.ISO/IEC 10646:2014 "Information technology – Universal Coded Character Set (UCS)" sections 9 and 10.{{cite book |title=The Unicode Standard version 7.0 |date=2014 |chapter-url=https://www.unicode.org/versions/Unicode7.0.0/ch02.pdf#G11153 |chapter=Chapter 2 General Structure |at=2.5 Encoding Forms}}

UTF-16 is specified in the latest versions of both the international standard ISO/IEC 10646 and the Unicode Standard. "UCS-2 should now be considered obsolete. It no longer refers to an encoding form in either 10646 or the Unicode Standard." UTF-16 will never be extended to support a larger number of code points or to support the code points that were replaced by surrogates, as this would violate the Unicode Stability Policy with respect to general category or surrogate code points.{{cite web|url=https://unicode.org/policies/stability_policy.html|title=Unicode Character Encoding Stability Policies|website=unicode.org}} (Any scheme that remains a self-synchronizing code would require allocating at least one Basic Multilingual Plane (BMP) code point to start a sequence. Changing the purpose of a code point is disallowed.)

Each Unicode code point is encoded either as one or two 16-bit code units. Code points less than 2¹⁶ ("in the BMP") are encoded with a single 16-bit code unit equal to the numerical value of the code point, as in the older UCS-2. Code points greater than or equal to 2¹⁶ ("above the BMP") are encoded using two 16-bit code units. These two 16-bit code units are chosen from the UTF-16 surrogate range {{tt|0xD800–0xDFFF}} which had not previously been assigned to characters. Values in this range are not used as characters, and UTF-16 provides no legal way to code them as individual code points. A UTF-16 stream, therefore, consists of single 16-bit codes outside the surrogate range, and pairs of 16-bit values that are within the surrogate range.

{{hatnote|U+D800 to U+DFFF have a special purpose, see below.}}

Both UTF-16 and UCS-2 encode code points in this range as single 16-bit code units that are numerically equal to the corresponding code points. These code points in the Basic Multilingual Plane (BMP) are the only code points that can be represented in UCS-2.{{Citation needed|date=November 2015}} As of Unicode 9.0, some modern non-Latin Asian, Middle-Eastern, and African scripts fall outside this range, as do most emoji characters.

Code points from the other planes are encoded as two 16-bit code units called a surrogate pair. The first code unit is a high surrogate and the second is a low surrogate (These are also known as "leading" and "trailing" surrogates, respectively, analogous to the leading and trailing bytes of UTF-8.{{cite book |title=The Unicode Standard, Version 7.0—Core Specification |editor1-last=Allen |editor1-first=Julie D. |editor2-last=Anderson |editor2-first=Deborah |editor3-last=Becker |editor3-first=Joe |editor3-link=Joe Becker (Unicode) |editor4-last=Cook |editor4-first=Richard |publisher=The Unicode Consortium |date=2014 |place=Mountain View |url=https://www.unicode.org/versions/Unicode7.0.0/ |section=3.8 Surrogates |page=118 |chapter-url=https://www.unicode.org/versions/Unicode7.0.0/ch03.pdf |archive-url=https://ghostarchive.org/archive/20221009/https://www.unicode.org/versions/Unicode7.0.0/ch03.pdf |archive-date=2022-10-09 |url-status=live |access-date=3 November 2014 }}):

• 0x10000 is subtracted from the code point (U), leaving a 20-bit number (U') in the hex number range 0x00000–0xFFFFF.
• The high ten bits (in the range 0x000–0x3FF) are added to 0xD800 to give the first 16-bit code unit or high surrogate (W1), which will be in the range {{color|#920000|0xD800–0xDBFF}}.
• The low ten bits (also in the range 0x000–0x3FF) are added to 0xDC00 to give the second 16-bit code unit or low surrogate (W2), which will be in the range {{color|#000092|0xDC00–0xDFFF}}.

Illustrated visually, the distribution of U' between W1 and W2 looks like:{{Cite journal|url=https://tools.ietf.org/html/rfc2781.html|title=UTF-16, an encoding of ISO 10646|last1=Yergeau|first1=Francois|last2=Hoffman|first2=Paul|website=tools.ietf.org|date=February 2000|language=en|access-date=2019-06-18}}

U' = yyyyyyyyyyxxxxxxxxxx // U - 0x10000

W1 = 110110yyyyyyyyyy // 0xD800 + yyyyyyyyyy

W2 = 110111xxxxxxxxxx // 0xDC00 + xxxxxxxxxx

Since the ranges for the high surrogates ({{color|#920000|0xD800–0xDBFF}}), low surrogates ({{color|#000092|0xDC00–0xDFFF}}), and valid BMP characters (0x0000–0xD7FF, 0xE000–0xFFFF) are disjoint, it is not possible for a surrogate to match a BMP character, or for two adjacent code units to look like a legal surrogate pair. This simplifies searches a great deal. It also means that UTF-16 is self-synchronizing on 16-bit words: whether a code unit starts a character can be determined without examining earlier code units (i.e. the type of code unit can be determined by the ranges of values in which it falls). UTF-8 shares these advantages, but many earlier multi-byte encoding schemes (such as Shift JIS and other Asian multi-byte encodings) did not allow unambiguous searching and could only be synchronized by re-parsing from the start of the string. UTF-16 is not self-synchronizing if one byte is lost or if traversal starts at a random byte.

Because the most commonly used characters are all in the BMP, handling of surrogate pairs is often not thoroughly tested. This leads to persistent bugs and potential security holes, even in popular and well-reviewed application software (e.g. {{CVE|2008-2938|2012-2135}}).

{{Refimprove section|date=August 2023}}

The official Unicode standard says that no UTF forms, including UTF-16, can encode the surrogate code points. Since these will never be assigned a character, there should be no reason to encode them. However, Windows allows unpaired surrogates in filenames{{cite web |title=Maximum Path Length Limitation |url=https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation |website=Microsoft | date=2022-07-18 |access-date=2022-10-10 |quote=[…] the file system treats path and file names as an opaque sequence of WCHARs}} and other places, which generally means they have to be supported by software in spite of their exclusion from the Unicode standard.

UCS-2, UTF-8, and UTF-32 can encode these code points in trivial and obvious ways, and a large amount of software does so, even though the standard states that such arrangements should be treated as encoding errors.

It is possible to unambiguously encode an unpaired surrogate (a high surrogate code point not followed by a low one, or a low one not preceded by a high one) in the format of UTF-16 by using a code unit equal to the code point. The result is not valid UTF-16, but the majority of UTF-16 encoder and decoder implementations do this when translating between encodings.{{citation needed|date=October 2011}}

To encode U+10437 (𐐷) to UTF-16:

• Subtract 0x10000 from the code point, leaving 0x0437.
• For the high surrogate, shift right by 10 (divide by 0x400), then add 0xD800, resulting in 0x0001 + 0xD800 = 0xD801.
• For the low surrogate, take the low 10 bits (remainder of dividing by 0x400), then add 0xDC00, resulting in 0x0037 + 0xDC00 = 0xDC37.

To decode U+10437 (𐐷) from UTF-16:

• Take the high surrogate (0xD801) and subtract 0xD800, then multiply by 0x400, resulting in 0x0001 × 0x400 = 0x0400.
• Take the low surrogate (0xDC37) and subtract 0xDC00, resulting in 0x37.
• Add these two results together (0x0437), and finally add 0x10000 to get the final code point, 0x10437.

The following table summarizes this conversion, as well as others. The colors indicate how bits from the code point are distributed among the UTF-16 bytes. Additional bits added by the UTF-16 encoding process are shown in black.

{{anchor|UTF-16LE|UTF-16BE}}

UTF-16 and UCS-2 produce a sequence of 16-bit code units. Since most communication and storage protocols are defined for bytes, and each unit thus takes two 8-bit bytes, the order of the bytes may depend on the endianness (byte order) of the computer architecture.

To assist in recognizing the byte order of code units, UTF-16 allows a byte order mark (BOM), a code point with the value U+FEFF, to precede the first actual coded value.{{efn|UTF-8 encoding produces byte values strictly less than 0xFE, so either byte in the BOM sequence also identifies the encoding as UTF-16 (assuming that UTF-32 is not expected).}} (U+FEFF is the invisible zero-width non-breaking space/ZWNBSP character).{{efn|Use of U+FEFF as the character ZWNBSP instead of as a BOM has been deprecated in favor of U+2060 (WORD JOINER); see [https://www.unicode.org/faq/utf_bom.html#BOM Byte Order Mark (BOM) FAQ] at Unicode.org. But if an application interprets an initial BOM as a character, the ZWNBSP character is invisible, so the impact is minimal.}} If the endian architecture of the decoder matches that of the encoder, the decoder detects the 0xFEFF value, but an opposite-endian decoder interprets the BOM as the noncharacter}} value U+FFFE reserved for this purpose. This incorrect result provides a hint to perform byte-swapping for the remaining values.

If the BOM is missing, RFC 2781 recommends{{efn|{{IETF RFC|2781}} section 4.3 says that if there is no BOM, "the text SHOULD be interpreted as being big-endian." According to section 1.2, the meaning of the term "SHOULD" is governed by {{IETF RFC|2119}}. In that document, section 3 says "... there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course".}} that big-endian (BE) encoding be assumed. In practice, due to Windows using little-endian (LE) order by default, many applications assume little-endian encoding. It is also reliable to detect endianness by looking for null bytes, on the assumption that characters less than U+0100 are very common. If more even bytes (starting at 0) are null, then it is big-endian.

The standard also allows the byte order to be stated explicitly by specifying UTF-16BE or UTF-16LE as the encoding type. When the byte order is specified explicitly this way, a BOM is specifically not supposed to be prepended to the text, and a U+FEFF at the beginning should be handled as a ZWNBSP character. Most applications ignore a BOM in all cases despite this rule.

For Internet protocols, IANA has approved "UTF-16", "UTF-16BE", and "UTF-16LE" as the names for these encodings (the names are case insensitive). The aliases UTF_16 or UTF16 may be meaningful in some programming languages or software applications, but they are not standard names in Internet protocols.

Similar designations, UCS-2BE and UCS-2LE, are used to show versions of UCS-2.

A "character" may use any number of Unicode code points.{{Cite web|title=It's not wrong that "🤦🏼‍♂️".length == 7|url=https://hsivonen.fi/string-length/|access-date=2021-03-15|website=hsivonen.fi}} For instance an emoji flag character takes 8 bytes, since it is "constructed from a pair of Unicode scalar values"{{Cite web|title=Apple Developer Documentation|url=https://developer.apple.com/documentation/swift/string|access-date=2021-03-15|website=developer.apple.com}} (and those values are outside the BMP and require 4 bytes each). UTF-16 in no way assists in "counting characters" or in "measuring the width of a string".

UTF-16 is often claimed to be more space-efficient than UTF-8 for East Asian languages, since it uses two bytes for characters that take 3 bytes in UTF-8. Since real text contains many spaces, numbers, punctuation, markup (for e.g. web pages), and control characters, which take only one byte in UTF-8, this is only true for artificially constructed dense blocks of text.{{citation needed|date=November 2022}} A more serious claim can be made for Devanagari and Bengali, which use multi-letter words and all the letters take 3 bytes in UTF-8 and only 2 in UTF-16.

In addition the Chinese Unicode encoding standard GB 18030 always produces files the same size or smaller than UTF-16 for all languages, not just for Chinese (it does this by sacrificing self-synchronization).

UTF-16 is used for text in the OS API of all currently supported versions of Microsoft Windows{{cite web |url=https://learn.microsoft.com/en-us/windows/win32/intl/unicode |title=Unicode |website=Microsoft Learn |access-date=2011-03-08 |quote=These functions use UTF-16 (wide character) encoding (…) used for native Unicode encoding on Windows operating systems.}} (and including at least Windows CE since Windows CE 5.0{{cite web |url=https://learn.microsoft.com/en-us/previous-versions/windows/embedded/ms904394(v=msdn.10) |title=Working With Unicode Surrogates (Windows CE 5.0) |date=2012-09-14 |website=Microsoft Learn}} and Windows NT since Windows 2000{{cite web |url=https://learn.microsoft.com/en-us/windows/win32/intl/surrogates-and-supplementary-characters |title=Surrogates and Supplementary Characters |date=2022-05-24 |website=Microsoft Learn |quote=Windows 2000 introduces support for basic input, output, and simple sorting of supplementary characters. However, not all system components are compatible with supplementary characters.}}). Windows 9x and NT prior to Windows 2000 only supported UCS-2.{{cite web |title=Unicode|publisher=microsoft.com |url=https://msdn.microsoft.com/en-us/library/dd374081.aspx |access-date=2009-07-20}}{{cite web |title=Surrogates and Supplementary Characters |publisher=microsoft.com |url=https://msdn.microsoft.com/en-us/library/dd374069.aspx |access-date=2009-07-20}} Since Windows 10 version 1903 (or insider build 17035) it has been possible to use UTF-8 in the API,{{cite web|title=Use UTF-8 code pages in Windows apps|url=https://learn.microsoft.com/en-us/windows/apps/design/globalizing/use-utf8-code-page |access-date=2020-06-06 |quote=As of Windows version 1903 (May 2019 update), you can use the ActiveCodePage property in the appxmanifest for packaged apps, or the fusion manifest for unpackaged apps, to force a process to use UTF-8 as the process code page. [...] CP_ACP equates to CP_UTF8 only if running on Windows version 1903 (May 2019 update) or above and the ActiveCodePage property described above is set to UTF-8. Otherwise, it honors the legacy system code page. We recommend using CP_UTF8 explicitly. |website=learn.microsoft.com |language=en-us}} though most software, such as Windows File Explorer, still uses UTF-16 API. Microsoft has stated that "UTF-16 [..] is a unique burden that Windows places on code that targets multiple platforms"{{Cite web |title=UTF-8 support in the Microsoft Game Development Kit (GDK) - Microsoft Game Development Kit |url=https://learn.microsoft.com/en-us/gaming/gdk/_content/gc/system/overviews/utf-8 |access-date=2023-03-05 |website=learn.microsoft.com |language=en-us |quote=By operating in UTF-8, you can ensure maximum compatibility [..] Windows operates natively in UTF-16 (or WCHAR), which requires code page conversions by using MultiByteToWideChar and WideCharToMultiByte. This is a unique burden that Windows places on code that targets multiple platforms. [..] The Microsoft Game Development Kit (GDK) and Windows in general are moving forward to support UTF-8 to remove this unique burden of Windows on code targeting or interchanging with multiple platforms and the web. Also, this results in fewer internationalization issues in apps and games and reduces the test matrix that's required to get it right.}} Files and network data tend to be a mix of UTF-16, UTF-8, and legacy byte encodings.

SMS text messaging effectively uses UTF-16. The documentation specifies UCS-2 but UTF-16 is necessary for Emoji to work.{{cite web|url=https://www.twilio.com/engineering/2012/11/08/adventures-in-unicode-sms|title=Adventures in Unicode SMS|date=2012-11-08|publisher=Twilio|author=Chad Selph|access-date=2015-08-28|archive-url=https://web.archive.org/web/20150908104520/https://www.twilio.com/engineering/2012/11/08/adventures-in-unicode-sms|archive-date=2015-09-08|url-status=dead}}

The IBM i operating system designates CCSID (code page) 13488 for UCS-2 encoding and CCSID 1200 for UTF-16 encoding, though the system treats them both as UTF-16.{{cite web |url=https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_74/nls/rbagsucs2.htm |title=UCS-2 and its relationship to Unicode (UTF-16) |publisher=IBM |access-date=2019-04-26}}

UTF-16 is used by the Qualcomm BREW operating systems; the .NET environments; and the Qt cross-platform graphical widget toolkit.

Symbian OS used in Nokia S60 handsets and Sony Ericsson UIQ handsets uses UCS-2. iPhone handsets use UTF-16 for Short Message Service instead of UCS-2 described in the 3GPP TS 23.038 (GSM) and IS-637 (CDMA) standards.{{cite web|url=https://www.twilio.com/engineering/2012/11/08/adventures-in-unicode-sms|title=Adventures in Unicode SMS|author-last=Selph|author-first=Chad|date=2012-11-08|publisher=Twilio|archive-url=https://web.archive.org/web/20121109052626/https://www.twilio.com/engineering/2012/11/08/adventures-in-unicode-sms|access-date=2015-08-28|archive-date=2012-11-09}}

The Joliet file system, used in CD-ROM media, encodes file names using UCS-2BE (up to sixty-four Unicode characters per file name).

Python version 2.0 officially only used UCS-2 internally, but the UTF-8 decoder to "Unicode" produced correct UTF-16. There was also the ability to compile Python so that it used UTF-32 internally, this was sometimes done on Unix. Python 3.3 switched internal storage to use one of ISO-8859-1, UCS-2, or UTF-32 depending on the largest code point in the string.{{cite web |url=https://www.python.org/dev/peps/pep-0393/ |title=PEP 0393 – Flexible String Representation |work=Python.org |access-date=2015-05-29}} Python 3.12 drops some functionality (for CPython extensions) to make it easier to migrate to UTF-8 for all strings.{{Cite web |title=PEP 623 – Remove wstr from Unicode {{!}} peps.python.org |url=https://peps.python.org/pep-0623/ |access-date=2023-02-24 |website=peps.python.org}}

Java originally used UCS-2, and added UTF-16 supplementary character support in J2SE 5.0. Despite awareness of UTF-8{{Cite web |title=JEP 400: UTF-8 by Default |url=https://openjdk.org/jeps/400 |access-date=2023-03-12 |website=openjdk.org}} all strings are still UTF-16 (since Java 9, strings containing only ISO-8859-1 characters can be "compressed" to bytes{{Cite web |url=https://www.oracle.com/java/technologies/javase/9-new-features.html|title=JDK 9 Release Notes - New Features}}).

JavaScript may use UCS-2 or UTF-16.{{Cite web|url=https://mathiasbynens.be/notes/javascript-encoding|title=JavaScript's internal character encoding: UCS-2 or UTF-16? · Mathias Bynens|website=mathiasbynens.be}} As of ES2015, string methods and regular expression flags have been added to the language that permit handling strings from an encoding-agnostic perspective.

UEFI uses UTF-16 to encode strings by default.

Swift, Apple's preferred application language, used UTF-16 to store strings until version 5 which switched to UTF-8.{{Cite web|date=2019-03-20|title=UTF-8 String|url=https://swift.org/blog/utf8-string/|access-date=2020-08-20|website=Swift.org|language=en}}

Quite a few languages make the encoding part of the string object, and thus store and support a large set of encodings including UTF-16. Most consider UTF-16 and UCS-2 to be different encodings. Examples are the PHP language{{cite web|url=https://php.net/manual/en/mbstring.supported-encodings.php|title=PHP: Supported Character Encodings - Manual|website=php.net}} and MySQL.{{Cite web |title=MySQL :: MySQL 8.0 Reference Manual :: 10.9.2 The utf8mb3 Character Set (3-Byte UTF-8 Unicode Encoding) |url=https://dev.mysql.com/doc/refman/8.0/en/charset-unicode-utf8mb3.html |access-date=2023-02-24 |website=dev.mysql.com}}

A method to determine what encoding a system is using internally is to ask for the "length" of string containing a single non-BMP character. If the length is 2 then UTF-16 is being used. 4 indicates UTF-8. 3 or 6 may indicate CESU-8. 1 may indicate UTF-32, but more likely indicates the language decodes the string to code points before measuring the "length".

In many languages, quoted strings need a new syntax for quoting non-BMP characters, as the C-style "\uXXXX" syntax explicitly limits itself to 4 hex digits. The following examples illustrate the syntax for the non-BMP character {{unichar|1D11E|MUSICAL SYMBOL G CLEF}}:

• The most common (C++, C#, D, and several other languages) is an upper-case 'U' with 8 hex digits such as "\U0001D11E".{{cite web

|url=http://en.csharp-online.net/ECMA-334:_9.4.1_Unicode_escape_sequences

|title=ECMA-334: 9.4.1 Unicode escape sequences|website=en.csharp-online.net

|archive-url=https://web.archive.org/web/20130215065218/http://en.csharp-online.net/ECMA-334:_9.4.1_Unicode_escape_sequences

|archive-date=2013-02-15}}

• Java 7 regular expressions, ICU, and Perl, use "\x{1D11E}".
• ECMAScript 2015 (JavaScript) uses "\u{1D11E}".
• In many other cases (such as Java outside of regular expressions),Lexical Structure: Unicode Escapes in {{cite web |url=https://docs.oracle.com/javase/specs/jls/se6/html/lexical.html#3.3 |title=The Java Language Specification, Third Edition|website = Sun Microsystems, Inc. |year = 2005 | access-date=2019-10-11}} the only way to get non-BMP characters is to enter the surrogate halves individually: "\uD834\uDD1E".

• Comparison of Unicode encodings
• Plane (Unicode)
• UTF-8
• CESU-8
• UTF-32

{{notelist}}

{{reflist|30em}}

• [https://www.unicode.org/faq/utf_bom.html#utf16-4 A very short algorithm for determining the surrogate pair for any code point]
• [https://www.unicode.org/notes/tn12/ Unicode Technical Note #12: UTF-16 for Processing]
• [https://www.unicode.org/faq/utf_bom.html#utf16-11 Unicode FAQ: What is the difference between UCS-2 and UTF-16?]
• [https://www.unicode.org/charts/charindex.html Unicode Character Name Index]
• {{IETF RFC|2781|link=no}}: UTF-16, an encoding of ISO 10646
• [https://docs.oracle.com/javase/6/docs/api/java/lang/String.html#charAt(int) java.lang.String documentation, discussing surrogate handling]

{{Unicode navigation}}

{{Character encoding}}

Category:Encodings

Category:Character encoding

Category:Unicode Transformation Formats

Category:Computer-related introductions in 1991