World Library  
Flag as Inappropriate
Email this Article


Article Id: WHEBN0000040317
Reproduction Date:

Title: Utf-16  
Author: World Heritage Encyclopedia
Language: English
Subject: Unicode, UTF-8, Byte order mark, Universal Coded Character Set, NTFS
Publisher: World Heritage Encyclopedia


UTF-16 (16-bit Unicode Transformation Format) is a character encoding capable of encoding all 1,112,064 possible characters in Unicode. The encoding is variable-length, as code points are encoded with one or two 16-bit code units. (also see Comparison of Unicode encodings for a comparison of UTF-8, -16 & -32)

The older UCS-2 (2-byte Universal Character Set) is a similar character encoding that was superseded by UTF-16 in version 2.0 of the Unicode standard in July 1996.[1] UCS-2 produces a fixed-length format by simply using the code point as the 16-bit code unit. UTF-16 expands the code space significantly by using surrogate pairs to encode code points above 0xFFFF, and produces the same result as UCS-2 for all code points in the range 0-0xFFFF that had been or ever will be assigned a character.

UTF-16 is officially defined in Annex Q of the international standard ISO/IEC 10646.[2] It is also described in "The Unicode Standard" version 2.0 and higher, as well as in the IETF's RFC 2781.


The Unicode code space is divided into seventeen planes of 216 (65,536) code points each, though some code points have not yet been assigned character values, some are reserved for private use, and some are permanently reserved as non-characters. The code points in each plane have the hexadecimal values xx0000 to xxFFFF, where xx is a hex value from 00 to 10, signifying the plane to which the values belong.

Code points U+0000 to U+D7FF and U+E000 to U+FFFF

The first plane (code points U+0000 to U+FFFF) contains the most frequently used characters and is called the Basic Multilingual Plane or BMP. 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. The code points in the BMP are the only code points that can be represented in UCS-2. Within this plane, code points U+D800 to U+DFFF (see below) were never assigned character values in UCS-2, and in UTF-16 are reserved for high and low surrogates used to encode codepoint values greater than U+FFFF.

Code points U+010000 to U+10FFFF

Code points from the other planes (called Supplementary Planes) are encoded in UTF-16 by pairs of 16-bit code units called surrogate pairs, by the following scheme:

UTF-16 decoder
High \ Low DC00 DC01    …    DFFF
D800 010000 010001 0103FF
D801 010400 010401 0107FF
DBFF 10FC00 10FC01 10FFFF
  • 0x010000 is subtracted from the code point, leaving a 20-bit number in the range 0..0x0FFFFF.
  • The top ten bits (a number in the range 0..0x03FF) are added to 0xD800 to give the first code unit or high surrogate, which will be in the range 0xD800..0xDBFF.
  • The low ten bits (also in the range 0..0x03FF) are added to 0xDC00 to give the second code unit or low surrogate, which will be in the range 0xDC00..0xDFFF.

(High and low surrogates are also known as "leading" and "trailing" surrogates, respectively, analogous to the leading and trailing bytes of UTF-8.[3] Note that "high" surrogates have lower code-point numbers than "low" surrogates.)

Since the ranges for the high surrogates, low surrogates, and valid BMP characters are disjoint, searches are simplified: it is not possible for part of one character to match a different part of another character. 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. UTF-8 shares these advantages, but many earlier multi-byte encoding schemes 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 Basic Multilingual Plane, 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, CVE-2012-2135).[4]

Code points U+D800 to U+DFFF

The Unicode standard permanently reserves these code point values for UTF-16 encoding of the high and low surrogates, and they will never be assigned a character, so there should be no reason to encode them. The official Unicode standard says that no UTF forms, including UTF-16, can encode these code points.

However UCS-2, UTF-8, and UTF-32 can encode these code points in trivial and obvious ways, and large amounts of software does so even though the standard states that such arrangements should be treated as encoding errors. It is possible to unambiguously encode them in UTF-16 by using a code unit equal to the code point, as long as no sequence of two code units can be interpreted as a legal surrogate pair (that is, as long as a high surrogate is never followed by a low surrogate). The majority of UTF-16 encoder and decoder implementations translate between encodings as though this were the case.

