Quoted-Printable Encode / Decode
Encode text as Quoted-Printable for MIME email, or decode QP-encoded strings.
MIME email standards require message bodies to use printable ASCII, but most text in the world contains characters outside that range β accented Latin characters, quotation marks, and non-Latin scripts. Quoted-Printable encoding was invented to handle this: it keeps ASCII characters as-is (making the encoded text mostly readable) while encoding non-ASCII bytes as `=XX` sequences, where XX is the byte value in hexadecimal.
This tool encodes UTF-8 text to Quoted-Printable format for use in MIME-compliant email headers or bodies, and decodes QP-encoded strings back to readable text. It is useful for email developers, anyone debugging raw MIME messages in mail server logs, and developers building systems that must interoperate with legacy email infrastructure.
How to Encode and Decode Quoted-Printable Online
- 1
Paste Your Input
Paste plain text to encode as Quoted-Printable, or paste a QP-encoded string to decode.
- 2
Choose Encode or Decode
Encoding converts non-ASCII characters to =XX hex sequences while leaving printable ASCII unchanged. Decoding reverses the process including soft line breaks.
- 3
Copy the Result
Copy the output for use in email clients, MIME tools, or debugging.
How Quoted-Printable Encoding Works
Quoted-Printable (RFC 2045) replaces any byte whose value is outside the printable ASCII range (33β126), or that is a tab or space at the end of a line, with an equals sign followed by two uppercase hex digits β `=C3=A9` for the UTF-8 encoding of `Γ©`. The equals sign itself is encoded as `=3D`. Lines in QP-encoded content must not exceed 76 characters; a soft line break is encoded as `=\r\n` (a trailing equals sign before the CRLF) to indicate that the logical line continues.
QP is a 'mostly printable' encoding: English text encodes with very little overhead because ASCII characters pass through unchanged. This readability was the design goal β a human reading a raw MIME message should be able to understand the gist of the content even without decoding it. By contrast, Base64 encodes everything, producing output that is completely opaque to humans.
Why Use FileCrank Quoted-Printable Tool?
- β RFC 2045 compliant Quoted-Printable encoding and decoding.
- β Handles soft line breaks (= at end of line) correctly.
- β Keeps mostly-ASCII content human-readable after encoding.
- β Runs entirely in your browser β no data sent to any server.
Features & Specs
Frequently Asked Questions
What is Quoted-Printable encoding used for?
Quoted-Printable is used in MIME email to encode message bodies that contain non-ASCII characters while keeping the message largely readable in its raw form. It is standard for text/plain and text/html email parts with non-ASCII content.
How does Quoted-Printable differ from Base64 for email encoding?
Quoted-Printable leaves ASCII-printable characters unchanged, making the encoded text mostly readable. Base64 encodes everything, producing compact but unreadable output. Use QP for mostly-ASCII content; use Base64 for binary attachments.
What is the = at the end of a Quoted-Printable line?
A = at the end of a line is a soft line break β it means the line continues on the next line with no actual newline in the decoded content. QP limits line length to 76 characters and uses this convention to wrap longer lines.
Why does my decoded QP output still have =?UTF-8?Q? around it?
That is RFC 2047 encoded word syntax used in email headers, not the same as QP body encoding. Strip the =?charset?Q? prefix and ?= suffix before pasting the inner QP string into this decoder.
Quoted-Printable vs. Base64 in MIME Email
MIME allows content-transfer-encoding to be either `quoted-printable` or `base64`. QP is preferred for text content that is mostly ASCII, as the encoded form remains human-readable and the size overhead is minimal for Latin text. Base64 is preferred for binary attachments and text that is heavily non-ASCII, as it produces a fixed 33% expansion regardless of content. Most email clients choose automatically, but developers building MIME message generators should understand both options.
Related Tools
Base64 Encode / Decode
Encode text or binary data to Base64 and decode Base64 strings back to plain text, instantly in your browser.
UUencode / UUdecode
Encode text or binary data as UUencode format, or decode UUencoded blocks back to the original.
HTML Entities Encode / Decode
Encode special characters to HTML entities and decode HTML entities back to plain text.
FileCrank Quoted-Printable Encode / Decode handles RFC 2045 compliant QP encoding for MIME email, keeping ASCII content readable while encoding non-ASCII characters as =XX sequences.
Advertisement