How to use the quoted-printable tool
- Set Direction to Encode or Decode.
- Paste your text into Input. For decoding, paste the raw body from the email source.
- When encoding, pick Line breaks: CRLF (email standard) or LF.
- Copy the Encoded or Decoded result.
What it does and when to use it
Email was designed for 7-bit ASCII text. Quoted-printable is one of the two standard ways MIME uses to carry other bytes, the other being Base64. It suits text that is mostly plain English with a few accents or symbols, because the plain parts stay readable.
You meet it when you view the source of an email, debug a newsletter template, write a raw message for an SMTP test, or read an exported .eml file. Seeing =E2=80=99 where an apostrophe should be is the classic sign of quoted-printable text that was not decoded.
For bodies that are mostly binary, Base64 is shorter; see the Base64 encoder. If the escapes you see look like %C3%A9 instead, that is URL encoding and the URL decoder is the right tool. For é style text, use the HTML decoder.
How it works
This follows the quoted-printable rules in RFC 2045, section 6.7.
Encoding. Each line is turned into UTF-8 bytes. Printable ASCII characters (byte values 33 to 126) are kept as they are, except =. Spaces and tabs are kept too, unless they are the last character on the line. Every other byte is written as = followed by two upper-case hex digits. When a line would pass 76 characters, it is split with a soft break, an = at the end, and an escape is never cut in half.
Decoding. Trailing spaces at line ends are removed, soft breaks are joined, each =XX becomes one byte, and the bytes are read as UTF-8. If they are not valid UTF-8, you see them as hex with a warning.
It all happens in your browser.
Worked examples
Café = coffee → Caf=C3=A9 =3D coffee
Caf=C3=A9 =3D coffee → Café = coffee (Decode)
"Ends with a space " → Ends with a space=20
A long line, encoded with LF line breaks:
This line is deliberately long so that the quoted-printable encoder has to =
insert a soft line break somewhere
Limits and tips
- Decoding assumes the original charset was UTF-8. Older emails in ISO-8859-1 or Windows-1252 will show as hex because single bytes such as
=E9are not valid UTF-8 on their own. - The tool works on the body text only. It does not parse email headers or encoded words such as
=?UTF-8?Q?…?=.
Frequently asked questions
Why does my email show =C3=A9 and =20 instead of letters?
What is the = at the end of some lines?
Why is the equals sign itself written as =3D?
Should I choose CRLF or LF?
Is quoted-printable a kind of encryption?
Sources
- RFC 2045: MIME Part One — Format of Internet Message Bodies (section 6.7) — IETF / RFC Editor, accessed 2026-10-08
How do we know nothing is uploaded? Test it yourself on the privacy proof page.