U+FF1F

FULLWIDTH QUESTION MARK

Po — Other Punctuation
Common
Basic Multilingual Plane (BMP)
65311

Encoding Table

This table shows the exact bytes used to represent FULLWIDTH QUESTION MARK in each encoding. Unicode encodings (UTF-8, UTF-16, UTF-32) support every character; legacy encodings only cover a limited character set and show "not supported" when a character falls outside their range.

Encoding Bytes (Hex) Bytes (Decimal) Byte count
UTF-8 EF BC 9F 239 188 159 3
UTF-16 LE 1F FF 31 255 2
UTF-16 BE FF 1F 255 31 2
UTF-32 LE 1F FF 00 00 31 255 0 0 4
UTF-32 BE 00 00 FF 1F 0 0 255 31 4
ASCII not supported
Latin-1 (ISO-8859-1) not supported
Windows-1252 not supported
ISO-8859-2 (Latin-2) not supported
ISO-8859-5 (Cyrillic) not supported
KOI8-R not supported
Shift-JIS 81 48 129 72 2
EUC-JP A1 A9 161 169 2
GBK A3 BF 163 191 2
Big5 A1 48 161 72 2

Escape Sequences

How to reference this character in source code, markup, and URLs.

none
?
?
\FF1F
\uFF1F
%EF%BC%9F
\uff1f
65311

View the glyph in different fonts and scripts on our sibling site.

View U+FF1F on CharLookup.com ↗

UTF-8 Binary Breakdown

UTF-8 encodes this character as 3 bytes. The leading 1110 prefix on byte 1 signals a 3-byte sequence. Bytes 2 and 3 begin with 10 to mark them as continuation bytes.

Byte 1
1 1 1 0 1 1 1 1
EF
·
Byte 2
1 0 1 1 1 1 0 0
BC
·
Byte 3
1 0 0 1 1 1 1 1
9F
UTF-8: EF BC 9F · 3 bytes · Codepoint U+FF1F

Unicode Properties

Introduced in Unicode 1.1
ON — Other Neutral

Compatibility decomposition (wide) — the sequence below represents the same underlying meaning in a simpler form.

Nearby Characters in Halfwidth and Fullwidth Forms