This is the last of the ten pillar guides on this site, and it’s the one that explains a question every other page has occasionally sidestepped: why does a calculator, a spreadsheet, or a script sometimes disagree with the rules taught elsewhere on this site? Two separate things are going on, and they get confused constantly. One is floating-point representation error — a genuine limitation of how computers store decimal numbers in binary. The other is which rounding convention a specific tool chose to implement — a design decision, not a bug, and one our rounding guide already showed varies even among the eight standard methods. This page covers both, tool by tool.

<!– BLOCK: B02 – Inline Mini-Calculator –> <!– DEV NOTE: Embed the main Significant Figures Calculator here, with a visible note in the UI: “This calculator uses an arbitrary-precision decimal engine, not native floating-point math — see why below.” Shortcode: [sfc_calculator mode=”mini” show_engine_note=”true”]. –>

[Live Significant Figures Calculator embeds here] — Built on an arbitrary-precision decimal engine specifically to avoid every issue on this page. See Example 1 for why that choice matters.

Two Separate Problems, Constantly Confused

Problem 1: floating-point representation error. Computers store numbers in binary, and most ordinary decimal fractions cannot be represented exactly in binary — only decimals whose fractional part is a finite sum of negative powers of two can (0.5, 0.25, 0.125, 0.75, and combinations of these). Everything else — 0.1, 0.2, 0.3, and the overwhelming majority of decimals anyone actually types — gets stored as the closest available binary approximation, not the exact value. This is why 0.1 + 0.2 famously displays as 0.30000000000000004 in most programming languages: neither 0.1 nor 0.2 was ever exactly 0.1 or 0.2 internally, and the tiny errors compound. This isn’t a flaw in any particular language — it’s inherent to IEEE 754 binary floating point, the format almost universally used to store decimal numbers in software.

Problem 2: different tools implement different rounding conventions, on purpose. Even without any representation error at all, tools genuinely disagree on what to do at an exact halfway tie — this is the same round-half-up vs. round-half-to-even distinction covered generally elsewhere on this site, just made concrete by specific software. Excel rounds ties away from zero. Python and R round ties to the nearest even digit. JavaScript rounds ties toward positive infinity — which, as Example 3 shows, is a third, distinct behavior from both of the others once negative numbers are involved.

The practical fix, and the one this site uses. Neither problem is solved by “being more careful” — it’s solved by not using native binary floating-point math for anything where the exact digit matters. Python’s decimal module, most spreadsheet-adjacent BigDecimal-style libraries, and this site’s own calculators all sidestep both problems by doing arithmetic in exact base-10 decimal instead of binary — which is exactly why the SignificantFiguresCalculator rule on this site requires every numeric tool to use an arbitrary-precision decimal engine rather than a language’s native float type.

Worked Examples

Example 1 — The 0.1 + 0.2 problem, and why it happens

In most languages, evaluating 0.1 + 0.2 returns 0.30000000000000004, not 0.3. Neither 0.1 nor 0.2 exists exactly in binary — each is stored as the nearest representable approximation, off by a tiny amount in the 17th significant digit or so. Adding two such approximations surfaces the error. A sig-fig calculator built on native floating point can silently produce a wrong final digit on results like this; one built on an exact decimal engine never encounters the problem, because it never converts the input to binary in the first place.

Example 2 — Rounding to significant figures in Excel

Excel’s native ROUND() function only rounds to a number of decimal places — it has no built-in “round to N significant figures” mode. The standard workaround combines ROUND() with LOG10() to first find the input’s order of magnitude:

=ROUND(value, sig_figs - 1 - INT(LOG10(ABS(value))))

Rounding 1234.567 to 3 significant figures: LOG10(1234.567) ≈ 3.09, INT(3.09) = 3. Sig figs (3) − 1 − 3 = −1. =ROUND(1234.567, -1) → 1230

Rounding 0.004567 to 2 significant figures: LOG10(0.004567) ≈ −2.34, INT(−2.34) = −3 (INT always rounds toward negative infinity, which is exactly what’s needed here). Sig figs (2) − 1 − (−3) = 4. =ROUND(0.004567, 4) → 0.0046

Both results are correct sig-fig roundings, confirmed independently. This same formula pattern works in Google Sheets without modification.

Example 3 — The same tie, five platforms, three different answers

Rounding 2.5 and −2.5 to the nearest integer:

JavaScript is the outlier. It agrees with Excel on the positive case (3) but disagrees with everything else on the negative case, because it rounds every exact tie toward positive infinity rather than away from zero — matching the precise “round half up” definition from our rounding guide, not the more commonly assumed “away from zero” behavior most developers expect. MDN’s own documentation flags this explicitly as a difference from most other languages’ round() functions.

Example 4 — What R’s own documentation admits about representation error

R’s official manual for round() contains a specific, notable caveat: because 0.15 cannot be represented exactly in binary, round(0.15, 1) could return either 0.1 or 0.2, depending on which binary approximation of 0.15 the system actually stored — the rounding rule applies to the stored value, not the value as printed. This is Problem 1 (representation error) and Problem 2 (rounding convention) colliding in a single, officially-documented example: even knowing R uses round-half-to-even doesn’t fully predict the output, because the input itself might not be exactly what it looks like.

Example 5 — SQL engines don’t all agree either

A real 2026 compatibility issue in a SQLite-compatible database (Turso) surfaced exactly this problem: ROUND(2.25, 1) returned 2.2 (rounding to even) in one engine while SQLite itself returns a different result at the same tie, rounding away from zero instead. Database engines built to be “mostly compatible” with each other can still diverge at exactly the halfway point — the same lesson as Example 3, in a database context instead of a spreadsheet or scripting one.

Where This Still Trips People Up

• “My calculation is wrong” is often “my tool’s rounding convention differs from what I expected” — not a bug, and not something more careful arithmetic fixes. See Example 3.
• Floating-point error and rounding-convention differences are two separate problems that look identical from the outside. A wrong-looking last digit could be either one — Example 4 shows a case where they overlap.
• Assuming “round half away from zero” is the universal default is the single most common wrong assumption — it’s Excel’s behavior, but not Python’s, R’s, or (at the negative tie) even JavaScript’s.
• Porting a calculation between tools can silently change a result’s last digit at exactly the values where it matters most — a spreadsheet model rebuilt in Python, or vice versa, can disagree at ties without either implementation being wrong.
• The decimal module (Python) or equivalent exact-arithmetic libraries exist precisely to sidestep Problem 1 — reaching for one is the fix when floating-point error, not rounding convention, is the actual issue.

How Six Platforms Round the Same Tie

R’s signif() function is worth calling out specifically: unlike round(), it’s designed for significant figures directly (signif(1234.567, 3) returns 1230 without any LOG10 workaround) — the one tool covered here that doesn’t need Example 2’s formula trick.

The Standard Underneath All of This

Nearly every general-purpose language’s floating-point behavior — including the round-half-to-even default in Python and R — traces back to IEEE 754 (equivalently, IEC 60559), the international standard defining binary floating-point arithmetic. It’s the same standard referenced in our rounding guide as the source of round-half-to-even’s status as a computing default. JavaScript’s departure from that default at the negative tie is a deliberate language-specification choice, not a deviation from IEEE 754 itself, which governs number storage rather than mandating one particular round() function’s tie-breaking behavior.

Common Mistakes

1. Assuming a rounding discrepancy between two tools is a calculation error, when it’s very often just two different, individually valid conventions — see Example 3.
2. Not knowing a language’s default tie-breaking rule before relying on it for anything where the last digit matters.
3. Using native floating-point math for exact decimal work — currency, sig-fig calculators, anything where 0.1 + 0.2 needs to actually equal 0.3 — instead of an exact decimal type.
4. Forgetting that Excel’s ROUND() rounds decimal places, not significant figures, and getting a wrong answer from a direct ROUND(value, sig_figs) call.
5. Assuming R’s round() is deterministic for values like 0.15 without accounting for representation error — see Example 4.
6. Porting a spreadsheet formula or script between platforms without checking tie-breaking behavior, and being surprised when a boundary case changes.

Practice Problems

Concept: Floating-point representation

Q1. Which of these can be represented exactly in binary floating point? A) 0.1 B) 0.3 C) 0.25 D) 0.7 Answer: C) 0.25 — it’s 2⁻², a finite sum of negative powers of two.

Q2. Why does 0.1 + 0.2 display as 0.30000000000000004 in most languages? A) It’s a language bug B) Both 0.1 and 0.2 are stored as imperfect binary approximations, and adding them surfaces the compounded error C) The language rounds down incorrectly D) This only happens in JavaScript Answer: B.

Concept: Excel’s sig-fig formula

Q3. What does =ROUND(1234.567, 3-1-INT(LOG10(ABS(1234.567)))) evaluate to? A) 1234.57 B) 1230 C) 1200 D) 1235 Answer: B) 1230.

Q4. Why doesn’t Excel’s ROUND() round to significant figures directly? A) It’s not possible in Excel B) ROUND() only takes a decimal-places argument, so LOG10() is needed to convert a sig-fig count into the right decimal-places value C) Excel doesn’t support sig figs at all D) It requires a paid add-in Answer: B.

Concept: Python and R’s banker’s rounding

Q5. What does Python’s round(2.5) return? A) 3 B) 2 C) 2.5 D) An error Answer: B) 2 — banker’s rounding.

Q6. R’s documentation warns round(0.15, 1) could return either 0.1 or 0.2. Why? A) R has a bug B) 0.15 isn’t exactly representable in binary, so rounding applies to whichever approximation was actually stored, not the printed value C) R rounds randomly D) It depends on the R version only Answer: B.

Concept: JavaScript’s distinct tie-breaking

Q7. What does JavaScript’s Math.round(-2.5) return? A) -3 B) -2 C) -2.5 D) An error Answer: B) -2 — rounds toward positive infinity, not away from zero.

Q8. How does Math.round()‘s rule at the negative tie differ from Excel’s and Python’s rules, even where the numeric results happen to match? A) It doesn’t differ from either — all three use the same underlying rule B) It rounds toward positive infinity — a distinct rule from Excel’s “away from zero” and Python’s “to even,” even on inputs where it happens to land on the same number as one of them C) It always throws an error on negative numbers D) Only positive numbers are supported Answer: B.

Concept: Cross-platform divergence

Q9. Given input 2.5, which platforms from Example 3 agree with each other and differ from JavaScript’s positive-side result? A) None — all five platforms agree on 2.5 B) Python and R both round to 2, while Excel, MATLAB, and JavaScript all round to 3 C) Only MATLAB differs D) Only Excel differs Answer: B.

Q10. Why does this cross-platform divergence matter practically? A) It never matters — differences are always negligible B) A calculation rebuilt in a different tool can produce a different final digit at a tie, with no error in either tool’s logic C) Only academic exercises are affected D) Only currency calculations are ever affected Answer: B.

Same Tie, Three Rules

Input: -2.5

• → -3: Excel, Google Sheets, MATLAB (half away from zero)
• → -2: Python, R (half to even) and JavaScript (half toward positive infinity) — same result, different rule

Quick Reference

Continue Learning

Related fundamentals:

• Rounding Numbers: Every Method and Rule Explained
• Significant Figures: The Complete Guide

Go deeper on one platform at a time:

• How to Round to Significant Figures in Excel
• Significant Figures in Google Sheets
• Rounding to Significant Figures in Python
• Why Python’s round() Uses Banker’s Rounding
• Floating Point Errors That Break Sig Fig Calculations
• Sig Figs in R, MATLAB, JavaScript, and SQL — Behavior Compared
• Scientific Notation on the TI-84 and Casio fx-991

Tools:

• Significant Figures Calculator
• Rounding Mode Comparator

Sources and Further Reading

• MDN Web Docs, Math.round() — JavaScript — the primary source for JavaScript’s toward-positive-infinity tie-breaking behavior, including MDN’s own note distinguishing it from most other languages. (developer.mozilla.org)
• R Core Team, R: Rounding of Numbers (official R documentation) — the source for R’s IEC 60559 rounding behavior and its own documented caveat about representation error affecting values like 0.15, cited in Example 4. (stat.ethz.ch)
• note.nkmk.me, Round Numbers in Python — reused from our rounding pillar, confirming Python’s round() implements round-half-to-even by default. (note.nkmk.me)

Review and Methodology

Reviewed by: [Pending — reviewer assignment required before publication] Last reviewed: [Pending] Methodology: Every platform-specific behavior claim is sourced to that platform’s own official documentation (MDN for JavaScript, R Core Team for R) rather than a secondary summary, and every formula and worked example was independently tested during drafting. This site’s own calculators use an arbitrary-precision decimal engine, not native floating-point math, validated against a versioned regression fixture set.

Changelog

v1.0 — Initial draft completed, 2026-08-10.

The post Significant Figures in Excel, Sheets, Python, R, and Calculators: A Precision Reference appeared first on SignificantFiguresCalculator.

Our rounding methods guide introduced these four names at a summary level and flagged one correction along the way: ISO 80000-1 doesn’t mandate round-half-to-even, contrary to a common assumption. This page goes all the way in on what each standard actually says, using the standards’ own worked examples rather than invented ones wherever possible. The centerpiece is a genuinely consequential fact: the same test result can pass under one ASTM E29 method and fail under the other, on the exact same data, with no calculation error on anyone’s part.

Four Standards, Four Different Jobs

ASTM E29 — comparing a result to a specification, not rounding a number in the abstract. E29’s core content is two named methods for deciding whether a test result meets a written specification limit:

• Absolute Method: the specification limit is exact, however it’s written. “2.50 in. max” means exactly two and a half inches — the test result is compared directly, with no rounding grace, and any deviation, however small, means nonconformance.
• Rounding Method: the test result is rounded to the same number of decimal places the specification is written to, and then compared. A result that rounds down to the limit passes, even if its raw value technically exceeded it. E29 explicitly does not pick a winner between these — it requires whichever document is referencing it (a product spec, a purchase contract, an internal standard) to state which method applies. Separately, in its guidance on how many digits a test result itself should retain (tied to the test method’s own repeatability), E29’s own materials point to round-half-to-even for the specific case of resolving an exact tie — a narrower, different question from the Absolute/Rounding choice above.

ISO 80000-1, Annex B — general-purpose numeric rounding, not conformance-specific. ISO 80000-1 devotes a full normative annex to rounding, covering multiple accepted methods — including conventional (half-up) rounding — rather than mandating a single universal one. It’s written for general scientific and engineering use, not specifically for the pass/fail conformance-testing context E29 addresses.

NIST GLP-9 — laboratory rounding, with three named options. NIST’s own laboratory rounding guidance documents three explicitly accepted methods: even/odd (round ties to the nearest even digit — “banker’s rounding”), standard spreadsheet rounding (round ties away from zero, matching Excel’s default), and always round up (used specifically when rounding an uncertainty, where erring conservative is the safer direction). GLP-9 requires the laboratory to document in writing which of the three it uses — it does not pick one for you, any more than ISO 80000-1 or ASTM E29 do.

Classroom rounding — the single-method baseline. Round half up, full stop, taught as if it were the only method in existence — which is exactly why the other three come as a surprise the first time someone encounters a real specification, a real lab, or a real standards document.

The pattern across all three professional standards: none of them mandate one universal tie-breaking rule. All three explicitly document multiple accepted options and require the applicable one to be stated in writing. The idea of a single “correct” rounding method is a classroom simplification that doesn’t survive contact with any of the actual standards.

Worked Examples

Example 1 — The same result, two different verdicts (ASTM E29)

Specification: “2.50 in. max.” Test result: 2.504 in.

Absolute Method: compare 2.504 directly against 2.50. It exceeds the limit. Result: does not conform.

Rounding Method: round 2.504 to the spec’s stated precision (2 decimal places) — the third decimal is 4, so it rounds down to 2.50. Compare 2.50 against the 2.50 limit: equal, within bounds. Result: conforms.

Same measurement, same specification, opposite conclusions — determined entirely by which method the governing document specified. ASTM’s own guidance frames this precisely: the Rounding Method effectively extends a specification’s limits by half the rounding interval in the passing direction. Here, with a 0.01 rounding interval, “2.50 max” effectively becomes “conforms up to 2.505” under the Rounding Method, while the Absolute Method holds the line at exactly 2.50 with no grace at all.

Example 2 — NIST GLP-9’s three options on one uncertainty value

Uncertainty to round to 2 significant figures: 0.125 — an exact tie at the third significant digit.

Even/odd method: the digit before the tie (2) is already even, so it stays — rounds down to 0.12. Standard spreadsheet method: ties round away from zero — rounds up to 0.13. Always-round-up method: rounds up to 0.13, by definition.

Two of the three options agree here; the even/odd method alone gives a different answer, purely because of which of the three documented GLP-9 options a lab has chosen to use.

Example 3 — What ISO 80000-1 does and doesn’t dictate

A measured value, 47.65, needs rounding to 3 significant figures.

Under ISO 80000-1’s conventional (half-up) method, covered in its Annex B: the digit being dropped is 5 exactly, with nothing following — round up → 47.7.

This looks identical to the plain classroom rule, because for this particular input it is — ISO 80000-1 explicitly permits conventional rounding as one of its accepted methods, not a competing alternative to it. The standard’s actual contribution isn’t a different answer here; it’s the requirement that whoever is rounding state which of the annex’s accepted methods they used, so a second party can reproduce the result.

Example 4 — All four side by side

The same raw value, 12.345, rounded to 2 decimal places under each framework’s documented approach:

Three out of four land on 12.35. The even/odd option is the outlier — not wrong, just a different documented choice, and exactly the kind of divergence that makes stating your method explicitly a real requirement rather than a formality.

Where This Still Trips People Up

