My Tools Garage

Quoted-Printable Encoder

Encode and decode quoted-printable (RFC 2045) text.

in-browser

How to use

  1. 1 Choose Encode to convert plain text, or Decode to read quoted-printable.
  2. 2 Paste or type your text in the input box.
  3. 3 Read the converted result on the right.
  4. 4 Copy the output for your email or MIME part.

About Quoted-Printable Encoder

The Quoted-Printable Encoder converts text to and from the quoted-printable format defined in RFC 2045, the encoding email systems use to carry non-ASCII characters through channels that only reliably handle 7-bit ASCII.

In encode mode it takes your UTF-8 text and represents any byte that is not safe printable ASCII as an "=XX" escape using uppercase hexadecimal, always escapes the equals sign itself, protects trailing spaces and tabs, and soft-wraps long lines at 76 characters with a trailing "=" so the output stays within the limits mail transfer agents expect.

In decode mode it reverses the process: it strips the soft line breaks, turns every "=XX" escape back into its byte, and interprets the resulting stream as UTF-8 so accented letters, symbols and other multibyte characters come back exactly as they were.

If it meets a malformed escape — an "=" that is not followed by two hex digits or a valid soft break — it reports a clear error instead of silently corrupting the text.

This is handy when you are debugging an email header or body, inspecting a raw MIME part, or preparing content for a transport that mandates quoted-printable.

Everything runs locally in your browser, so your text is never uploaded or logged, and the tool keeps working offline once the page has loaded.

FAQ

What does an "=XX" sequence mean?

It is one byte written as an equals sign followed by two hexadecimal digits. For example "=C3=A9" is the two-byte UTF-8 encoding of é.

Why is a line ending in "=" with nothing after it?

That is a soft line break used to wrap long lines at 76 characters. The decoder removes it so the original text is reassembled.

What happens with an invalid escape when decoding?

The tool stops and shows an error describing the bad "=" sequence, rather than producing corrupted output.