Contact

ROUNDSIG Function (LibreOffice Calc)

Math Beginner LibreOffice Calc

Learn the ROUNDSIG function in LibreOffice Calc: Rounds a number to predefined significant digits.

Verification status: Official documentation referenced; example outcomes independently reasoned or arithmetically checked where stated. Not executed in LibreOffice Calc. How formula examples are checked

Validation scope: Native observations below refer to saved LibreOffice Calc 25.2.3.2 Linux evidence dated 13 October 2026 at 06:04 UTC. This later review checked artifact hashes and all 79 ODS/result pairs, recomputed 47 numerical cases, and separately checked the two tiny subtraction residuals with a relative-only tolerance. Calc was not rerun. Current Help and saved version-specific diagnostics remain distinct.

ROUNDSIG rounds a numeric value to a chosen number of significant decimal digits. It is useful when the number of meaningful digits matters more than the number of places after a decimal point: laboratory measurements, scientific notation, engineering estimates, summary reports, and figures with very different magnitudes.

Quick answer: =ROUNDSIG(123.456789;5) returns 123.46, while =ROUNDSIG(0.000123456789;5) returns 0.00012346. Both results contain five significant digits even though one is greater than 100 and the other is much smaller than 1.

Syntax and arguments

=ROUNDSIG(Value; Digits)
Argument Required? What it does Example
Value Yes Numeric expression or a cell containing the quantity to round. Can be positive, negative, or zero. A2, 123.456789
Digits Yes Number of significant decimal digits in the result. Official Help requires a positive integer. 3, B2

There are exactly two required arguments, without optional defaults. Digits=3 does not mean three digits after the decimal point. The ; separating arguments follows the English-language Calc formulas documented by LibreOffice Help; localized settings may change separators, names, number formats, or decimal punctuation. For portable sharing, check the recipient’s application and locale rather than assuming semicolons and decimal points will paste unchanged.

The precise official formulation and the requirement that Digits be a positive integer are from LibreOffice Calc Help: ROUNDSIG, checked 2026-10-13.

Try it immediately

Enter the following numbers as numbers, not as quoted text. The formulas can be placed in column C.

Cell Enter Example formula in C Native-verified result
A2 123.456789 =ROUNDSIG(A2;5) 123.46
A3 0.000123456789 =ROUNDSIG(A3;5) 0.00012346
A4 123456789 =ROUNDSIG(A4;4) 123500000
A5 1005 =ROUNDSIG(A5;3) 1010
A6 -1234.567 =ROUNDSIG(A6;3) -1230
A7 0 =ROUNDSIG(A7;4) 0

Each underlying literal equivalent was executed with Calc 25.2.3.2. Cell-reference variants use the same documented argument form; the independent assertion set was built primarily from numeric literals, so the table’s cell-based instructions should not be mistaken for additional separately counted native assertions. A returned numerical 123500000 could display as 1.235E+08 when the cell uses a scientific-number format. Formatting is not a change in the calculated value.

What ‘significant’ means

For an ordinary nonzero decimal number, count from its first nonzero digit and then count subsequent digits. Leading zeros merely locate the decimal point; they are not counted. Zeros between meaningful digits do occupy positions. For example, 0.000123456789 has first significant digit 1, not the zeros before it. To retain five significant digits, ROUNDSIG uses the sequence 1,2,3,4,5 and looks at the next digit when rounding.

This differs from ROUND, which counts decimal places relative to the decimal separator. For instance, =ROUNDSIG(123.456789;3) rounds to approximately 123, while =ROUND(123.456789;3) would target three digits after the decimal point instead. The latter comparison is the mathematical distinction specified by the functions; this batch did not include an independent native assertion for the ROUND expression.

Input and requested precision Formula Native-verified value Why
Four digits in a large integer =ROUNDSIG(123456789;4) 123500000 The fifth digit causes the fourth to round up.
Two digits in a 15-digit number =ROUNDSIG(123456789012345;2) 120000000000000 Scientific display may show 1.2E14.
Two digits, negative fraction =ROUNDSIG(-0.004567;2) -0.0046 Initial zeros are not significant.
Three digits, carry into next order =ROUNDSIG(999.99;3) 1000 Rounding crosses the thousand boundary.
Three digits, tiny carry =ROUNDSIG(0.00099999;3) 0.001 Carry changes the exponent/order of magnitude.
Many digits requested =ROUNDSIG(12345.67;7) 12345.67 No additional mathematical precision is invented.

