Next down
—
—
No adjacent representable value is available in that direction.
Inspect IEEE 754 storage for float16, bfloat16, float32, and float64 so you can see sign, exponent, mantissa, rounding error, and the next representable values.
Use this page when the question is how a floating-point value is stored, not just how to rewrite digits. For plain integer base conversion, use the base converter.
Wave 4 dev-data expansion
Choose decimal, hex, or binary input. The copied share URL stores only the selected mode and format, not the input value.
Decimal input lets you see the rounding error introduced by the selected format.
Source value
—
—
—
—
—
—
No adjacent representable value is available in that direction.
—
—
No adjacent representable value is available in that direction.
A base converter rewrites the same integer in a different numeral system. Floating-point inspection is different: the decimal value may need rounding before it fits into the chosen sign, exponent, and mantissa layout. That is why this page shows both the stored value and the rounding error.
The decimal number 0.1 does not have a finite binary expansion. Every binary floating-point format stores the nearest representable value instead. Wider mantissas reduce the error, but they do not make 0.1 exact.
float16 keeps more mantissa bits, so it is usually more precise near 1. bfloat16 keeps the same exponent width as float32, so it reaches much larger and smaller magnitudes with less precision. That trade-off is why bfloat16 appears in modern ML workflows.
When every exponent bit is 1, the value is either infinity or NaN depending on the mantissa. When every exponent bit is 0 and the mantissa is non-zero, the value is subnormal. Signed zero is also real in IEEE 754, so -0 and +0 can have different bit patterns.
A base converter rewrites the same integer into binary, octal, decimal, or hexadecimal. Float inspector shows how a floating-point number is rounded and stored with sign, exponent, and mantissa bits under IEEE 754 rules.
Because 0.1 has no finite binary expansion. The selected format stores the nearest representable binary fraction, which introduces a small rounding error.
float16 keeps more mantissa bits, so it is more precise near 1. bfloat16 keeps the same exponent width as float32, so it preserves a wider dynamic range but with fewer fraction bits.
This page copies a settings-only URL so test values stay out of the address bar, browser history, and shared links. The input remains local unless you copy it yourself.
To reduce load, comments are fetched only when needed.