Toolsky

Free Online Tools & Utilities for Every Task.

Encode Quoted Printable

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

Some systems still refuse to carry anything richer than plain ASCII: older mail relays, strict ticketing gateways, plain-text protocols and certain embedded devices all expect 7-bit-clean input. Feed them a sentence with an é or a € in it and characters get stripped, mangled or rejected outright. Quoted-printable encoding is the standard workaround — it rewrites the unsafe bytes as equals-sign escape sequences while leaving ordinary text readable. This encoder does the rewriting for you: type or paste your regular text, click Encode, and take away the encoded version.

Why Text Gets Encoded This Way

Quoted-printable exists because of a compromise. Sending raw 8-bit text through a 7-bit channel is unreliable, but fully armoring the text in Base64 makes it unreadable and inflates mostly-English content by a third. Quoted-printable takes the middle path defined by the MIME standards: printable ASCII characters pass through unchanged, and only bytes that could cause trouble — non-ASCII characters, control characters, trailing spaces, and the equals sign itself — are replaced by an equals sign and two hexadecimal digits. The encoded result stays legible to a human scanning it, survives any transport that handles ASCII safely, and decodes back to the exact original.

The situations that call for encoding by hand are narrower than decoding, but real. Developers build quoted-printable fixtures to test that a mail parser or import script handles accented content correctly. Administrators crafting a message at a raw SMTP prompt need the body pre-encoded, because the terminal session will not do it for them. Data teams preparing text for a legacy gateway — an old fax-to-email bridge, a strict ticketing system, an embedded device that accepts only ASCII input — encode first so that names, addresses and currency amounts arrive as sent rather than as mojibake.

What the Encoder Produces

  • UTF-8 bytes as =XX escapes — each byte of a non-ASCII character becomes an equals sign plus its hexadecimal value, so é becomes =C3=A9.
  • The equals sign escaped — a literal = in your text becomes =3D, so decoders never mistake it for an escape.
  • Lines wrapped at 76 characters — long lines are folded with a soft break (an equals sign at line end), as the standard requires.
  • Trailing whitespace protected — spaces and tabs at the ends of lines are encoded rather than left for a mail server to trim away.
  • Plain ASCII untouched — ordinary words and punctuation stay exactly as typed, keeping the output readable.

How to Encode Text as Quoted-Printable

  1. Type or paste the text you need to encode into the box.
  2. Check it once for stray formatting — you are encoding exactly what is in the box.
  3. Click the Encode button.
  4. Review the output: accented characters should now appear as =XX sequences and long lines should be folded.
  5. Copy the encoded text into your email source, test fixture, data file or legacy system.
  6. If you need to confirm the round trip, run the output through the matching decoder and compare it with your original.

A Worked Example: One Line of French

Take the sentence Le café coûte 5 €. Three characters in it are not ASCII: é (U+00E9), û (U+00FB) and the euro sign (U+20AC). In UTF-8, é is the two bytes C3 A9, û is C3 BB, and € is the three bytes E2 82 AC. The encoded line therefore reads Le caf=C3=A9 co=C3=BBte 5 =E2=82=AC — same sentence, every unsafe byte armored. Notice that the space before the euro sign stays a plain space, because spaces inside a line are perfectly safe; only trailing spaces get encoded. A text to Base64 encoder would have turned the entire sentence into an unreadable string; quoted-printable leaves the French plainly visible, which is precisely why it remains the encoding of choice for message bodies.

Encoding Pitfalls Worth Avoiding

Double-encoding is the most common self-inflicted wound: encode an already-encoded text and the equals signs themselves become =3D, so one decode pass leaves you with single-encoded gibberish instead of the original. Always start from clean text. Second, know your character set: this encoding operates on UTF-8 bytes, so if the receiving system expects the text in a legacy encoding such as ISO-8859-1, convert the text first or the bytes will decode into wrong characters at the far end. Third, do not confuse body encoding with header encoding — in message headers, a sibling scheme called Q-encoding writes spaces as underscores, but that rule does not apply here, and hand-adding underscores corrupts the body. Finally, resist "tidying" the output: the folded lines and trailing equals signs are load-bearing, and reflowing them by hand will break the encoding.

Frequently Asked Questions About Quoted-Printable Encoding

When should I use quoted-printable instead of Base64?

When the content is mostly ordinary text and a human might need to read the encoded form — email bodies are the textbook case. For binary data or heavily non-ASCII content, Base64's uniform overhead is the better trade.

How much bigger does the encoded text get?

Plain ASCII costs nothing extra. Each non-ASCII byte grows from one byte to three characters, so a sentence with a few accents grows slightly, while text in a script like Chinese can approach triple size in UTF-8 form.

Why are lines in the output so short?

The standard limits encoded lines to 76 characters. Rather than truncate anything, the encoder folds longer lines using a soft break — an equals sign at the end — which decoders remove when rejoining the text.

Can I encode text with emojis?

Yes. Emojis are just multi-byte UTF-8 characters, so each becomes a run of =XX sequences — four bytes, twelve characters, per emoji. It works, though the encoded form stops being readable very quickly.

Does the decoder at the other end need to know I used UTF-8?

Yes. Quoted-printable transports bytes; the charset label (normally carried in a Content-Type header) tells the receiver how to turn those bytes back into characters. Without it, accented text may decode into the wrong symbols.

What happens if I paste already-encoded text into the encoder?

It gets encoded again: every equals sign becomes =3D. If you are holding encoded text, send it to the quoted-printable decoder instead — that is the tool that turns it back into readable text.

Plain Text That Survives Old Email Systems

Quoted-printable is unfashionable and indispensable at the same time: the moment your text has to cross a channel that only trusts ASCII, encoding it properly is the difference between your accents arriving intact and arriving as question marks.