Convert values across binary, octal, decimal, and hexadecimal, then run bitwise and shift operations. Use it to check encodings and bit masks quickly.
How to validate conversions and bitwise results
Start from the source representation
Pick the base that matches your original value, then confirm the other three views before you touch signed mode or any operator. This makes it obvious whether a mismatch comes from parsing or from later interpretation.
Use bit width intentionally
32-bit and 64-bit modes change the valid range, padding, and the way NOT or shifts are displayed. If you are documenting protocols or packet formats, keep the same width for every comparison run.
Check signed mode separately
Signed view does not change the stored bit pattern. It only changes how the decimal result is interpreted with two's complement, so compare signed and unsigned views side by side when debugging negative values.
Sanity-check bitwise operations
- Use aligned binary output to verify AND, OR, XOR, and NOT at the bit level.
- Confirm whether your shift amount should preserve sign elsewhere before comparing with another tool.
- If a value is out of range for the chosen width, widen the register before trusting the decimal view.
FAQ
Which radices are supported?
Binary, octal, decimal, and hex are supported. Choose the input base and the other representations update instantly.
How can I run bitwise operations?
Choose an operator, then enter the second operand or shift amount. Pick 32-bit or 64-bit width and switch between unsigned and signed (two's complement) interpretation.
Why does the decimal value change when I switch to signed mode?
Signed mode reads the same 32-bit or 64-bit pattern as two's complement. The bits do not change; only the decimal interpretation does.
Why are leading zeros kept in binary and hex output?
Leading zeros make bit width explicit and help you inspect masks, shifts, and register layouts without guessing how many bits are in play.
What happens if my value does not fit the selected width?
The tool flags values outside the chosen width because overflow changes the stored bit pattern. Increase the width or trim the input before comparing downstream results.
How it’s calculated
- The parser reads your value in the selected radix (bin/oct/dec/hex) and stores it as an internal unsigned integer.
- If you choose “signed,” the decimal view interprets the same bit pattern as two’s complement for 32-bit or 64-bit width.
- AND/OR/XOR run on the masked internal value. NOT flips every bit inside the selected width.
- Shift operations move bits and fill with zeros. The signed/unsigned option changes only decimal display, not stored bits.
- Binary, octal, decimal, and hex outputs all come from the same internal value, so the views stay consistent.