Windows code pages are sets of characters orcode pages (known ascharacter encodings in other operating systems) used inMicrosoft Windows from the 1980s and 1990s. Windows code pages were gradually superseded whenUnicode was implemented in Windows,^{[citation needed]} although they are still supported both within Windows and other platforms, and still apply whenAlt code shortcuts are used.

Current Windows versions supportUnicode, new Windows applications should use Unicode (UTF-8) and not 8-bit character encodings.^[1]

There are two groups of system code pages in Windows systems: OEM and Windows-native ("ANSI") code pages.(ANSI is theAmerican National Standards Institute.) Code pages in both of these groups areextended ASCII code pages. Additional code pages are supported by standard Windows conversion routines, but not used as either type of system code page.

ANSI code pages (officially called "Windows code pages"^[2] after Microsoft accepted the former term being a misnomer^[3]) are used for native non-Unicode (say,byte oriented) applications using agraphical user interface on Windows systems. The term "ANSI" is a misnomer because these Windows code pages do not comply with anyANSI (American National Standards Institute) standard;code page 1252 was based on an early ANSI draft that became the international standardISO 8859-1,^[3] which adds a further 32 control codes and space for 96 printable characters. Among other differences, Windows code-pages allocate printable characters to the supplementary control code space, making them at best illegible to standards-compliant operating systems.^[a]

Mostlegacy "ANSI" code pages have code page numbers in the pattern 125x. However,874 (Thai) and the East Asian multi-byte "ANSI" code pages (932,936,949,950), all of which are also used as OEM code pages, are numbered to match IBM encodings, none of which are identical to the Windows encodings (although most are similar). Whilecode page 1258 is also used as an OEM code page, it is original to Microsoft rather than an extension to an existing encoding. IBM have assigned their own, different numbers for Microsoft's variants, these are given for reference in the lists below where applicable.

All of the 125x Windows code pages, as well as 874 and 936, are labelled byInternet Assigned Numbers Authority (IANA) as "Windows-number", although "Windows-936" is treated as a synonym for "GBK". Windows code page 932 is instead labelled as "Windows-31J".^[4]

ANSI Windows code pages, and especially the code page1252, were so called since they were purportedly based on drafts submitted or intended for ANSI. However, ANSI andISO have not standardized any of these code pages. Instead they are either:^[3]

• Supersets of the standard sets such as those ofISO 8859 and the various national standards (likeWindows-1252 vs.ISO-8859-1),
• Major modifications of these (making them incompatible to various degrees, likeWindows-1250 vs.ISO-8859-2)
• Having no parallel encoding (likeWindows-1257 vs.ISO-8859-4;ISO-8859-13 was introduced much later). Also,Windows-1251 follows neither the ISO-standardisedISO-8859-5 nor the then-prevailingKOI-8.

Microsoft assigned about twelve of thetypography and business characters (including notably, theeuro sign, €) in CP1252 to thecode points 0x80–0x9F that, in ISO 8859, are assigned toC1 control codes. These assignments are also present in many other ANSI/Windows code pages at the same code-points. Windows did not use the C1 control codes, so this decision had no direct effect on Windows users. However, if included in a file transferred to a standards-compliant platform like Unix or MacOS, the information was invisible and potentially disruptive.^[a]

TheOEM code pages (original equipment manufacturer) are used byWin32 console applications, and byvirtual DOS, and can be considered a holdover fromDOS and the originalIBM PC architecture. A separate suite of code pages was implemented not only due to compatibility, but also because thefonts of VGA (and descendant) hardware suggest encoding ofline-drawing characters to be compatible withcode page 437. Most OEM code pages share many code points, particularly for non-letter characters, with the second (non-ASCII) half of CP437.

A typical OEM code page, in its second half, does not resemble any ANSI/Windows code page even roughly. Nevertheless, two single-byte, fixed-width code pages (874 forThai and 1258 forVietnamese) and four multibyteCJK code pages (932,936,949,950) are used as both OEM and ANSI code pages. Code page 1258 usescombining diacritics, as Vietnamese requires more than 128 letter-diacritic combinations. This is in contrast toVISCII, which replaces some of theC0 (i.e. ASCII) control codes.

