Octal Encoder Decoder
Convert text and byte-oriented octal without hiding invalid groups, ASCII limits, or UTF-8 decoding failures.
Paste normal text to encode, or octal values such as 131 157 162 171 to decode back into readable text.
Conversion Settings
Options
Formatting changes only the representation. Decoding still validates every supplied group instead of silently dropping malformed tokens.
Octal here represents bytes, not characters
One byte ranges from decimal 0 to 255, which is octal 000 to 377. ASCII uses only 0 to 127. UTF-8 can use several bytes for one visible character, so a character such as é or an emoji produces multiple octal groups rather than one “Unicode octal value.”
The byte table therefore describes encoded bytes. Values above 127 are not displayed as if each byte were a standalone Unicode character.
Decoding without guessing past bad input
Separated or escaped values
Inputs such as 131 157 162, 131,157,162, and \131\157\162 have explicit group boundaries that can be validated independently.
Unseparated octal is inherently ambiguous
A stream such as 10112 could be split in more than one way. Three-digit mode accepts complete three-digit byte groups instead of silently choosing a convenient parse.
ASCII and UTF-8 answer different questions
ASCII mode accepts only byte values 0–127. UTF-8 mode accepts the full byte range but requires the complete byte sequence to be valid UTF-8 before it is presented as readable text. Invalid UTF-8 is reported rather than replaced with the Unicode replacement character.
Escaped octal depends on the language reading it
A backslash followed by octal digits is familiar from C-family and Unix tooling, but exact escape grammar varies by language and command. Treat the escaped form here as a byte representation, then check the parser that will consume it. Unix permission values such as 755 are a separate use of base eight and are not byte strings.
Browser boundary
Conversion happens in the browser and no network request is needed by the conversion logic. This page does not interpret chmod permissions or execute octal escapes in a programming language.
Reference point
UTF-8 is defined by RFC 3629. The important boundary here is simple: octal represents byte values; UTF-8 defines how sequences of those bytes represent Unicode text.