Zoho Sheet HEX2DEC Function: Hexadecimal to Decimal with Examples
Convert hexadecimal values to decimal in Zoho Sheet with exact datasets, place-value checks, documented limits and practical examples.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
HEX2DEC converts a hexadecimal representation into decimal. For the positive integer 42, the source numeral is 2A and the converted result is 42. The base changes; the represented quantity does not. The decimal result is useful for arithmetic on values supplied in another base.
Syntax and availability
HEX2DEC(hexadecimal_number)
Zoho’s official HEX2DEC entry was checked on October 15, 2026. It describes the rolling web service. The first supported release and last functioning version are unknown; current documentation is separate from those historical endpoints. Mobile/offline parity is unverified. Results below are independent integer calculations, not native Zoho execution.
The required source contains at most ten characters, using only 0–9 and A–F. Hexadecimal input is documented as case-insensitive: A and a have the same meaning. Quote literal hexadecimal strings, for example “FF”. The checked entry does not fully specify signed interpretation of maximum-width values; these examples use small positive values and make no unsigned or two’s-complement promise at that boundary.
There is no output-width argument. Leading zeroes used only for a source identifier’s layout are not preserved by conversion to a decimal quantity. Keep the original input when its exact written form matters.
Visible official control
Zoho explicitly gives =HEX2DEC("FF") with result 255. This provides a compact starting control before working with cell references. Other vendor examples refer to cells whose inputs are not visible in the extracted help; the complete worksheet below supplies its own inputs rather than inventing those hidden cells.
Complete reproducible worksheet
Create Conversions with Source in A1, Decimal_check in B1, Converted in C1. Enter the following values in A2:B7. Set column A to text before entering hexadecimal strings so digit-looking codes remain source text; do not include the display quotes in the cell contents. Column B is an independent explanatory value, not an argument to the conversion formula.
| Row | A: source | B: decimal check | C: expected |
|---|---|---|---|
| 2 | 1 | 1 | 1 |
| 3 | 7 | 7 | 7 |
| 4 | F | 15 | 15 |
| 5 | 2A | 42 | 42 |
| 6 | 3F | 63 | 63 |
| 7 | FF | 255 | 255 |
Enter C2 =HEX2DEC(A2) and fill through C7.
In a copy change A5 from 2A to 2B and update its explanatory B5 to 43. C5 becomes 43. Other records remain unchanged. This gives a one-unit sensitivity check with a fully specified input.
Advanced: combine two explicitly ordered bytes
Put the text values 12 and A5 in G2 and H2, representing a high byte and a low byte. In I2 use =HEX2DEC(G2)*256+HEX2DEC(H2). The expected result is 4773, because 18×256+165=4773.
If the source specification instead says the first byte is the low byte, use =HEX2DEC(H2)*256+HEX2DEC(G2). That gives 42258. Both computations are mathematically valid, but they describe different byte orders. HEX2DEC does not discover the order for you.
The separate control =HEX2DEC("12A5") also has expected result 4773: 1×4096+2×256+10×16+5. In a copy change H2 from A5 to A6. The high-byte-first result increases to 4774; the reversed-order result increases to 42514, a step of 256. This sensitivity check is useful when reviewing a device export before aggregation. Check the device’s actual format and avoid assuming that a ten-character word is unsigned.
Errors and troubleshooting
The official entry identifies invalid source digits as #NUM!. Thus HEX2DEC("G") is an invalid-digit control. Respect the ten-character input contract; the checked page does not separately establish an exact error token for every overlength, signed or malformed value.
The shared help glossary mentions name, type and reference errors without defining a complete coercion matrix for this function. Check the source base, legal characters, cell type and literal quotation before investigating more complex formulas. Do not add 0x, 0b or other programming-language prefixes unless a product reference explicitly permits them.
Keep conversion and arithmetic separate. A nondecimal display can look like a decimal number, yet ordinary subtraction on that display need not measure the intended change. Preserve raw identifiers, document the source’s sign and width convention, and verify exported leading zeroes in the receiving system. Matching function names across spreadsheet products do not establish identical limits or behavior.