How do I use this rounding calculator?

The rounding mode is already selected. Type your value without thousands separators, for example 12.346. 12.346 rounds to 12.35. The original decimal is used directly, avoiding binary floating-point surprises.

What if my number is exactly halfway?

Check the tie rule. Half up moves a positive halfway value upward; Half even selects the nearest even result at a tie. The calculator compares the rules and explains negative values separately.

Is nearest hundredth the same as nearest hundred?

No. A hundredth is 0.01 and uses two decimal places. A hundred is 100 and rounds to a whole-number multiple of 100. A thousandth is 0.001; a thousand is 1,000.

Rounding to the Nearest Hundredth Calculator

The hundredths place is the second digit after the decimal point. Keep two decimal places and inspect the third digit. This page opens on the right rounding mode with a worked example: 12.346 rounds to 12.35. Replace the number with your own and check the named tie rule beside the result.

2 decimal places · half up12.35Rounded up · the ten rules do not all agree

Value

Round to

Places

Ties

Round to a fixed number of digits after the point. A negative count rounds to the left of the point instead: −3 rounds to the nearest thousand.

Half up. Nearest neighbour; an exact midpoint goes up the number line, toward +∞. So 2.5 → 3 and −2.5 → −2. This is what most people were taught at school, and it is not symmetric about zero.

12.346 sits between 12.34 and 12.35, nearer 12.35. There is no tie here, so Half up (like every other nearest-neighbour rule) takes the closer one: 12.35.

Resulthalf up
12.35
Scientifichow many digits are actually claimed
1.235 × 10¹
For codee-notation, ready to paste
1.235e+1
Differencethe answer minus what you typed
+0.004
Grid pointsthe two values your number falls between
12.34 → 12.35
How this was readthe exact decimal these answers are built from
12.346
The exact stored valuewhat a 64-bit float really holds, not the number you typed
12.346000000000000085265128291212022304534912109375

The same number under all ten rules. Where they disagree none of them is wrong; they are different rules, and this is exactly where two spreadsheets quietly stop matching.

Rule	Result	Where you meet it
Half up · your rule	12.35	JavaScript Math.round(), school rounding
Half down	12.35	rare on its own; the mirror of half up
Half to even (banker's)	12.35	IEEE 754 default, Python round(), C# Math.Round(), NumPy
Half to odd	12.35	some signal-processing code; uncommon elsewhere
Half away from zero	12.35	Excel ROUND(), PHP round(), Java BigDecimal HALF_UP, most SQL engines
Half toward zero	12.35	Java BigDecimal HALF_DOWN
Ceiling	12.35	Math.ceil(), Excel CEILING()
Floor	12.34	Math.floor(), Excel INT()
Truncate (toward zero)	12.34	Math.trunc(), Excel TRUNC(), integer casts in C, Go and Rust
Away from zero	12.35	Excel ROUNDUP()

This rounds the number you typed, not the binary copy of it. Ask almost any language for 1.005 to two decimal places and it answers 1.00, because a 64-bit float cannot hold 1.005. What it holds is 1.00499999999999989, a hair below the midpoint, so the tie never happens. The arithmetic here is exact decimal, so 1.005 gives 1.01, and wherever that choice changes the answer this page says so and shows the value actually held in memory.

Common questions

How do I use this rounding calculator?: The rounding mode is already selected. Type your value without thousands separators, for example 12.346. 12.346 rounds to 12.35. The original decimal is used directly, avoiding binary floating-point surprises.
What if my number is exactly halfway?: Check the tie rule. Half up moves a positive halfway value upward; Half even selects the nearest even result at a tie. The calculator compares the rules and explains negative values separately.
Is nearest hundredth the same as nearest hundred?: No. A hundredth is 0.01 and uses two decimal places. A hundred is 100 and rounds to a whole-number multiple of 100. A thousandth is 0.001; a thousand is 1,000.

Exact, with one stated interpretation. All arithmetic is exact-decimal integer division on BigInts, with no floating point anywhere in the answer path, so results are correct to the last digit at any magnitude. Where treating your input as an exact decimal changes the answer, the page says so and shows both.