• “Round it properly” isn’t an instruction any of these standards would recognize. Every one of them requires a stated choice among named options — there’s no single “properly” to default to.
• The Absolute/Rounding Method choice is not the same decision as picking a tie-breaking rule. E29’s headline distinction is about whether to round before comparing to a spec at all — a totally different question from how to round when you do. Conflating the two is easy and common.
• Different parties in the same transaction tend to prefer different methods, and not by accident. Practitioners report that specification writers tend to assume the Absolute Method (strict, no grace) while producers and suppliers tend to assume the Rounding Method (which is more forgiving to them) — precisely because the outcome genuinely differs, as Example 1 shows. This is exactly why E29 insists the choice be written down rather than assumed.
• A standard “recommending” a method for one specific sub-case doesn’t mean it mandates that method everywhere. E29’s pointer toward even/odd rounding for retaining digits in a test result (tied to repeatability) is a narrower, specific piece of guidance — not a blanket replacement for the Absolute/Rounding Method framework.
• None of this matters until a value lands near a boundary. Every example on this page was deliberately chosen close to a rounding or specification boundary, because that’s the only place these methods actually diverge — comfortably mid-range values give the same answer under everything.

Which Standard Actually Applies

The honest summary: professional standards exist to force an explicit choice and make it reproducible, not to hand down one correct answer. The classroom is the only context on this list that doesn’t do that — which is fine for its purposes, and exactly why it stops being enough the moment a real specification or lab report is involved.

Where to Verify This Directly

ASTM E29 is a purchasable standard (currently E29-22) available through ASTM’s own store; the mechanics described here — the Absolute Method, the Rounding Method, and the requirement to state which applies — are drawn from ASTM’s own published explainer materials, not a secondary summary of the paywalled text itself. NIST GLP-9 is freely available directly from nist.gov. ISO 80000-1’s Annex B is part of a purchasable ISO standard; the characterization here (multiple accepted methods, no single mandate) is cross-referenced across several independent secondary sources rather than the primary text, since ISO standards are not freely republishable — treat this page as a map to the real documents, not a substitute for them in any compliance-relevant setting.

Common Mistakes

1. Assuming a specification’s stated method without checking. Whether “2.50 max” gets the Absolute or Rounding Method treatment isn’t guessable from the number alone — see Example 1.
2. Treating E29’s Absolute/Rounding Method choice as the same thing as a tie-breaking rounding rule. They answer different questions entirely.
3. Assuming ISO 80000-1 or NIST GLP-9 hands down one mandatory method, when both explicitly document several and require the choice to be stated.
4. Applying classroom round-half-up in a context that specifies a different documented standard, without checking which one actually governs.
5. Citing a rounding standard’s guidance for one specific sub-case as if it applied universally — see the E29 even/odd nuance in the gotchas above.
6. Not writing down which method was used, which is the one requirement every professional standard on this page shares, and the one step classroom rounding never bothers to teach.

Practice Problems

Concept: ASTM E29’s Absolute vs. Rounding Method

Q1. A specification states “2.50 in. max.” A test result reads 2.504 in. Under the Absolute Method, does this conform? A) Yes B) No C) It depends on the lab D) Only if rounded first Answer: B) No — any deviation, however small, fails under the Absolute Method.

Q2. Same scenario — 2.504 in. against a “2.50 in. max” spec. Under the Rounding Method, does this conform? A) Yes, since 2.504 rounds to 2.50 B) No C) It depends on the lab D) Only under the Absolute Method Answer: A.

Concept: NIST GLP-9’s three options

Q3. Under GLP-9’s even/odd method, an uncertainty of 0.125 rounds to 2 significant figures as: A) 0.12 B) 0.13 C) 0.1 D) 0.130 Answer: A) 0.12 — the digit before the tie (2) is already even.

Q4. Under GLP-9’s standard spreadsheet method, 0.125 rounds to 2 significant figures as: A) 0.12 B) 0.13 C) 0.1 D) 0.130 Answer: B) 0.13.

Concept: ISO 80000-1

Q5. ISO 80000-1’s Annex B on rounding: A) Mandates round-half-to-even as the only acceptable method B) Documents multiple accepted rounding methods, including conventional (half-up) rounding C) Only applies to chemistry D) Has been withdrawn and replaced Answer: B.

Q6. A lab rounds a value using ISO 80000-1’s conventional method and gets the same answer a classroom round-half-up rule would give. What does this mean? A) ISO 80000-1 is redundant B) Conventional rounding under ISO 80000-1 is the same operation as classroom half-up rounding — agreement is expected, not a coincidence C) The lab made an error D) ISO 80000-1 doesn’t apply to this case Answer: B.

Concept: Which standard applies where

Q7. Which standard specifically governs comparing a test result to a written specification limit? A) NIST GLP-9 B) ASTM E29 C) Classroom rounding D) ISO 80000-1 exclusively Answer: B.

Q8. Which document specifically addresses rounding a measurement uncertainty in a calibration or testing laboratory? A) ASTM E29 exclusively B) NIST GLP-9 C) Classroom textbooks D) None of these address uncertainty Answer: B.

Concept: Why explicit method statements matter

Q9. What’s the single rounding method most classroom instruction defaults to, without stating it as a choice? A) Round half to even B) Round half up C) Truncation D) Always round up Answer: B.

Q10. Why do ASTM E29, ISO 80000-1, and NIST GLP-9 all require the applicable method to be stated in writing rather than assumed? A) It’s a bureaucratic formality with no real effect B) Different methods can genuinely produce different pass/fail or reported-value outcomes on identical data, so ambiguity has real consequences C) Rounding doesn’t actually matter in professional practice D) Only classroom rounding has real consequences Answer: B.

How Far the Limit Moves

Specification: “2.50 in. max”

• Absolute Method boundary: exactly 2.50 — nothing above passes
• Rounding Method effective boundary: 2.505 — the region from 2.50 to 2.505 passes only under this method
• Test result 2.504 falls inside that gap: fails Absolute, passes Rounding

Quick Reference

Continue Learning

Related fundamentals:

• Rounding Numbers: Every Method and Rule Explained
• Significant Figures: The Complete Guide

Go deeper on one topic at a time:

• What Is ASTM E29 Rounding and Who Uses It?
• Banker’s Rounding Explained (and Why Excel and Python Disagree)
• Significant Figures in Engineering Drawings and Tolerances

Tools:

• Tolerance / Conformance Checker
• Rounding Mode Comparator

Sources and Further Reading

• ASTM, Some Fine Points of Determining Conformity to Specification — ASTM’s own explainer on the Absolute Method and Rounding Method, including the “limits effectively extended by half the rounding interval” framing used in Example 1. (astm.org)
• ASTM, How Do You Round Fractions? Significant Digits and Converting to a Decimal — ASTM’s own guidance on retaining digits in a test result, including the even/odd rounding nuance discussed in the rule statement above. (astm.org)
• NIST GLP 9 (2019), Rounding — reused from our rounding pillar, the primary source for GLP-9’s three documented options. (nist.gov)
• ISOBudgets, How to Round Uncertainty to 2 Significant Digits (ISO 17025) — reused from our rounding pillar, the cross-reference confirming ISO 80000-1 documents conventional rounding rather than mandating a single method. (isobudgets.com)

Review and Methodology

Methodology: All standards claims are sourced to official/authorized publishers only (astm.org, nist.gov) or clearly-labeled secondary cross-references (isobudgets.com) — third-party sites found to host unauthorized copies of paywalled standard text were used for background verification only and are not cited or linked. Every worked example was independently recomputed during drafting.

Changelog

v1.0 — Initial draft completed, 2026-08-10.

The post Rounding Standards Compared: ASTM E29, ISO 80000-1, NIST, and Classroom Rules appeared first on SignificantFiguresCalculator.

This is the second subject-specific pillar on this site, after Significant Figures in Chemistry. Where that page’s standout fact was about atomic mass, this one’s is about physical constants: since 2019, several of the constants a physics formula relies on are exactly defined, with zero uncertainty — while others, used just as often, are genuinely experimental values still being refined today. Knowing which is which changes how you treat them in a calculation. Everything below builds directly on reading instrument uncertainty and error propagation covered earlier in this site — this page is where those ideas meet an actual lab bench.

Three Places Sig Figs Enter a Physics Lab Report

Reading uncertainty: where it actually comes from. For an analog scale (ruler, protractor, analog dial), the conventional reading uncertainty is half the smallest marked division — you can reliably estimate a position to about that precision by eye, but not much finer. For a digital display, the convention is ±1 in the last displayed digit, unless the manufacturer states a larger accuracy specification (many digital instruments are less accurate than their display resolution suggests, and the stated spec should win when it’s larger). For manually triggered timing (a stopwatch started and stopped by hand), the dominant uncertainty is almost never the stopwatch’s own resolution — it’s human reaction time, typically 0.1–0.3 seconds, which is usually far larger than the 0.01 s the display shows.

Which constants in your formula are exact — and which aren’t. Since the 2019 redefinition of the SI, seven physical constants have been fixed by international agreement to have exact values with zero uncertainty: the speed of light, the Planck constant, the elementary charge, the Boltzmann constant, the Avogadro constant, the caesium-133 hyperfine transition frequency, and the luminous efficacy of a defined visible radiation. Treat these exactly the way you’d treat an exact number — they never limit a calculation’s precision. Most other constants a physics formula uses are not on this list, including the gravitational constant, G, which remains a genuinely experimental value, redetermined periodically, and is in fact one of the least precisely known constants in physics. Mathematical constants like π are a separate case entirely: they’re not physical measurements at all, so they carry no uncertainty and can be used to as many digits as a calculation needs.

Propagating uncertainty through a physics formula. Most physics-lab formulas are combinations of multiplication, division, and powers — our error propagation guide covers the general rules; the one that trips people up most in a physics context specifically is the power rule, because so many common formulas square or take a square root of a measured quantity (period, distance, velocity). Squaring a measured value doubles its relative uncertainty’s contribution to the result — a fact easy to miss if you’re only thinking in sig-fig-counting terms rather than actual propagated uncertainty. See Example 3.

Worked Examples

Example 1 — Reading uncertainty, two ways

Analog: a ruler marked in millimeters is used to measure a block’s length, read as 45 mm. Conventional uncertainty: half the smallest division = ± 0.5 mm → report as 45.0 ± 0.5 mm.

Digital: a digital caliper displays 12.47 mm. Absent a stated manufacturer accuracy spec, conventional uncertainty is ± 1 in the last digit = ± 0.01 mm → report as 12.47 ± 0.01 mm.

Neither convention claims the instrument is accurate — only that this is the precision it can be read to. An uncalibrated digital caliper can still read 12.47 ± 0.01 mm and be systematically wrong, exactly as covered in accuracy vs. precision.

Example 2 — Exact constants vs. a genuinely measured one

Exact, by definition (2019 SI redefinition):

• Speed of light: c = 299,792,458 m/s, exactly
• Planck constant: h = 6.62607015 × 10⁻³⁴ J·s, exactly
• Elementary charge: e = 1.602176634 × 10⁻¹⁹ C, exactly
• Avogadro constant: N_A = 6.02214076 × 10²³ /mol, exactly

Not exact — a real, still-improving experimental value:

• Gravitational constant: G ≈ 6.674 × 10⁻¹¹ N·m²/kg², with a relative uncertainty around 2 × 10⁻⁵ — roughly ten thousand times less precisely known than c, h, or e, which have zero uncertainty by definition.

If a calculation uses c, h, e, or N_A, treat them as exact — infinite significant figures, never the limiting factor. If it uses G, treat it as a measured quantity with its own real (comparatively large) uncertainty that has to be propagated like any other input.

Example 3 — A full calculation: finding g from a pendulum

Measured: length L = 0.950 ± 0.002 m, period T = 1.955 ± 0.004 s (averaged over multiple swings). Formula: g = 4π²L/T².

Raw calculation, guard digits kept: g = 4π² × 0.950 / (1.955)² = 39.4784 × 0.950 / 3.822025 ≈ 9.813 m/s²

Relative uncertainties: u(L)/L = 0.002/0.950 ≈ 0.211%. u(T)/T = 0.004/1.955 ≈ 0.205% — but T is squared in the formula, so its contribution to g’s relative uncertainty doubles: 2 × 0.205% = 0.409%.

Quadrature (GUM) method: √(0.211%² + 0.409%²) ≈ 0.460% → absolute uncertainty = 9.813 × 0.00460 ≈ 0.045

Answer: g = 9.813 ± 0.045 m/s² (quadrature). The simple worst-case method (0.211% + 0.409% = 0.620%) gives a wider ± 0.061 m/s² instead — both defensible, per our error propagation guide, depending on which one your course expects.

Example 4 — Comparing to the accepted value

Measured: g = 9.813 m/s² (Example 3). Accepted standard value: g_n = 9.80665 m/s² exactly — a value fixed by international agreement in 1901, distinct from the actual local gravitational acceleration, which genuinely varies by location and altitude.

Percent error = |9.813 − 9.80665| / 9.80665 × 100% = 0.00635 / 9.80665 × 100%

Answer: 0.065% percent error — small enough to indicate a well-executed experiment, and a result that sits comfortably within the ± 0.045 m/s² uncertainty band calculated in Example 3, which is exactly what a successful comparison to an accepted value should show.

Example 5 — Why raw data shouldn’t be rounded early

A student records five trial times for the pendulum: 1.95 s, 1.96 s, 1.95 s, 1.96 s, 1.96 s — already rounded to 2 decimal places at the moment of recording, because “that’s what the final answer needed anyway.” The stopwatch actually displayed 3 decimal places each time. Averaging the pre-rounded values and averaging the full-precision values can land on different last digits — the same double-rounding effect covered generally elsewhere on this site, here costing real data rather than just an arithmetic exercise. Record raw data to the full precision the instrument actually shows; round only the final calculated result.

Where This Still Trips People Up

• A digital reading isn’t automatically more accurate, just more precise-looking. ± 1 in the last digit describes readability, not whether the instrument was ever calibrated — see accuracy vs. precision.
• π is not in the same category as G. π is a mathematical constant with no physical measurement behind it at all — treat it as exact to as many digits as needed. G is a physical constant that genuinely had to be measured, and still carries real uncertainty.
• Stopwatch resolution overstates real timing precision. A stopwatch showing hundredths of a second doesn’t mean your timing is good to 0.01 s — human reaction time dominates, and reporting timing uncertainty as “± the stopwatch’s resolution” understates the true uncertainty substantially.
• Squaring doesn’t leave sig figs unchanged just because it “looks like” ordinary multiplication. Treating T² as simple multiplication (matching T’s own sig fig count) happens to give a similar classroom-level answer, but it hides that the relative uncertainty genuinely doubles — a distinction that matters the moment you’re doing real propagation instead of digit-counting. See Example 3.
• Not every constant with a lot of digits is exact. G is often written to 4–5 sig figs on a formula sheet, which can look just as “fixed” as c or h — the digit count gives no visual clue that one is exact and the other isn’t.

Instrument Uncertainty by Type

The general pattern: the “obvious” number (the smallest marked division, the display’s last digit) is a reasonable starting estimate, but the actual limiting factor is sometimes somewhere else entirely — human reaction time being the clearest example.

Where the Constants Data Comes From

The exact/measured split in Example 2 comes directly from the BIPM’s own account of the SI’s seven defining constants, adopted at the 26th General Conference on Weights and Measures in 2018 and in force since 20 May 2019. The gravitational constant, by contrast, has no such fixed definition — its currently accepted value comes from CODATA’s periodic recommended-values adjustment, which is revised as new experiments improve on it, precisely because it remains a measured quantity rather than a defined one.

Common Mistakes

1. Rounding raw data at the moment of recording instead of keeping full instrument precision until the final calculation — see Example 5.
2. Reporting timing uncertainty as the stopwatch’s display resolution, ignoring the much larger human reaction time contribution.
3. Treating every constant in a formula as equally exact, when only the seven SI defining constants actually carry zero uncertainty — see Example 2.
4. Applying the multiplication sig-fig rule to a squared term without recognizing that relative uncertainty, not just sig fig count, doubles under squaring.
5. Calculating percent error against the measured value instead of the accepted value in the denominator — it’s always accepted value on the bottom.
6. Assuming a digital instrument’s readout is accurate just because it’s precise — see the accuracy/precision gotcha above.

Practice Problems

Concept: Reading uncertainty from instruments

Q1. A ruler marked in millimeters is used to measure a length. What’s the conventional reading uncertainty? A) ± 1 mm B) ± 0.5 mm C) ± 0.1 mm D) ± 2 mm Answer: B) ± 0.5 mm — half the smallest division.

Q2. A digital scale displays 24.5 g with no stated accuracy specification. What’s the conventional reading uncertainty? A) ± 0.5 g B) ± 5 g C) ± 0.1 g D) ± 1 g Answer: C) ± 0.1 g — ± 1 in the last displayed digit.

Concept: Exact vs. measured constants

Q3. Since the 2019 SI redefinition, which of these has exactly zero uncertainty? A) Gravitational constant, G B) Planck constant, h C) Local gravitational acceleration, g D) None of these Answer: B.

Q4. Why does the gravitational constant G remain experimentally measured while the Planck constant h does not? A) G is less scientifically important B) G was not fixed by the 2019 redefinition and continues to be determined by experiment, unlike h, e, k, and N_A C) G changes measurably over time D) G has no physical units Answer: B.

Concept: Power propagation

Q5. In g = 4π²L/T², if T has a 0.2% relative uncertainty, what’s its contribution to g’s relative uncertainty before combining with L’s? A) 0.1% B) 0.2% C) 0.4% D) 0.04% Answer: C) 0.4% — squaring doubles the relative uncertainty contribution.

Q6. If T’s relative uncertainty dominates the combined uncertainty in g, which measurement most needs improving to tighten the final result? A) L, always B) T, since squaring amplifies its relative uncertainty C) Neither matters D) The constant 4π² Answer: B.

