BIN2HEX in Collabora Office: Translate Binary Fields into Padded Hexadecimal Text
Convert binary strings to hexadecimal in Collabora Calc, preserve explicit field widths and distinguish grouped bits from decimal arithmetic.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
Quick answer: BIN2HEX returns hexadecimal text for a binary string. Use an explicit output width when padding matters: =BIN2HEX("101010";4) has independently expected text 002A.
Availability and version history
- Introduced: the original Collabora release and launch date are not established by the reviewed sources.
- Availability: documented in Collabora Office 26.04 desktop help.
- Platform scope: online and mobile deployment support is not inferred from the desktop documentation.
- Checked: October 14, 2026. Function-specific documentation and independent controls; no native Collabora execution.
Syntax and documented limits
=BIN2HEX(Number [; Places])
Number is a binary string of at most ten bits. The source documents a sign bit and two’s-complement input for negative values. Places is the number of output positions and is optional in the signature.
The short reference does not state the omitted Places default, fractional-Places handling or a complete output-width/error policy. All positive examples below supply a sufficient integer width. Negative-input output length and padding interactions remain unverified rather than being imported from another spreadsheet.
Hexadecimal digits 0–9 represent their ordinary values; A–F represent 10–15. Four binary positions fit into one hex digit. Leading zeros pad a representation without changing its numeric value.
Example 1: translate a small binary column
Format A2:A6 as Text before entering these strings. In B2 use =BIN2HEX(A2;2) and fill through B6.
| A, binary string | Expected two-character hex text | Decimal check |
|---|---|---|
| 1 | 01 | 1 |
| 1010 | 0A | 10 |
| 101010 | 2A | 42 |
| 11110000 | F0 | 240 |
| 11111111 | FF | 255 |
The decimal-check column is explanatory. To calculate it independently, put =BIN2DEC(A2) in C2 and fill down. The last row is an eight-bit positive value; the input function’s negative convention applies to its full ten-bit format.
For 101010, left-pad conceptually to 0010 1010. The groups represent 2 and A, giving 2A. This is grouping by four bits, not reading the digits “101010” as a decimal integer.
Example 2: preserve a specified output width
Evaluate the following in separate cells:
=BIN2HEX("101010";2)
=BIN2HEX("101010";4)
=BIN2HEX("101010";6)
Expected text is 2A, 002A and 00002A. The quantity is always 42. The extra zeros satisfy different representation widths; they do not create larger values or extra significant bits.
The official source supplies a directly comparable control: =BIN2HEX("1100100";6) returns 000064. Binary 1100100 is decimal 100, and 6×16+4=100 confirms the hex value.
Advanced example: separate fields before translating
An eight-character import defines two four-bit fields. Put 11010010 in E2. Convert each field separately:
=BIN2HEX(LEFT(E2;4);1)
=BIN2HEX(RIGHT(E2;4);1)
Expected text is D and 2. The complete conversion =BIN2HEX(E2;2) gives D2. Its decimal value is 13×16+2=210.
This works because the specified boundaries align with four-bit hex digits. If the file used a three-bit first field, copying the same LEFT/RIGHT lengths would change its meaning. Define the record layout before choosing a display conversion.
Advanced check: compare quantities through a common decoder
For the first table, enter =HEX2DEC(B2) in D2 and fill through D6. The results should equal the independently calculated C2:C6 values: 1, 10, 42, 240 and 255. HEX2DEC supplies the reverse numeric interpretation.
A comparison =C2=D2 therefore has modeled result TRUE for every row. That checks the chosen examples and their layout; it is not a native application certification or validation of arbitrary strings.
Scope and common mistakes
BIN2HEX produces text. Keep a separate decoded numeric column when totals, numeric comparisons or distances matter. Hex labels such as 10 and F have numeric values 16 and 15; ordinary text ordering need not follow that order.
Do not silently exceed the ten-bit input contract. Input 1111111111 is in the signed region, whereas 11111111 is the positive quantity 255. This guide deliberately leaves the negative output-width rule open because the specific section does not explain it.
Invalid digits, too-small Places, omitted padding and exact error codes remain unverified. BIN2DEC explains the input’s signed interpretation; HEX2BIN handles the opposite direction under its own documented scope.
References and verification
Complete function-specific documentation reviewed. Outputs are independently calculated positional models or explicitly documented controls, not captured native application results. Formulas use English names and semicolon separators; optional-argument brackets describe syntax and are not typed into a working formula.