OCT2HEX Function in ONLYOFFICE Spreadsheet Editor: Syntax and Worked Examples

Convert Octal Strings to Hexadecimal. Three octal digits can represent a byte: octal 377 becomes hexadecimal FF. Their characters differ because the base is different, not because the underlying value changed. The exact English-reference syntax is =OCT2HEX(number, [places]), documented by the official ONLYOFFICE OCT2HEX function article (checked 2026-10-13 UTC). Octal 377 = 255 decimal = hexadecimal FF; requesting five places produces 000FF as an independent mathematical expectation.

Verification: Results are independently calculated mathematical expectations. Native ONLYOFFICE Docs web or Desktop execution, localized parsing and runtime error capture were not performed.

OCT2HEX expresses the same integer in hexadecimal rather than octal. This can be useful when translating legacy octal configuration values to modern hex-oriented technical documentation or validating a base-conversion pipeline.

What the notation means

• Decimal/base 10: each digit’s value is weighted by powers of 10.
• Octal/base 8: valid digits are 0–7, weighted by powers of 8.
• Hexadecimal/base 16: digits are 0–9 and letters A–F (A=10 through F=15), weighted by powers of 16.
• A base conversion preserves the integer. Zero padding with places (when supported) changes the output’s character count, not the represented quantity.

For a cell containing an octal or hexadecimal identifier, format it as Text before typing any leading zeros. Literal strings in the formulas are wrapped in double quotation marks, e.g. "377" rather than a bare number assumed to be octal. The underlying reference does not exhaustively specify every numeric-to-text coercion; check the stored cell type when recreating this worksheet.

=OCT2HEX(number, [places])

The square brackets around places (when present) mean optional, not literal square brackets to enter in the cell. The vendor reference orders the arguments exactly as printed above; swapping them changes the meaning. See the vendor’s documented syntax and notes.

1. In a new, otherwise empty worksheet, enter Scenario in A1 and Octal source (Text) in B1. Enter Places in C1, Minimum output in D1 and Padded output in E1.
2. Format column B as Text before filling it; this preserves base digits and leading zeros. For reproducibility, enter the B-column source values from the rows below without the article’s backtick punctuation.
3. Enter 5 as the numeric Places setting in C2:C21. Put =OCT2HEX(B2) into D2, and =OCT2HEX(B2,C2) into E2; copy each formula down to row 21.
4. Compare the spreadsheet outputs to the independent expectations. If your installation differs, note the software edition and version, formula language, region, source cell type and entered formula. An expected result is not a claimed live test.
5. Save the workbook with its sample values so a reviewer can repeat the comparison. To inspect a hidden leading zero, click the source cell and check the formula bar as well as the displayed cell.

Input and expected-output worksheet

Independent calculation method: Parse the input numeral in its stated source radix using exact integer arithmetic, then format that same integer in the destination radix. For the fixed-width column, left-pad the resulting string with the digit 0 to the requested width. These computations were checked with a separate Python integer conversion routine. That routine is not an ONLYOFFICE interpreter; outputs and text handling must still be verified in an installed editor.

Direct formulas to paste in an empty cell

Reproducibility note: Quoted numeral literals keep the source notation intact. Results that look like text codes should not be coerced to ordinary decimals when copied into another program. To preserve fixed-width output, ensure destination cells have appropriate formatting before downstream use; the exact returned cell type is a native-test question.

1. Translate an octal byte

OCT2HEX expresses the same integer in hexadecimal rather than octal. For this application enter =OCT2HEX("377"); the independently expected result is FF. 377 octal = 255 decimal = FF hexadecimal.

2. Legacy permissions label

OCT2HEX expresses the same integer in hexadecimal rather than octal. For this application enter =OCT2HEX("755"); the independently expected result is 1ED. 755 octal = 493 decimal = 1ED hexadecimal. A numeric conversion does not decode the meaning of permission bits.

3. Nibble boundary

OCT2HEX expresses the same integer in hexadecimal rather than octal. For this application enter =OCT2HEX("20"); the independently expected result is 10. 20 octal = 16 decimal = 10 hexadecimal.

4. Maximum 16-bit positive label

OCT2HEX expresses the same integer in hexadecimal rather than octal. For this application enter =OCT2HEX("177777"); the independently expected result is FFFF. 177777 octal = 65535 decimal = FFFF hexadecimal, a four-hex-digit magnitude.

5. Cross-base confirmation without rounding