Concept: Percent error against an accepted value

Q7. A pendulum experiment measures g = 9.81 m/s², against the accepted value 9.80665 m/s². What’s the percent error, to 2 significant figures? A) 0.034% B) 0.34% C) 3.4% D) 0.0034% Answer: A) 0.034%.

Q8. Percent error is always calculated relative to which value? A) The measured value B) The accepted/true value C) The average of both D) Neither — it’s a plain difference with no denominator Answer: B.

Concept: Lab report data-handling conventions

Q9. When recording raw data in a lab notebook, the correct practice is to: A) Round immediately to the number of sig figs expected in the final answer B) Record the full precision the instrument actually shows, and round only the final calculated result C) Always record exactly 3 sig figs regardless of the instrument D) Record only whole numbers Answer: B.

Q10. Why shouldn’t intermediate values be rounded throughout a multi-step lab calculation? A) It’s fine to round at every step B) Rounding at each step compounds error and can shift the final answer’s last digit — the same double-rounding problem covered generally elsewhere on this site C) Only final answers need any precision D) Intermediate values don’t need units Answer: B.

Exact vs. Measured, Side by Side

Exact — defined, zero uncertainty:

• c = 299,792,458 m/s
• h = 6.62607015 × 10⁻³⁴ J·s
• e = 1.602176634 × 10⁻¹⁹ C
• N_A = 6.02214076 × 10²³ /mol

Measured — real, ongoing uncertainty:

• G = 6.674 × 10⁻¹¹ N·m²/kg² ± ~0.00015 × 10⁻¹¹ (relative uncertainty ≈ 2 × 10⁻⁵, still being refined by CODATA)

Quick Reference

Continue Learning

Related fundamentals:

• Accuracy, Precision, and Uncertainty
• Error Propagation: How Uncertainty Moves Through a Calculation
• Exact Numbers and Why They Never Limit Precision

Related subjects:

• Significant Figures in Chemistry
• Significant Figures Constants Reference
• Significant Figures in Engineering Drawings and Tolerances
• Significant Figures in Astronomy

Exam-specific guidance:

• Significant Figures Rules for AP Physics and AP Chemistry
• Significant Figures for GCSE and A-Level Sciences

Tools:

• Error Propagation Calculator
• Percent Error Calculator

Sources and Further Reading

• BIPM, The International System of Units (SI): Defining Constants — the primary source for which seven physical constants carry exactly zero uncertainty since the 2019 redefinition, cited throughout Example 2. (bipm.org)
• Wikipedia, Elementary Charge — cross-referenced for the exact 2019-defined value of e used in Example 2, consistent with multiple independent technical sources checked during drafting. (en.wikipedia.org)
• NIST Technical Note 1297, Guidelines for Evaluating and Expressing the Uncertainty of NIST Measurement Results — reused from earlier pillars, relevant here for the reading-uncertainty and reporting conventions applied throughout. (emtoolbox.nist.gov)

Review and Methodology

Methodology: The exact/measured constants distinction is drawn directly from BIPM’s own SI documentation, not a secondary summary. Every worked example was independently recomputed during drafting. Calculator results referenced on this page use an arbitrary-precision decimal engine, not native floating-point math, validated against the site’s versioned regression fixture set.

Changelog

v1.0 — Initial draft completed, 2026-08-10.

The post Significant Figures in Physics Lab Reports: A Complete Working Guide appeared first on SignificantFiguresCalculator.

Everything here builds on the core rules, arithmetic, and logarithms covered earlier in this site — this page is about applying them in the specific contexts a chemistry student or lab tech actually runs into. It also covers a genuinely surprising fact almost no other sig-figs resource mentions: for fourteen elements, there is no single “correct” atomic mass to plug into a calculation — the official value is a range, not because anyone’s measurement is imprecise, but because the atomic mass of these elements actually varies depending on where the sample came from. See Example 1.

Three Chemistry-Specific Rules

Molar mass: sum atomic masses using the addition rule, with atom counts as exact multipliers. A chemical formula’s subscripts (the “2” in H₂O, the “4” in CH₄) are exact counts of atoms — not measurements — so per our exact-numbers rule, multiplying an atomic mass by its subscript never reduces precision. What does limit precision is the atomic masses themselves: sum the (possibly multiplied) atomic masses using the ordinary addition rule — round the total to match the fewest decimal places among the values being summed. See Example 2.

pH: only the decimal places carry meaning, because pH is a logarithm. pH = −log₁₀[H⁺]. As established in our scientific notation guide, a logarithm’s mantissa (the decimal part) is what carries precision — the integer part just reflects order of magnitude. So the number of decimal places in a reported pH should match the number of significant figures in the concentration it came from — not the total digit count of the pH value. The same logic runs in reverse when converting a pH back to a concentration. See Examples 3 and 4.

Stoichiometry: mole ratios are exact; the measured quantity is the limit. The coefficients in a balanced chemical equation (the “2” in CH₄ + 2O₂ → CO₂ + 2H₂O) are exact, defined ratios — they never limit sig figs, no matter how the equation is written. The quantity that actually limits precision is whatever was measured: a given mass, volume, or concentration. Molar masses sit in between — they have their own real precision (see Example 1), but for a typical intro-level calculation, the measured starting quantity is usually the tightest constraint. As always, carry extra guard digits through intermediate mole calculations and round only the final answer. See Example 5.

Worked Examples

Example 1 — Atomic mass isn’t always a fixed number

Most sig fig guidance treats atomic mass as a known constant with obvious precision. It’s more interesting than that. The IUPAC body responsible for atomic weights (CIAAW) publishes the standard atomic weight of fourteen elements — including hydrogen, carbon, nitrogen, oxygen, and chlorine — as an interval, not a single value, because the true atomic mass genuinely varies with the terrestrial source of the sample. Hydrogen’s standard atomic weight is the interval [1.00784, 1.00811]; nitrogen’s is [14.00643, 14.00728]. For everyday calculation, CIAAW also publishes a single “abridged” conventional value for each — 1.0080 for hydrogen, for instance — which is what ends up printed on a classroom periodic table. The precision printed on your periodic table is itself a rounded, conventional choice, not an exact physical constant — which is exactly the kind of thing this site’s rule-attribution approach exists to make visible.

Example 2 — Molar mass with an exact multiplier

Calculate the molar mass of CH₄, using H = 1.008, C = 12.01 (standard 2-decimal-place classroom values).

4 × H = 4 × 1.008 = 4.032 — the “4” is an exact atom count, so this keeps all of 1.008’s precision (3 decimal places); no rounding happens at this step.

C + 4H = 12.01 + 4.032. Addition rule: match the fewest decimal places. 12.01 has 2, 4.032 has 3 — fewest is 2. Raw sum = 16.042 → round to 2 decimal places.

Answer: 16.04 g/mol.

Example 3 — pH from concentration

Calculate the pH of a solution with [H⁺] = 3.2 × 10⁻⁴ M (2 significant figures).

pH = −log₁₀(3.2 × 10⁻⁴) = −(0.505 − 4) = −(−3.495) = 3.49485…

Since [H⁺] has 2 sig figs, the pH should be reported to 2 decimal places — not 2 sig figs total. Rounding 3.49485 to 2 decimal places (the third decimal digit is 4, so round down):

Answer: pH = 3.49.

Example 4 — Concentration from pH (the reverse direction)

A solution has pH = 4.30 (2 decimal places). Find [H⁺].

[H⁺] = 10^(−pH) = 10^(−4.30) ≈ 5.012 × 10⁻⁵ M

Since the pH was given to 2 decimal places, [H⁺] should be reported to 2 significant figures — the reverse of Example 3’s rule, applied in the opposite direction.

Answer: [H⁺] = 5.0 × 10⁻⁵ M.

Example 5 — Full stoichiometry calculation

How many grams of CO₂ are produced from the complete combustion of 15.0 g of CH₄? Balanced equation: CH₄ + 2O₂ → CO₂ + 2H₂O. Molar mass CH₄ = 16.04 g/mol (Example 2). Molar mass CO₂ = 12.01 + 2(16.00) = 44.01 g/mol.

Moles of CH₄ = 15.0 g ÷ 16.04 g/mol = 0.93516… mol (guard digit kept, not yet rounded)

Mole ratio CH₄ : CO₂ is 1 : 1 — an exact ratio from the balanced equation, so it doesn’t touch the precision at all: moles of CO₂ = 0.93516… mol.

Mass of CO₂ = 0.93516… mol × 44.01 g/mol = 41.156… g (still unrounded)

Now round, once, at the very end — to 3 significant figures, matching the original 15.0 g (the tightest constraint in the whole calculation):

Answer: 41.2 g of CO₂.

Where This Still Trips People Up

• Different periodic tables print different precision, and that alone can shift a final answer’s last digit — a table rounded to whole numbers, one rounded to 2 decimal places, and IUPAC’s 5-sig-fig abridged values will not always agree past the first digit or two. This is one of the most common, and most innocent, reasons a “wrong” answer turns out to be a rounding-source mismatch rather than an actual error.
• Mole ratios are not measurements and never limit sig figs, but they’re routinely treated as if a “2” in a balanced equation had only 1 sig fig. It doesn’t — it’s exact, like every other stoichiometric coefficient.
• pH sig figs run backwards from the intuition most students bring in. A pH of 3.49 doesn’t have “3 sig figs” in the ordinary sense — its 2 decimal places correspond to 2 sig figs in the original concentration. Counting pH digits the normal way overstates the precision.
• Antilog conversions (pH → concentration) need the same care in reverse — see Example 4. It’s easy to remember the forward rule and forget it has a mirror image.
• “Exact” atomic mass isn’t quite the right mental model for the fourteen interval elements in Example 1 — even the conventional single-value numbers on a periodic table are themselves a rounded compromise, not a physical constant measured to arbitrary precision.

Precision Conventions by Source

There’s no single “correct” choice among these — the right move is to use whatever periodic table your course or exam actually provides, and expect a small final-digit mismatch against anyone using a different source. This is also the most common reason a calculator and a teacher disagree on a chemistry sig-fig answer without either one being wrong.

Where the Atomic Weight Data Comes From

The interval values in Example 1 come from CIAAW (the Commission on Isotopic Abundances and Atomic Weights), the IUPAC body that has published critical evaluations of atomic weights since 1902. Its most recent full report groups elements into those with well-documented natural isotopic variation (given as an interval), those limited by current measurement ability, and everything else (given as abridged 5-sig-fig values). This isn’t a chemistry-education simplification — it’s the literal reason a periodic table’s numbers look the way they do.

Common Mistakes

1. Treating a stoichiometric coefficient as if it limited sig figs. It’s exact — see Example 5.
2. Counting pH digits the normal way instead of matching decimal places to the concentration’s sig figs — see Example 3.
3. Forgetting the antilog direction has its own rule when converting pH back to concentration — see Example 4.
4. Rounding intermediate mole values during a multi-step stoichiometry calculation instead of carrying guard digits to the end — see Example 5.
5. Assuming a “wrong” chemistry answer is a calculation error when it’s actually a periodic-table-precision mismatch — see the comparison table above.
6. Multiplying an atomic mass by its subscript as if the subscript were a measured value, rather than recognizing it as an exact atom count that never limits precision.

Practice Problems

Concept: Molar mass with exact multipliers

Q1. Calculate the molar mass of H₂O (H = 1.008, O = 16.00). A) 18.0 g/mol B) 18.02 g/mol C) 18.016 g/mol D) 18.1 g/mol Answer: B) 18.02 g/mol (2 × 1.008 = 2.016, exact multiplier; 2.016 + 16.00 → round to 2 decimal places, matching O’s precision).

Q2. In calculating the molar mass of CO₂ (C = 12.01, O = 16.00), how many decimal places does the final answer have, and why? A) 3, matching the most precise atomic mass B) 2, matching the fewest decimal places among the summed terms C) 4, matching the total atom count D) 0, molar mass is always a whole number Answer: B.

Concept: pH from concentration

Q3. [H⁺] = 3.2 × 10⁻⁴ M (2 sig figs). What is the correctly reported pH? A) 3.5 B) 3.49 C) 3.494846 D) 3 Answer: B) 3.49.

Q4. Why does pH get reported with a number of decimal places (not total sig figs) matching the concentration’s sig figs? A) It’s an arbitrary convention B) Because pH is a logarithm, and only the mantissa carries precision — the integer part just reflects order of magnitude C) Because pH is always between 0 and 14 D) Because concentrations are always exact Answer: B.

Concept: Concentration from pH (antilog)

Q5. A solution has pH = 4.30 (2 decimal places). What is [H⁺], correctly rounded? A) 5.0 × 10⁻⁵ M B) 5.01 × 10⁻⁵ M C) 5 × 10⁻⁴ M D) 0.0000501 M Answer: A) 5.0 × 10⁻⁵ M.

Q6. If a pH is reported to 3 decimal places, how many significant figures should the corresponding [H⁺] have? A) 2 B) 3 C) 4 D) It depends on the specific pH value Answer: B) 3.

Concept: Exact mole ratios

Q7. In the balanced equation CH₄ + 2O₂ → CO₂ + 2H₂O, the coefficients (1, 2, 1, 2) are: A) Measured values with their own sig figs B) Exact numbers that never limit the calculation’s precision C) Approximate, typically to 1 sig fig D) Dependent on the amount of reactant used Answer: B.

Q8. 15.0 g of CH₄ (molar mass 16.04 g/mol) combusts completely. How many moles of CH₄ is this, correctly rounded? A) 0.9 mol B) 0.935 mol C) 0.93516 mol D) 0.94 mol Answer: B) 0.935 mol (3 sig figs, matching 15.0 g).

Concept: Full stoichiometry

Q9. Continuing Q8 (0.935 mol CH₄, a 1:1 mole ratio to CO₂, CO₂ molar mass 44.01 g/mol), how many grams of CO₂ are produced? A) 41 g B) 41.2 g C) 41.16 g D) 41.156 g Answer: B) 41.2 g.

Q10. Why is the final answer in Q9 limited to 3 significant figures, even though the molar masses used had 4? A) Molar masses are always ignored for sig fig purposes B) The originally given mass (15.0 g) has only 3 sig figs and is the least precise measured quantity in the whole calculation C) CO₂ is always reported to 3 sig figs D) The mole ratio limits it to 3 sig figs Answer: B.

One Element, Two Kinds of Number

Hydrogen:

• True standard atomic weight: an interval, [1.00784, 1.00811] — it genuinely varies by sample source
• Conventional abridged value (what’s printed on most periodic tables): 1.0080
• Common classroom rounding: 1.008 or 1.01

Nitrogen:

• True standard atomic weight: an interval, [14.00643, 14.00728]
• Conventional abridged value: 14.007
• Common classroom rounding: 14.01

Quick Reference

Continue Learning

Related fundamentals:

• Significant Figures: The Complete Guide
• Exact Numbers and Why They Never Limit Precision
• Significant Figures in Logarithms and pH

Go deeper on one chemistry topic at a time:

• Significant Figures in Stoichiometry Problems
• pH and Sig Figs: Why Only the Decimals Count
• Molar Mass: How Many Sig Figs Should You Use?
• Significant Figures in Titration Calculations
• Significant Figures Rules for AP Chemistry
• Significant Figures in IB Sciences (Internal Assessment)
• Significant Figures for GCSE and A-Level Sciences
• Why Your Teacher’s Sig Fig Answer Differs From the Calculator’s

Tools:

• Molar Mass & Stoichiometry Calculator
• Significant Figures Calculator

Sources and Further Reading

• CIAAW (Commission on Isotopic Abundances and Atomic Weights), Standard Atomic Weights 2024 — the current official table, including the fourteen elements published as intervals rather than single values, cited throughout Example 1. (ciaaw.org)
• CIAAW, Abridged Standard Atomic Weights 2024 — the conventional single-value, 5-significant-figure table most closely matching what appears on a printed periodic table. (ciaaw.org)
• Prohaska, T. et al., Standard atomic weights of the elements 2021 (IUPAC Technical Report), Pure and Applied Chemistry — the full technical report explaining why fourteen elements are given as intervals and how the abridged values are derived. (degruyterbrill.com)

Review and Methodology

Methodology: Atomic mass data is drawn directly from CIAAW’s current published tables (see Sources), not a secondary periodic table. Every worked example was independently recomputed during drafting. Calculator results referenced on this page use an arbitrary-precision decimal engine, not native floating-point math, validated against the site’s versioned regression fixture set.

Changelog

v1.0 — Initial draft completed, 2026-08-10.

The post Significant Figures in Chemistry: Stoichiometry, pH, and Molar Mass appeared first on SignificantFiguresCalculator.

This page picks up directly where Accuracy, Precision, and Uncertainty left off. That page established that random error is what uncertainty describes, and that it behaves statistically rather than as a fixed offset. This page is about what happens when you calculate with several such uncertain values at once — add them, multiply them, raise them to a power — and need to know how uncertain the result is. It also closes a loop that’s been open since our sig figs guide: the addition and multiplication rules taught there (match decimal places; match sig fig count) are not arbitrary. They’re a simplified, digit-counting shortcut for exactly the calculation this page does properly, with real numbers. Example 4 below shows the two converging.

Two Methods, Not One

The simple (worst-case) method.

• Addition and subtraction: add the absolute uncertainties. If y = x₁ + x₂ (or x₁ − x₂), then u(y) = u(x₁) + u(x₂).
• Multiplication and division: add the relative (percentage) uncertainties. If y = x₁ × x₂ (or x₁ ÷ x₂), then u(y)/y = u(x₁)/x₁ + u(x₂)/x₂.

This method assumes the worst case: every input error pointed in the least favorable direction at once. It’s easy to compute by hand, which is why it’s what most intro science courses teach — but it’s deliberately pessimistic.

