Toolsky

Free Online Tools & Utilities for Every Task.

Decode Quoted Printable

To decode a regular text to Quoted Printable, type in the box on top and click the Decode button.

Open the raw source of almost any email containing an accented name or a non-English sentence and you will find passages like Gr=C3=BC=C3=9Fe aus M=C3=BCnchen — perfectly good German wearing an ASCII disguise. That disguise is quoted-printable, a transfer encoding defined in RFC 2045 that email systems use to carry 8-bit text through channels built for plain 7-bit ASCII. This decoder reverses the process: paste the encoded text in, and you get the readable original back.

What Quoted-Printable Is Doing in Your Email

Quoted-printable keeps most printable ASCII characters exactly as they are, which is why encoded English text still looks mostly readable. Anything outside that safe set — accented letters, currency symbols, typographic punctuation, and the equals sign itself — is replaced by an equals sign followed by the two hexadecimal digits of the character's byte value. Non-ASCII characters usually travel as their UTF-8 byte sequence, so a single letter often becomes two or three =XX groups in a row. Long lines are also folded with a "soft break": an equals sign at the very end of a line means the line continues, and the break itself is not part of the message. Decades of email are stored in this format, which is why developers, archivists and support staff still meet it weekly.

You are most likely to meet the raw form in specific places: the .eml file a customer forwards when a message "looks broken", the mail-server log an administrator greps while tracing a delivery failure, an exported archive from a retired helpdesk system, or the body source that a ticketing tool pasted into a case instead of rendering. In each situation the mail client that would normally decode silently is out of the loop, and a person is staring at the transport format directly. A dedicated decoder restores what the client would have shown.

What This Decoder Handles

  • =XX byte sequences — converted back into the bytes they represent, then read as characters in the message's character set.
  • Soft line breaks — a trailing equals sign simply rejoins the split line instead of leaving a stray character behind.
  • Encoded equals signs — =3D in the source comes back as a literal = in the output.
  • Escaped spaces and tabs — trailing whitespace in the original is often stored as =20 or =09, and decodes back to real spacing.
  • Whole message bodies — paste a full encoded body, headers and all, and read the text sections in plain form.

How to Decode Quoted-Printable Text

  1. Copy the encoded text from the email source, log file or document where you found it.
  2. Paste it into the input box.
  3. Click the Decode button.
  4. Read the converted text in the output — accented characters and punctuation should now appear normally.
  5. Copy the result wherever you need it: a ticket reply, a document, a translation tool.
  6. If some characters still look wrong, check the message's declared charset — the bytes decode differently under UTF-8 and legacy single-byte encodings.

A Worked Example: Reading a Mangled Subject Line

Take the greeting Gr=C3=BC=C3=9Fe aus M=C3=BCnchen. Working through it: =C3=BC is the two-byte UTF-8 form of ü, and =C3=9F is the UTF-8 form of ß. Substituting those in gives Grüße aus München — "Greetings from Munich". Notice the pattern: each =C3 begins a two-byte character, which is the visual signature of UTF-8 text in quoted-printable. Once you can spot it, you can even guess at short fragments by eye, but for anything longer than a subject line the decoder earns its keep — a full paragraph contains hundreds of these groups, interleaved with soft line breaks every 76 characters or so.

Where Decoding Goes Wrong

The classic failure is a character-set mismatch. The =XX groups are bytes, and bytes only become letters through a charset: =C3=BC means ü under UTF-8, but interpreted as Latin-1 the same bytes surface as two stray characters, à and ¼. If your output is full of à sequences, the text was decoded with the wrong charset — the original message's Content-Type header names the right one, and an email header decoder can make finding it easier. Second trap: underscores. In email headers, a related Q-encoding uses underscores for spaces, but in message bodies quoted-printable does not — an underscore in the body is just an underscore, so do not "fix" them. Finally, truncated pastes break codes: if the copied text ends mid-sequence, like =C, that fragment cannot decode, so copy generously.

Frequently Asked Questions About Quoted-Printable Decoding

Why does email use quoted-printable at all?

Because much of the mail infrastructure was built for 7-bit ASCII. Quoted-printable lets accented and non-English text survive those channels while staying mostly human-readable and adding little size when the text is predominantly plain ASCII.

What is the difference between quoted-printable and Base64?

Both are transfer encodings, but Base64 turns everything into an opaque block of letters — better for binary attachments — while quoted-printable leaves plain ASCII readable and only escapes what it must. A Base64 to text decoder handles the other format.

What does an equals sign at the end of a line mean?

It is a soft line break: the encoder folded a long line to stay within the 76-character limit, and the break is not real content. Decoding removes it and joins the line back together.

Why do some decoded characters appear as à followed by another symbol?

That is the signature of UTF-8 bytes being read as Latin-1. The encoded data is fine; it just needs to be interpreted with the character set the message declares, which is UTF-8 in the overwhelming majority of modern mail.

Can I decode only part of a message?

Yes — decoding works on any fragment, as long as you do not cut through the middle of an =XX sequence. Copy a complete paragraph and the result will be complete.

Does decoding change any of the readable text?

No. Characters that were stored literally pass through untouched; only the =XX escapes, soft breaks and encoded whitespace are transformed back into the characters they represent.

How do I encode text back into quoted-printable afterwards?

Use the matching quoted-printable encoder — encode and decode are exact inverses, so a decoded message can be re-encoded losslessly.

Turning Email Gibberish Back Into Language

Quoted-printable looks like corruption until you know the trick: equals sign, two hex digits, repeat. Decode the text once and the message underneath is exactly what its sender typed — accents, ß and all.