Quoted-Printable Decoder (=20, =E2=80=99 in Emails)|Turn an encoded email body back into plain text
An email body full of =20, =E2=80=99 and lines ending in = is not corrupted. It is quoted-printable, the body encoding defined in RFC 2045. Here=E2=80=99s the agenda reads "Here’s the agenda". Paste the body here and you get the readable text back.
💡 About this tool
You usually see this form when a message is shown as stored rather than decoded: the "view source" window, a saved message opened in a text editor, or a log, ticket or export that copied the raw body.
What the tool does with what you paste:
- =XX becomes one byte: every
=followed by two hex digits (0–9, A–F) is turned back into that byte.=20is a space,=3Dis an equals sign, and=E2=80=99is the three bytes of a curly apostrophe in UTF-8 - Lines ending in = are joined: the rules limit an encoded line to 76 characters, so longer lines are wrapped with a
=at the end. The tool removes that=and joins the line to the next one, even when the wrap falls in the middle of a character - Trailing spaces are removed: RFC 2045 says white space at the end of a line was added in transport and must be deleted when decoding
- The character set is applied: if the pasted text contains
charset=, that character set is used, otherwise UTF-8. You can pick another one in the menu
An = that is not followed by two hex digits is left as it is.
🧐 Frequently Asked Questions
Q. What does =20 mean in an email?
It is a space. In quoted-printable, a byte can be written as = plus its value in hex, and the space character is 32, or 20 in hex. The rules require this form for a space at the end of a line, because some mail servers strip or add spaces there.
Q. What is =E2=80=99?
It is the right single quotation mark ’, which word processors put in place of a straight apostrophe. In UTF-8 it takes three bytes, E2 80 99, so in quoted-printable it becomes three =XX codes. =E2=80=9C and =E2=80=9D are the curly double quotes, and =E2=80=93 is an en dash.
Q. Why do some lines end with =?
That = is a soft line break. RFC 2045 requires encoded lines to be no more than 76 characters long, and an equals sign as the last character on a line means the line continues on the next one. It is not part of the message.
Q. Why do I get "�" in the result?
The bytes do not fit the character set they were read with. Try another one in the menu, such as Windows-1252 or ISO-8859-1 for older Western European mail. A body that was cut off in the middle can also lose its last character.
Q. Can it decode =?UTF-8?B?…?= in a subject line?
Not on this page. Subjects and attachment names use encoded-words, a separate rule (RFC 2047). Use the Email Subject Decoder on this site for those.
📚 The compromise in the name
RFC 2045 describes quoted-printable as meant for data that is mostly printable US-ASCII, and says that such data "remains largely recognizable by humans" once encoded. That is the whole idea: an English message with a few curly quotes stays readable even when nobody decodes it.
The same section calls it "a compromise between readability and reliability in transport" and points to Base64 when reliability matters more. Base64 writes every 3 bytes as 4 characters whatever they are, so it is never readable, but it never depends on the text being mostly ASCII either.