The quadrature method (the GUM’s actual method).

• Addition and subtraction: combine absolute uncertainties in quadrature. u(y) = √[u(x₁)² + u(x₂)²].
• Multiplication and division: combine relative uncertainties in quadrature. u(y)/y = √[(u(x₁)/x₁)² + (u(x₂)/x₂)²].

This is what the international measurement standard — the GUM (JCGM 100:2008) — actually specifies, under the name the law of propagation of uncertainty. It reflects a real statistical fact: if two error sources are genuinely independent, it’s very unlikely both land at their worst possible value on the same measurement, so the realistic combined uncertainty is smaller than the simple sum.

Quadrature is always smaller than or equal to simple addition. For any two non-negative numbers a and b, √(a² + b²) ≤ a + b, with equality only when one of them is zero. This isn’t a coincidence specific to uncertainty — it’s the same geometric fact that makes the diagonal of a rectangle shorter than the sum of its two sides. Every example below demonstrates it numerically.

Powers. If y = xⁿ, the relative uncertainty scales directly with the power: u(y)/y = |n| · u(x)/x. Squaring a value with 2% relative uncertainty gives a result with 4% relative uncertainty; cubing it gives 6%.

Where this formula actually comes from. The GUM derives both versions from one general formula, for y = f(x₁, x₂, …, xₙ) with independent inputs: uc²(y) = Σᵢ (∂f/∂xᵢ)² · u²(xᵢ) — the sum of each input’s uncertainty, weighted by how sensitively the result responds to that input. This is a first-order Taylor series approximation of the function f, which is why it works cleanly for the simple operations covered here but can break down for strongly nonlinear functions or unusually large uncertainties — in those harder cases, the GUM’s own supplementary guide (JCGM 101:2008) recommends a Monte Carlo simulation instead of the direct formula.

When inputs aren’t independent. Everything above assumes the input uncertainties come from unrelated sources. If two measurements share a common cause of error — the same miscalibrated instrument used for both, for instance — the quadrature formula on its own will underestimate the true combined uncertainty, and a covariance term (GUM Section 5.2) has to be added. This is a real caveat, not a footnote: shared error sources are common in practice, and this is exactly the setting where naive quadrature gives a falsely reassuring answer.

The connection back to significant figures. Our sig figs guide rounds a sum to the fewest decimal places among its terms, and a product to the fewest significant figures. That’s precisely a crude, discrete version of the simple method above — “the least precise input limits the result” — without ever calculating an actual numeric uncertainty. Example 4 makes this explicit.

Worked Examples

Example 1 — Addition: simple vs. quadrature

Values: x₁ = 12.5 ± 0.3, x₂ = 8.2 ± 0.2. Sum = 20.7.

Simple method: u(sum) = 0.3 + 0.2 = 0.5 → 20.7 ± 0.5

Quadrature method: u(sum) = √(0.3² + 0.2²) = √(0.09 + 0.04) = √0.13 ≈ 0.36 → 20.7 ± 0.36

The quadrature uncertainty is about 28% smaller — a real, meaningful difference, not rounding noise.

Example 2 — Multiplication: simple vs. quadrature

Values: x₁ = 5.0 ± 0.2 (4% relative), x₂ = 3.0 ± 0.1 (3.33% relative). Product = 15.0.

Simple method: relative u = 4% + 3.33% = 7.33% → absolute u = 15.0 × 0.0733 ≈ 1.10 → 15.0 ± 1.10

Quadrature method: relative u = √(4%² + 3.33%²) = √(0.16% + 0.111%)… expressed as decimals: √(0.04² + 0.0333²) = √(0.0016 + 0.00111) ≈ 0.0521 (5.21%) → absolute u = 15.0 × 0.0521 ≈ 0.78 → 15.0 ± 0.78

Again quadrature comes in noticeably tighter — roughly 29% smaller than the simple estimate.

Division works identically — it’s the same relative-uncertainty rule, just with the values divided instead of multiplied. For x₁ = 20.0 ± 0.4 (2% relative) divided by x₂ = 4.0 ± 0.2 (5% relative), quotient = 5.0:

Simple method: relative u = 2% + 5% = 7% → absolute u = 5.0 × 0.07 = 0.35 → 5.0 ± 0.35

Quadrature method: relative u = √(2%² + 5%²) = √29% ≈ 5.39% → absolute u = 5.0 × 0.0539 ≈ 0.27 → 5.0 ± 0.27

Example 3 — Powers

Value: x = 4.0 ± 0.1 (2.5% relative uncertainty). Calculate y = x².

Relative uncertainty of y: |2| × 2.5% = 5%. With y = 16.0, absolute uncertainty = 16.0 × 0.05 = 0.8.

Answer: y = 16.0 ± 0.8. Squaring doesn’t just square the value — it doubles the relative uncertainty.

Example 4 — Where sig figs and real propagation meet

Values, using only the implied precision of the written digits: 12.5 (written to 1 decimal place, implying roughly ±0.05) and 8.2 (also 1 decimal place, ±0.05).

Simple method: u(sum) = 0.05 + 0.05 = 0.10 → sum is trustworthy to about ±0.1 Quadrature method: u(sum) = √(0.05² + 0.05²) = √0.005 ≈ 0.07 → sum is trustworthy to about ±0.07

Both land in the same place: trust the first decimal place of the sum, not the second. Compare that to the sig-fig addition rule from our sig figs guide: round the sum to the fewest decimal places among the inputs — here, 1 decimal place either way. The sig-fig rule and the numeric propagation agree, because the sig-fig rule is a shortcut for exactly this reasoning. It just skips calculating an actual uncertainty value and jumps straight to “keep this many digits.” (This “implied uncertainty from the last written digit” is itself a rough convention, not a substitute for a real stated uncertainty — see our earlier gotcha on this — but it’s precisely the assumption sig fig rules are quietly built on.)

Example 5 — Propagating through a real calculation

Scenario: the area of a rectangle, with length L = 5.20 ± 0.05 cm and width W = 3.10 ± 0.04 cm. Area = L × W = 16.12 cm².

Relative uncertainties: u(L)/L = 0.05/5.20 ≈ 0.962%, u(W)/W = 0.04/3.10 ≈ 1.29%.

Simple method: relative u = 0.962% + 1.29% = 2.25% → absolute u = 16.12 × 0.0225 ≈ 0.36 → Area = 16.12 ± 0.36 cm²

Quadrature method: relative u = √(0.962%² + 1.29%²) ≈ 1.61% → absolute u = 16.12 × 0.0161 ≈ 0.26 → Area = 16.12 ± 0.26 cm²

This is what “uncertainty moves through a calculation” actually looks like end to end: two independently measured lengths, each with its own uncertainty, combining into one uncertainty on the derived area — smaller under quadrature, larger under the worst-case method, both defensible depending on what the number needs to guarantee.

Where This Still Trips People Up

• Uncertainties add for subtraction too. It’s tempting to think subtracting two values should partly cancel their uncertainties, since the central values are being subtracted. They don’t. u(x₁ − x₂) = u(x₁) + u(x₂) under the simple method, exactly like addition — the values subtract, but the uncertainties never do.
• Quadrature assumes independence. If two uncertainties share a root cause (the same uncalibrated instrument, the same flawed technique), quadrature alone understates the real combined uncertainty — see the correlated-inputs note above.
• This is a linear approximation. Both methods rest on a first-order Taylor expansion. For strongly nonlinear functions, or uncertainties that are large relative to the measured value, the approximation itself can break down, and a full propagation (Monte Carlo, per JCGM 101:2008) may be needed.
• “Just use the biggest uncertainty” isn’t propagation. Every genuine source of uncertainty contributes some real variance to the result, even the smaller ones — ignoring all but the largest source underestimates the true combined uncertainty, sometimes substantially, as Examples 1 and 2 show.
• Powers use the relative uncertainty, not the absolute one. A common error is applying u(y) = n · u(x) directly to absolute uncertainties; the power multiplies the relative uncertainty, and you convert back to an absolute value afterward — see Example 3.

Which Method Different Contexts Actually Use

Neither method is the “correct” one in general — they answer different questions. The simple method answers “what’s the largest this error could plausibly be if everything went wrong at once?” Quadrature answers “what’s the realistic, statistically expected uncertainty, assuming independent random errors?”

Where the Method Comes From

The quadrature approach isn’t a house convention — it’s the GUM’s (JCGM 100:2008) defined law of propagation of uncertainty, laid out in its Section 5, and it’s what our accuracy/precision pillar refers to as the formal companion to the VIM’s definitions. For the harder case of strongly nonlinear models or non-Gaussian input distributions, the GUM’s supplementary guide, JCGM 101:2008, describes a Monte Carlo alternative — propagating full probability distributions through the calculation by simulation rather than relying on the first-order approximation used here. That level of rigor is outside the scope of a sig figs calculator, but it’s worth knowing the name if a calculation ever demands it.

Common Mistakes

1. Adding absolute uncertainties for a multiplication problem, or relative uncertainties for an addition problem — these are reversed, exactly like the sig-fig arithmetic rules they mirror.
2. Assuming subtraction cancels uncertainty. It doesn’t — see the gotcha above.
3. Reporting the simple (worst-case) result as if it were a realistic statistical uncertainty, when quadrature is what scientific reporting convention actually expects.
4. Ignoring correlation between input uncertainties that share a common source.
5. Applying u(y) = n·u(x) to absolute uncertainty for a power calculation, instead of applying the multiplier to the relative uncertainty first — see Example 3.
6. Treating the biggest single uncertainty as the whole answer, discarding every other real contributing source.

Practice Problems

Concept: Simple method — addition

Q1. Using the simple method, x₁ = 5.0 ± 0.2 and x₂ = 3.0 ± 0.1 are added. What’s the propagated uncertainty? A) 0.1 B) 0.2 C) 0.3 D) 0.22 Answer: C) 0.3 (0.2 + 0.1).

Q2. Using the simple method, what’s the propagated uncertainty when subtracting x₂ from x₁ (same values as Q1)? A) 0.1 B) 0.2 C) 0.3 D) 0 Answer: C) 0.3 — uncertainties add regardless of whether the operation is addition or subtraction.

Concept: Quadrature — addition

Q3. Using quadrature, x₁ = 5.0 ± 0.2 and x₂ = 3.0 ± 0.1 are added. What’s the propagated uncertainty (2 sig figs)? A) 0.30 B) 0.22 C) 0.15 D) 0.10 Answer: B) 0.22 (√(0.2² + 0.1²) = √0.05 ≈ 0.22).

Q4. Why is the quadrature result in Q3 smaller than the simple result in Q1? A) It’s a rounding error B) Quadrature accounts for the statistical unlikelihood of both errors being at their worst simultaneously C) Quadrature only works for multiplication D) They should be identical Answer: B.

Concept: Relative uncertainty and multiplication

Q5. x = 5.0 ± 0.2. What is its relative uncertainty? A) 0.2% B) 2% C) 4% D) 20% Answer: C) 4% (0.2/5.0).

Q6. Using the simple method, x₁ has 4% relative uncertainty and x₂ has 3% relative uncertainty. What’s the propagated relative uncertainty of x₁ × x₂? A) 1% B) 5% C) 7% D) 12% Answer: C) 7% (4% + 3%).

Concept: Quadrature and multiplication

Q7. Using quadrature, x₁ has 4% relative uncertainty and x₂ has 3% relative uncertainty. What’s the propagated relative uncertainty? A) 3% B) 5% C) 7% D) 12% Answer: B) 5% (√(4² + 3²) = √25 = 5 — the same 3-4-5 relationship as a right triangle).

Q8. Why does multiplication propagate through relative uncertainties rather than absolute ones? A) It’s an arbitrary convention B) A product’s sensitivity to each factor scales with the size of the other factor, which normalizes naturally into a percentage C) Absolute uncertainty doesn’t apply to multiplication D) There’s no real difference Answer: B.

Concept: Powers

Q9. x = 4.0 ± 0.1 (2.5% relative uncertainty). What is the relative uncertainty of y = x³? A) 2.5% B) 5% C) 7.5% D) 25% Answer: C) 7.5% (3 × 2.5%).

Q10. Using Q9, with x = 4.0 so y = x³ = 64.0, what is the absolute uncertainty of y? A) 0.1 B) 1.6 C) 4.8 D) 16 Answer: C) 4.8 (64.0 × 0.075).

Simple vs. Quadrature, Same Inputs

Addition: 12.5 ± 0.3 + 8.2 ± 0.2 = 20.7 ± ?

• Simple method → ± 0.50 (wider bar)
• Quadrature method → ± 0.36 (narrower bar)

Multiplication: 5.0 ± 0.2 × 3.0 ± 0.1 = 15.0 ± ?

• Simple method → ± 1.10 (wider bar)
• Quadrature method → ± 0.78 (narrower bar)

Quick Reference

Rule of thumb: quadrature ≤ simple, always. Use simple for a guaranteed worst-case bound; use quadrature for a realistic statistical estimate.

Continue Learning

Related fundamentals:

• Accuracy, Precision, and Uncertainty: What Each One Actually Measures
• Significant Figures: The Complete Guide

Go deeper on one topic at a time:

• Absolute Error vs. Relative Error vs. Percent Error
• What Measurement Uncertainty Actually Is
• How to Read Uncertainty From a Ruler, Burette, or Digital Meter
• How Many Sig Figs Should an Uncertainty Have?
• Reporting Mean and Standard Deviation With Correct Precision
• Why Significant Figures Are a Simplification of Real Uncertainty

Tools:

• Error Propagation Calculator
• Absolute & Relative Uncertainty Calculator

Sources and Further Reading

• JCGM 100:2008, Evaluation of Measurement Data — Guide to the Expression of Uncertainty in Measurement (GUM), Section 5 — the primary source for the law of propagation of uncertainty and the general combined-uncertainty formula used throughout this page. (bipm.org)
• GUM Section 5, Determining Combined Standard Uncertainty (ISO-hosted full text) — confirms the formula’s basis in a first-order Taylor series approximation, cited above for the method’s known limits with nonlinear functions. (iso.org)
• NIST Technical Note 1297, Guidelines for Evaluating and Expressing the Uncertainty of NIST Measurement Results — reused from our accuracy/precision pillar, NIST’s own implementation guide of the same GUM methodology applied here. (emtoolbox.nist.gov)

Review and Methodology

Methodology: All formulas are cross-checked directly against the GUM (JCGM 100:2008) text, not a secondary paraphrase. Every worked example was independently recomputed during drafting. Calculator results referenced on this page use an arbitrary-precision decimal engine, not native floating-point math, validated against the site’s versioned regression fixture set.

Changelog

v1.0 — Initial draft completed, 2026-08-10.

The post Error Propagation: How Uncertainty Moves Through a Calculation appeared first on SignificantFiguresCalculator.

This is the concept that everything else in this silo builds on — Error Propagation is about calculating with these ideas, this page is about actually understanding them first. It matters more than it looks: “precision” and “accuracy” get used interchangeably in casual speech, but they describe genuinely different failure modes with genuinely different fixes. A miscalibrated instrument can produce beautifully consistent, high-sig-fig, completely wrong numbers all day long. Knowing which problem you actually have determines whether the fix is “calibrate the equipment” or “take more measurements” — and those are not interchangeable solutions.

Three Different Properties

Accuracy: closeness to the true value. If the true length of an object is 10.00 cm and your measurement reads 10.01 cm, that’s accurate — it’s close to reality. Accuracy is about correctness relative to something external and (ideally) known.

Precision: closeness of repeated measurements to each other. If you measure the same object five times and get 10.01, 10.02, 10.01, 10.00, 10.01 cm, that’s precise — the numbers agree with each other tightly, regardless of whether they’re actually close to the object’s true length. Precision is entirely internal to the measurement process; it says nothing on its own about correctness.

These are independent. A measurement process can be accurate without being precise (scattered, but centered on the truth), precise without being accurate (tightly clustered, but centered on the wrong value), both, or neither. See Example 1.

Uncertainty: a calculated, honest range of doubt. Where accuracy and precision describe qualities of a measurement process, uncertainty is a specific number attached to a specific result — typically written as a value ± a range, ideally with a stated confidence level. It answers “how far off might this reported number plausibly be?” It is not the same thing as “how many significant figures I happened to write down” — sig figs are a rough, informal stand-in for precision; a real uncertainty is a deliberately calculated quantity. See Example 4.

What actually causes each problem: systematic vs. random error. This is the part most classroom treatments skip, and it’s the part that determines what you actually do about a bad measurement.

• Systematic error is a consistent bias in one direction — a scale that was never zeroed, a ruler with a worn end, a flawed procedure applied the same way every time. It damages trueness (and therefore accuracy), and critically, it does not average out. Every single reading is wrong in the same direction by roughly the same amount, no matter how many times you repeat the measurement.
• Random error is unpredictable scatter — estimating between the smallest marked lines on a ruler, small environmental fluctuations, ordinary human variability in reading an instrument. It damages precision, and it does average out: because random errors are roughly as likely to be too high as too low, taking the mean of many repeated readings makes the average more reliable even though any single reading might still be off.

This is the single most useful practical takeaway on this page: taking more measurements and averaging them fixes a precision problem. It does nothing for an accuracy problem. If your instrument is miscalibrated, averaging a thousand readings from it just gives you an extremely precise, extremely wrong number.

A formal refinement, for anyone working to a real standard. The classroom version above treats accuracy and precision as two independent axes — which is the right mental model for everyday use. Formal metrology, however, defines “accuracy” more narrowly: the international vocabulary of metrology (the VIM, jointly maintained by the BIPM, ISO, and six other international bodies) treats accuracy as the combination of trueness and precision, not a separate third thing. In this stricter usage, a measurement process that’s true on average but wildly scattered isn’t fully “accurate” even though a lucky individual reading might land near the truth — it has good trueness and poor precision, and “accuracy” requires both. This distinction rarely matters for classroom work, but it matters in exactly the industrial and lab-conformance contexts where this site’s ASTM E29 guide also applies.

