📦 UUEncode/UUDecode - Unix binary-to-text encoding

🔧
⚙️
📝
💡 Examples: Text data, binary data, file contents 💡 Examples: begin 644 filename.txt / encoded lines / end
⚡
📤 
{{ outputText }}
📋
Filename:
{{ fileInfo.filename }}
Permissions:
{{ fileInfo.permissions }} ({{ fileInfo.permissionString }})
Content Length: {{ fileInfo.contentLength }} bytes
📊
Original Size:
{{ stats.originalSize }} bytes
Encoded Size:
{{ stats.encodedSize }} bytes
Overhead: {{ stats.overhead }}%
Lines: {{ stats.lines }}
⚠️ {{ error }}
💡
To Encode: Enter text or binary data to convert to UUEncoded format
To Decode: Enter UUEncoded data (must include begin/end markers)
File Options: Set filename and permissions for proper UUEncode headers
Legacy Format: Compatible with original Unix uuencode/uudecode utilities

ℹ️ About UUEncode/UUDecode

UUEncode (Unix-to-Unix encoding) converts arbitrary bytes into printable ASCII text so older mail, shell, and Usenet workflows can carry file data through text-only channels. This page works as a UUEncode encoder, UUDecode decoder, and quick checker for classic begin/end blocks.

The format is documented by the POSIX uuencode and uudecode utilities, with compatible behavior described in the GNU sharutils manual. Modern Internet mail normally uses MIME transfer encodings from RFC 2045, so UUEncode is best treated as a legacy interoperability format rather than a new protocol choice.

How UUEncoded data is structured:

  • Header line: begin 644 file.txt stores a Unix mode and suggested output filename.
  • Data lines: each line starts with a length character and typically carries up to 45 source bytes encoded as 60 printable characters.
  • Zero-length line: a backtick or space marks the end of encoded data before the final end marker.
  • Six-bit packing: every three input bytes become four printable characters, similar in shape to Base64 but with a different alphabet and wrapper.

Example UUEncode block: 

begin 644 hello.txt
#2&5L;&\@5V]R;&0
`
end

Use this tool when you need to decode an old .uue attachment, inspect a Usenet post, generate a POSIX-style uuencoded sample, or compare UUEncode with Base64, XXEncode, BinHex, and quoted-printable output.

Important limitations:

  • UUEncode is not encryption, signing, compression, malware scanning, or integrity verification.
  • The filename and mode in the header are metadata only; sanitize filenames before saving decoded content.
  • Line wrapping, whitespace changes, or missing begin/end markers can make legacy decoders fail.
  • For new email and web APIs, Base64 from RFC 2045 or RFC 4648 is usually more interoperable.

Processing is local to the page UI unless you call the API endpoint directly; avoid pasting secrets unless you are comfortable with that processing path.

API Usage Example:

POST /api/tools/encoding-decoding/uuencode
Content-Type: application/json

{
    "text": "Hello World!",
    "operation": "encode",
    "filename": "data.txt",
    "permissions": "644"
}
Ready