Fullwidth Latin Capital U

The extra width is for alignment, not a new pronunciation.

Ｕ comes from East Asian fixed-grid computing, where wide CJK characters and narrow ASCII letters had to share a line. A recognizable computer-era ancestor appears in Japan's JIS C 6226-1978, established in January 1978. Unicode later preserved fullwidth ASCII forms so older mixed encodings could round-trip. The forms developed as an encoding and typesetting solution, not as a one-off invention.

The wide form lets a Latin letter occupy the same square cell as a kanji in mixed text. Ordinary U is its narrow counterpart. In vertical Japanese text, a single Latin letter may sit upright in a fullwidth cell; longer Latin runs are usually rotated or set horizontally. In horizontal Japanese text, proportional Western fonts are generally preferred.

Where do people use Ｕ?

Use it when width matters or the wide look is intentional.

A Japanese input field may distinguish fullwidth from halfwidth Latin letters, so Ｕ can be required even though it reads as U. As of 2026, Japan's Digital Agency recommends conversion assistance when a system requires fullwidth alphanumerics, since entering them can be difficult. If no width is specified, ordinary U is usually the better fit.

From the 2010s onward, fullwidth text also became a vaporwave styling cue in track titles and other online display text. There, the extra width gives a retro look; it does not change the letter.

Will Ｕ match U in software?

No. Looking alike does not make them the same character.

Unicode maps Ｕ to U as a wide compatibility counterpart. Compatibility normalization such as NFKC can convert it to U, but a field or search only does that if it applies normalization.

Treat them as different when entering a code, account name, search term, or identifier. If instructions require fullwidth input, use Ｕ; if they require halfwidth or ASCII, use U.