Worked Examples

Example 1 — All four combinations

True value: 10.00 cm. Four sets of four repeated measurements:

Set B is the dangerous one: every reading agrees with every other reading almost exactly, which feels trustworthy, and every single one of them is wrong.

Example 2 — A closer look at “precise but wrong”

Set B from Example 1: 12.50, 12.51, 12.49, 12.50 cm, against a true value of 10.00 cm.

The spread here is tiny — deviations from the mean of 0, +0.01, −0.01, and 0 cm give a sample standard deviation of roughly 0.008 cm, well under a hundredth of a centimeter. By any statistical measure, this is an excellent, highly precise data set. It is also wrong by 2.50 cm, a 25% error relative to the true value. Writing “12.50 cm” — three significant figures, looking every bit as authoritative as Set A’s correct answer — communicates nothing about this 2.50 cm gap. Sig figs describe precision. They cannot, on their own, tell you whether the instrument was ever calibrated correctly.

Example 3 — Calculating percent error

Calculation: measured value 24.7 g, true/accepted value 25.0 g

Percent error = |measured − true| / true × 100% = |24.7 − 25.0| / 25.0 × 100% = 0.3 / 25.0 × 100%

Answer: 1.2%. This is the standard way accuracy actually gets quantified and reported — a single number describing how far off a result is, as a proportion of the accepted value.

Example 4 — Reporting a value with its uncertainty

Raw data: a calculated value of 12.7346 cm with a calculated uncertainty of 0.0623 cm

Standard metrology guidance (the GUM, JCGM 100:2008, §7.2.6) is to round the uncertainty first — typically to 1 or 2 significant figures — and then match the reported value’s decimal places to it, not the other way around.

Round 0.0623 to 2 significant figures → 0.062 (3 decimal places). Round 12.7346 to the same 3 decimal places → 12.735.

Answer: 12.735 ± 0.062 cm. Reporting more decimal places on the value than the uncertainty justifies — say, 12.7346 ± 0.062 — implies a false precision the data doesn’t actually support.

Example 5 — Why averaging doesn’t fix everything

Scenario: a student measures a table’s length five times with a metal ruler whose zero mark is worn down by 0.5 cm (unknown to the student): 152.3, 152.4, 152.2, 152.3, 152.5 cm.

The small differences between these five readings — 152.2 up to 152.5 cm — are random error: ordinary variation in how precisely a ruler can be read by eye. The consistent 0.5 cm the entire set is offset from the table’s true length is systematic error, caused by the worn zero mark, and it affects every single reading the same way.

Averaging the five readings gives a mean of 152.34 cm — a more reliable, more precise central estimate than any single reading, because averaging cancels out random scatter. It does nothing about the 0.5 cm systematic offset. That error is baked into every measurement this ruler will ever produce, no matter how many times the table gets measured with it.

Where This Still Trips People Up

• A precise-looking number is not the same as a correct one. Three, four, even six sig figs can accompany a measurement that’s simply wrong — see Example 2. Precision and correctness are independent properties.
• “Just take more measurements” only fixes half the problem. It reduces random error beautifully. It does nothing for systematic error — see Example 5. If results are consistently biased, the fix is recalibration or procedural correction, not more repetitions of the same flawed method.
• Casual English blurs accuracy and precision together — “a precision instrument” is often assumed to also mean an accurate one, but precision alone says nothing about whether the instrument was ever calibrated against a true reference.
• An uncertainty isn’t the same as “the last digit is a guess.” Some intro courses use “assume ±1 in the last significant figure” as a rough shortcut, and it’s a reasonable estimate for a single unlabeled reading — but it’s a simplification, not a substitute for an actually calculated uncertainty like the one in Example 4.
• A single lucky reading can look accurate from a bad process. Set C in Example 1 has a correct mean, but any individual measurement drawn from it could be off by half a centimeter. Accuracy of the average is not the same guarantee as accuracy of any one result.

How “Accuracy” Gets Defined Differently

The classroom version is the right mental model for day-to-day sig fig work — it’s simpler and it’s what Example 1’s four-quadrant table above uses. The VIM version matters once you’re working to an actual standard (calibration certificates, lab accreditation, conformance testing), where “accurate” is a defined term with real consequences attached to it.

Where the Definitions Come From

The formal split between trueness, precision, and accuracy comes from the VIM — the International Vocabulary of Metrology, JCGM 200:2012 — jointly maintained by the BIPM, ISO, IEC, and five other international standards bodies specifically so that “accuracy” means the same thing to a lab in Jakarta as it does to one in Geneva. The VIM’s own guidance is explicit that trueness reflects systematic error and is unrelated to random error, which is exactly the causal split covered in this page’s rule statement above. The companion document, the GUM (JCGM 100:2008), governs how the uncertainty number itself gets calculated and rounded once trueness and precision are understood — the mechanics of that calculation are covered in Error Propagation.

Common Mistakes

1. Assuming more decimal places or sig figs means a more accurate result. They only ever imply more precision — see Example 2.
2. Trying to fix a systematic error by averaging more readings. Averaging only helps with random error — see Example 5.
3. Reporting a value’s precision beyond what its uncertainty justifies. If the uncertainty is ±0.06, reporting the value to five decimal places is false precision — see Example 4.
4. Confusing “error” with “uncertainty.” Error is the actual (usually unknowable) difference between a measurement and the truth. Uncertainty is a defensible, calculated estimate of how large that error plausibly is — the two words get used interchangeably in casual speech but mean different things.
5. Treating a single accurate-looking reading as proof the whole process is reliable, when it could simply be a lucky draw from a wide, imprecise scatter.
6. Using “precision instrument” and “accurate instrument” as synonyms — a precise instrument that’s never been calibrated can produce confidently wrong numbers indefinitely.

Practice Problems

Concept: Accuracy vs. precision

Q1. A set of measurements clusters tightly together but far from the true value. This demonstrates: A) High accuracy, low precision B) High precision, low accuracy C) High accuracy and precision D) Low accuracy and precision Answer: B.

Q2. A set of measurements scatters widely but averages out close to the true value. This demonstrates: A) High accuracy, low precision B) High precision, low accuracy C) High accuracy and precision D) Low accuracy and precision Answer: A.

Concept: Formal (VIM) definitions

Q3. In the formal metrology vocabulary (VIM), “accuracy” is best described as: A) A synonym for precision B) A combination of trueness and precision C) Only about repeated measurements agreeing D) Only about the number of significant figures used Answer: B.

Q4. “Trueness,” in the VIM sense, relates most directly to: A) Random error B) Systematic error (bias) C) Rounding error D) Sig fig count Answer: B.

Concept: Systematic vs. random error

Q5. Averaging many repeated measurements primarily helps reduce: A) Systematic error B) Random error C) Both equally D) Neither Answer: B.

Q6. A scale that is never zeroed before use, and so reads 50 g high on every single measurement, is exhibiting: A) Random error B) Systematic error C) Rounding error D) High precision, no accuracy problem at all Answer: B.

Concept: Percent error

Q7. A measured value is 24.7 g against a true value of 25.0 g. What is the percent error? A) 0.3% B) 1.2% C) 3.0% D) 12% Answer: B) 1.2%.

Q8. A measured value is 48 m/s against a true value of 50 m/s. What is the percent error? A) 2% B) 4% C) 96% D) 0.04% Answer: B) 4%.

Concept: Reporting uncertainty

Q9. Per standard metrology guidance, when reporting a value together with its uncertainty, which is rounded first? A) The value B) The uncertainty C) Both, independently and separately D) Neither needs rounding Answer: B.

Q10. An uncertainty is calculated as 0.0623 units. Rounded to 2 significant figures, it becomes: A) 0.06 B) 0.062 C) 0.0623 D) 0.1 Answer: B) 0.062.

The Bullseye, With Real Numbers

• Top-left (accurate + precise): Set A — 9.98, 10.01, 9.99, 10.02 → tight cluster, centered on the bullseye (true value 10.00)
• Top-right (precise, not accurate): Set B — 12.50, 12.51, 12.49, 12.50 → tight cluster, off-center by 2.50
• Bottom-left (accurate on average, not precise): Set C — 9.20, 10.65, 9.85, 10.30 → scattered, but centered on the bullseye
• Bottom-right (neither): Set D — 13.50, 9.50, 12.50, 10.50 → scattered and off-center

Quick Reference

Continue Learning

Related fundamentals:

• Significant Figures: The Complete Guide
• Error Propagation: How Uncertainty Moves Through a Calculation

Go deeper on one topic at a time:

• Absolute Error vs. Relative Error vs. Percent Error
• How to Calculate Percent Error (and Report It Correctly)
• What Measurement Uncertainty Actually Is
• How to Read Uncertainty From a Ruler, Burette, or Digital Meter
• Propagating Uncertainty Through Addition and Multiplication
• How Many Sig Figs Should an Uncertainty Have?
• Reporting Mean and Standard Deviation With Correct Precision
• Why Significant Figures Are a Simplification of Real Uncertainty

Tools:

• Percent Error Calculator
• Absolute & Relative Uncertainty Calculator

Sources and Further Reading

• JCGM 200:2012, International Vocabulary of Metrology — Basic and General Concepts and Associated Terms (VIM), jointly published by the BIPM, ISO, IEC, and five other international bodies — the primary source for the trueness/precision/accuracy relationship described throughout this page. (bipm.org)
• NIST Technical Note 1297, Guidelines for Evaluating and Expressing the Uncertainty of NIST Measurement Results — NIST’s implementation guide of the GUM, cited here for the uncertainty-rounding rule used in Example 4 (reused from our rounding pillar, where it’s also cited for the same underlying GUM guidance). (emtoolbox.nist.gov)
• Cherry Biotech, Accuracy and Precision in Measurements — a clear secondary explainer connecting VIM terminology to the parallel statistical vocabulary (bias and variability) and to ISO 5725. (cherrybiotech.com)

Review and Methodology

Methodology: Definitions and the trueness/precision/accuracy relationship are cross-checked directly against BIPM’s own VIM documentation (see Sources), not inferred from secondary explainers. Calculator results referenced on this page use an arbitrary-precision decimal engine, not native floating-point math, validated against the site’s versioned regression fixture set.

Changelog

v1.0 — Initial draft completed, 2026-08-10.

The post Accuracy, Precision, and Uncertainty: What Each One Actually Measures appeared first on SignificantFiguresCalculator.

This page covers three things the title promises, in the order you’ll actually need them: how to convert numbers into and out of scientific notation, how significant figures work once you’re there (short version — cleanly, which is the whole point), and how to actually do arithmetic in this format without the two mistakes that trip up almost everyone: forgetting to match exponents before adding, and forgetting to renormalize after multiplying. Along the way it also covers e-notation (the “3.5e3” your calculator shows) and engineering notation (the “45 × 10⁶” your electrical engineering textbook prefers) — related formats that are easy to conflate with standard scientific notation but follow different rules.

The Three Notation Formats

Standard scientific notation. Written as a × 10ⁿ, where the mantissa a satisfies 1 ≤ |a| < 10, and the exponent n is any integer — positive, negative, or zero. 3.5 × 10³ = 3,500. 3.5 × 10⁻³ = 0.0035.

E-notation. The exact same concept, written on a single line without superscripts: aEn or aen replaces “a × 10ⁿ.” 3.5E3 and 3.5e3 both mean 3.5 × 10³ = 3,500. This is a typographic convention, not a mathematical one — it exists because early computer displays and plain text couldn’t render a superscript exponent, and it stuck. The “e” here has nothing to do with Euler’s number (e ≈ 2.71828); it’s purely a separator meaning “times ten to the power of.” This is worth stating plainly because it’s a genuinely common point of confusion the first time someone sees a calculator or spreadsheet output “e” instead of “× 10.”

Engineering notation. The same underlying idea, with two added constraints: the exponent must be a multiple of 3 (…,−6, −3, 0, 3, 6, 9,…), and correspondingly the mantissa’s allowed range expands to 1 ≤ |a| < 1000. The payoff for the wider mantissa range is that the exponent now lines up exactly with a named SI prefix — 10³ is kilo, 10⁶ is mega, 10⁻³ is milli — which is why engineering and electronics work generally prefers it over standard scientific notation.

The exponent is always exact. This is worth stating explicitly because it connects directly back to our significant figures guide: the exponent is a defined integer describing magnitude, not a measurement. It never carries uncertainty, is never itself subject to sig fig rounding, and never counts toward — or against — a number’s significant figure total. Only the mantissa’s digits do that.

Orders of magnitude. Loosely, this just means the exponent itself. Two quantities that differ by one order of magnitude differ by roughly a factor of 10; three orders of magnitude apart means roughly a factor of 1,000. It’s a fast way to compare scale without needing exact values — a typical bacterium (on the order of 10⁻⁶ m) and a grain of sand (on the order of 10⁻⁴ m) differ by about two orders of magnitude, meaning the grain of sand is roughly 100 times larger, well before either measurement gets pinned down more precisely.

Worked Examples

Example 1 — Converting to scientific notation

Large number: 45,000,000 → move the decimal point left until one non-zero digit remains before it (7 places) → 4.5 × 10⁷

Small number: 0.0000032 → move the decimal point right until one non-zero digit remains before it (6 places), and the exponent is negative because the original number is less than 1 → 3.2 × 10⁻⁶

Example 2 — Converting back to standard form

From a positive exponent: 3.2 × 10⁵ → move the decimal point 5 places right → 320,000

From a negative exponent: 5.6 × 10⁻⁴ → move the decimal point 4 places left → 0.00056

Example 3 — Significant figures carry over exactly

Number: 5.60 × 10⁴

Only the mantissa’s digits count: 5, 6, 0. The trailing zero counts because it’s written after the decimal point in normalized form — the same Case 3 rule from our zeros guide.

Answer: 3 significant figures. This is also the fix for the ambiguous 45000 case: writing it as 4.50 × 10⁴ instead states, unambiguously, that 3 sig figs were intended — no guessing required.

Example 4 — Multiplication

Calculation: (2.0 × 10³) × (3.0 × 10²)

Multiply the mantissas, add the exponents: (2.0 × 3.0) × 10^(3+2) = 6.0 × 10⁵.

Answer: 6.0 × 10⁵ (600,000). No renormalization needed here since 6.0 already falls within 1–10.

Example 5 — Multiplication that needs renormalizing

Calculation: (5.0 × 10⁴) × (4.0 × 10³)

Multiply and add exponents as before: (5.0 × 4.0) × 10^(4+3) = 20 × 10⁷. But 20 is outside the 1–10 mantissa range, so this isn’t finished — shift the decimal point and adjust the exponent to compensate: 20 × 10⁷ = 2.0 × 10¹ × 10⁷ = 2.0 × 10⁸.

Forgetting this last step is one of the most common errors in scientific-notation arithmetic — the math is right, but the answer isn’t in valid scientific notation until it’s renormalized.

Example 6 — Division

Calculation: (8.0 × 10⁷) ÷ (2.0 × 10³)

Divide the mantissas, subtract the exponents: (8.0 ÷ 2.0) × 10^(7−3) = 4.0 × 10⁴.

Example 7 — Addition: the exponent-matching trap

Calculation: 5.2 × 10⁶ + 3.1 × 10⁵

These have different exponents, so the mantissas cannot be added directly — 5.2 + 3.1 = 7.3 is not a meaningful intermediate step here, and neither 7.3 × 10⁶ nor 7.3 × 10⁵ is correct. Convert to matching exponents first. Rewrite 3.1 × 10⁵ with an exponent of 6: 3.1 × 10⁵ = 0.31 × 10⁶. Now add: 5.2 × 10⁶ + 0.31 × 10⁶ = 5.51 × 10⁶.

Check against standard form: 5,200,000 + 310,000 = 5,510,000 = 5.51 × 10⁶. Confirmed. Unlike multiplication and division, addition and subtraction in scientific notation always require this exponent-matching step first — there’s no shortcut around it.

Example 8 — Raising a scientific-notation number to a power

Calculation: (3.0 × 10²)³

Raise the mantissa to the power, multiply the exponent by that power: 3.0³ × 10^(2×3) = 27 × 10⁶. The mantissa (27) is outside the 1–10 range, so renormalize: 27 × 10⁶ = 2.7 × 10¹ × 10⁶ = 2.7 × 10⁷.

Check against standard form: 3.0 × 10² = 300, and 300³ = 27,000,000 = 2.7 × 10⁷. Confirmed. The same renormalizing habit from Example 5 applies here — raising a mantissa to a power is exactly the kind of step that pushes it outside the valid range.

Example 9 — Converting to engineering notation

Number: 45,000,000 (the same number from Example 1, where it became 4.5 × 10⁷ in standard scientific notation)

Engineering notation needs the exponent to be a multiple of 3. The nearest one at or below 7 is 6, so shift the decimal point to compensate: 45,000,000 = 45 × 10⁶. The mantissa (45) is now outside the 1–10 range that standard scientific notation requires, but well within engineering notation’s 1–1000 range — and 10⁶ maps directly onto the “mega” prefix, so this is also correctly read as 45 megaunits of whatever’s being measured.

Where This Still Trips People Up

