TFT

Quoted-Printable Encoder and Decoder

Encode text to Quoted-Printable format for safe email transmission, or decode Quoted-Printable text back to readable content. This tool ensures compatibility with email standards and character sets.

Quoted-Printable Encoder/Decoder

Encode text to Quoted-Printable format or decode Quoted-Printable back to text

About Quoted-Printable

Quoted-Printable is an encoding method used in email (MIME) to encode 8-bit data using mostly printable ASCII characters. It's efficient for text that is mostly ASCII with occasional non-ASCII characters.

Non-printable characters are encoded as =XX where XX is the hexadecimal value. Lines are limited to 76 characters, with soft line breaks indicated by = at the end of a line. Common characters like letters and numbers remain unencoded.

How the Quoted-Printable Encoder/Decoder Works

Enter text to encode to Quoted-Printable format, or paste QP-encoded text to decode. The tool handles both encoding and decoding instantly.

Quoted-Printable encodes non-ASCII characters as =XX where XX is the hex byte value. ASCII printable characters mostly pass through unchanged. Soft line breaks use = at line ends.

The encoder preserves readability for mostly-ASCII text. The decoder converts =XX sequences back to original bytes. Handles soft line breaks automatically.

When You'd Actually Use This

Sending international email

Email with non-ASCII characters needs encoding. Quoted-Printable preserves readable ASCII. Recipients see proper international text.

Debugging MIME messages

Email headers and bodies use QP encoding. Decode to read actual content. Understand MIME structure and encoding.

Processing email archives

Old email stored in mbox or maildir format. Decode QP-encoded messages. Extract readable content from archives.

Working with HTTP headers

Some HTTP headers use QP encoding. Decode header values with special characters. Understand web protocol details.

Creating MIME-compliant messages

Building email systems? Encode message bodies properly. QP for mostly-ASCII text. Ensure compatibility with all email clients.

Analyzing spam headers

Spam often uses encoding to hide content. Decode QP to analyze actual message. Security research and spam filtering.

What to Know Before Using

Best for mostly-ASCII text.QP is efficient when most characters are ASCII. Heavy non-ASCII content is better as Base64. QP keeps ASCII readable.

Line length is limited.Maximum 76 characters per line. Soft line breaks (= at end) continue long lines. Decoders handle this automatically.

Equals sign needs encoding.Literal = becomes =3D. This prevents confusion with encoded sequences. Always encoded, never passed through.

Whitespace at line end is encoded.Spaces or tabs at line ends must be encoded. Prevents trimming by mail systems. =20 for space, =09 for tab.

Pro tip: When debugging email, look for = followed by two hex digits. That's an encoded byte. =0D=0A is CRLF. =3D is literal equals sign.

Common Questions

What is Quoted-Printable?

MIME content transfer encoding. Encodes non-ASCII as =XX hex. Keeps ASCII readable. Defined in RFC 2045 for email.

When is QP better than Base64?

QP for mostly-ASCII text with few special chars. Base64 for binary or heavy non-ASCII. QP is more readable for humans.

What characters are encoded?

Non-ASCII (above 127), equals sign, and whitespace at line ends. Most printable ASCII passes through unchanged.

What are soft line breaks?

Lines ending with = continue on next line. The = is removed during decoding. Allows long lines within 76-char limit.

Can QP encode binary?

Technically yes, but inefficient. Every non-ASCII byte becomes 3 characters. Base64 is better for binary data.

Is QP still used?

Yes, in email systems. Modern email clients use it for text with special characters. Still part of MIME standard.

How do I recognize QP encoding?

Look for =XX patterns where XX is hex. Text is mostly readable with occasional encoded sequences. Lines may end with =.