What Is a UUE File? Binary Data Wrapped in Text, and How to Decode It
UUE files are binary files that uuencode turned into text. We tested no file, so every fact comes from public pages that we name. Jump to your question below, or work through it in order.
What Is a UUE File? Binary data turned into text
Short answer
UUE files are binary files that uuencode turned into text. You must decode one to get your original back.
We tested no UUE file, because we had no sample and no decoder session. Every fact on this page comes from public pages that we name and link.
To get your file back, use the open steps. For the command line, use the decode steps. If your file will not open, begin with the causes.
UUE files are binary files that uuencode turned into text. You must decode one to get your original back. We tested no UUE file for this page, so every fact below comes from public pages that we link.
Picture an old email with a block of odd letters and symbols in the body. That block was a file. FileInfo says the ending stands for Unix to Unix Encoding, and that people used it to send documents by email without damage.
Mary Ann Horton wrote uuencode and uudecode at UC Berkeley in 1980, per Wikipedia. The name comes from Unix to Unix Copy. MIME has largely replaced it, and we cover that in the Base64 part.
Our ZIP file page covers the archive type that people compare to text wrapped files. A UUE file wraps one file in text, and a ZIP file packs many files in binary.
Where You Meet One Today
Email and Usenet posts used the format, per Wikipedia. Archives of that mail can still contain it. Names like report.uue are only examples, so look at the first lines of any odd text file.
You can also meet it as text inside a message body. Then no .uue file exists. Copy the text from the begin line to the end line into a new file before you decode it.
How we wrote this page
We made no test for this page. We had no UUE file and no decoder session that we could use. Our other pages show lab results, and this one does not.
Every fact comes from a page that we name. The sources are FileInfo, Wikipedia and the Linux man pages for uuencode and uudecode. We checked them all on 7 November 2026.
UUE File Facts at a Glance
| Property | Value |
|---|---|
| Meaning | Unix to Unix Encoding, a text form of a binary file, per FileInfo. |
| Ending |
The ending is .uue.
|
| Made by | The uuencode tool, first written by Mary Ann Horton in 1980, per Wikipedia. |
| Opened with | WinZip on Windows, Archive Utility on Mac and uudecode on Linux, per FileInfo. |
| Encoding | Three bytes become four printable characters, per Wikipedia. |
| Size | About a third bigger than the original, per Wikipedia. |
| Replaced by | Base64 in MIME for most mail, per Wikipedia. |
| Our tests | None. We had no UUE file and no decoder session. |
Is it a mail file and not an encoded attachment? The EML file page and the MBOX file page cover two mail formats.
How Does UUencoding Work? Three bytes in and four characters out
UUencoding splits every three bytes into four 6 bit values and adds 32 to every value. The result is four printable characters. Wikipedia gives the method, and we encoded no file ourselves.
The method is short. Wikipedia describes it in a few lines, and our figure shows every stage from bytes to characters.
Three Bytes Become Four Characters
- Take three bytes of your file. That is 24 bits.
- Split the 24 bits into four groups of 6 bits.
- Treat every group as a number from 0 to 63, and add 32.
- Write the character for that number. The characters range from a space to an underscore.
A Worked Example
Wikipedia encodes the letters Cat. The result is #0V%T. Its first character, #, means three bytes follow. Four more characters stand for those letters.
The Zero Rule
Zero values would become spaces, and spaces can vanish in mail. Wikipedia says encoders write a backtick for zero, and some use a space.
Why 32 Is Added
Raw 6 bit values from 0 to 63 include control codes that mail systems can drop. Adding 32 moves every value into printable characters. Wikipedia says results range from a space to an underscore, which gives 64 characters.
Line Length and the Letter M
Full lines have 45 bytes, which become 60 data characters. The count 45 plus 32 gives 77, which is the letter M. That is why many lines start with M, and you can spot UUE text from far away.
Padding at the End
Files seldom end on a three byte boundary. Wikipedia says encoders subtract padding bytes from the count, so decoders add no extra output.
The Cat Example in Numbers
Our arithmetic shows how. The letters C, a and t are hex 43, 61 and 74. Their 24 bits split into the values 16, 54, 5 and 52. Adding 32 gives 48, 86, 37 and 84, which are the characters 0, V, % and T.
A count of three bytes plus 32 gives 35, which is the character #. That is why this text starts with #. We worked it out on paper and tested no tool.
A method, not a test. The steps come from Wikipedia. We encoded no file to compare.
What Is Inside a UUE File? A begin line, data lines and an end line
UUE files have a begin line, many data lines and an end line. Begin lines give mode and file name. Every data line starts with a length character. Wikipedia and the man pages give the parts.
A text editor shows this layout. Follow the figure for parts, then use the table for details.
The Parts, Line by Line
| Part | What the sources say |
|---|---|
| Begin line |
The word begin, then the file mode in three octal digits, then the name for the restored file. An example is begin 644 cat.txt.
|
| Length character | Every data line starts with one. It is the byte count plus 32. |
| Full lines | Most full lines have 45 bytes. Their length character is the letter M. |
| Padding | The count leaves out padding bytes, so the decoder adds no extra output. |
| Zero length line | A line with a zero count comes before the end line. |
| End line | The word end closes the file. |
A Tiny File, Line by Line
begin 644 cat.txt
#0V%T
`
end
Line one is a begin line. Line two has three letters, Cat, with # for a count of three. The backtick line has zero length. The last line closes the file.
The Base64 Variant
The man page for uuencode describes the -m option. It writes MIME Base64 data. The first line starts with begin-base64, and the last line is four equal signs.
Parts from public pages. We opened no UUE file. A file from another tool can differ from the example, so open yours in a text editor.
Why Do UUE Files Exist? Email and Usenet could not pass raw bytes
Binary files broke on email and Usenet, because many systems could not pass 8 bit data. UUencoding changed them into safe text. Wikipedia says mail systems later passed 8 bit data without trouble, and MIME largely replaced the format.
Wikipedia says the tool let binary files, especially compressed ones, survive email and Usenet posts. Systems that could not pass 8 bit data could corrupt raw bytes, so the text form was the safe choice.
Who Wrote It and When
Mary Ann Horton wrote uuencode and uudecode at UC Berkeley in 1980, per Wikipedia. The name comes from Unix to Unix Copy, and the tools came first for mail between Unix machines.
Why the Text Form Worked
Printable characters passed through mail systems unchanged. The cost was size, which we cover in the size part.
Why You Meet It Less Today
Want the steps now? See how to open a UUE file.
How Do You Open a UUE File? Decode it with a program for your system
Open a UUE file by decoding it. FileInfo lists WinZip on Windows, Apple Archive Utility on Mac and the uudecode command on Linux. We opened no file, and we list no menus because we tested no program.
FileInfo names the programs for every system. StuffIt Deluxe is on its lists too, and FileInfo calls it discontinued. Choose the program for your system from the table.
| System | Program |
|---|---|
| Windows | WinZip. FileInfo calls it a free trial. StuffIt Deluxe is listed as paid and discontinued. |
| Mac | Apple Archive Utility, which comes with macOS. StuffIt Deluxe for Mac 16 is listed as discontinued. |
| Linux | The uuencode and uudecode commands, which FileInfo says come with the system. |
Why a Text Editor Helps
UUE files are text, so any text editor opens them. You see a begin line first, with a mode and a file name. That name shows the type of file inside before you decode anything.
Four Steps That Work for Any Program
- Copy the UUE file, and keep the original untouched.
- Open the copy in a text editor. Check for a begin line at the top.
- Choose a program from the table, and decode the copy into an empty folder.
- Open the new file in the program that matches its ending.
We list no menu names, because we tested none of these programs. FileInfo also names a web based decoder. We link none, and you should not upload private files to a site you do not know.
How Do You Decode a UUE File on Linux? One command and one option
On Linux and Mac terminals, uudecode followed by a file name decodes UUE files. Option -o sets another output name. The man page says uudecode overwrites an existing file if you can write to it.
The man page for uudecode gives this syntax. We used no command. The page lists exit status 0 for success.
uudecode file.uue
uudecode -o restored.pdf file.uue
A Safer Command Habit
List your folder before you decode. Look for a file with the name from the begin line. If one exists, move it away, or use -o with another name. Then decode.
What the Command Does
Exit Status in Scripts
Scripts can test exit status. Zero means success, and anything higher means error, per the man page. Check status before you open decoded output.
Syntax Notes
A file name is optional. Without one, uudecode takes standard input, per the man page. That lets you pass encoded text from another command straight in.
Send the Output to the Screen
The option -o with /dev/stdout sends the decoded content to standard output. Use that to pass the data to another command.
Syntax, not a session. The man page gives the syntax and the rules. We used no command, and your system can differ.
How Do You Make a UUE File? The uuencode command and its Base64 option
Uuencode makes text forms of files. Syntax is uuencode, then an optional -m, then your file, then a name to restore. Output goes to standard output, so use a redirect to save it.
The man page for uuencode gives this syntax. We used no command, so our example follows syntax and not a test.
uuencode report.pdf report.pdf > report.uue
uuencode -m report.pdf report.pdf > report.b64.uue
Check Your Output
Open the new text in an editor after you encode. Look for a begin line, data lines and an end line. If all three are present, the text is ready to send.
The Two Arguments
First comes your file to encode. If you leave it out, uuencode takes standard input. Second comes a pathname that uudecode uses when it restores your file.
The Base64 Option
Option -m switches from old encoding to MIME Base64. The man page says Base64 uses a 64 character alphabet plus an equal sign for padding, with lines of 76 characters or fewer.
Check the Receiver First
Wikipedia says MIME has largely replaced the format. Check what the receiver needs before you encode a file.
What Does the UUE Begin Line Control? The file name, the mode and overwrites
A begin line names the file that uudecode makes and sets its mode. The man page says that name comes from encoded data, and the option -o replaces it. Mode bits come from data too, and umask does not apply.
The uudecode manual gives these rules. A text editor shows the begin line, which is first in the data.
| Item | What the page says |
|---|---|
| Output name | The target pathname comes from the encoded data. The option -o overrides it. |
| Mode bits | They come from the permission bits in the data. The umask does not apply. |
| Mode errors | If uudecode cannot set the mode, that is not treated as an error. Standard output is the exception. |
| Existing file | With write permission, uudecode overwrites it. Without write permission, it fails. |
| Standard output | A name of - or /dev/stdout in the data sends the content to standard output. |
What 644 Means
The begin line stores the mode as three octal digits. Wikipedia gives 644 as an example. The mode matters mainly on Unix like systems, so Windows tools can ignore it.
Why It Matters
Begin lines from sources you do not know can name files in your folder. Decode into an empty folder, and look at the begin line first.
Change the Name Safely
Use -o with a name that you choose. The page says it replaces any pathname in the data, so editing is not needed.
How Big Is a UUE File? About a third more than the original
UUE files are about a third bigger than originals. Four characters stand for three bytes, and begin lines, length characters and end lines add a little more. Wikipedia gives the overhead, and our example is arithmetic.
The Wikipedia page puts overhead at roughly 33 percent, plus headers and delimiters. Method causes it. Every 3 bytes of data become 4 characters of text.
| Size | What follows |
|---|---|
| 3 bytes | Become 4 characters, which is the one third gain. |
| 45 bytes | Make a full line of 60 data characters, plus the length character. |
| 3,000,000 bytes | Make about 4,000,000 data characters, and about 4.1 million with line overhead. This is our arithmetic. |
What This Means in Practice
Files that fit a mail limit before encoding can stop fitting after. Check the size of your text file, not your original.
Estimate Your Own Size
Multiply your original size by about 1.38 for quick estimates. Our arithmetic counts 62 characters for every 45 bytes, with one character for line breaks. Windows line breaks use two, so results grow a little.
Why Mail Limits Matter
Mail systems cap message size. An encoded file that is a third bigger can cross that cap while the original stayed under it. Split big files or share a link instead.
What We Did Not Measure
We encoded no file, so we have no measured sizes. The numbers follow from the method and from Wikipedia.
Is a UUE File Safe to Open? You cannot see inside until you decode
These files hide content in text, so you cannot see what is inside before you decode. Risks are files you did not make and begin lines that name files in your folder. We decoded nothing and scanned nothing, so we make no claim about malware.
Content is the first risk. A decoded file can be any type, so treat it like an attachment from a sender you do not know. Begin lines are the second risk, and the begin line part covers them.
Text Pasted Into Mail
Encoded text in message bodies needs the same care. Do not paste unknown text into tools that you do not trust. Copy it to your own computer, save it as text and decode it there.
Five Steps for a UUE File You Did Not Make
- Keep the original, and work on a copy.
- Ask where the file came from.
- Open the copy in a text editor, and look at the begin line.
- Decode into an empty folder.
- Scan the decoded file before you open it.
What we did not test. We decoded no file and scanned none. These steps lower the risk of surprises and do not remove it.
Why Will Your UUE File Not Open? Seven causes, and what to do about every one
Seven causes stop these files from opening, and your file causes only some of them. Start with text, then program, then output folder.
Work down the list in order. We tested none of these on any file, so every fix comes from the pages that we name or from our own reasoning. Keep the original UUE file safe while you try.
How Does UUE Differ From Base64? Same job, different alphabets
UUE and Base64 do the same job with different alphabets. Base64 uses letters, digits, plus and slash, and it has largely replaced UUE in MIME. The uuencode -m option writes Base64 data. We tested none of them.
This table lists neighbors of UUE files. We opened none of them, so every line comes from pages that we name.
| Type | What public sources say |
|---|---|
| UUE | Begin and end lines, a mode in octal and data lines that start with a length character. |
| Base64 | An alphabet of letters, digits, plus and slash, per Wikipedia. Lines are at most 76 characters, per the man page. |
| uuencode -m | The uuencode tool with Base64 data. The first line starts with begin-base64, per the man page. |
| yEnc | Another encoding for binary posts, per Wikipedia. We list no more detail. |
| ZIP | A binary archive. See our page on ZIP archives for how it differs from a text form. |
UUE or Base64
Both convert bytes into printable text. Wikipedia says MIME, which uses Base64, has largely replaced the old format.
Which Should You Use
Wikipedia says MIME has largely replaced uuencode, so choose Base64 for new messages unless your receiver asks for the old form. Check with them first.
UUE or ZIP
UUE files wrap one file in text. ZIP files pack and compress files as binary data. You can encode ZIP files as UUE text to send them through old mail systems.
What Is the UUE Format Made Of? The facts we could check, and where they came from
Wikipedia and Linux man pages give the layout of UUE files. FileInfo gives the name and programs. Every value below has a source, and we tested no file.
| Part | What we could check |
|---|---|
| Name | Unix to Unix Encoding, per FileInfo. |
| Author | Mary Ann Horton at UC Berkeley in 1980, per Wikipedia. |
| Group size | Three input bytes become four characters, per Wikipedia. |
| Offset | Every 6 bit value gets 32 added, per Wikipedia. |
| Line length | Most full lines have 45 bytes and start with the letter M, per Wikipedia. |
| Begin line | The word begin, an octal mode and a file name, per the man pages. |
| End | A zero length line, then the word end, per Wikipedia. |
| Zero value | A backtick in most encoders and a space in some, per Wikipedia. |
| Base64 form | Starts with begin-base64 and ends with four equal signs, per the man page. |
| Overhead | Roughly 33 percent plus headers and delimiters, per Wikipedia. |
About the Values We List
Every value comes from a page that we name. The Wikipedia page on uuencoding gives method and history. Man pages for uuencode and uudecode give syntax.
The FileInfo record for UUE gives the name and programs. We claim nothing beyond our list, and a tool can write the format a little differently.
Why These Sources
FileInfo covers the name and programs. Wikipedia covers method and history. Man pages cover commands. We chose them because anyone can open and check them.
What We Left Out
We had no UUE file and no decoder session. We encoded and decoded nothing. Source pages can change, and we checked them on 7 November 2026.
Sources Checked
For the method, see Wikipedia on uuencoding. For the commands, see the uuencode man page and the uudecode man page.
For the name and the programs, see FileInfo on .uue.
Frequently Asked Questions About UUE Files
What is a UUE file?
UUE files are binary files that uuencode turned into text. The ending stands for Unix to Unix Encoding, per FileInfo. You must decode one to get your original back. We tested no UUE file.
How do I open a UUE file?
Decode it. FileInfo lists WinZip on Windows, Apple Archive Utility on Mac and the uudecode command on Linux. Copy the file first, and decode into an empty folder. We tested none of these programs.
How do I decode a UUE file on Linux?
Use the uudecode command with the file name. The option -o sets another output name. The man page says an existing file is overwritten if you have write permission. We used no command ourselves.
How does UUencoding work?
It splits every three bytes into four 6 bit values and adds 32 to every value. The result is four printable characters. Wikipedia gives the example Cat, which becomes the text #0V%T.
What is inside a UUE file?
Four kinds of lines. The first gives mode and name. Data lines start with a length character. Zero length lines come last, then the end line. Most full lines have 45 bytes, per Wikipedia.
Why are UUE files bigger than the original?
Four characters stand for three bytes, so the text is about a third bigger. Wikipedia puts the overhead at roughly 33 percent, plus headers and delimiters. We measured no file.
Who made the UUE format?
Mary Ann Horton wrote uuencode and uudecode at UC Berkeley in 1980, per Wikipedia. The name comes from Unix to Unix Copy. The tools let binary files survive email and Usenet.
What is the difference between UUE and Base64?
Both convert bytes into text. Base64 uses letters, digits, plus and slash. Wikipedia says MIME, which uses Base64, has largely replaced UUE. The uuencode -m option writes Base64 data.
Why will my UUE file not open?
The text can lack a begin line, or the end line can be missing. Other causes are the Base64 form, a discontinued program, a locked output file, lost Mac data and changed text. Work down the cause list in the part called Why Will Your UUE File Not Open.
Is a UUE file safe to open?
You cannot see what is inside before you decode it, so treat it like an attachment from a sender you do not know. We decoded nothing and scanned nothing, so we make no claim about malware.
Can a UUE file overwrite my files?
The man page says uudecode takes the output name from the begin line and overwrites an existing file if you have write permission. Decode into an empty folder, and use -o to choose the name.
Did you test a UUE file?
No. We had no UUE file and no decoder session. Every answer on this page comes from public pages that we name in the sources part. We encoded and decoded nothing.
Still Stuck With a UUE File? Where to go next, depending on what went wrong
Check the text and the begin line first. The cause list names what to try in order.
Is it a mail file and not an encoded attachment? The EML message page and the MBOX mailbox page cover two mail formats.
Is it an archive? The ZIP archive page covers that format.
Is it a binary file with an unknown ending? The page on DAT data files covers a common unknown file.
Is it a file type you do not know? Browse the full library of file types, or send it on the submit a file type page.
Do you need the sources? Use the format part for the facts and where they came from.