• “e” is not Euler’s number. 3.5e3 means 3.5 × 10³ = 3500, full stop. It has no relationship to e ≈ 2.71828, despite using the same letter. This isn’t just a calculator quirk, either — it’s valid floating-point literal syntax in essentially every modern programming language (Python, JavaScript, and C all accept 1e10 directly in source code), which is part of why the convention is worth understanding even outside a calculator display.
• Addition and subtraction always need matching exponents first; multiplication and division never do. These are opposite requirements for the two pairs of operations, and mixing them up (matching exponents before multiplying, or skipping the match before adding) is the single most common scientific-notation arithmetic error. See Examples 4–7.
• A multiplication or division result can land outside the valid mantissa range and need renormalizing before it’s actually finished — see Example 5. An un-renormalized answer like “20 × 10⁷” isn’t wrong arithmetic, it’s just not valid scientific notation yet.
• Engineering notation’s mantissa range is 1 to 1000, not 1 to 10. It’s easy to apply the standard scientific-notation range by habit and “fix” a perfectly correct engineering-notation number like 45 × 10⁶ into something that breaks the multiple-of-3 exponent rule.
• A negative sign on the mantissa and a negative sign on the exponent mean very different things. −4.5 × 10³ is a negative number (−4,500). 4.5 × 10⁻³ is a small positive number (0.0045). Confusing which part carries the minus sign is an easy transcription error with a large effect on the result.
• Calculators don’t all display this the same way — raised superscript exponents, E-notation, and a small “×10” indicator are all common, and some calculators only switch to scientific notation automatically past a certain magnitude threshold. See our software and calculator guide for model-specific behavior.

Comparing the Three Formats

All three formats represent identical values — the difference is purely presentational, driven by what’s easiest to type, read, or map onto a unit prefix in the context you’re working in.

Standards Note

NIST’s own SI style guide devotes dedicated sections to the mechanics covered here: prefix usage and the rules for combining a prefix symbol with a unit symbol are set out in Chapter 6, while the general rules for expressing a quantity’s numerical value — including how many digits are meaningful — are in Chapter 7, the same chapter cited in our zeros guide for the ambiguous-trailing-zero problem this page’s Example 3 resolves.

Common Mistakes

1. Adding or subtracting in scientific notation without matching exponents first — see Example 7.
2. Forgetting to renormalize a multiplication or division result that lands outside the 1–10 mantissa range — see Example 5.
3. Treating the “e” in e-notation as Euler’s number.
4. Applying the wrong mantissa range — using 1–10 where 1–1000 (engineering notation) was called for, or vice versa.
5. Confusing a negative mantissa with a negative exponent — one makes the number negative, the other makes it small.
6. Losing significant figures during conversion — writing 4,500,000 as 4 × 10⁶ when the original data justified 4.5 × 10⁶ (2 sig figs), silently discarding a real digit in the process of reformatting.

Practice Problems

Concept: Converting to scientific notation

Q1. Convert 6,700,000 to scientific notation. A) 6.7 × 10⁵ B) 6.7 × 10⁶ C) 67 × 10⁵ D) 0.67 × 10⁷ Answer: B) 6.7 × 10⁶.

Q2. Convert 0.000045 to scientific notation. A) 4.5 × 10⁻⁵ B) 4.5 × 10⁻⁴ C) 4.5 × 10⁴ D) 45 × 10⁻⁶ Answer: A) 4.5 × 10⁻⁵.

Concept: Significant figures in scientific notation

Q3. How many significant figures does 5.60 × 10⁴ have? A) 2 B) 3 C) 4 D) 5 Answer: B) 3 — the trailing zero in the mantissa counts.

Q4. Which of these unambiguously states 4 significant figures for a value of 32,000? A) 3.2 × 10⁴ B) 3.20 × 10⁴ C) 3.200 × 10⁴ D) 32 × 10³ Answer: C) 3.200 × 10⁴ — four mantissa digits: 3, 2, 0, 0.

Concept: Multiplication and division

Q5. (2.0 × 10³) × (3.0 × 10²) = ? A) 6.0 × 10⁴ B) 6.0 × 10⁵ C) 5.0 × 10⁵ D) 6.0 × 10⁶ Answer: B) 6.0 × 10⁵.

Q6. (8.0 × 10⁷) ÷ (2.0 × 10³) = ? A) 4.0 × 10⁴ B) 4.0 × 10²¹ C) 6.0 × 10⁴ D) 4.0 × 10¹⁰ Answer: A) 4.0 × 10⁴.

Concept: Addition and subtraction

Q7. What has to happen before you can add 5.2 × 10⁶ and 3.1 × 10⁵? A) Nothing — add the mantissas directly B) Convert both to the same exponent first C) Add the exponents together D) Multiply one of them by 10 first, then add exponents Answer: B.

Q8. 5.2 × 10⁶ + 3.1 × 10⁵ = ? A) 8.3 × 10⁶ B) 5.51 × 10⁶ C) 8.3 × 10¹¹ D) 5.2 × 10⁶ Answer: B) 5.51 × 10⁶.

Concept: Engineering notation

Q9. Which of these is correctly written in engineering notation for 67,000? A) 6.7 × 10⁴ B) 67 × 10³ C) 0.67 × 10⁵ D) 670 × 10² Answer: B) 67 × 10³ — exponent 3 is a multiple of 3, and 67 falls within the 1–1000 mantissa range.

Q10. Convert 250,000,000 to engineering notation. A) 2.5 × 10⁸ B) 25 × 10⁷ C) 250 × 10⁶ D) 2500 × 10⁵ Answer: C) 250 × 10⁶.

One Number, Four Formats

Number: 45,000,000

• Standard form: 45,000,000
• Scientific notation: 4.5 × 10⁷
• E-notation: 4.5E7
• Engineering notation: 45 × 10⁶ (= 45 megaunits)

Number: 0.0000032

• Standard form: 0.0000032
• Scientific notation: 3.2 × 10⁻⁶
• E-notation: 3.2E-6
• Engineering notation: 3.2 × 10⁻⁶ (already aligned — exponent −6 is a multiple of 3)

Quick Reference

Format rules:

Arithmetic rules:

Common SI prefixes (engineering notation exponents):

Continue Learning

Related fundamentals:

• Significant Figures: The Complete Guide
• Which Zeros Are Significant? Every Case, Settled

Go deeper on one topic at a time:

• How to Convert Any Number to Scientific Notation
• E-Notation vs Scientific Notation: What 3.5e3 Actually Means
• Engineering Notation vs Scientific Notation
• Adding and Subtracting in Scientific Notation
• SI Prefixes Table with Significant Figure Notes
• Orders of Magnitude Explained
• Scientific Notation on the TI-84 and Casio fx-991

Tools:

• Scientific / E-Notation Converter
• Engineering Notation Converter

Sources and Further Reading

• NIST Guide to the SI, Chapter 6, Rules and Style Conventions for Printing and Using Units — covers SI prefix usage and symbol-combination rules referenced in the Quick Reference table above. (nist.gov)
• NIST Guide to the SI, Chapter 7, Rules and Style Conventions for Expressing Values of Quantities — the same chapter cited in our zeros guide, relevant here for how many digits of a quantity’s numerical value are meaningful. (nist.gov)
• Engineering LibreTexts, 1.3: Scientific and Engineering Notation — an open engineering-education reference confirming the engineering-notation mantissa range (1–1000) and multiple-of-three exponent rule used throughout this page. (eng.libretexts.org)

Review and Methodology

Methodology: Format definitions and worked examples are cross-checked against the NIST and open-education sources listed above. Calculator results referenced on this page use an arbitrary-precision decimal engine, not native floating-point math, validated against the site’s versioned regression fixture set.

Changelog

v1.0 — Initial draft completed, 2026-08-10.

The post Scientific Notation: Complete Guide with Sig Figs, Conversion, and Arithmetic appeared first on SignificantFiguresCalculator.

Significant figures tell you how many digits to keep. Rounding is the mechanical operation you use to actually get there. Our Complete Guide to Significant Figures covers the “how many” question; this page covers the “by what method” question — which turns out to have real, non-obvious answers that different fields, tools, and standards genuinely disagree on. The single most useful thing on this page is probably the negative-number example in Case 3 below: it’s the one place where two methods that look identical for positive numbers quietly diverge, and it trips up more people than any other rounding question.

The 8 Rounding Methods

1. Round half up (toward positive infinity). Look at the first digit being dropped. 5 or more: round up. Less than 5: round down. At an exact tie, this method always moves toward positive infinity — which, for a positive number, means “up” in the everyday sense, but for a negative number means toward the less negative option. This is the method most people mean when they say “normal rounding,” though as Case 3 shows, it’s more precisely defined than that phrase suggests.

2. Round half down (toward negative infinity). The mirror image of half up: at an exact tie, always move toward negative infinity. Rare as a standalone method, but it’s the necessary reference point for understanding the next two.

3. Round half away from zero. At a tie, move to whichever neighbor has the larger absolute value. For positive numbers this behaves exactly like round half up. For negative numbers it does not — it behaves like round half down, because “away from zero” for a negative number means more negative. This is the method Excel and Google Sheets use by default.

4. Round half toward zero. The opposite: at a tie, move to whichever neighbor has the smaller absolute value. Positive numbers behave like round half down; negative numbers behave like round half up. Genuinely rare as a deliberate choice, but useful to know as the fourth point on this compass.

5. Round half to even (“banker’s rounding,” “statistician’s rounding,” “Gaussian rounding,” “Dutch rounding”). At a tie, round to whichever neighbor is an even number. 2.5 rounds to 2 (already even); 3.5 rounds to 4 (the even neighbor). This is the default in IEEE 754 floating-point arithmetic, in Python’s built-in round(), and in NIST’s own laboratory rounding guidance — not because it’s “more correct” in any single case, but because across many values it eliminates the systematic upward drift that half-up rounding introduces. See Example 4.

6. Truncation (round toward zero, unconditionally). Simply discard the extra digits — no evaluation of their value at all. 2.789 truncated to one decimal place is 2.7, not 2.8, even though 2.789 is closer to 2.8. Truncation isn’t really “rounding” in the precision-preserving sense; it’s a deliberate choice to always underestimate the magnitude, and it’s common in contexts like currency display (truncating sub-cent fractions) and low-level computing.

7. Ceiling (round toward positive infinity, unconditionally). Always round up to the next value, regardless of how close the original number is. Used where under-provisioning is the worse failure mode — billing systems that round usage up to the next full unit, for instance.

8. Floor (round toward negative infinity, unconditionally). Always round down. Used where over-provisioning is the worse failure mode, or as the standard method for integer division in many programming languages.

There’s also a ninth, rarer method worth knowing by name: stochastic rounding, which rounds up or down with a probability proportional to how close the number is to each neighbor (a number 70% of the way to the next integer rounds up 70% of the time, at random). It shows up in large-scale numerical computing and machine learning training, where it prevents rounding bias from accumulating across millions of operations — well outside the scope of a sig fig calculator, but worth recognizing the name if you encounter it.

Worked Examples

Example 1 — One number, eight methods

Number: 2.5, rounded to the nearest integer

Three methods give 3; five give 2. This is the single clearest illustration of why “just round it” isn’t a complete instruction.

Example 2 — A non-tie, for contrast

Number: 2.3, rounded to the nearest integer

Every method that evaluates the dropped digit agrees here: half up, half down, half away from zero, half toward zero, half to even, and truncation all give 2. Only ceiling gives 3, because ceiling always rounds up regardless of how close the number actually is. This is the useful baseline: methods only disagree with each other at exact ties (or, for ceiling/floor/truncation, essentially all the time relative to normal rounding) — Example 1’s split is the exception that matters, not the rule.

Example 3 — Negative numbers: where “half up” and “away from zero” split

Number: −2.5, rounded to the nearest integer

Notice that round half up and round half away from zero — which give identical results for every positive number — disagree here. This is the single most common source of “why did my spreadsheet give a different answer than my calculator” confusion. If a method matters for negative data, name it precisely, don’t just say “round half up.”

Example 4 — Why banker’s rounding exists

Numbers: 0.5, 1.5, 2.5, 3.5, 4.5, rounded to the nearest integer

Half up rounds every single tie upward — five out of five, unconditionally. Half to even alternates, because consecutive half-integers alternate between having an even lower neighbor and an even upper neighbor — three down, two up here, and it trends toward an even 50/50 split the longer the sequence runs. Averaged over a dataset with many exact-halfway values (common in currency and instrument readings that land on a clean 0.5 unit), half up’s one-directional rounding introduces a small but real upward drift; half to even’s alternation cancels almost all of it out. That’s the entire justification for banker’s rounding — not that any single answer is “more correct,” but that the aggregate behavior over many values is closer to unbiased.

Example 5 — Double rounding

Number: 0.149, rounded to 1 decimal place

Direct: the second decimal digit is 4, which is less than 5, so round down → 0.1

Two-step (round to 2 decimals, then round that result to 1): 0.149 → 0.15 (third decimal is 9, rounds up) → then 0.15 → 0.2 (second decimal is 5, rounds up)

Direct rounding gives 0.1. Rounding in two stages gives 0.2 — a different answer, from the same starting number, purely because of an intermediate rounding step that shouldn’t have happened. This is exactly why the guard-digit rule in our sig figs guide exists, and it applies to plain rounding just as much as it applies to significant figures.

Example 6 — Decimal places and significant figures are different targets

Number: 1234.567

Rounded to 2 decimal places: look at the third decimal (7), round up → 1234.57 Rounded to 2 significant figures: keep only the first two digits (1, 2); the next digit (3) rounds down → 1200 (better written 1.2 × 10³)

Same number, same instruction word (“round”), wildly different results — because “2 decimal places” and “2 significant figures” are counting entirely different things. See Rounding vs. Significant Figures for the full explanation.

Where the Methods Still Cause Problems

• “Round half up” is not always well-defined for negatives. Some sources use the phrase loosely to mean “round half away from zero.” As Example 3 shows, these genuinely diverge below zero — always name which one you mean if it matters.
• Your spreadsheet and your programming language don’t necessarily agree. Excel’s ROUND() uses half away from zero; Python’s built-in round() uses half to even. The exact same formula, run in two different tools, can give different answers at a tie — not a bug in either one, just a different documented default.
• Ceiling, floor, and truncation diverge from “normal” rounding on almost every number, not just at ties. It’s easy to assume all rounding methods only disagree at the exact halfway point; ceiling and floor actually disagree with round-to-nearest on the vast majority of inputs, since they ignore how close the number actually is.
• Rounding more than once compounds error in a way that’s easy to miss in a multi-stage spreadsheet or database pipeline, where an intermediate value gets displayed (and silently re-stored) at reduced precision before a later calculation uses it. See Example 5.
• Regulatory and contractual contexts sometimes mandate a specific method, removing the choice entirely — tax calculations, billing increments, and lab conformance testing (see below) often specify the rounding method in writing precisely because the “obvious” choice isn’t universal.

How Different Tools and Standards Round a Tie

The practical takeaway: if a rounded answer needs to be reproducible by someone else — a classmate, a colleague, an auditor — state which method you used. “Round half up” alone is ambiguous enough about negative numbers that professional guidance documents spell it out explicitly rather than assuming it’s understood.

Standards Note

It’s worth being precise about what the standards actually say, since it’s easy to assume a named standard mandates one “correct” method. Neither NIST’s GLP-9 nor ISO 80000-1 does this — both are structured as a menu of accepted methods with a requirement to document which one is in use, not a single universal rule. ASTM E29 is different in kind: it’s not primarily about tie-breaking at all, but about how a result gets compared to a written specification limit once its precision is already settled. The full comparison across all of these lives in Rounding Standards Compared: ASTM E29, ISO 80000-1, NIST, and Classroom Rules.

Common Mistakes

1. Treating “round half up” and “round half away from zero” as interchangeable. They agree for positive numbers and disagree for negative ones — see Example 3.
2. Assuming a spreadsheet or programming language rounds the way a textbook does. Excel and Python disagree with each other by default, and neither is “wrong.”
3. Rounding through multiple stages instead of once at the end, introducing double-rounding error (Example 5).
4. Confusing “round to N decimal places” with “round to N significant figures.” These are different operations that can give very different results on the same number (Example 6).
5. Truncating when asked to round, or rounding when asked to truncate. Near a boundary these can diverge by a full unit.
6. Assuming every method only disagrees at the exact halfway point. Ceiling, floor, and truncation diverge from ordinary rounding across most of the number line, not just at ties.

Practice Problems

Concept: Identifying methods

Q1. Which method always moves a tie toward positive infinity — so 4.5 rounds to 5, and −4.5 rounds to −4? A) Round half to even B) Round half up C) Round half away from zero D) Truncation Answer: B. By definition, round half up always moves toward positive infinity at a tie.

Q2. Which method always increases the magnitude at a tie — so 4.5 rounds to 5, and −4.5 rounds to −5? A) Round half up B) Round half away from zero C) Round half toward zero D) Round half to even Answer: B. “Away from zero” means larger absolute value in both directions.

Concept: Banker’s rounding

Q3. Under round half to even, what does 2.5 round to? A) 2 B) 3 C) 2.5 D) It’s undefined Answer: A) 2 — because 2 is the even neighbor.

Q4. Under round half to even, what does 3.5 round to? A) 3 B) 4 C) 3.5 D) It’s undefined Answer: B) 4 — because 4 is the even neighbor.

Concept: Negative numbers

Q5. Under strict round half up (toward positive infinity), what does −2.5 round to? A) −3 B) −2 C) −2.5 D) 0 Answer: B) −2. Toward positive infinity means the less negative option.

Q6. Under round half away from zero, what does −2.5 round to? A) −3 B) −2 C) −2.5 D) 0 Answer: A) −3. Away from zero means the larger-magnitude, more negative option.

Concept: Decimal places vs. significant figures

Q7. Rounding 1234.567 to 2 decimal places gives: A) 1200 B) 1234.57 C) 1230 D) 1234.6 Answer: B) 1234.57.

Q8. Rounding 1234.567 to 2 significant figures gives: A) 1234.57 B) 12 C) 1200 D) 1234.6 Answer: C) 1200 (best written 1.2 × 10³) — a completely different operation from decimal-place rounding.

