The most common real-world octal you will ever expand is a Unix permission. Three digits, three audiences — owner, group, others — and each digit is one rwx triple where the three bits are read, write, execute in that order:
755 → 111 101 101 → owner rwx, group r-x, others r-x. The standard for scripts and directories everyone may enter but only the owner may change.
644 → 110 100 100 → owner rw-, everyone else r--. The standard for web files: writable by you, readable by all.
700 → 111 000 000 → owner rwx, nobody else anything. Private keys and personal directories.
One honest limit: octal permissions pack neatly into triples, but general bytes do not — a byte is 8 bits, not a multiple of 3, which is why hex dominates everywhere except this one Unix habit. If you ever need the numeric value rather than the bit pattern, the decimal readout under the result has it (755 octal = 493), and the binary to decimal converter goes further with signed options.
Common Mistakes
- Mistake: reading octal digits as decimal. Octal
755 is not seven hundred fifty-five — it is 7×64 + 5×8 + 5 = 493 in decimal. Correction: check the base before trusting a number; the converter shows both.
- Mistake: dropping leading zeros inside a triple. 5 is
101, not 11 — losing the leading zero shifts every later bit. Correction: each octal digit is exactly 3 bits, zeros included; 10 octal expands to 001 000.
- Mistake: typing 8 or 9 into octal. Correction: those digits do not exist in base 8. If they appear, the number was decimal — the converter flags the exact position rather than converting the wrong thing.
Practice
1. Expand octal 700. 7 = 111, 0 = 000 twice — answer: 111 000 000, owner rwx and nothing for anyone else.
2. What is octal 17 in binary and decimal? 001 111 — decimal 15 (1×8 + 7).
3. Read the permission 640. 6 = 110 = rw-, 4 = 100 = r--, 0 = 000 = --- — owner rw-, group r--, others no access. Verify all three in the converter above.