InUnicode, aPrivate Use Area (PUA) is a range ofcode points that, by definition, will not be assigned characters by the standard.^[1] Three Private Use Areas are defined: one in theBasic Multilingual Plane (U+E000–U+F8FF), and one each in, and nearly covering,planes 15 and 16 (U+F0000–U+FFFFD,U+100000–U+10FFFD). They are intentionally left undefined so that third parties may assign their own characters without conflicting with Unicode Standard assignments. Under the Unicode Stability Policy, the Private Use Areas will remain allocated for that purpose in all future Unicode versions.^[2]

Assignments to private-use code points need not be "private" in the sense of strictly internal to an organisation; a number of assignment schemes have been published by several organisations. Such publication may include a font that supports the definition (showing the glyphs), and software making use of the private-use characters (e.g., a graphics character for a "print document" function). By definition, multiple private parties may assign different characters to the same code point, with the consequence that a user may see one private character from an installed font where a different one was intended.

Under the Unicode definition, code points in the Private Use Areas are not noncharacters, reserved, or unassigned. Theircategory is "Other, private use (Co)", and no character names are specified. No representative glyphs are provided, and character semantics are left to private agreement.

Private-use characters are assigned Unicode code points whose interpretation is not specified by this standard and whose use may be determined by private agreement among cooperating users. These characters are designated for private use and do not have defined, interpretable semantics except by private agreement.... No charts are provided for private-use characters, as any such characters are, by their very nature, defined only outside the context of this standard.^[3]

There are three PUA blocks in Unicode.^[3][4][5]

In the Basic Multilingual Plane (plane 0), the block titled Private Use Area (PUA) has 6400 code points.

Planes 15 and 16 are almost^{[note 1]} entirely assigned to two further Private Use Areas: Supplementary Private Use Area-A (SPUA-A) and Supplementary Private Use Area-B (SPUA-B). InUTF-16 a subset of the high surrogates (U+DB80..U+DBFF) is used for these and only these planes, and are calledHigh Private Use Surrogates.

In Unicode 1.0.0, the Private Use Area extended from U+E800 to U+FDFF^[6] (i.e. did not include U+E000..E7FF, but additionally included the U+F900..FDFF range now occupied byCJK Compatibility Ideographs,Alphabetic Presentation Forms andArabic Presentation Forms-A). This was changed to U+E000..F8FF in Unicode 1.0.1,^[7] and remained so in Unicode 1.1.^[8] The range U+D800..DFFF, used forUTF-16 surrogates since Unicode 2.0, was unassigned and not part of the Private Use Area in any Unicode 1.x version.

Planes E0 (224) through FF (255), and groups 60 (96) though 7F (127) of theUniversal Coded Character Set (i.e. U+E00000 through U+FFFFFF and U+60000000 through U+7FFFFFFF) were also designated as private use. These ranges were removed when UCS was restricted to the seventeen planes reachable in UTF-16.^[9]

Many people and institutions have created character collections for the PUA. Some of these private use agreements are published, so other PUA implementers can aim for unused or less-used code points to prevent overlaps. Several characters and scripts previously encoded in private use agreements have actually been fully encoded in Unicode, necessitating mappings from the PUA to other Unicode code points.