=OCT2HEX(DEC2OCT(255)) → FF; =OCT2HEX("377",5) → 000FF (mathematical expected values). These are independent compositions of documented functions, not formulas executed in ONLYOFFICE. Round-tripping is an excellent future desktop/web test, because it simultaneously probes coercion, function availability, and output text formatting. It is not evidence of behavior in any particular version.

6. Formula portability and identifiers

If using OCT2HEX for imported device codes, keep the original string and the converted string in separate columns. Add another column with the original base (8, 10 or 16) so downstream consumers do not interpret octal 377 as decimal 377. Retain the raw source when leading zeros or digit count carry meaning outside mathematics (for instance, a fixed-width external identifier).

Only the rules explicitly attributed to the official OCT2HEX article are treated as vendor-established; the following error cases were not triggered in an actual ONLYOFFICE editor.

Source-rule summary

• The vendor documents #NUM! if the octal input is not recognized.
• The vendor documents #NUM! if the source contains more than 10 characters.
• The vendor documents #NUM! if places is too small to fit the converted hexadecimal output.
• The vendor documents #NUM! if places is less than or equal to zero.

Do not assume an outcome without checking the actual installed edition

• The reference does not give a full signed-input and two’s-complement model for ten-digit octal numbers. Do not treat other spreadsheet programs as ONLYOFFICE evidence.
• The exact output type, letter-case display, whitespace normalization, and noninteger width processing should be verified natively.

Practical troubleshooting sequence

1. Verify the function name and argument count exactly against the official page. A one-argument-only function cannot take a width parameter.
2. Verify the input base: octal uses 0–7; hexadecimal uses 0–9 and A–F; decimal is base 10. An apparently numeric cell might not contain the intended numeral representation.
3. If a leading zero matters, change the source cell to Text before re-entering the value. Verify the formula bar retains it.
4. If the function has places, first omit it to establish the shortest expected output mathematically; then enter a positive integer large enough for that output. A width counts characters, not bits or decimal places.
5. For an unexpected error, record the exact formula, source type, locale and app version; inspect the vendor’s documented error rules before attributing it to a specific behavior.
6. If passing values between multiple conversion functions, inspect whether the intermediate result is textual or numeric in that exact editor. Do not conclude success merely because formatting makes a number look plausible.

Cases requiring native compatibility checks

• =OCT2HEX("7777777777") (signed ten-digit convention is unspecified by the checked page).
• =OCT2HEX(" 377 ") (whitespace behavior not established).
• =OCT2HEX("377",1.5) (noninteger places behavior not established).
• =OCT2HEX("0000000377") (leading zeros make ten characters; inspect the target edition).

This is documentation-based research for ONLYOFFICE Spreadsheet Editor, not a general Excel guide. The current function catalogue lists the function under Engineering; the English Insert Functions instructions show formulas beginning with = and (in their example grammar) comma-separated arguments. The ONLYOFFICE Advanced Settings help documents selectable formula languages and regional options. In other language/region setups, verify the localized function label, argument separator and decimal settings in the editor before pasting the English formula; no localized syntax was executed here.

Docs web vs Desktop Editors: ONLYOFFICE maintains Docs release notes separately from Desktop Editors release notes. The functions’ current online help is an unversioned reference, not a support matrix. Docs 10.0.0 is listed in its changelog dated 2026-10-10, while the Desktop changelog reviewed on 2026-10-13 has a separate version history. Neither checked changelog establishes a first-supported version for this specific base-conversion function. Accordingly, treat older Desktop, web installations and external file imports as not natively verified. No native execution, screenshot, runtime error capture, or edition-to-edition compatibility testing was performed for this manuscript.

The following links lead to official vendor references checked on 2026-10-13 UTC.

• OCT2DEC — ONLYOFFICE official reference — compare alternative input/output bases and formula argument order.
• HEX2OCT — ONLYOFFICE official reference — compare alternative input/output bases and formula argument order.
• HEX2DEC — ONLYOFFICE official reference — compare alternative input/output bases and formula argument order.
• ONLYOFFICE Insert Functions catalogue and English entry instructions — official category and manual formula-entry guidance.
• ONLYOFFICE Advanced Spreadsheet Settings — formula language, region and separator options.
• ONLYOFFICE Docs release history and Desktop Editors release history — separate platform histories, not function-by-function first-release evidence.

For any native compatibility check, record the edition, version, operating system/browser, formula language, region, source-cell type and actual observed output.