📧 Quoted-Printable Encoder/Decoder

🔧
📝
💡 Examples: Text with special chars: Café, naïve, résumé 💡 Examples: Caf=C3=A9, na=C3=AFve, r=C3=A9sum=C3=A9
⚡
📤 
{{ outputText }}
📊
Original Size:
{{ stats.originalSize }} bytes
Encoded Size:
{{ stats.encodedSize }} bytes
Overhead: {{ stats.overhead }}%
⚠️ {{ error }}
💡
To Encode: Enter plain text with international characters or special symbols
To Decode: Enter quoted-printable encoded text (contains =XX sequences)
Common Applications: Email encoding, MIME headers, text transmission

ℹ️ About Quoted-Printable Encoder/Decoder

Quoted-Printable is the MIME content-transfer encoding used when a message body is mostly readable text but still needs to survive 7-bit mail gateways, line-length limits, and bytes outside US-ASCII. It keeps ordinary printable characters visible and writes other bytes as =XX hexadecimal escapes, as defined in RFC 2045 section 6.7.

Common use cases:

  • Encode UTF-8 email bodies that contain characters such as é, smart quotes, or non-breaking spaces.
  • Decode raw MIME parts from support tickets, mail logs, spam samples, and saved .eml messages.
  • Inspect why a message body contains escapes such as =C3=A9, =20, or soft line breaks.
  • Prepare mostly-text payloads where readability matters more than Base64's compact, opaque output.

How the encoding works:

  • Safe printable bytes normally remain unchanged; the equals sign itself becomes =3D.
  • Non-ASCII UTF-8 bytes are encoded one byte at a time, so Café becomes Caf=C3=A9.
  • Spaces and tabs at the end of a line must be escaped, for example a trailing space becomes =20.
  • Encoded lines are limited to 76 characters; a final = before CRLF marks a soft line break.

Example: a MIME body containing Café = menu is typically encoded as Caf=C3=A9 =3D menu. When long lines are wrapped, the inserted soft break is removed again during decoding.

Limitations: Quoted-Printable is not encryption and does not hide message content. It depends on the correct character set, usually UTF-8, being known from the MIME headers. Dense binary data is better sent as Base64 using the MIME rules in RFC 2045 section 6.8. MIME header words use the related but different encoded-word syntax from RFC 2047, so do not treat every Subject: or address header as a plain Quoted-Printable body.

Standards notes: RFC 5322 defines the email line-length background, while RFC 6532 documents modern internationalized email headers. This tool is useful for conversion and inspection, but final email delivery still depends on the MIME headers generated by your mail library.

API Usage Example:

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

{
    "text": "Café naïve résumé",
    "operation": "encode"
}
Ready