IEEE 754 Inspector

The IEEE 754 Inspector dissects the binary representation of floating-point numbers according to the IEEE 754-2008 standard, revealing the sign bit, biased exponent field, and significand (mantissa) fraction bits for both 32-bit single-precision (float32) and 64-bit double-precision (float64) formats. It shows the exact decimal value the floating-point representation encodes, the rounding error relative to your input, and correctly handles special values including positive zero, negative zero, positive and negative infinity, quiet NaN, signaling NaN, and subnormal denormalized numbers. This tool is indispensable for debugging floating-point precision limitations in numerical computations.

Browse all Developer tools

How to Use

Enter a decimal number in the input field to see its IEEE 754 bit pattern decomposed into sign (1 bit), exponent (8 or 11 bits), and mantissa (23 or 52 bits) fields displayed as a color-coded binary string. Toggle between single (float32) and double (float64) precision to compare how the same value is represented at different precisions and observe the difference in rounding error. Alternatively, enter a raw 32-bit or 64-bit hex value to decode it into the corresponding floating-point number.

Common Use Cases

• •C, C++, and Rust systems programmers debugging unexpected floating-point behavior by inspecting the exact IEEE 754 bit patterns of computed values to identify precision loss, rounding direction, and ULP errors
• •Computer science educators teaching IEEE 754 floating-point representation by interactively showing students why 0.1 + 0.2 does not equal 0.3 and how the biased exponent and significand combine to represent decimal fractions
• •Embedded systems engineers inspecting float32 register values from hardware debuggers by entering the raw hex value from GDB, J-Link, or OpenOCD output to decode the floating-point meaning
• •Numerical computing and scientific programming developers verifying the behavior of division by zero, overflow to infinity, and NaN propagation in their floating-point arithmetic implementations
• •Game developers and graphics programmers investigating precision artifacts, z-fighting, and floating-point snapping issues by examining the exact bit patterns at different distances from the coordinate origin

Take a break and play free browser games