Important: Excel-style or scientific textual formatting such as displaying 120000000000000 as 1.2E14 is a display decision. It does not prove that trailing zeros are measured, verified, or physically meaningful. If laboratory precision must be communicated with explicit trailing zeros, carefully select a number format or use a string representation, documenting that such formatting is presentation only.

How Calc decides where to round

A conceptual way to understand the operation for finite, nonzero x and positive integer n is:

  1. Find the power of ten of the first significant digit: k = FLOOR(LOG10(ABS(x))).
  2. The intended decimal rounding-place index is n - 1 - k.
  3. Round x to that many places, including negative place counts for hundreds, thousands, and so on.

For example, 12345.67 begins at 10^4. Keeping three significant digits corresponds to rounding at the hundreds place, producing 12300. For 0.0098765, its first significant digit is at 10^-3: keeping two digits rounds at the fourth decimal place, producing 0.0099.

A conceptual comparison, for nonzero values in a suitable ordinary numeric range, is:

=ROUND(A2;B2-1-INT(LOG10(ABS(A2))))

That is an explanatory, not natively tested in this batch, expression. Use IF(A2=0;0;...) to guard LOG10(0) if adapting it. Rounding behavior at extreme magnitudes, midway values, and floating-point boundaries can differ from a built-in function; test the specific workbook. There is no need to replace native ROUNDSIG with this longer formula in Calc.

Worked measurement report

Imagine readings in millimetres arrive at very different sizes. Place the unrounded values in column B and the number of requested significant figures in column C. In D2 use:

=ROUNDSIG(B2;C2)

Copy down only after confirming that every C value is a positive integer. For a constant report rule, use =ROUNDSIG(B2;3) instead. Examples from the native numerical fixture:

Measured value Significant digits Rounded numerical value Interpretation
1005 3 1010 Four-digit reading rounded to three significant digits.
0.009875 2 0.0099 Small magnitudes handled without manually counting zeros.
-0.00000004237 3 -0.0000000424 A negative measurement retains its sign.
234.56789 3 235 Standard magnitude with an upward last-digit decision.
7.0001E-7 4 7E-7 At tested binary-float precision, trailing information was dropped.

Practical caution: apply significant-figure rounding at a defined reporting boundary, not repeatedly inside every intermediate calculation, because rounding at each stage can compound errors. Keep raw observations in one column and derived display/report values in another. This is a workflow recommendation, not a guarantee of metrological uncertainty compliance.

Rounding midway values and negative values

Midway examples can distinguish rounding conventions. In Calc 25.2.3.2 native tests, =ROUNDSIG(2.5;1) returned 3, and =ROUNDSIG(-2.5;1) returned -3; =ROUNDSIG(1005;3) returned 1010, with the negative counterpart yielding -1010. These observations are version-specific. The official ROUNDSIG page describes significant-digit rounding, but does not provide an exhaustive specification of every binary-float tie case. Do not infer behavior for all versions or for values whose entered decimal representation is not exactly representable in binary.

Advanced uses

1. Scientific and engineering notation

Instead of estimating the number of decimal places for each row, use ROUNDSIG to put measurements on a comparable precision scale. =ROUNDSIG(123456789012345;2) returned 120000000000000 in the tested Calc; a scientific display format can represent it as 1.2E14. The displayed exponent does not change the underlying stored number.

2. Precision controlled by a data column

Store validated integer precision settings in C2:C100. Use =ROUNDSIG(B2;C2), and apply data validation (whole numbers greater than zero) to the settings column. This avoids scattered hard-coded rounding rules when different measurements need different reporting precision.

3. Comparing an original calculation with its published figure

Keep B2 as the full-precision computation; put =ROUNDSIG(B2;3) into C2. When auditing, report both so differences caused by presentation rounding remain visible. In a financial or billing workflow, use the legally or contractually required decimal/monetary rounding rule instead of casually substituting significant figures.

4. Guard against invalid precision settings

A defensive pattern for nonnumeric or invalid settings is conceptually:

=IF(ISNUMBER(C2);IF(AND(C2>=1;C2=INT(C2));ROUNDSIG(B2;C2);"Check Digits");"Check Digits")

