Convert Gray Code to Octal

In two logical stages. Stage one is Gray → standard binary via the MSB-first XOR chain (binary[0] = gray[0]; then binary[i] = binary[i-1] ⊕ gray[i]). Stage two is binary → octal: group the binary from the right into chunks of 3 bits; each chunk becomes one octal digit 0-7. Example: Gray 111101101 → Binary 101110110 → Octal 566.

Yes. The octal render uses JavaScript’s native BigInt, which has no fixed upper bound. A 256-bit or 1,024-bit Gray code produces its exact octal representation – ordinary Number arithmetic would silently round past 9,007,199,254,740,991 (2⁵³ − 1) and give wrong answers. BigInt prevents that entirely.

Three real use cases. One: Unix file permissions – chmod 755 is still the canonical form. Two: legacy PDP-11/VMS systems and microcontroller datasheets that specify values in octal. Three: compact binary display when hex is too dense – 3-bit octal digits map neatly onto 9-bit or 12-bit fields common in older ADC and DSP hardware.

When enabled and the octal value is 3 or 4 digits, the breakdown shows the symbolic mode string. 755 → rwxr-xr-x, 644 → rw-r--r--, 1755 → rwxr-xr-t (with sticky bit), 4755 → rwsr-xr-x (with setuid). Values of other digit counts are skipped.

The octal output is still correct – it just uses the minimum octal digits needed. 4-bit Gray 1011 decodes to binary 1101 (13), which is octal 15 (two digits). There’s no forced zero-padding to align to 3-bit chunks; if you need padding, prepend zeros to the input manually.

Only that line fails. The tool walks the input line-by-line, so a stray 2 in one row becomes a single red entry (“Line 3: invalid character ‘2’ at position 2”) in the breakdown while every other line still converts. The stats row shows exactly how many succeeded versus failed, and Copy/Download capture only the good results.

Yes. Every byte of processing happens in your browser’s JavaScript engine – nothing is uploaded, logged, or retained by any server. You can open the Network tab in DevTools to confirm: no requests fire during conversion. The page keeps working after you disconnect from the internet.

Only the prefix. 0o755 is the Python 3 / ES6 / Rust literal form that tells a compiler or interpreter “this is octal, not decimal.” 755 is the bare form used by Unix chmod and most shell tooling. The tool’s “Include 0o prefix” toggle lets you choose which your downstream consumer expects.

Yes – the conversion is lossless. Decode a Gray value to octal here, then use an octal-to-binary-to-Gray-code tool (or an octal-to-Gray-code converter) and you’ll recover the original bits. The Gray ↔ binary mapping is bijective, and binary ↔ octal is bijective for any bit width.

Fast. The decoder is O(n) in total bit length and the BigInt octal render is O(digits). 10,000 lines of 64-bit Gray code finish under 100 ms on a modern laptop. The breakdown caps display at 50 rows for layout performance, but the output textarea always contains every successful conversion.