Each character is converted to its ASCII/Unicode code point and then represented in base-8 (octal). Octal values are separated by spaces. Useful in Unix/Linux contexts where octal is commonly used for file permissions. Runs entirely in your browser.
Paste your text and the tool encodes it to UTF-8 bytes, then formats each byte as a 3-digit octal number (000–377). ASCII 'A' becomes 101, ' ' becomes 040, and so on. Multi-byte UTF-8 characters expand into multiple triplets — useful when you need an octal escape sequence for a C string, a Bash printf, or a legacy system that only speaks octal.
Decoder mode reads space-separated or contiguous 3-digit octal numbers and reconstructs the original text. Each octal triplet must be in the range 000–377; values from 400 upwards aren't valid bytes. Malformed UTF-8 sequences fall back to the Unicode replacement character.
A byte (0–255) needs three octal digits because 8^2 = 64 isn't enough — the largest single byte (377 octal = 255 decimal) requires three digits. Output is zero-padded to keep alignment.
Mostly in legacy contexts: Unix file permissions (chmod 755), C string escape sequences (\101), and some embedded toolchains. For most modern uses hex is more practical.
UTF-8 — so 'café' becomes 4 bytes (143 141 146 351 in decimal-formatted octal — actually 143 141 146 303 251 for the UTF-8 ç+é encoding).
The decoder expects 3 digits per byte for unambiguous parsing. If you have non-padded octal, prefix shorter values with leading zeros first.
Explore the full suite of ENCODERS tools and 290+ other free utilities at Chunky Munster.