Early computer systems had limited storage and restricted the number ofbits available to encode acharacter. Although earlier proprietary encodings had fewer, theAmerican Standard Code for Information Interchange (ASCII) settled on seven bits: this was sufficient to encode a 96 member subset of the characters used in the US. As eight-bitbytes came to predominate, Microsoft (and others) expanded the repertoire to 224, to handle a variety of other uses such a box-drawing symbols. The need to provideprecomposed characters for the Western European and South American markets required a different character set: Microsoft established the principle of code pages, one for each alphabet. For thesegmental scripts used in most of Africa, the Americas, southern and south-east Asia, the Middle East and Europe, a character needs just one byte but two or more bytes are needed for theideographic sets used in the rest of the world. The code-page model was unable to handle this challenge.

Since the late 1990s, software and systems have adoptedUnicode as their preferred character encoding format: Unicode is designed to handle millions of characters. All current Microsoft products andapplication program interfaces use Unicode internally,^{[citation needed]} but some applications continue to use the default encoding^{[clarification needed]} of the computer's 'locale' when reading and writing text data to files or standard output.^{[citation needed]} Therefore, files may still be encountered that are legible and intelligible in one part of the world but unintelligiblemojibake in another.

Microsoft adopted a Unicode encoding (first the now-obsoleteUCS-2, which was then Unicode's only encoding), i.e.UTF-16 for all itsoperating systems from Windows NT onwards, but additionally supportsUTF-8 (akaCP_UTF8) sinceWindows 10 version 1803.^[5]UTF-16 uniquely encodes all Unicode characters in theBasic Multilingual Plane (BMP) using 16 bits but the remaining Unicode (e.g.emojis) is encoded with a 32-bit (four byte) code – while the rest of the industry (Unix-like systems and the web), and now Microsoft choseUTF-8 (which uses one byte for the 7-bitASCII character set, two or three bytes for other characters in the BMP, and four bytes for the remainder).

This list isincomplete; you can help byadding missing items.(April 2014)

The following Windows code pages exist:

These nine code pages are allextended ASCII 8-bitSBCS encodings, and were designed byMicrosoft for use as ANSI codepages on Windows. They are commonly known by their IANA-registered^[6] names aswindows-<number>, but are also sometimes calledcp<number>, "cp" for "code page". They are all used as ANSI code pages; Windows-1258 is also used as an OEM code page.

The Windows-125x series includes nine of the ANSI code pages, and mostly covers scripts fromEurope andWest Asia with the addition ofVietnam. System encodings forThai and forEast Asian languages were numbered to match similar IBM code pages and are used as both ANSI and OEM code pages; these are covered in following sections.

These are also ASCII-based. Most of these are included for use as OEM code pages; code page 874 is also used as an ANSI code page.

These often differ from the IBM code pages of the same number: code pages 932, 949 and 950 only partly match the IBM code pages of the same number, while the number 936 was used by IBM for another Simplified Chinese encoding which is now deprecated and Windows-951, as part of akludge, is unrelated to IBM-951. IBM equivalent code pages are given in the second column. Code pages 932, 936, 949 and 950/951 are used as both ANSI and OEM code pages on the locales in question.

A few further multiple-byte code pages are supported for decoding or encoding using operating system libraries, but not used as either sort of system encoding in any locale.

Microsoft strongly recommends using Unicode in modern applications, but many applications or data files still depend on the legacy code pages.

• Programs need to know what code page to use in order to display the contents of (pre-Unicode) files correctly. If a program uses the wrong code page it may show text asmojibake.
• The code page in use may differ between machines, so (pre-Unicode) files created on one machine may be unreadable on another.
• Data is often improperly tagged with the code page, or not tagged at all, making determination of the correct code page to read the data difficult.
• These Microsoft code pages differ to various degrees from some of the standards and other vendors' implementations. This isn't a Microsoft issueper se, as it happens to all vendors, but the lack of consistency makes interoperability with other systems unreliable in some cases.
• The use of code pages limits the set of characters that may be used.
• Characters expressed in an unsupported code page may be converted to question marks (?) or otherreplacement characters, or to a simpler version (such as removing accents from a letter). In either case, the original character may be lost.

• National Language Support (NLS) API Reference. Table showing ANSI and OEM codepages per language (from web-archive since Microsoft removed the original page)
• IANA Charset Name Registrations
• Unicode mapping table for Windows code pages
• Unicode mappings of windows code pages with "best fit"

• Windows code pages

• CS1 Japanese-language sources (ja)
• Articles with short description
• Short description is different from Wikidata
• All articles with unsourced statements
• Articles with unsourced statements from October 2020
• Wikipedia articles needing clarification from October 2024
• Incomplete lists from April 2014