How to Convert Octal to Decimal by Hand

To convert octal to decimal by hand, multiply each octal digit by 8 raised to its position (rightmost × 8⁰, next × 8¹, and so on) and add the results — 755₈ becomes 7×64 + 5×8 + 5 = 493. Try it in our free number base converter; worked examples, the Unix-permissions connection, and the reverse method are below.

What octal actually is: base 8, digits 0–7

Octal is the base-8 number system: it uses only the digits 0 through 7, and each position is worth eight times the one to its right — exactly as decimal positions are worth ten times the one to their right. The number 755 in octal (written 755₈ to avoid confusion) means 7×64 + 5×8 + 5×1 = 493 in decimal. There is no digit '8' or '9' in octal; the moment you see one, you are not looking at octal. Octal's claim to fame is its tidy relationship with binary: since 8 = 2³, every octal digit corresponds to exactly three bits (0 = 000, 7 = 111). That made octal the compact notation of choice on early 12-bit, 24-bit, and 36-bit machines, where word sizes divided evenly by three. Modern 8-bit bytes favor hexadecimal instead (two hex digits per byte), but octal survives in one place every developer meets: Unix file permissions.

The place-value method: multiply by powers of 8

The method is the same place-value expansion you learned for decimal, with 8 as the base. Step 1: write the powers of 8 above the digits, starting with 8⁰ = 1 at the rightmost: … 512, 64, 8, 1 (that is 8³, 8², 8¹, 8⁰). Step 2: multiply each digit by the power beneath it. Step 3: add the products. For 755₈: 7×64 = 448, 5×8 = 40, 5×1 = 5; 448 + 40 + 5 = 493. The powers of 8 worth memorizing: 8⁰ = 1, 8¹ = 8, 8² = 64, 8³ = 512, 8⁴ = 4096, 8⁵ = 32768. With those six anchors you can convert any octal number you will ever meet by hand — octal rarely exceeds five or six digits outside of textbooks, because real-world octal (permissions, legacy codes) lives in the 1–4 digit range. The method is identical to binary-to-decimal conversion; only the base changes.

Worked examples: 755, 777, 100, and 1234

755₈: 7×64 + 5×8 + 5×1 = 448 + 40 + 5 = 493 — the famous chmod value, decoded below. 777₈: 7×64 + 7×8 + 7×1 = 448 + 56 + 7 = 511 — the maximum three-digit octal value, and a useful sanity anchor (777₈ = 511, just as FF₁₆ = 255). 100₈: 1×64 + 0×8 + 0×1 = 64 — a clean demonstration that '100' in any base equals the base squared. 1234₈: 1×512 + 2×64 + 3×8 + 4×1 = 512 + 128 + 24 + 4 = 668. 17₈: 1×8 + 7 = 15 — note that 17₈ is fifteen, a good reminder that octal digits run out at 7 and the 'teens' start early. Work each example by writing the powers above the digits first; the most common arithmetic slip is misaligning a digit with the wrong power, and the written powers make that impossible.

Why octal exists: 3 bits per digit and Unix permissions

Octal's superpower is the 3-bit grouping: 8 = 2³, so each octal digit is exactly three binary digits — 0 = 000 through 7 = 111. On the PDP-8 and other 12-bit machines, a word was four octal digits, and programmers thought in octal the way modern programmers think in hex. Then bytes standardized on 8 bits, which is not divisible by 3, and hex (two digits per byte) took over — except in Unix permissions, where octal is immortal. chmod 755 means: owner = 7 (111 = read+write+execute), group = 5 (101 = read+execute), others = 5 (101 = read+execute). Each octal digit is one permission triple, readable at a glance: 644 is rw-r--r--, 700 is rwx------, 777 is rwxrwxrwx. You do not need the decimal value (493) to use chmod — but understanding that 755₈ = 493 is what turns the permission digits from magic numbers into a number system you actually comprehend.

Octal to decimal converter: the instant method

By hand builds the mental model; a tool does the arithmetic. Paste any octal value into our free number base converter and get the decimal — plus binary and hex — instantly. Reach for the tool when the octal string is long, when you are verifying homework or exam answers, or when you need the binary expansion alongside (the converter shows all bases at once, which is genuinely useful for permission math: type 755, see 111101101 in binary, and the rwxr-xr-x pattern becomes visible). The by-hand method earns its keep in interviews, exams, and the moment someone asks 'what does chmod 755 actually mean' — being able to say 'each digit is three permission bits; 7 is 111, full access' marks you as someone who understands the system rather than memorizes it. Learn it here, automate it there.

Decimal to octal: the reverse method

To convert decimal back to octal, repeatedly divide by 8 and read the remainders bottom-to-top. Convert 493 to octal: 493 ÷ 8 = 61 remainder 5; 61 ÷ 8 = 7 remainder 5; 7 ÷ 8 = 0 remainder 7. Read the remainders from last to first: 755₈ — and there is our chmod value again, confirming the round trip. Another: 511 ÷ 8 = 63 r7; 63 ÷ 8 = 7 r7; 7 ÷ 8 = 0 r7 → 777₈. And 64: 64 ÷ 8 = 8 r0; 8 ÷ 8 = 1 r0; 1 ÷ 8 = 0 r1 → 100₈. The divide-by-8 loop is the mirror of the multiply-by-powers method — one expands place values, the other peels them off. Our decimal-to-hex guide uses the identical loop with 16 as the divisor; learn one, and you have both. Verify every reverse conversion by converting forward again — two methods agreeing is a confirmed answer.

Octal vs hexadecimal: when each wins

Both are binary shorthand; the winner depends on the word size. Hexadecimal wins for bytes: 8 bits = exactly 2 hex digits, so FF is one byte, FFFF is two — clean, no fractions. The same byte in octal is 377, a three-digit value that crosses byte boundaries awkwardly (the top bit of a byte belongs to a fourth octal digit). Octal wins for 3-bit groups: Unix permissions are three triples, so octal digits map one-to-one onto owner/group/other — hex would need fractional digits. For humans: hex digits A–F are slightly harder to read aloud than octal's 0–7, which is why some legacy systems (aviation transponder codes, for example) stayed octal. The practical rule: think in hex for memory, colors, and bytes (see our binary-to-hex guide); think in octal for permissions and legacy 3-bit-grouped data. And when the numbers get big — file sizes in powers of two — our gigabytes to megabytes converter handles the binary-prefix arithmetic that underlies all of this.

Common mistakes: the digit 8, leading zeros, and base confusion

Three errors account for nearly every wrong octal conversion. Mistake 1: using digits 8 or 9. Octal has no 8 — '18' is not an octal number, and any converter will reject it. If your input contains 8 or 9, you are looking at decimal (or a typo). Mistake 2: misreading leading zeros. In C, Python 2, and many config formats, a leading zero marks octal — 0755 means octal 755 (decimal 493), not decimal 755. Forgetting this has caused real bugs, including the famous permission errors from writing 755 instead of 0755. Mistake 3: converting in the wrong direction. 'Convert 493 to octal' (divide by 8 → 755₈) and 'convert 493₈ to decimal' (multiply by powers → 315) are different questions with different answers — always confirm which base the input is in before starting. When in doubt, sanity-check with anchors: 10₈ = 8, 100₈ = 64, 777₈ = 511. If your method cannot reproduce those three, recheck the arithmetic before trusting anything bigger. All base-conversion guides live on the ToolNest homepage, alongside 130+ free tools.