Byte order encoding schemes

UTF-16 and UCS-2 produce a sequence of 16-bit code units. Each unit thus takes two 8-bit bytes, and 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 unit with the value U+FEFF, to precede the first actual coded value.[5] (U+FEFF is the invisible zero-width non-breaking space/ZWNBSP character.)[6] 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 non-character 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 says that big-endian encoding should be assumed. (In practice, due to Windows using little-endian order by default, many applications also assume little-endian encoding by default.) If there is no BOM, one method of recognizing a UTF-16 encoding is searching for the space character (U+0020) which is very common in texts in most languages.

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. Many applications ignore the BOM code at the start of any Unicode encoding. Web browsers often use a BOM as a hint in determining the character encoding.[7]

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.

UCS-2 encoding is defined to be big-endian only. In practice most software defaults to little-endian, and handles a leading BOM to define the byte order just as in UTF-16. Although the similar designations UCS-2BE and UCS-2LE imitate the UTF-16 labels, they do not represent official encoding schemes.

Use in major operating systems and environments

UTF-16 is used for text in the OS API in Microsoft Windows 2000/XP/2003/Vista/7/8/CE.[8] Older Windows NT systems (prior to Windows 2000) only support UCS-2.[9] In Windows XP, no code point above U+FFFF is included in any font delivered with Windows for European languages.[10][11] Files and network data tend to be a mix of UTF-16, UTF-8, and legacy byte encodings.

IBM iSeries systems designate code page CCSID 13488 for UCS-2 character encoding, CCSID 1200 for UTF-16 encoding, and CCSID 1208 for UTF-8 encoding.[12]

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.

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

The Python language environment officially only uses UCS-2 internally since version 2.0, but the UTF-8 decoder to "Unicode" produces correct UTF-16. Since Python 2.2, "wide" builds of Unicode are supported which use UTF-32 instead;[13] these are primarily used on Linux. Python 3.3 no longer ever uses UTF-16, instead strings are stored in one of ASCII/Latin-1, UCS-2, or UTF-32, depending on which code points are in the string, with a UTF-8 version also included so that repeated conversions to UTF-8 are fast.[14]

Java originally used UCS-2, and added UTF-16 supplementary character support in J2SE 5.0.

