Contact

ODD in Excel: Round Away from Zero and Build Odd-Sized Layouts

Math and trigonometry Intermediate Microsoft Excel

Use Excel ODD with signed examples, exact odd boundaries, centered-layout models and clear zero and precision limits.

Verification status: See the evidence and test scope described in this guide. How formula examples are checked

Quick answer: ODD rounds a number away from zero to an odd integer. =ODD(4.2) has expected result 5, and =ODD(-4.2) gives āˆ’5. An input that is already an odd integer remains unchanged.

Availability and version history

  • Introduced: First introduction version is not established by the official history reviewed.
  • Availability: official help lists Excel for Microsoft 365, Excel for Microsoft 365 for Mac, Excel 2024, Excel 2024 for Mac, Excel 2021, Excel 2021 for Mac, Excel 2019, Excel 2016.
  • Checked: October 14, 2026; official ODD reference. Documentation and independently calculated examples; no native Excel execution or broader platform certification.

Syntax and rule

=ODD(number)

The numeric argument is required. Microsoft explicitly describes away-from-zero adjustment for both signs and a #VALUE! error for a nonnumeric argument. This is a parity rule, not ordinary rounding to the nearest whole number.

The signed examples below use English function names and decimal-point numbers. The dedicated reference’s listed examples do not pin the zero-input special case, so this guide does not claim a newly verified native ODD(0) result. The layout model below uses positive sizes.

Example 1: test both signs and an existing odd value

Enter āˆ’4.2, āˆ’3, āˆ’0.2, 0.2, 3, 4.2 in A2:A7. Fill =ODD(A2) down.

Expected results are āˆ’5, āˆ’3, āˆ’1, 1, 3, 5. Negative values increase in magnitude when an adjustment is needed. The exact values āˆ’3 and 3 stay where they are.

A nearest-integer rule would round 4.2 to four, but ODD cannot return four because four is not odd. The requirement chooses the allowed set of outputs before the magnitude direction is applied.

Example 2: compare even and odd targets

=ODD(4.2)
=EVEN(4.2)
=ODD(-4.2)
=EVEN(-4.2)

Expected results are 5, 6, āˆ’5 and āˆ’6. Both functions move away from zero when needed, but they select different parity classes. Neither result is a count of decimal places.

See EVEN for paired-capacity examples. Choose parity from the model rather than substituting one function solely because its result is numerically close.

Advanced example: choose a positive odd number of positions

A fictional one-dimensional display needs a unique center position with equal numbers of positions on either side. For positive minimum sizes 1, 2, 3, 4, 8, use ODD to select capacities.

Expected capacities are 1, 3, 3, 5, 9. For a selected size n, the center’s one-based position is (n+1)/2, giving 1, 2, 2, 3, 5. The number of positions on each side is (nāˆ’1)/2, giving 0, 1, 1, 2, 4.

If D2 contains a requested positive size and E2 contains =ODD(D2), use =(E2+1)/2 for the center. This is a discrete layout model, not a claim about every image-processing or statistical window convention.

Advanced example: define the rounding stage before adding

Two separate displays each require a minimum of four positions. Giving each an odd capacity requires five positions apiece, totaling 10:

=ODD(4)+ODD(4)

One combined display with a minimum of eight positions instead needs odd capacity 9 through =ODD(4+4). These results serve different requirements. Adding first changes the number of centers and the physical arrangement.

Advanced check: applying the rule twice

For the finite control āˆ’4.2, ODD returns āˆ’5 and ODD(ODD(āˆ’4.2)) also returns āˆ’5. An already allowed integer is a fixed point of the documented rule.

This check can catch an implementation that blindly adds one even after reaching an odd integer. It does not establish how every floating-point value near an odd boundary is represented in a native client.

Troubleshooting

Inspect the stored value, sign, requested parity and units. Negative values are legitimate signed numeric controls but are invalid as physical position counts in this example. Keep zero handling, unusual type conversion and extreme magnitudes separately tested instead of inferring them from a few successful positive inputs.

References and verification

Worked inputs are fictional. Decimal answers are independently calculated mathematical expectations rounded to nine places, not captured native results. Extreme magnitudes, complete coercion matrices and cross-version numerical accuracy remain untested.