Overview
Enter one or more octal-encoded byte values - separated by spaces or commas, like "110 151" - and get the equivalent Base64 string, "SGk=". Each token is treated as a single byte written in octal, not as a digit of one giant octal integer: "110 151" is the two separate bytes 72 and 105 (spelling "Hi" in ASCII), converted directly to Base64, the exact inverse of what the Base64 to Octal Converter produces. Every token is validated twice - first that it only contains valid octal digits (0-7; an "8" or "9" anywhere is rejected immediately as not octal at all), then that its decoded value actually fits in a byte, 0-255 (octal 0-377) - a token like "400" is made entirely of valid octal digits but decodes to 256, one past the maximum, so it is rejected rather than silently truncated or wrapped. Runs entirely client-side.
Best for: Converting octal-dumped byte values (from a debugger, hex editor in octal mode, or legacy log) into Base64
How to use this tool
- Enter octal byte values. Space or comma-separated, like "110 151" - each token is one byte.
- Each token is validated. Only digits 0-7 are allowed, and the decoded value must fit in a byte (0-255 / octal 0-377).
- Bytes are encoded to Base64. The validated byte sequence is Base64-encoded directly, with no intermediate text step.
- Copy the result. The Base64 output has its own copy button.
Frequently asked questions
Because octal byte dumps represent a sequence of independent bytes, not a single numeric value - "110 151" is the two bytes 72 and 105 (spelling "Hi"), not the much larger integer you would get by parsing "110151" as one octal number. This tool follows the byte-sequence convention, matching the reverse Base64 to Octal Converter.
Every character in "400" (4, 0, 0) is a valid octal digit, but the token as a whole decodes to 256 in decimal - one past 255, the highest value a single byte can hold. A byte can never represent 256, so accepting it would mean silently truncating or wrapping to an incorrect value; it is rejected instead.
"128" contains the digit 8, which is not a valid octal digit (octal only uses 0-7) - it is rejected at the character-validation stage, before the byte-range check even runs.