In many languages quoted strings need a new syntax for quoting non-BMP characters, as the "\uXXXX" syntax explicitly limits itself to 4 hex digits. The most common (used by C#, D and several other languages) is to use an upper-case 'U' with 8 hex digits such as "\U0001D11E"[15] In Java 7 regular expressions and ICU and Perl, the syntax "\x{1D11E}" must be used. In many other cases (such as Java outside of regular expressions)[16] the only way to get non-BMP characters is to enter the surrogate halves individually, for example: "\uD834\uDD1E" for U+1D11E.

These implementations all return the number of 16-bit code units rather than the number of Unicode code points when the equivalent of strlen() is used on their strings, and indexing into a string returns the indexed code unit, not the indexed code point,[17][18][19] this leads some people to claim that UTF-16 is not supported. However the term "character" is defined and used in multiple ways within the Unicode terminology,[20] so an unambiguous count is not possible and there is no reason for strlen to attempt to return any such value. Most of the confusion is due to obsolete ASCII-era documentation using the term "character" when a fixed-size "byte" or "octet" was intended.


Consider the encoding of U+10437 (𐐷):

  • Subtract 0x10000 from 0x10437. The result is 0x00437, 0000 0000 0100 0011 0111.
  • Split this into the high 10-bit value and the low 10-bit value: 0000000001 and 0000110111.
  • Add 0xD800 to the high value to form the high surrogate: 0xD800 + 0x0001 = 0xD801.
  • Add 0xDC00 to the low value to form the low surrogate: 0xDC00 + 0x0037 = 0xDC37.

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.

Character Binary code point Binary UTF-16 UTF-16 hex
code units
hex bytes
hex bytes
$ U+0024 0000 0000 0010 0100 0000 0000 0010 0100 0024 00 24 24 00
U+20AC 0010 0000 1010 1100 0010 0000 1010 1100 20AC 20 AC AC 20
𐐷 U+10437 0001 0000 0100 0011 0111 1101 1000 0000 0001 1101 1100 0011 0111 D801 DC37 D8 01 DC 37 01 D8 37 DC
𤭢 U+24B62 0010 0100 1011 0110 0010 1101 1000 0101 0010 1101 1111 0110 0010 D852 DF62 D8 52 DF 62 52 D8 62 DF

Example code

C functions to convert Unicode code points from/to UTF-16 streams, assuming there are read and write functions that handle the 16-bit code units. The decoder requires the ability to "push back" a 16-bit code unit so the next read gets it (this is a popular but not the only method of dealing with unpaired surrogates):

void write_utf16(unsigned code_point)
   if (code_point < 0x10000) {
  } else if (code_point <= 0x10FFFF) {
    write_unsigned_short((code_point >> 10) + 0xD7C0);
    write_unsigned_short((code_point & 0x3FF) + 0xDC00);
  } else {
    error("invalid code_point");

unsigned read_code_point_from_utf16()
  unsigned code_unit = read_unsigned_short();
  if (code_unit >= 0xD800 && code_unit <= 0xDBFF) {
    unsigned code_unit_2 = read_unsigned_short();
    if (code_unit_2 >= 0xDC00 && code_unit_2 <= 0xDFFF)
      return (code_unit << 10) + code_unit_2 - 0x35FDC00;
  return code_unit;

See also


  1. ^ "Questions about encoding forms". Retrieved 12 November 2010. 
  2. ^ ISO/IEC 10646-1:2000(E), pp. 890-892; ISO/IEC 10646:2003(E), pp. 1364-1366; ISO/IEC 10646:2012(E) Final Committee Draft (FCD), p. 2208; The FCD contains a reference to clauses 9 and 10, pp. 15-17.
  3. ^ Allen, Julie D.; Anderson, Deborah;  
  4. ^
  5. ^ UTF-8 encoding produces byte values strictly less than 0xFE, so either byte in the BOM sequence also identifies the encoding as UTF-16.
  6. ^ Use of U+FEFF as the character ZWNBSP instead of as a BOM has been deprecated in favor of U+2060 (WORD JOINER); see Byte Order Mark (BOM) FAQ at But if an application interprets an initial BOM as a character, the ZWNBSP character is invisible, so the impact is minimal.
  7. ^ Encoding test pages (load these files and check the encoding that the browser selects)
  8. ^ Unicode (Windows). Retrieved 08 March 2011 "These functions use UTF-16 (wide character) encoding (...) used for native Unicode encoding on Windows operating systems."
  9. ^ "Description of storing UTF-8 data in SQL Server". December 7, 2005. Retrieved 2008-02-01. 
  10. ^ "Unicode". Retrieved 2009-07-20. 
  11. ^ "Surrogates and Supplementary Characters". Retrieved 2009-07-20. 
  12. ^ "Character conversion".  
  13. ^ PEP 261
  14. ^ PEP 393
  15. ^ ECMA-334, section 9.4.1
  16. ^ Java Language Specification, Third Edition, section 3.3
  17. ^ Austin, Calvin (May 2004). "J2SE 5.0 in a Nutshell". Retrieved 2008-06-17. Supplementary Character Support ,
  18. ^ "Javadoc for java.lang.String.charAt(int)". 
  19. ^ "C Sharp Language Specification". Retrieved 2009-07-08. 
  20. ^

External links

  • A very short algorithm for determining the surrogate pair for any codepoint
  • Unicode Technical Note #12: UTF-16 for Processing
  • Unicode FAQ: What is the difference between UCS-2 and UTF-16?
  • Unicode Character Name Index
  • RFC 2781: UTF-16, an encoding of ISO 10646
  • java.lang.String documentation, discussing surrogate handling
This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.

Copyright © World Library Foundation. All rights reserved. eBooks from World eBook Library are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.