Skip to main content

UUencode / UUdecode

Encode text or binary data as UUencode format, or decode UUencoded blocks back to the original.

Input
0 chars | 0 bytes
Encode
Output
0 chars | 0 bytes

UUencoding is one of the oldest binary-to-text encodings in the Unix world, developed in the early 1980s to transfer binary files over UUCP (Unix-to-Unix Copy) networks that could only handle ASCII text. You will encounter it in old Usenet archives, legacy shell scripts, and source code that predates MIME. Understanding UUencode is essential for working with historical Unix data.

This tool encodes text or binary data to UUencode format β€” complete with the `begin` and `end` markers and permission mode that define a valid UU file β€” and decodes UUencoded blocks back to their original content. Useful for preserving or migrating legacy archive content, analysing old mail archives, and understanding how binary transfer worked before Base64 became universal.

How to UUencode and UUdecode Online

  1. 1

    Paste Your Input

    Paste text or binary input to encode as a UUencoded block, or paste an existing UUencoded block (including begin and end lines) to decode.

  2. 2

    Encode or Decode

    The tool generates or parses the begin/end marker syntax and validates the block structure.

  3. 3

    Copy the Result

    Copy the encoded block or the decoded content. Useful for legacy email archives, Usenet data, and CTF challenges.

How UUencoding Works

UUencoding converts three input bytes (24 bits) into four output characters, similar to Base64, but uses a different 64-character alphabet. Each 6-bit group is mapped to an ASCII character by adding 32 to its value, putting output characters in the range 32–95 (space through underscore). Each output line is preceded by a length character β€” the number of bytes encoded on that line plus 32 β€” allowing the decoder to determine exactly how many bytes each line represents.

A UUencoded file begins with `begin MODE FILENAME` where MODE is the Unix file permission octet and FILENAME is the original filename, and ends with a line containing a grave accent (`` ` ``) followed by `end`. The filename and permissions are part of the encoding, which makes UUencode slightly richer in metadata than Base64, though this advantage is rarely useful today.

Why Use FileCrank UUencode / UUdecode?

  • βœ“ Generates and parses correct begin/end marker syntax.
  • βœ“ Validates block structure and reports errors clearly.
  • βœ“ Handles legacy email and Usenet UUencoded attachments.
  • βœ“ Runs entirely in your browser β€” no data sent to any server.

Features & Specs

Max File Size
Up to 100 MB
Privacy
Files deleted after about an hour
Price
Free, no signup
Processing
100% client-side
Your data never leaves your browser β€” all processing is local.No account or signup required.Free with no usage limits.

Frequently Asked Questions

What is UUencoding?

UUencoding (Unix-to-Unix encoding) converts binary data to printable ASCII for transmission over text-only channels. Each group of 3 bytes is encoded as 4 printable characters. A UUencoded file starts with a begin [permissions] [filename] line and ends with an end line.

Is UUencode still used today?

Rarely, but it does still appear in legacy email archives, old Usenet posts, and occasionally in CTF security challenges. Modern email uses MIME with Base64 encoding.

What is the difference between UUencode and Base64?

Both convert binary to printable ASCII but use different character sets and line formats. UUencode uses characters with ASCII values 32–95. Base64 uses A–Z, a–z, 0–9, +, and /. UUencode includes begin/end headers; Base64 typically does not.

My UUencoded block gives a decode error β€” what is wrong?

Common issues: missing begin or end line, corrupted line-length characters (first character of each line encodes the line length), or non-printable characters introduced by line-ending conversion. Paste the exact block including begin and end lines.

UUencode vs. Base64 vs. MIME

UUencode is historically significant but obsolete for new work. Base64 is strictly superior: it is more widely implemented, has a cleaner alphabet that avoids the space character (which caused corruption in some mail systems), and is defined in MIME standards that every modern email client and HTTP library understands. Use this tool to read legacy data rather than to produce new encodings β€” for any new binary-to-text need, Base64 is the right choice.

FileCrank UUencode / UUdecode encodes and decodes UUencoded blocks including begin/end marker syntax, useful for legacy email, Usenet archives, and CTF challenges.

Advertisement

Ad