Zoho Sheet BIN2OCT Function: Binary to Octal with Examples

BIN2OCT(binary_number; [num_of_digits])

Zoho’s official BIN2OCT 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 and 1. Numeric literals in the examples are digit sequences in the source base, not ordinary decimal quantities. 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.

The second argument chooses the output width. When the representation is shorter, Zoho pads its left side with zeroes; an insufficient width is an error, not permission to cut off significant digits. Use positive integer widths here. Fractional widths, blank inputs and Boolean coercion are not verified.

Square brackets mark an optional argument and are not typed into a formula. Omitting width gives the unpadded representation in the ordinary positive examples. Follow your workbook’s locale separator; these formulas use semicolons.

Zoho explicitly gives =BIN2OCT(1111) with result 17. 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.

Create Conversions with Source in A1, Decimal_check in B1, Converted in C1, and Padded in D1. Enter the following values in A2:B7. Enter the source numerals exactly as shown, without grouping commas or base prefixes. Column B is an independent explanatory value, not an argument to the conversion formula.

Enter C2 =BIN2OCT(A2) and fill through C7. Fill D2 =BIN2OCT(A2;5) through D7. The zeroes in D belong to the representation, not to a larger numeric value.

In a copy change A5 from 101010 to 101011 and update its explanatory B5 to 43. C5 becomes 53 and D5 becomes 00053. Other records remain unchanged. This gives a one-unit sensitivity check with a fully specified input.

Use the supplied nine-bit word 111101001 in G2 and =BIN2OCT(G2;3) in H2. The expected result is 751. Split the input from the right into 111 | 101 | 001; the group values are 7,5,1. Its decimal value is 489, because 7×64+5×8+1=489.

For a hypothetical permission-code report, let each three-bit group represent weights 4,2,1 in a supplied specification. The first group includes all three weights, the second includes 4 and 1, and the third includes only 1. This worksheet merely displays the stated grouping; it does not change a file’s permissions or infer a security policy.

Change G2 to 111101000 in a copy. H2 becomes 750, with decimal value 488. That is a one-unit change even though an octal display is not an ordinary decimal measurement. A width of five produces 00751 for the original input. Retain the original bit sequence when bit positions carry meaning beyond their numeric value.

The documented #NUM! cases include an output that needs more places than the requested width, and width zero or negative. For example, =BIN2OCT(11111111;1) cannot hold 377 in one position. Increasing the width preserves the whole representation; shortening the source value would change the data.

An invalid source digit also produces the documented #NUM! error; BIN2OCT(2) is an invalid-digit control. The official error list also explicitly rejects binary inputs longer than ten characters. Do not remove an error merely to make a report appear complete: retain the raw value and investigate the format or width rule.

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.