This formula has not been separately executed in this batch, so treat it as an adaptation example rather than a native-verified output. It expects numeric B2. The outer IF rejects nonnumeric C2 before evaluating INT; upstream errors and the value being rounded still need their own validation. INT and logical functions may be localized or use different separators depending on locale.

Error handling and troubleshooting

Symptom Cause or tested observation What to do
Err:502 with zero digits =ROUNDSIG(123.45;0) produced Calc error code 502. Use an integer greater than zero.
Err:502 with negative digits =ROUNDSIG(123.45;-2) produced the same error. Use a valid positive count.
Err:511 =ROUNDSIG(123.45) and =ROUNDSIG() lacked required arguments. Supply both arguments.
#VALUE! on nonnumeric literal =ROUNDSIG("abc";2) returned a value error (native error code 519). Convert/clean imported text; do not silently substitute guessed numeric values.
Precision appears ignored =ROUNDSIG(12345.67;7) leaves the number unchanged. You requested at least as many significant digits as are visible in the input.
Rounded result shows many zeros =ROUNDSIG(123456789;4) produces 123500000. Check the cell’s number format and exponent display.
Tiny number rounds to apparent zero Decimal display precision may hide a small nonzero calculated value. Switch to a scientific or higher-precision display format and inspect the formula bar.
Wrong separator / parse error Different locales can use different list and decimal separators. Follow the Formula Wizard or your installation’s function assistant.
Unexpected result near a precision boundary Spreadsheet numbers typically use finite binary floating-point precision. Audit entered source values; avoid inferring exact decimal representation from printed digits.

Documentation-versus-execution nuance: LibreOffice 26.8 Help states that Digits must be an integer greater than zero. However, the 25.2.3.2 native diagnostic =ROUNDSIG(123.45;1.5) returned 100, rather than an error. Similarly, numeric-looking string digits and TRUE() were coerced in that build. These are observations, not supported usage recommendations; they do not override the documented requirement. Enter clean positive integers for predictable files.

Zero, large magnitudes, and practical limits

In native tests =ROUNDSIG(0;4) returned 0; no logarithm guard is needed for the built-in function. Very small =ROUNDSIG(1E-300;2) returned 1E-300 in the observed Calc build. =ROUNDSIG(9.99999999999999E99;3) returned approximately 1E+100 after rounding. These observations do not establish support for unlimited exponent size or arbitrary decimal precision: Calc stores numerical values within implementation limits. Requesting many significant digits cannot recover information absent from the input’s stored floating-point value.

Compatibility, origin, and platform scope

According to LibreOffice’s official ROUNDSIG Help checked 2026-10-13, this function has been available since LibreOffice 5.4. The same page states that it was not included in OpenDocument OpenFormula 1.3 and identifies its extension namespace as ORG.LIBREOFFICE.ROUNDSIG. That namespace matters when exchanging formula-containing files: availability in the LibreOffice engine is not a guarantee that another program will parse, retain, or recalculate the same expression.

Target Evidence / action
LibreOffice Calc 25.2.3.2, Linux Native execution verified with 25 successful numerical assertions and 12 separately recorded diagnostics.
LibreOffice versions from 5.4 Official documentation claim, not a full matrix of versions tested here.
Current online 26.8 Help Documentation read on 13 October 2026; 26.8 engine not executed.
Microsoft Excel Not natively tested. Do not assume the LibreOffice extension name is accepted. Consider a carefully validated numeric expression using broadly supported functions if portability is required.
Google Sheets Not natively tested. Do not assume the LibreOffice extension name is accepted. Adapt and verify any replacement.
Windows / macOS LibreOffice builds Not executed here; no operating-system-specific behavior was measured.
OpenFormula 1.3 exchange Official Help identifies this as an extension, not a standard OpenFormula 1.3 function.

Source and verification notes (checked 13 October 2026)

  1. Official function definition, syntax, four official examples, 5.4 introduction, extension namespace, ODF 1.3 exclusion: LibreOffice 26.8 Help — ROUNDSIG. Retrieved/reviewed 2026-10-13.
  2. Reproducible numerical and diagnostic cases: saved dated results, ODS and calculation script. Formula engine: LibreOffice Calc 25.2.3.2 Linux, executed through UNO on 2026-10-13. Numeric assertions based on independently calculated Decimal significant-figure rounding; actual Calc values recorded separately.