Concept: Double rounding and truncation

Q9. Rounding 0.149 directly to 1 decimal place gives 0.1. What does rounding it to 2 decimal places first, then to 1, give instead? A) 0.1 B) 0.15 C) 0.2 D) 0.14 Answer: C) 0.2 — a genuine double-rounding error from the intermediate step.

Q10. What’s the key difference between rounding and truncating? A) They’re the same operation B) Truncation only applies to negative numbers C) Truncation discards extra digits regardless of their value; rounding adjusts based on what’s discarded D) Rounding only applies in scientific contexts Answer: C.

One Number, Eight Outcomes

Input: 2.5

• → 3: round half up · round half away from zero · ceiling
• → 2: round half down · round half toward zero · round half to even · truncation · floor

Input: −2.5

• → −2: round half up (toward +∞) · round half toward zero · round half to even
• → −3: round half down (toward −∞) · round half away from zero

Quick Reference

Continue Learning

Related fundamentals:

• Significant Figures: The Complete Guide
• Rounding vs. Significant Figures: Not the Same Thing

Go deeper on one method at a time:

• Round Half Up vs. Round Half Even: Which Does Your Class Use?
• Banker’s Rounding Explained (and Why Excel and Python Disagree)
• Truncation vs. Rounding: When Cutting Digits Is Correct
• Rounding Rules for Negative Numbers
• Round Half Away From Zero vs. Round Half Toward Zero
• The Double Rounding Error That Changes Your Final Answer
• Why Different Calculators Give Different Rounded Answers
• Rounding Standards Compared: ASTM E29, ISO 80000-1, NIST

Tools:

• Rounding Mode Comparator — see all eight methods on one input at once
• Round to N Decimal Places
• Round to N Significant Figures

Sources and Further Reading

• NIST GLP 9 (2019), Rounding — NIST’s laboratory guidance defining three accepted rounding options (even/odd, standard spreadsheet, and always-round-up) and requiring documentation of which is used. (nist.gov)
• ISOBudgets, How to Round Uncertainty to 2 Significant Digits (ISO 17025) — a practitioner explainer cross-referencing how ISO 80000-1, ASTM E29, NIST GLP-9, and the GUM each define conventional and banker’s rounding. (isobudgets.com)
• note.nkmk.me, Round Numbers in Python — technical reference confirming Python’s round() implements round-half-to-even by default, consistent with IEEE 754. (note.nkmk.me)

Review and Methodology

Methodology: Every method definition and worked example above is cross-checked against the primary standards and software documentation listed in Sources. Calculator results referenced on this page use an arbitrary-precision decimal engine, not native floating-point math, validated against the site’s versioned regression fixture set.

Changelog

v1.0 — Initial draft completed, 2026-08-10.

The post Rounding Numbers: Every Method and Rule Explained appeared first on SignificantFiguresCalculator.

Every non-zero digit in a number is automatically significant — nobody argues about whether the “7” in 470 counts. Zero is the only digit that ever needs a rule to settle its status, which is why it causes almost all of the confusion in this topic. Our Complete Guide to Rules, Zeros, and Exceptions covers the five general rules at a summary level; this page goes through every zero scenario in full, including a couple of edge cases — the “100.” convention, and what happens to zeros after a unit conversion — that most references skip entirely.

The 7 Zero Cases

Case 1 — Leading zeros: never significant. Any zero before the first non-zero digit exists only to mark where the decimal point falls. It carries no information about how precisely the number was measured. (Example 1)

Case 2 — Captive zeros: always significant, no exceptions. A zero sitting between two non-zero digits always counts — including strings of several captive zeros in a row. There is no version of this rule with a caveat. (Example 2)

Case 3 — Trailing zeros with a decimal point present: always significant. This holds regardless of the number’s magnitude — whether the whole part is 45 or 0. A zero written after the decimal point, following the last non-zero digit, is there because someone confirmed that position is exactly zero, not because it’s a placeholder. (Example 3)

Case 4 — Trailing zeros with no decimal point: genuinely ambiguous. This is the one real weak spot in plain decimal notation. A whole number’s trailing zeros could reflect an exact measurement or could just be unknown placeholders down to that precision, and the written digits alone don’t say which. NIST’s own SI style guide uses precisely this example: written as 1200 m, it’s simply not possible to tell from the digits whether the last two zeros are significant or only indicate magnitude. (Example 4)

Case 5 — Trailing zeros inside scientific notation: always significant. This is exactly why scientific notation exists — writing a number in the form a.bcd × 10ⁿ makes every digit in the mantissa a deliberate, precision-bearing choice. There’s no ambiguity left to resolve. (Example 5)

Case 6 — The standalone zero: one significant figure, by convention. This case comes up rarely and matters little in practice — a bare “0” is nearly meaningless without a stated uncertainty. More useful to remember: a zero that results from a calculation should still carry whatever decimal places the calculation’s own rules require. (Example 6)

Case 7 — Zeros created by unit conversion: not a simple digit-matching rule. Converting a measurement using an exact factor (say, feet to meters) does not mean “keep the same number of significant figures as before” in every case. What actually has to be preserved is the original measurement’s relative precision — and matching that can mean keeping a different number of digits than a naive sig-fig count would suggest. (Example 7)

The one-line decision path, if you just need the shortcut: Is the zero before the first non-zero digit? Not significant. Is it between two non-zero digits? Significant. Is it after the last non-zero digit? Significant if a decimal point is present anywhere in the number (or you’re already in scientific notation) — ambiguous if not.

Worked Examples — One Per Case

Example 1 — Leading zeros (Case 1)

Number: 0.007060

The “0.00” only marks the decimal position. From the first non-zero digit onward: 7, 0, 6, 0 — the trailing zero counts because a decimal point is present.

Answer: 4 significant figures.

Example 2 — Captive zeros (Case 2)

Number: 40008

Every digit sits between the leading 4 and the trailing 8, so nothing here is a leading or trailing zero — all three zeros are captive and all count: 4, 0, 0, 0, 8.

Answer: 5 significant figures.

Example 3 — Trailing zeros with a decimal point, at two magnitudes (Case 3)

Numbers: 3.20 and 0.0320

3.20 → the decimal point is present, so the trailing zero after the “2” counts: 3, 2, 0. 0.0320 → the leading “0.0” isn’t counted, but from the first non-zero digit onward the same logic applies: 3, 2, 0.

Answer: 3 significant figures, both times. The rule doesn’t change with the number’s size — only the presence of the decimal point and the position relative to the first non-zero digit matter.

Example 4 — Ambiguous trailing zeros (Case 4)

Number: 45000, written with no decimal point and no other context

The two non-zero digits (4, 5) must count. Each of the three trailing zeros might or might not be significant, depending on what was actually measured:

Answer: anywhere from 2 to 5 significant figures — genuinely undecidable from “45000” alone. Whoever recorded this number needs to specify which one they meant.

Example 5 — Trailing zeros in scientific notation (Case 5)

Number: 3.00 × 10⁵

Every digit in the mantissa — 3, 0, 0 — was placed there deliberately.

Answer: 3 significant figures, unambiguously.

Example 6 — The standalone zero (Case 6)

Calculation: 5.00 g − 5.00 g

The raw result is 0, but the addition/subtraction rule still applies: match the fewest decimal places among the inputs, which is 2.

Answer: 0.00 g — not bare “0.” The trailing zeros here communicate how precisely you know the result is zero; they aren’t optional decoration.

Example 7 — Zeros created by unit conversion (Case 7)

Calculation: Convert 36 ft to meters, using the exact factor 1 ft = 0.3048 m

Raw product: 36 × 0.3048 = 10.9728. The naive approach — “36 has 2 sig figs, so keep 2” — gives 11 m. But NIST’s own worked example in its SI conversion guide shows this loses information: the relative rounding error of “36” is about ±1.4%, while “11” carries a relative error of about ±4.5% — more than three times worse. Rounding instead to 11.0 m (3 sig figs) keeps the relative error at about ±0.45%, close to the original measurement’s precision without overstating it.

Answer: 11.0 m — three significant figures, not two, because what matters after a conversion is preserving the original’s relative precision, not mechanically matching its digit count.

Where Even the Rules Get Tested

• One extra zero changes everything. 0.07 has 1 significant figure; 0.070 has 2. It’s a single keystroke, and it’s the difference between “roughly a tenth” and “measured to the nearest thousandth.”
• The decimal-comma trap. Many countries write 1,200 to mean one thousand two hundred, and others write 1.200 to mean the same thing — while yet others use exactly those punctuation marks with the opposite meaning (1.200 as one-point-two-zero-zero, with the period as the decimal marker). If you’re reading data from an international source, confirm which convention it uses before you count a single zero.
• Overline and underline notation don’t survive copy-paste. Some texts mark an ambiguous trailing zero as significant with a bar over it, or underline the last significant digit. Both work fine on a printed page and both routinely vanish when the number is copied into an email, a spreadsheet cell, or a text message — silently reintroducing the exact ambiguity the notation was meant to remove. Scientific notation doesn’t have this failure mode, which is the real reason it has mostly replaced overlines in modern usage.
• Not every zero-containing string is a measurement. A product code, a phone number, or an ID number can be full of zeros with no significant-figures meaning at all. Sig fig rules apply to numbers representing measured or calculated quantities — check that you’re looking at one before you start counting.
• Different tools resolve Case 4 differently by default — see the comparison below, because this one catches people off guard constantly.

How Different Tools and Contexts Handle the Ambiguous Case

Case 4 — a whole number’s trailing zeros with no decimal point — is where “how many sig figs does this have” stops being a question with one universal answer. Here’s how it typically gets resolved in practice. These are general tendencies, not universal rules — when it matters, check the specific source or tool’s own documentation.

This is also exactly why a calculator’s answer and a textbook’s answer can legitimately disagree on a problem involving a number like 100 — neither is “wrong,” they’re using different default assumptions about a case that plain notation leaves genuinely open.

Where the Rules Come From

The ambiguous-trailing-zero problem isn’t a classroom invention — it shows up in NIST’s own official style guide for using the SI, which uses almost the identical example given in Case 4 above to illustrate why plain notation can’t settle the question on its own. The unit-conversion nuance in Case 7 comes from the same document’s worked guidance on rounding converted values. Neither is a rounding-standard deep dive in the way ASTM E29 and the GUM are — those govern rounding procedure once a value’s precision is already known. This page is about the narrower, upstream question: figuring out what a number’s zeros are actually telling you before any rounding starts.

Common Mistakes

1. Assuming all trailing zeros in a whole number are automatically insignificant. This is the mirror image of assuming they’re all significant — both blanket assumptions are wrong. Case 4 numbers are genuinely ambiguous, not secretly one-sided.
2. Dropping a confirmed trailing zero when transcribing data — turning a measured 3.20 into 3.2 and silently discarding real precision information in the process.
3. Treating “0” as having no significant figures, or as undefined. By convention it has one — see Case 6.
4. Missing a regional decimal-comma swap when working with international data or literature.
5. Treating the zeros created by an exact unit conversion as automatically matching the original sig fig count, when the correct answer depends on relative error — see Case 7 and Example 7.
6. Losing overline or underline notation when copying a number between documents, formats, or devices.

Practice Problems

Concept: Leading zeros

Q1. How many significant figures are in 0.0080? A) 1 B) 2 C) 3 D) 4 Answer: B) 2. The leading zeros aren’t counted; 8 and the trailing 0 (decimal point present) both count.

Q2. How many significant figures are in 0.36? A) 1 B) 2 C) 3 D) 4 Answer: B) 2. The “0” before the decimal point is a leading zero and isn’t counted; only 3 and 6 are significant.

Concept: Captive zeros

Q3. How many significant figures are in 40008? A) 2 B) 3 C) 4 D) 5 Answer: D) 5. All three zeros sit between non-zero digits, so all five digits count.

Q4. How many significant figures are in 2.005? A) 1 B) 2 C) 3 D) 4 Answer: D) 4. Both zeros are captive, between the 2 and the 5.

Concept: Trailing zeros with a decimal point

Q5. How many significant figures are in 3.200? A) 2 B) 3 C) 4 D) 5 Answer: C) 4. The decimal point is present, so all three trailing digits after the “3” count.

Q6. How many significant figures are in 0.0500? A) 1 B) 2 C) 3 D) 4 Answer: C) 3. The leading zeros aren’t counted; 5 and the two trailing zeros are (decimal point present).

Concept: Ambiguous trailing zeros

Q7. Written as 90000 with no other context, what’s the most defensible statement about its significant figures? A) Definitely 1 B) Definitely 5 C) Ambiguous — could be 1 to 5 D) Definitely 2 Answer: C. Without a decimal point or scientific notation, this is genuinely undecidable from the digits alone.

Q8. Written as 3000 with no other context, what are the minimum and maximum plausible significant figure counts? A) Min 1, max 4 B) Min 1, max 3 C) Min 2, max 4 D) Min 4, max 4 (fixed) Answer: A. At minimum, only the “3” is confirmed significant; at maximum, all four digits could be exact.

Concept: Zeros from unit conversion

Q9. A rough measurement of 5 kg (1 significant figure) is converted using the exact factor 1 kg = 1000 g, giving a raw value of 5000 g. How should this be reported? A) 5000 g (4 sig figs) B) 5 × 10³ g (1 sig fig) C) 500 × 10¹ g D) 5.000 × 10³ g Answer: B. The conversion factor is exact and doesn’t add precision; the result should still reflect the original measurement’s 1 significant figure.

Q10. In the 36 ft → meters conversion from Example 7, why is the answer reported as 11.0 m (3 sig figs) rather than 11 m (2 sig figs, naively matching “36”)? A) Because 11 m rounds incorrectly B) Because 3 sig figs happens to look better C) Because 11 m’s relative error is much larger than the original measurement’s D) Because meters always get 3 sig figs Answer: C. Matching relative error, not digit count, is what the conversion actually requires — 11 m would discard real precision that 36 ft carried.

Zero Cases at a Glance

DEV NOTE: Render as an annotated-number graphic — green highlight for significant, grey for not significant, amber/striped for the genuinely ambiguous case. Text version below is the content spec for the design/dev team, not final reader-facing copy.

0.00[7][0][6][0] → bracketed digits significant → 4 significant figures (Case 1 + Case 3 combined)

[4][0][0][0][8] → every digit bracketed, none are leading or trailing → 5 significant figures (Case 2)

45000 → four legitimate readings depending on intended precision:

• 4.5 × 10⁴ (amber/ambiguous as written) → 2 sig figs
• 4.50 × 10⁴ → 3 sig figs
• 4.500 × 10⁴ → 4 sig figs
• 4.5000 × 10⁴ → 5 sig figs

Quick Reference

Continue Learning

DEV NOTE: Bake into the WikiWriter import payload at publish time per the music-dictionary.org rule.

Back to the fundamentals:

• Significant Figures: The Complete Guide to Rules, Zeros, and Exceptions

Go deeper on one case at a time:

• Are Leading Zeros Significant? (No — Here’s Why)
• Are Trailing Zeros Significant? It Depends on the Decimal Point
• Captive Zeros: Why Zeros Between Digits Always Count
• Why 1200 Can Have 2, 3, or 4 Significant Figures
• The Overline (Bar) Notation for Ambiguous Trailing Zeros
• Exact Numbers and Why They Never Limit Precision

Related topics:

• Scientific Notation: Complete Guide
• Rounding Standards Compared: ASTM E29, ISO 80000-1, NIST

Tools:

• Significant Figures Calculator
• Sig Fig Counter — with zero-highlighting built in

Sources and Further Reading

• NIST Guide to the SI, Chapter 7, Rules and Style Conventions for Expressing Values of Quantities — NIST’s own official style guide, which directly addresses the ambiguous-trailing-zero problem using an equivalent example to Case 4 above. (nist.gov)
• NIST Guide to the SI, Appendix B, Conversion Factors — the source of the Case 7 / Example 7 reasoning on rounding converted values by relative error rather than simple digit-matching. (nist.gov)
• A2LA, Figuring Out Significance: What Are Significant Figures — a laboratory accreditation body’s explainer connecting these definitions to NIST SP 811 §7.9 and everyday lab practice. (a2la.org)

Review and Methodology

Methodology: Every case above is cross-checked against NIST’s own SI style guide (see Sources). Calculator results referenced on this page use an arbitrary-precision decimal engine, not native floating-point math, validated against the site’s versioned regression fixture set.

Changelog

v1.0 — Initial draft completed, 2026-08-10.

The post Which Zeros Are Significant? Every Case, Settled. appeared first on SignificantFiguresCalculator.

Most people learn significant figures as a single fixed rulebook. In practice, “3 sig figs” can mean slightly different things depending on whether you’re in a general chemistry class, an AP exam, an IB internal assessment, or a materials-testing lab working from ASTM E29. The five counting rules below are universal. What changes across contexts is how rounding is applied on top of them — and that’s usually where students lose points and where lab reports get flagged. This guide covers both: the rules themselves, and where the conventions built on top of them diverge.

Use the calculator below for instant answers with the rule shown, or read on for the full explanation.

Every digit, justified

Significant Figures Calculator

Count, round, or evaluate — and see exactly which rule limited the answer. Handles decimals, scientific notation, and multi-step expressions with full guard digits.

Number or expression Mode Auto-detect Count sig figs Round Evaluate expression

