TYPE Function in Zoho Sheet: Numeric Type Codes 1, 2, 4, 16, 64 and 128

=TYPE(value)

value is the single required argument, which may be a literal, an expression or a cell reference. The public article does not describe optional flags, keyword overrides or any default when the argument is omitted. It returns one of the numeric category codes below; don’t expect it to return strings such as "number" or "array". Zoho TYPE Help.

The last row is deliberately not turned into a fabricated demonstration: Zoho’s source does not specify an ordinary reproducible value of type 128. Likewise, not every way of producing an array or an error has been separately verified; the vendor’s documented literal-array expression is the most reliable example.

Enter these expressions into separate blank cells in Zoho Sheet. Vendor examples are labelled; other expected values are independently reasoned from the vendor’s table.

The first three rows reproduce the formulas and expected codes printed by Zoho. The remaining rows are independent deductions from the function’s category definitions—not native test logs.

Build a real input table

Add =TYPE(A2) into B2, and copy down to B5. For A5, entering just 18 into a general-format cell may result in a number; to create text deliberately, use a formula in A5 such as ="18" and then check its result. This input distinction is central: TYPE identifies a value type, not what the digits seem to mean to a person. If your locale automatically changes quoted digit strings into numeric values during import, verify their actual type before interpreting the output.

Identify an actual error-typed input

The official TYPE table says errors receive code 16, but does not include a working nested-error example. For a native test proposal, enter =NA() in A7 and then =TYPE(A7) in B7. The independently expected code is 16 based on the documented rule; however, the particular cell-reference/error-propagation interaction remains NOT NATIVE TESTED. Do not claim this as an observed result until checked in Zoho.

1. Conditional import validation

When importing vendor price data, one column can display =TYPE(A2) as a diagnostic flag. If the code is 2, a price-looking entry may actually be text; if it is 1, it is numerically typed. This lets you keep the raw value untouched while a separate review process decides whether text-to-number conversion is appropriate. Type alone does not establish that a numeric value is within range, correctly converted from currency, or safe to aggregate.

2. Map numeric codes to readable labels

In a companion cell, =IF(TYPE(A2)=2;"Text — check input";"Other type") is a useful illustrative condition. It distinguishes one documented type without making assumptions about all remaining codes. For production, expand the mapping only after testing errors, array behavior and the returned 128 category in your account; a simple IF chain without testing can hide unknown types. The computed label is an expected result from the classifier semantics, not evidence of live execution.

3. Keep the distinctions among related functions

TYPE identifies six broad classes, while ISNUMBER checks a numeric or logical value according to Zoho’s own definition, ISLOGICAL checks genuine TRUE/FALSE, and ISTEXT checks text. Thus a Zoho-specific rule can surprise users trained on another spreadsheet: ISNUMBER’s published description includes logical values, even though TYPE classifies Booleans with a separate code 4. Both statements can hold because functions implement different tests; do not assume TYPE=1 is literally equivalent to Zoho ISNUMBER in all cases.

4. Distinguish TYPE from CELL("TYPE")

=CELL("TYPE";A2) returns a letter category for referenced cell contents: b, l, or v in Zoho’s documentation. =TYPE(A2) uses numeric codes 1/2/4/16/64/128. When you build an audit report, give these columns different headers (e.g. “CELL class” and “Value type”) so analysts do not compare fundamentally different code systems. Use CELL when you need address/format metadata too; use TYPE for the kind of an input.

5. Difference from ERRORTYPE

Zoho’s ERRORTYPE(reference) returns specific numeric identifiers for individual spreadsheet errors (for example, 7 for #N/A! and 2 for divide-by-zero) and can itself give #N/A! when the referenced cell is not an error. TYPE’s 16 is the broad class, not a substitute for diagnosing which error occurred. If you want to distinguish a missing lookup from a broken reference, a classifier alone is not enough.

• #NAME!: Check that you typed TYPE, quoted text such as "Zoho", and used the correct formula prefix and delimiter.
• #VALUE!: Zoho’s general error list includes wrong data types; the TYPE function article does not specify a complete error matrix for unsupported argument structures.
• #REF!: A missing or deleted cell reference should be fixed at the source. Do not reinterpret an invalid reference as a legitimate ordinary value.
• Error propagation: The help lists error code 16 without detailing the evaluation order for every nested formula; TYPE(NA()) should be verified in a real Zoho workbook.
• Empty cell versus empty string: The page does not state whether these map to 1, 2, or 128 in all circumstances. Do not infer their classifications from Excel behavior.
• Arrays and range values: The documented example TYPE({4,3,2}) gives 64. It does not by itself establish how all dynamically generated ranges and arrays interact with a scalar TYPE formula.
• Other category 128: No sample input is documented in the article; keep 128 in the table but don’t manufacture a representative input and expected outcome.
• Locale/dates: Numbers formatted as dates can have engine-specific representations. The public TYPE page does not provide date handling details; use a native date-value test.

Does TYPE turn text into a number? No, it returns a code describing a value; the original value remains unchanged.

Are quoted numbers numeric? A quoted literal is text for the type-classification rule. The deliberate distinction is helpful when auditing imported numeric-looking strings.

Why are there two different error-related numbers? TYPE’s 16 means the input belongs to the error class. ERRORTYPE returns a specific error’s numerical identifier.

Why is TRUE not classified as number 1? Zoho lists Booleans separately as TYPE=4, even though its ISNUMBER documentation mentions logical values. Different tests answer different questions.

Is code 128 safe to rely on? It is a documented code, but without an official reproducible input example or native testing this guide cannot promise when it appears.

• Zoho Sheet: TYPE — exact numeric type codes, syntax, official array/text/Boolean examples (2026-10-13).
• Zoho Sheet: CELL — distinct letter-coded content classifier (2026-10-13).
• Zoho Sheet: ERRORTYPE — specific spreadsheet error identifiers (2026-10-13).
• Zoho Sheet: ISLOGICAL, ISNUMBER and ISTEXT — related type predicates; no claim of equivalence (2026-10-13).

The linked function page is in Zoho’s public, English-language Zoho Sheet knowledge base, which documents the function in the current cloud spreadsheet product. It does not provide an official first-supported release number, a paid-plan minimum, or a tested matrix for Android, iOS, desktop beta, offline mode, and imported Excel/Google files. Therefore none is asserted here. Test the formulas in your actual account and platform before a production migration.

For arguments separated by semicolons, the syntax in this guide follows the English Zoho Help examples. Zoho provides per-user/spreadsheet locale and language preferences. If your account displays different function names or separators, choose them using that environment’s formula help/autocomplete rather than copying punctuation blindly. Numeric examples with no separator should generally be the easiest to verify.

Compatibility evidence: These pages establish Zoho-documented functionality only. Similar names in Excel, Google Sheets or LibreOffice are not evidence of identical coercion, errors, blank-cell treatment, array semantics, imported-formula translation, or formatting behavior. The differences that matter for this function are discussed above; otherwise, migration parity remains not independently validated.

• Documentation research: individual Zoho function Help checked 2026-10-13; related links verified against Zoho’s official Help listings and article pages.
• Expected answers: arithmetic/type rules reasoned independently, not copied from another spreadsheet’s execution. Vendor-given examples are identified.
• Native Zoho execution: NOT RUN. No account was connected; cloud, mobile and desktop behavior were not tested.
• Testing priority: paste each one-cell example, compare displayed results, then repeat on your target locale; test any cautioned blank/error/array cases separately.