Convert Gray Code to Hexadecimal

In two logical stages. Stage one converts Gray bits to standard binary: the MSB passes through unchanged, then each subsequent bit is the XOR of the previous output bit with the current Gray bit. Stage two reads that binary as an unsigned integer and renders it in base 16. Gray 1011 → binary 1101 → hex 0xd (decimal 13).

So the semantics are unambiguous. A string like 1011 is a valid 4-bit binary Gray code AND a valid hex number – there’s no safe way to auto-detect which the user meant. This converter treats input as binary always; if you have Gray values already packed in hex form, use the “Gray code to hex” tool in the Hex category which has an explicit hex-input mode.

Yes – and far beyond. The decoder uses JavaScript’s native BigInt, so 256-bit or even 1,024-bit Gray codes produce exact decimal and hex output. Ordinary Number arithmetic would silently round off values past 2⁵³ − 1; BigInt has no fixed upper bound.

Only the case of alphabetic hex digits. With it on, you get 0xDEADBEEF; off, 0xdeadbeef. The 0x prefix itself is always lowercase when included. The underlying value is identical – it’s purely a display preference matching your logging or codebase conventions.

When a downstream formatter will add its own prefix or when you’re pasting into a context that expects bare hex (spreadsheet cell, CSV column, certain C macros like HEX_STR(%02X)). With the prefix off, 0xAF becomes just AF.

Nothing unusual – the tool still works correctly. The hex output shows the minimum nibbles needed to represent the value, so 5-bit Gray 10110 decodes to binary 11011 (decimal 27, hex 0x1b). There’s no forced zero-padding to align to nibble boundaries – the breakdown preserves the original bit width for reference.

Yes. Every byte of processing happens in your browser’s JavaScript runtime – no bytes are uploaded or logged by any server. Open the Network tab in DevTools to confirm no requests fire during conversion. The tool continues to work even after you disconnect from the internet.

This tool is binary-input-only – each line is always interpreted as raw Gray bits. The Hex-category companion has an additional “hex-packed” input mode where each hex digit represents 4 Gray bits (so 0xA means Gray bits 1010). Use this one for bit-level Gray sources like encoder datasheets; use the companion for pre-packed hex Gray streams.

Yes – paste one value per line. The tool processes each independently, so a corrupted line in row 47 becomes one red breakdown row while rows 1-46 and 48-end all convert successfully. The output textarea contains only the successful conversions; the stats row tells you the counts.

Use a hex-to-Gray-code converter. The round trip is lossless because Gray↔binary↔hex is bijective: encode a value to Gray with gray = bin XOR (bin >> 1), decode it back here, and you get the original. Both conversions run in O(n) bit length.