One of the more well-known and broadly implemented PUA agreements is maintained by theConScript Unicode Registry (CSUR). The CSUR, which is not officially endorsed or associated with the Unicode Consortium, provides a mapping for constructed scripts, such asKlingon pIqaD and Ferengi script (Star Trek),Tengwar andCirth (J.R.R. Tolkien's cursive and runic scripts), Alexander Melville Bell'sVisible Speech, and Dr. Seuss's alphabet fromOn Beyond Zebra. The CSUR previously encoded the undecipheredPhaistos characters, as well as theShavian andDeseret alphabets, which have all been accepted for official encoding in Unicode.

Another common PUA agreement is maintained by theMedieval Unicode Font Initiative (MUFI). This project is attempting to support all of the scribal abbreviations, ligatures,precomposed characters, symbols, and alternateletterforms found in medieval texts written in the Latin alphabet. The express purpose of MUFI is to experimentally determine which characters are necessary to represent these texts, and to have those characters officially encoded in Unicode. As of Unicode version 5.1, 152 MUFI characters have been incorporated into the official Unicode encoding.^{[needs update]}

Some agreed-upon PUA character collections exist in part or whole because the Unicode Consortium is in no hurry to encode them. Some, such as unrepresented languages, are likely to end up encoded in the future. Some unusual cases such as fictional languages are outside the usual scope of Unicode but not explicitly ruled out by the principles of Unicode, and may show up eventually (such as the Star Trek and Tolkien writing systems). In other cases, the proposed encoding violates one or more Unicode principles and hence is unlikely to ever be officially recognized by Unicode—mostly where users want to directly encode alternate forms, ligatures, or base-character-plus-diacritic combinations (such as the TUNE scheme).

• Emoji were originally defined in unused spaces inShift JIS mobile encodings, with different carriers supporting different emoji characters. Beforeemoji were added to the Unicode Standard in Unicode 6.0, Google and major Japanese phone carriers each defined their own Private Use Area mappings for emoji. The Japanese carriers defined their encoding schemes in the Basic Multilingual Plane's Private Use Area, whereas Google defined theirs in Supplementary Private Use Area-A.^[10]
• GB/T 20542-2006 ("Tibetan Coded Character Set Extension A") and GB/T 22238-2008 ("Tibetan Coded Character Set Extension B") areChinese national standards that use the PUA to encode precomposed Tibetanligatures.
• GBK and earlier versions ofGB 18030 used the PUA to provisionally encode characters not found in Unicode standards at the time of publication. In the 2022 version of the standard (GB 18030-2022), characters are instead mapped to their standard Unicode codepoints.^[11]
• TheInstitute of the Estonian Language uses the PUA to encode Latin and Cyrillic precomposed characters^[12] that have no Unicode encoding.
• TheFree Tengwar Font Project uses a different mapping from theConScript Unicode Registry that largely follows Michael Everson's 2001-03-07 Tengwar discussion paper, but diverges in some details.
• TheMARC 21 standard uses the PUA to encode East Asian characters present in MARC-8^[13] that have no Unicode encoding.
• TheSIL Corporate PUA uses the PUA to encode characters used in minority languages that have not yet been accepted into Unicode.
• TheSTIX Fonts project uses the PUA to provide a comprehensive font set of mathematical symbols and alphabets, many of which are also available in the SMP now, e.g. in theMathematical Alphanumeric Symbols block.
• TheSMuFL uses the PUA to encode new music notation symbols, extending theMusical Symbols Unicode block.
• The Tamil Unicode New Encoding (TUNE)^[14] is a proposed scheme for encodingTamil that overcomes perceived deficiencies in the current Unicode encoding.

Informally, the range U+F000 through U+F8FF is known as the Corporate Use Area. This originates from early versions of Unicode, which defined an "End User Zone" extending from U+E000 upward and a "Corporate Use Zone" extending from U+F8FF downward, with the boundary between the two left undefined.^[8]

• TheAdobe Glyph List used to use the PUA for some of its glyphs.^[15]
• Apple lists a range of 1,280 characters in its developer documentation^[16] from U+F400–U+F8FF within the PUA for Apple's use. Of those, only 311 are used, in the range U+F700–U+F8FF (NeXT (NeXTSTEP andOPENSTEP) andApple (macOSAppKit)).^[17]
  • One of these is U+F8FF, theApple logo, generally supported by Apple's 8-bit sets.
• WGL4 uses the PUA (U+F001 and U+F002) to encode duplicates of the ligatures fi (U+FB01) fl (U+FB02).^[18]
• Microsoft's defunct Services For Macintosh feature used U+F001 through U+F029 as replacements for special characters allowed inHFS but forbidden inNTFS, and U+F02A for the Apple logo.^[19][20]
• In old versions of itsRichEdit component, Microsoft mapped U+F020–U+F0FF within the PUA to symbol fonts. For any character in this range, RichEdit would show a character from a symbol font instead of the end-user-defined character (EUDC).^[21][22]
• AutoCAD^{[clarification needed]} uses U+F8FC–U+F8FE for ⌀ (diameter sign), ± (plus–minus sign) and ° (degree sign) respectively.^{[citation needed]}
• Some fonts place the Windows logo atU+F000.^{[citation needed]}
• The code pointU+F000 is a numeral succession starting at 13 or 18 in some video games likeAgar.io.^{[citation needed]}
• OnUbuntu,U+E0FF is displayed as the "Circle Of Friends" logo^[23] andU+F200 is "ubuntu" in theUbuntu typeface with a superscripted "Circle Of Friends" (this itself isU+F0FF).^[24]
• The3270 font includes theDebian logo atU+F100.^{[citation needed]}
• In theLinux Libertine font,U+E000 displaysTux, the mascot ofLinux.^{[citation needed]}
• TheFont Awesome icon font uses the PUA to display various glyphs.^{[citation needed]}
• Powerline, a status line plugin forVim, uses U+E0A0–U+E0A2 and U+E0B0–U+E0B3 for extrabox-drawing characters.^[25][26]
• In theFira Sans typeface used inFirefox OS,U+E003 is displayed as theMozilla logo (the dinosaur head).^{[citation needed]}
• Lotus Multi-Byte Character Set (LMBCS), the encoding and character set internally used byLotus/IBMLotus 1-2-3,Symphony,SmartSuite,Notes,Domino as well as a number of third-party products such asMicrosoft Works, uses some characters (U+F862-U+F89F andU+F8FB-U+F8FE) in the Private Use Area for symbols not defined in Unicode. Of these,U+F8FB is known to be reserved for acrown currency symbol ("Kr"), andU+F8FC andU+F8FD were later mapped toU+FB02 (fl) andU+FB01 (fi) respectively. Additionally, when UTF-16 codes are embedded in LMBCS, the UTF-16 codes corresponding toU+F601 throughU+F6FF are substituted for UTF-16 codes which would containnull bytes, since LMBCS is designed to not contain embedded null bytes.^[27][28]
• IBM reserved severalcode page IDs for PUA code pages:code page 1446 for the generic plane 15,code page 1447 for the generic plane 16,code page 1448 for the generic BMP PUA,code page 1445 (IBM AFP PUA No. 1) for plane 15 with IBM allocations in U+FFF00–U+FFFFD,^[29][30] andcode page 1449 (IBM default PUA) for the BMP PUA with IBM allocations in U+F83D–U+F8FF.^[31][32]
• The file system found in Windows uses theU+F000 toU+F0FF block to escapespecial characters.^{[citation needed]}
• NetApp translates characters in filenames that are allowed on Unix but invalid forSMB clients to PUA characters.^[33]
• Twitter's Chirp font provides some additional icons, likeU+E000 which corresponds to a left down arrow,U+EA00 which corresponds to the Twitter bird, andU+F8FF which corresponds to an Apple logo, possibly for compatibility with Apple fonts.^[34]

The concept of reserving specific code points for private use is based on similar earlier usage in other character sets. In particular, many otherwise obsolete characters in East Asian scripts continue to be used in specific names or other situations, and so some character sets for those scripts made allowance for private-use characters (such as the user-defined planes ofCNS 11643, orgaiji in certain Japanese encodings). The Unicode standard references these uses under the name "End User Character Definition" (EUCD).^[3]

Additionally, theC1 control block contains two codes intended for private use "control functions" byECMA-48: 0x91private use one (PU1) and 0x92private use two (PU2).^[35][36] Unicode includes these atU+0091<control-0091> andU+0092<control-0092> but defines them as control characters (categoryCc), not private-use characters (categoryCo).^[4][37]

Encodings that do not have private use areas but have more or less unused areas, such asISO/IEC 8859 andShift JIS, have seen uncontrolled variants of these encodings evolve.^[38] For Unicode, software companies can use the Private Use Areas for their desired additions.

• Unicode blocks
• Articles with unsupported Private Use Area characters

• CS1 German-language sources (de)
• Articles with short description
• Short description is different from Wikidata
• Wikipedia articles in need of updating from November 2021
• All Wikipedia articles in need of updating
• Wikipedia articles needing clarification from June 2020
• All articles with unsourced statements
• Articles with unsourced statements from March 2025