Contact

UNICODE in Google Sheets: First Characters and Numeric Inputs

Text Intermediate Google Sheets

Inspect Unicode code points in Google Sheets, understand numeric-to-string input conversion and diagnose spaces or visually similar text.

Verification status: See the evidence and test scope described in this guide. How formula examples are checked

Quick answer: UNICODE(text) returns the decimal code point of the first character. Google also allows numeric arguments, which are interpreted as strings; for example, the first character of numeric 234 is the digit 2, whose code point is 50.

Availability and version history

  • Introduced: first introduction date is not established by the reviewed official history; no desktop release number is inferred.
  • Availability: documented in the rolling Google Sheets service; these examples use the web worksheet workflow.
  • Checked: October 14, 2026; official UNICODE reference. Documentation and independent models, with no native Sheets execution or wider client certification.

Syntax and source-specific rules

=UNICODE(text)

Google says the input should not be empty and its first character must have a Unicode representation. The dedicated reference does not provide a complete error-code table for invalid strings. Its numeric-input rule is explicit, so it need not be borrowed from another spreadsheet.

A code point is not a numeric digit’s quantity, an alphabetic rank or a count of storage bytes. UNICODE examines the first character, not the meaning of the whole string.

Example 1: compare text and numeric arguments

Evaluate these formulas in separate cells:

Formula Expected code point
=UNICODE("Delta") 68
=UNICODE("delta") 100
=UNICODE(234) 50
=UNICODE("234") 50
=UNICODE(0) 48
=UNICODE(-7) 45

For −7, the first character of its ordinary decimal string is the minus sign, code point 45. The numeric examples are small integers, avoiding unverified scientific notation, locale-dependent decimal formatting or very large numeric conversions.

The strings Delta and Door both start with D and therefore have the same first-character code point. Equal UNICODE results do not prove equal full strings.

Example 2: an emoji is a code point, not an ASCII byte

=UNICODE("😀 note")
=UNICHAR(128512)

The first formula has the documented-rule expectation 128512, the grinning-face code point. The second reconstructs that character. Google’s sample uses the same emoji but omits quotation marks in its displayed formula; literal text in this tutorial is correctly quoted.

This is a first-code-point control, not a claim about every emoji sequence. Skin-tone modifiers, joined emoji and other multi-code-point constructions require separate inspection. A displayed picture can involve more than the one value returned by UNICODE.

Advanced example: locate a troublesome separator

Place ="Unit"&UNICHAR(160)&"B" in A2. In A3 place ="Unit B". The separator after Unit may look identical.

=UNICODE(MID(A2,5,1))
=UNICODE(MID(A3,5,1))

The expected outputs are 160 and 32. The first is a nonbreaking space and the second an ordinary space. To replace the known nonbreaking space, use =SUBSTITUTE(A2,UNICHAR(160)," "); inspecting its fifth character then gives 32.

Do not substitute blindly across an entire workbook before identifying the difference. A nonbreaking space may be intentional, and other invisible characters need their own explicit policies.

Advanced example: audit a short identifier position by position

Put B-2 in D2 and the positions 1, 2 and 3 in E2:E4. In F2 enter and fill down:

=UNICODE(MID($D$2,E2,1))

The result vector is 66, 45 and 50. Reconstructing these with =UNICHAR(F2)&UNICHAR(F3)&UNICHAR(F4) returns B-2. This simple ASCII fixture gives an unambiguous position map without assumptions about complex grapheme boundaries.

A visually similar dash is not necessarily code point 45. If a copied identifier contains another character at position 2, inspect that actual code point before deciding how to normalize it.

Composed and decomposed accents

Create G2 as =UNICHAR(233) and G3 as =UNICHAR(101)&UNICHAR(769). UNICODE returns 233 for G2 and 101 for G3. The strings may look similar, but the first stored character differs.

This diagnostic does not apply Unicode normalization or decide which spelling is appropriate. It only reveals a specific difference. Preserve raw text and use a separately defined normalization process if a data interchange requires one.

UNICHAR performs the inverse single-code-point construction, MID supports the simple-position examples and EXACT compares complete strings with case and hidden characters included. UNICODE is not a replacement for a whole-string equality test. Empty-string errors and numeric formatting outside the small-integer controls remain unverified.

References and verification

Examples use fictional data, English function names and comma separators. Expected outputs are independent mathematical calculations or explicitly documented rules, not native Sheets captures. Check the spreadsheet locale when reproducing punctuation-sensitive formulas.