Skip to content

Quoted-Printable Encoder

Encode and decode MIME quoted-printable text in your browser.

Updated

What is the Quoted-Printable Encoder?

Quoted-Printable Encoder helps you encode and decode MIME quoted-printable text directly in the browser. It is useful for email debugging, MIME payload inspection, and converting mostly-ASCII text with a few special characters into a transport-safe format.

Quoted-printable is designed for text that should stay readable while still surviving older email and 7-bit transport constraints. Printable ASCII stays visible, while unsafe bytes become =XX hex escapes and long lines are soft-wrapped with = at the end.

Use this tool when you need a fast, client-side way to inspect copied email content, verify MIME output, or convert decoded text back into a readable form. Everything runs locally, so your input stays in your browser.

How it works

Quoted-Printable encoding follows the MIME rules from RFC 2045. The encoder leaves most printable ASCII characters unchanged, but escapes bytes that are unsafe for transport, including the equals sign itself and non-ASCII bytes.

When text contains characters such as é, the encoder converts the underlying UTF-8 bytes into hexadecimal escapes like =C3=A9. It also supports soft line breaks so long lines can be split safely without changing the decoded result.

Decoding reverses that process by scanning for =XX sequences and converting them back into bytes. The tool also handles soft line breaks, so wrapped MIME content can be restored to plain text.

The workflow is simple:

  1. Paste your text or quoted-printable content.
  2. Choose Encode or Decode.
  3. Review the output, copy it, or download it for reuse.

Because the tool is browser-based, it is well suited for quick checks during email template work, message triage, and developer debugging sessions.

Examples

Encode accented text for email

Convert readable text into MIME-safe quoted-printable output.

Café déjà vu
Caf=C3=A9 d=C3=A9j=C3=A0 vu

Decode a quoted-printable message

Turn escaped MIME text back into human-readable text.

Hello=2C=20world=21
Hello, world!

Wrap long lines safely

Generate soft line breaks for long email-friendly content.

This is a very long line that should be wrapped so the output stays within MIME line limits.
This is a very long line that should be wrapped so the output stays within M=
IME line limits.

Frequently asked questions

What is quoted-printable encoding?

Quoted-printable is a MIME content-transfer encoding used to represent mostly plain text in a 7-bit safe form. Printable ASCII characters stay readable, while bytes that need escaping are written as =XX.

When should I use quoted-printable instead of Base64?

Use quoted-printable when the text is mostly readable ASCII with only a few special characters, such as accented letters or symbols. Base64 is usually better for binary data or content that is heavily non-ASCII.

Why does the encoder add = at the end of a line?

That is a soft line break. It lets the content stay within MIME line-length limits without changing the decoded text.

Can this tool decode malformed quoted-printable text?

Yes, it can handle malformed input in tolerant mode by preserving problematic parts instead of failing immediately. If the input is badly formed, the tool will warn you when it detects invalid sequences.

Is my text sent to a server?

No. The tool runs entirely in your browser, so your input stays local to your device.

Does quoted-printable work with UTF-8 text?

Yes. UTF-8 characters are encoded byte by byte, so letters like é become escaped sequences such as =C3=A9.

Related tools

More utilities you might find handy.

Encoding

Base32 Encoder Decoder

Encode text or hex to Base32 (RFC 4648) and decode Base32 strings back to UTF-8 instantly in your browser.
Encoding

Punycode Converter

Convert internationalized domain names (IDN) to Punycode and vice versa.
Encoding

URL Safe Base64 Encoder / Decoder

Encode and decode Base64 using the URL-safe alphabet (RFC 4648 §5) — replaces + with - and / with _ so output is safe in URLs, filenames, and JWTs without percent-encoding.