How this instrument works
Octal is positional notation built on eight symbols, 0 through 7, where each place counts a power of eight instead of a power of ten: the rightmost slot holds ones, the next holds eights, then sixty-fours, then five-hundred-twelves. Eight is two cubed, and that single fact is the whole reason engineers ever bothered with it — every octal digit corresponds to exactly three binary bits with nothing left over, so a long unreadable string of ones and zeros can be split into groups of three from the right and rewritten as one short, human-sized digit string with no ambiguity in either direction.
That three-bits-per-digit property made octal the working notation of early computing, because machine word lengths were often chosen in multiples of three rather than four. Digital Equipment Corporation's PDP-8, released in 1965, used a 12-bit word, and its front panel displayed and accepted values as exactly four octal digits on rows of toggle switches and indicator lamps. The larger scientific mainframes that came just before it, the IBM 7090 (1959) and 7094 (1962), addressed their 36-bit-word memory octally too, with addresses running from 00000 through 77777 — a 15-bit address split cleanly into five three-bit groups, and console lights grouped the same way for operators to read at a glance.
Hexadecimal overtook octal once computing settled on the 8-bit byte as its basic unit, starting with machines like the IBM System/360 and later microprocessors. An 8-bit byte splits evenly into two 4-bit hexadecimal digits, but not into whole 3-bit octal digits — one digit is left straddling a byte boundary. Octal never disappeared, though: Unix inherited it for file permission bits, because read, write and execute naturally form a group of exactly three, and Unix still expresses a permission set as three such triples in a row.
- Enter a whole number into the Decimal number field (x). It arrives preloaded at 64 so you can see a full conversion before changing anything.
- The Octal representation field updates on every keystroke, showing the base-8 digit string for whatever you typed.
- The calculator also lists the division steps behind that answer — each step divides the running quotient by 8 and keeps the remainder as the next octal digit.
- Only 0 or a positive whole number is accepted; a negative entry triggers the message 'Enter a non-negative whole number (0 or more).' and the field will not resolve.
- To go the other way, read the octal digits back to front, multiply each by the matching power of eight (1, 8, 64, 512, and so on) and add the results together.
Worked example — converting 64 to octal
Enter 64 in the Decimal number field. First division: 64 ÷ 8 gives quotient 8 with remainder 0, so the ones-place octal digit is 0. Second division: 8 ÷ 8 gives quotient 1 with remainder 0, so the eights-place digit is also 0. Third division: 1 ÷ 8 gives quotient 0 with remainder 1, so the sixty-fours-place digit is 1, and a quotient of 0 means the process stops there.
Reading those remainders from the last one computed back to the first gives 1, then 0, then 0 — so the Octal representation field shows 100. A quick check confirms it: 1 × 8² + 0 × 8¹ + 0 × 8⁰ equals 64 + 0 + 0, which is 64. Sixty-four is a tidy case to start with, since it is also 2 to the sixth power, but the same three-step division works for any whole number you type in.
Questions
What is the octal number system, in plain terms?
It is counting in base 8 instead of base 10: only the digits 0 through 7 exist, and each column is worth eight times the column to its right — ones, eights, sixty-fours, five-hundred-twelves, and onward. Reaching 8 in octal rolls over the same way reaching 10 does in decimal, so decimal 8 is written 10, decimal 16 is written 20, and decimal 64 is written 100.
Why did early computers rely on octal instead of decimal or hex?
Because eight is two cubed, so one octal digit represents exactly three binary bits with none left over — far easier for a human to read and key in than a long run of ones and zeros. Digital Equipment Corporation's 1965 PDP-8 used a 12-bit word shown as four octal digits on its front-panel switches, and the IBM 7090 and 7094 mainframes addressed their 36-bit memory octally, from 00000 through 77777. Hexadecimal needed 8-bit-byte machines like the IBM System/360 to become the practical standard, since a byte splits evenly into two 4-bit hex digits but not into whole 3-bit octal ones.
Why do Unix and Linux still write file permissions in octal, like chmod 755?
Because a Unix permission set is naturally three groups of three bits: read, write and execute for the file's owner, its group, and everyone else. Each three-bit group maps to a single octal digit worth 4 for read, 2 for write and 1 for execute, added together. Decimal 493 converts to octal 755, and 7-5-5 decodes as owner rwx, group r-x, other r-x — exactly what chmod 755 grants, spelled out in three digits instead of nine bit flags.
How do I convert a decimal number to octal by hand?
Divide repeatedly by 8, writing down each remainder, until the quotient reaches 0 — then read the remainders in the reverse order you found them. Decimal 8 gives one worked step: 8 ÷ 8 is quotient 1, remainder 0; then 1 ÷ 8 is quotient 0, remainder 1. Reading the remainders backward, 1 then 0, gives octal 10. The same steps for any larger number just take more divisions.
What is the largest three-digit octal number, and where does it show up?
It is 777, since each digit tops out at 7. In decimal that is 511, which is 2 to the ninth power minus one — the octal equivalent of decimal 999 being the largest three-digit decimal number. In Unix, permission mode 777 means read, write and execute granted to the owner, the group and everyone else at once, which is why chmod 777 is the well-known shorthand for 'wide open' file permissions, usually flagged as a security mistake rather than a setting anyone should leave in place.
Why did hexadecimal replace octal in most modern computing?
Once the 8-bit byte became the standard unit of memory, hexadecimal fit it perfectly: a byte splits into exactly two 4-bit hex digits with nothing left over. Octal's 3-bit digits do not divide 8 evenly, so a byte written in octal straddles a digit boundary and needs extra bits of padding to look clean. Octal held on wherever bit groups of three still matter, which today mostly means Unix file permissions and a handful of legacy 12-bit and 36-bit systems that never got byte-addressed hardware in the first place.
Does this calculator accept negative numbers or decimals?
No. The Decimal number field expects a whole number of 0 or more; typing a negative value returns the message 'Enter a non-negative whole number (0 or more).' instead of a result. Octal, like decimal and binary, has no single standard way to write digits after a point that this calculator produces, so the input is restricted to non-negative integers to keep every conversion exact.