Rounding method Round half up (0.5 → 1) Round half to even (banker's) Round half down Round up (ceiling) Round down (floor) Truncate

Try an example Copy link

0.00456 3 sig figs

0.00456

Significant figures

0.00456 has 3 significant figures.

The five counting rules

Rule	Significant?	Example
Non-zero digits	Always	123 → 3
Captive zeros (between non-zeros)	Always	4008 → 4
Leading zeros	Never	0.00456 → 3
Trailing zeros with a decimal point	Yes	1.200 → 4
Trailing zeros, no decimal point	Ambiguous	1200 → 2 (write 1.200×10³ for 4)

Operation rules

Operation	Rule	Example
Addition / subtraction	Result keeps the fewest decimal places of any term.	41.34 + 1.561 = 42.90
Multiplication / division	Result keeps the fewest significant figures of any factor.	2.5 × 3.42 = 8.6
Multi-step	Keep guard digits; round only at the final step.	(2.0 + 3.0) × 4.00 = 20
Exact numbers	Counted or defined values have infinite significant figures and never limit the result.	π, 100 (defined)

The 5 Rules of Significant Figures

Every significant-figures rule other sources describe is really a restatement of five cases. Learn these five and you can handle anything.

1. All non-zero digits are significant. 1, 2, 3, 4, 5, 6, 7, 8, and 9 always count, no matter where they appear in a number.

2. Zeros between non-zero digits (captive zeros) are always significant. The zero in 205 sits between two non-zero digits, so it counts. 205 has 3 significant figures. This one has no exceptions.

3. Leading zeros are never significant. Zeros that appear before the first non-zero digit only mark the position of the decimal point — they carry no precision information. 0.0056 has 2 significant figures (5 and 6); the three zeros in front of it are not counted.

4. Trailing zeros are significant when a decimal point is present. 25.00 has 4 significant figures. The two zeros after the decimal point are there on purpose — they tell you the measurement was precise enough to confirm those positions are exactly zero, not just unknown. This applies whether the decimal point falls before or after the zeros: 250.0 has 4 significant figures for the same reason.

5. Trailing zeros are ambiguous when no decimal point is present. This is the one genuine weak spot in ordinary decimal notation. Written as 4500, you cannot tell from the digits alone whether this was measured to the nearest thousand (2 sig figs), the nearest hundred (3 sig figs), or the nearest unit with the last two digits happening to be zero (4 sig figs). This isn’t a trick — it’s a real limitation of place-value notation, and it’s the reason scientific notation exists. Writing 4.5 × 10³, 4.50 × 10³, or 4.500 × 10³ states the precision explicitly and removes all doubt.

The exception that sits outside all five rules: exact numbers. Counted items (3 beakers, 12 students) and numbers fixed by definition (60 seconds in a minute; since 1959, exactly 2.54 cm in an inch) are not measurements at all. They carry effectively infinite significant figures and never limit the precision of a calculation they appear in — see Example 6 below.

Significant Figures in Arithmetic

Counting sig figs in a single number is only half the job. The moment you add, subtract, multiply, or divide, a second set of rules takes over — and mixing these two up is the single most common mistake on lab reports (see Common Mistakes below).

Addition and subtraction: match decimal places, not sig fig counts. The result can only be as precise, in absolute terms, as the least precise term you started with. Round the answer to the same number of decimal places as the input with the fewest decimal places — the sig fig counts of the individual numbers don’t matter here at all.

Multiplication and division: match sig fig counts. Here it’s the opposite. Round the result to the same number of significant figures as the input with the fewest significant figures.

Logarithms: match decimal places in the mantissa to sig figs in the original number. This one trips up almost everyone, including some calculators. Because the characteristic (the integer part of a log) only reflects order of magnitude, the sig figs of the original number should show up as decimal places in the mantissa (the part after the decimal point) of the log — not as the total digit count of the log. See Example 7.

In every case: round only once, at the very end. If a calculation has more than one step, carry extra guard digits through the intermediate steps and apply rounding only to the final answer. Rounding after each step compounds error and can change your final digit — sometimes visibly, as Example 5 below shows. This isn’t just a classroom convention; it’s also the explicit guidance in NIST’s own laboratory rounding procedure (GLP 9), which instructs that intermediate values not be rounded before the final uncertainty calculation.

Worked Examples

Example 1 — Counting with leading and trailing zeros

Number: 0.0045600

The leading zeros (0.00) only mark the decimal position and are not significant. Starting from the first non-zero digit, count everything through the end: 4, 5, 6, 0, 0. Because a decimal point is present, those final two zeros count.

Answer: 5 significant figures.

Example 2 — Counting in scientific notation

Number: 7.00 × 10⁶

Scientific notation sidesteps the ambiguous-trailing-zero problem entirely: only digits in the mantissa (7.00) count. That’s 7, 0, 0.

Answer: 3 significant figures. (The exponent never adds or removes sig figs — it just states magnitude.)

Example 3 — Addition

Calculation: 12.11 + 18.0 + 1.013

Raw sum: 31.123. Decimal places in each term: 12.11 has 2, 18.0 has 1, 1.013 has 3. The fewest is 1 (from 18.0), so the answer is limited to 1 decimal place.

Answer: 31.1 — not 31.123, even though that’s what a calculator will display.

Example 4 — Multiplication

Calculation: 6.75 × 3.2

Raw product: 21.6. Sig figs in each term: 6.75 has 3, 3.2 has 2. The fewest is 2, so the answer is rounded to 2 significant figures.

Answer: 22 — the correct rounding of 21.6 to 2 sig figs, not 21.6 itself.

Example 5 — Multi-step calculations and guard digits

Calculation: (12.5 × 3.42) ÷ 1.20

All three numbers have 3 significant figures, so the final answer should too. Here’s what happens with the two approaches:

Correct method — round once, at the end: 12.5 × 3.42 = 42.75 (keep full precision) 42.75 ÷ 1.20 = 35.625 Round to 3 sig figs → 35.6

Common mistake — round after the first step: 12.5 × 3.42 = 42.75 → rounded early to 3 sig figs = 42.8 42.8 ÷ 1.20 = 35.666… Round to 3 sig figs → 35.7

The two methods disagree in the final digit — 35.6 versus 35.7 — purely because of when rounding was applied, not because of any difference in the input data. This is exactly why guard digits matter, and exactly why professional metrology guidance (NIST GLP 9) explicitly prohibits rounding intermediate values before the final result.

Example 6 — Exact numbers

Calculation: 3 identical samples, each weighing 4.52 g. Total mass?

3 × 4.52 g = 13.56 g. The “3” here is a counted, exact number — it has no uncertainty and therefore no sig fig limit of its own. The only real measurement is 4.52 g, with 3 significant figures, so that’s what limits the answer.

Answer: 13.6 g — rounded to match 4.52’s 3 sig figs, not the “1 sig fig” you’d get by mistakenly treating “3” as a measurement.

Example 7 — Logarithms

Calculation: log(2.5 × 10²)

log₁₀(250) = 2.39794. The original number, 2.5 × 10², has 2 significant figures. Because a log’s mantissa (not its total digit count) carries the precision, the mantissa should be rounded to 2 decimal places to match.

Answer: 2.40 — the “2.” is just the order-of-magnitude characteristic and doesn’t count toward precision; only “.40” does, and it correctly reflects 2.5’s 2 sig figs.

Common Exceptions and Gotchas

The five rules cover the ordinary cases. These are the situations where people who know the rules still get tripped up.

• The same digits, three different precisions. 100, 100., and 1.00 × 10² all display the digits “1”, “0”, “0” — but they claim 1, 3, and 3 significant figures respectively (100. with an explicit trailing decimal point signals all three zeros are meant to count). A stray decimal point changes the meaning entirely.
• A “round” measurement isn’t automatically imprecise. If a graduated cylinder marked in 10 mL increments reads exactly 1200 mL, that trailing-zero ambiguity is a real practical problem, not just an academic one — the person recording it needs to write 1.20 × 10³ mL or add a note, or the next person to use that data won’t know how precise it actually was.
• Overline notation exists but is fading out. Some older textbooks put a bar over the last significant digit to resolve ambiguity — 1200 with a bar over the second zero means 3 sig figs are intended. It works on paper but is easy to lose in plain text, copy-paste, or a spreadsheet cell, which is why scientific notation has largely replaced it as the recommended fix.
• Not all constants are exact. Defined constants (60 seconds per minute, 2.54 cm per inch) carry infinite precision. Measured physical constants (like the gravitational constant, G) do not — they were determined experimentally, they have a stated uncertainty, and they do limit the precision of any calculation that uses them. Don’t treat “it’s a constant” as automatically meaning “it’s exact.”
• Zero, alone, has one significant figure. This almost never matters in practice — a measured value of zero is nearly meaningless without a stated uncertainty (0.0 ± 0.1 is very different information from 0.00 ± 0.01) — but it’s a common trick-question case.
• A tool that “shows more decimals” isn’t more accurate. See the note on IEEE 754 below — this is a display/storage artifact, not extra real precision.

How Conventions Differ

The five counting rules and the two arithmetic rules above are universal — nobody disputes them. What differs is how strictly rounding is enforced and what gets layered on top, depending on the setting. These are general tendencies, not official rulebooks — always check your own course’s rubric or your lab’s written procedure for anything graded or compliance-relevant.

A note on software and IEEE 754: IEEE 754 isn’t a significant-figures convention at all — it’s the binary format almost every calculator, spreadsheet, and programming language uses to store decimal numbers internally. It’s the reason 0.1 + 0.2 can display as 0.30000000000000004 in a browser console, and why a spreadsheet sometimes shows 12 digits after a calculation that should only have 3. A tool that respects sig fig rules has to actively round around IEEE 754’s raw output, not follow it. See our software behavior guide for how this plays out in Excel, Python, and calculators specifically.

Where This Comes From

The classroom rules above are taught consistently across chemistry and physics curricula, but two real standards sit behind the professional versions. ASTM E29 (“Standard Practice for Using Significant Digits in Test Data to Determine Conformance with Specifications”) governs how manufacturers and testing labs round a measured value before checking it against a written spec, using one of two defined approaches: the Absolute Method or the Rounding Method. The GUM (Guide to the Expression of Uncertainty in Measurement, published jointly by the BIPM and adopted by NIST) is the international reference for how measurement uncertainty itself should be calculated, rounded, and reported. Neither document is about “significant figures” as classroom shorthand — both are about doing the same underlying thing with the rigor a lab or a manufacturing line needs. The full comparison, with more worked examples from each standard, is in our Rounding Standards Compared guide.

Common Mistakes

If a sig fig answer got marked wrong and you’re not sure why, it’s almost always one of these six:

1. Rounding after every intermediate step instead of only at the end. This compounds small rounding errors and can flip your final digit — see Example 5.
2. Using the multiplication rule (matching sig fig count) on an addition problem, or the addition rule (matching decimal places) on a multiplication problem. These are two different rules for a reason; mixing them up is the single most common error on lab reports.
3. Treating leading zeros as significant. 0.003 has 1 sig fig, not 4.
4. Forgetting that a decimal point changes the trailing-zero rule. 250 and 250. are not necessarily the same claim about precision.
5. Rounding an exact or counted number as if it limited the calculation. “3 trials” is not a 1-sig-fig measurement — it’s an exact count and never limits your answer’s precision.
6. Reporting an uncertainty with more digits than the measurement supports — for example, 12.7 ± 0.34 cm. Standard practice (and the GUM’s own guidance) is to round the uncertainty first, usually to 1–2 sig figs, then match the measured value to it — giving 12.70 ± 0.34 or, more commonly, 12.7 ± 0.3.

Practice Problems

DEV NOTE: Wrap this section in Quiz structured data per Google’s Practice Problems markup — minimum 2 problems per concept is met here (2 per concept × 4 concepts = 8). Each Q/A pair below should render as a click-to-reveal multiple-choice widget, not static text, so it can qualify for the Practice Problems rich result.

Concept: Counting significant figures

Q1. How many significant figures are in 0.03080? A) 2 B) 3 C) 4 D) 5 Answer: C) 4. The leading zeros aren’t counted; starting from the first non-zero digit: 3, 0, 8, 0 — the trailing zero counts because a decimal point is present.

Q2. How many significant figures are in 7.00 × 10⁶? A) 1 B) 3 C) 6 D) 7 Answer: B) 3. Only the mantissa (7.00) counts; the exponent never adds or removes sig figs.

Concept: Zeros

Q3. Which digits in 0.020560 are significant? A) 2 B) 3 C) 4 D) 5 Answer: D) 5. The leading zeros aren’t counted; from the first non-zero digit onward: 2, 0, 5, 6, 0 — all five count.

Q4. A measurement is recorded as 4500 with no decimal point and no other notes. What can you say about its significant figures? A) Exactly 2 B) Exactly 3 C) Exactly 4 D) Ambiguous — could be 2, 3, or 4 Answer: D. Without a decimal point or scientific notation, trailing zeros in a whole number are genuinely ambiguous.

Concept: Addition and subtraction

Q5. What is 12.11 + 18.0 + 1.013, correctly rounded? A) 31.123 B) 31.12 C) 31.1 D) 31 Answer: C) 31.1. The raw sum is 31.123; the fewest decimal places among the terms is 1 (from 18.0), so the answer rounds to 1 decimal place.

Q6. In 154.2 − 3.85, which number limits the decimal places in the answer? A) 154.2 B) 3.85 C) Both equally D) Neither Answer: A) 154.2. It has 1 decimal place versus 3.85’s 2 — the fewest decimal places wins for addition/subtraction.

Concept: Multiplication and division

Q7. What is 6.75 × 3.2, correctly rounded? A) 21.6 B) 22 C) 21 D) 21.60 Answer: B) 22. The raw product is 21.6; 3.2 has the fewest sig figs (2), so the answer rounds to 2 sig figs: 22.

Q8. In 8.314 ÷ 2.0, which number limits the significant figures in the answer? A) 8.314 B) 2.0 C) Both equally D) Neither Answer: B) 2.0. It has 2 sig figs versus 8.314’s 4 — the fewest sig figs wins for multiplication/division.

Significant Figures at a Glance

DEV NOTE: Render as an actual annotated-number graphic (green highlight = significant, grey = not significant). Text version below is the content spec / fallback for accessibility and for the WikiWriter import; the design/dev team should build the visual asset from this spec, not publish the bracket notation as-is.

0.00[4][5][6][0][0] → bracketed digits are significant → 5 significant figures. The unbracketed “0.00” only marks the decimal position.

[7].[0][0] × 10⁶ → all three mantissa digits are significant → 3 significant figures. The exponent is never bracketed — it carries no precision information of its own.

4500 — same digits, three legitimate readings once rewritten:

• 4.5 × 10³ → 2 significant figures
• 4.50 × 10³ → 3 significant figures
• 4.500 × 10³ → 4 significant figures

Quick Reference

Continue Learning

Go deeper on specific rules:

• Which Zeros Are Significant? Every Case, Settled
• Exact Numbers and Why They Never Limit Precision
• Significant Figures in Addition and Subtraction
• Significant Figures in Multiplication and Division
• Significant Figures in Logarithms and pH
• The Overline Notation for Ambiguous Trailing Zeros

Related topics:

• Rounding Numbers: Every Method and Rule Explained
• Round Half Up vs Round Half Even (Banker’s Rounding)
• Rounding Standards Compared: ASTM E29, ISO 80000-1, NIST
• Scientific Notation: Complete Guide
• Error Propagation: How Uncertainty Moves Through a Calculation

Tools:

• Significant Figures Calculator
• Sig Fig Counter

Frequently Asked Questions

Do you count significant figures from the first non-zero digit, or from the decimal point? From the first non-zero digit, always. The decimal point’s position doesn’t affect counting — it only affects whether trailing zeros count (Rules 4 and 5 above).

How many significant figures does the number 0 have? By convention, one. In practice this almost never matters, because a measured zero is only meaningful alongside a stated uncertainty (0.0 ± 0.1 is very different information from 0.00 ± 0.01).

Is 100 one, two, or three significant figures? As written, genuinely ambiguous — it could be any of the three depending on the precision intended. This exact problem is why scientific notation exists.

Do significant figures apply to something like “there are 7 days in a week”? No. Counted and defined quantities are exact numbers with effectively infinite significant figures, and they never limit the precision of a calculation they appear in.

Why does my calculator or spreadsheet show far more digits than my answer should have? Because calculators and spreadsheets don’t track significant figures at all — they compute using whatever binary floating-point precision they have (typically 15–17 digits) and display as many as fit. Rounding to the correct sig figs is a step you (or a sig-fig-aware tool) apply on top of the raw output.

What’s the difference between significant figures and decimal places? Significant figures count all meaningful digits regardless of where the decimal point falls. Decimal places count only digits after the decimal point. 3.14 and 314 both have 3 significant figures but very different decimal-place counts (2 and 0).

Sources and Further Reading

• NIST Technical Note 1297, Guidelines for Evaluating and Expressing the Uncertainty of NIST Measurement Results — NIST’s own implementation guide of the international GUM, covering how measurement uncertainty is evaluated and reported. (emtoolbox.nist.gov)
• NIST GLP 9 (2019), Rounding — NIST laboratory guidance on when and how to round measurement results and their uncertainties, including the even/odd rounding method and the rule against rounding intermediate values. (nist.gov)
• ASTM E29-22, Standard Practice for Using Significant Digits in Test Data to Determine Conformance with Specifications — the industrial standard governing how test results are rounded before being checked against a written specification. (store.astm.org; explainer at astm.org)
• A2LA, Figuring Out Significance: What Are Significant Figures — a laboratory accreditation body’s explainer connecting classroom sig fig rules to NIST SP 811 §7.9 and real lab practice. (a2la.org)

Review and Methodology

Methodology: Rules and worked examples are cross-checked against NIST and ASTM primary sources (see above). All calculator results on this page are generated using an arbitrary-precision decimal engine, not native floating-point math, and are validated against a versioned regression fixture set before any release.

Changelog

v1.0 — Initial draft completed, 2026-08-10.

The post Significant Figures: The Complete Guide to Rules & Zeros appeared first on SignificantFiguresCalculator.