UUencode / UUdecode
将文本或二进制数据编码为 UUencode 格式,或将 UUencode 编码的块解码回原始内容。
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.
如何在线进行 UUencode 和 UUdecode
- 1
粘贴您的输入内容
粘贴文本或二进制输入以编码为 UUencode 块,或粘贴现有的 UUencode 块(包含 begin 和 end 行)进行解码。
- 2
编码或解码
工具生成或解析 begin/end 标记语法,并验证块结构。
- 3
复制结果
复制编码块或解码内容。适用于旧式电子邮件归档、Usenet 数据和 CTF 挑战。
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.
为什么使用 FileCrank UUencode / UUdecode?
- ✓ 生成并解析正确的 begin/end 标记语法。
- ✓ 验证块结构并清晰报告错误。
- ✓ 处理旧式电子邮件和 Usenet UUencode 附件。
- ✓ 完全在浏览器中运行——不向任何服务器发送数据。
功能与规格
常见问题
什么是 UUencoding?
UUencoding(Unix 到 Unix 编码)将二进制数据转换为可打印 ASCII,以便通过纯文本通道传输。每 3 个字节被编码为 4 个可打印字符。UUencode 文件以 begin [权限] [文件名] 行开头,以 end 行结尾。
UUencode 今天还在使用吗?
很少用了,但仍出现在旧式电子邮件归档、旧 Usenet 帖子以及偶尔的 CTF 安全挑战中。现代电子邮件使用 MIME 和 Base64 编码。
UUencode 和 Base64 有什么区别?
两者都将二进制数据转换为可打印 ASCII,但使用不同的字符集和行格式。UUencode 使用 ASCII 值 32-95 的字符,Base64 使用 A-Z、a-z、0-9、+ 和 /。UUencode 包含 begin/end 标头,Base64 通常没有。
我的 UUencode 块解码时出错——是什么问题?
常见问题:缺少 begin 或 end 行、行长字符损坏(每行第一个字符编码该行的长度)、或行尾转换引入了不可打印字符。请粘贴包含 begin 和 end 行的完整块。
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 编码和解码包含 begin/end 标记语法的 UUencode 块,适用于旧式电子邮件、Usenet 归档和 CTF 挑战。
Advertisement