📨 Email Subject Encoder & Decoder

Encode and decode email subjects using RFC 2047 — Quoted-Printable, Full Hex QP, and Base64. Works instantly in your browser with full UTF-8 support.

⬆️ Encoder

Enter Subject to Encode:

Quoted Printable Space Representation:

QP Encoded Output:

Full Hex Quoted Printable:

Base64 (RFC 2047):

🔢 Advanced Encoding

Hex-Encode Strategy:

Hex Encoded Output:

🌫️ Blurry Encoding

Blur Strategy:

Blurry Encoded Output:

🔀 Multiple Encoded Words

Split every N chars:

Multiple Encoded Words Output:

⬇️ Decoder

Quoted-Printable Decoder Input:

Decoded QP Output:

Base64 Decoder Input:

Decoded Base64 Output:

The Definitive Guide to Email Subject Encoding (RFC 2047)

In the world of email infrastructure, the "Subject" line isn't just a simple text field. It is a critical component of the MIME (Multipurpose Internet Mail Extensions) header. Historically, email headers were restricted to 7-bit ASCII characters. As the internet went global, the need to support international character sets and emojis led to the development of RFC 2047.

Our Email Subject Encoder/Decoder helps you navigate these complex standards, ensuring your messages are delivered exactly as intended across all major email clients like Outlook, Gmail, and Yahoo Mail.

🚀 Performance

Instant client-side encoding. No server-side processing or data transmission required.

🔒 Privacy First

Your data never leaves your browser. Fully secure for internal communication and sensitive campaigns.

✅ RFC 2047 Compliance

Fully supports 'Q' (Quoted-Printable) and 'B' (Base64) encoding formats with UTF-8 handling.

Understanding "Encoded-Word" Syntax

When you use an emoji or a non-English character in a subject line, it must be transformed into an "encoded-word." The syntax follows this pattern:

=?charset?encoding?encoded-text?=

Charset: Usually UTF-8 for modern applications.
Encoding: Q for Quoted-Printable (best for text with few special characters) or B for Base64 (best for non-Latin scripts).
Encoded-text: The actual data after being processed by the algorithm.

'Q' vs 'B' Encoding: Which Should You Use?

Selecting the right encoding strategy is vital for both deliverability and technical accuracy:

Quoted-Printable (Q) Best for Western European languages. It keeps standard ASCII characters readable while encoding others as =XX (Hex).

Base64 (B) Essential for languages like Arabic, Chinese, or Japanese. It converts data into a secure 64-character alphabet, ensuring no corruption during transit.

Best Practices for Email Marketers

To avoid triggering spam filters and ensure maximum open rates, follow these professional guidelines:

Keep it Short: While RFC 2047 allows for multi-word encoding, most mobile clients truncate subjects after 40-60 characters.
Test Emojis: Not all emojis render correctly on older versions of Outlook. Use our decoder to verify your encoding before hitting send.
Avoid Double Encoding: Ensure your email sending software isn't encoding an already encoded subject line, which will lead to "Garbage Text" (Mojo Bake) symptoms.

Frequently Asked Questions (FAQ)

What is RFC 2047?

It is a standard used to represent non-ASCII character sets in SMTP message headers, specifically the Subject, From, To, and CC fields.

Why does my subject look like "=?utf-8?q?..." in the headers?

This is the standard representation. Most modern email clients automatically decode this and show the "friendly" text to the recipient.

Does this tool support and preserve UTF-8?

Yes. Our encoder automatically detects the character set as UTF-8 to ensure maximum compatibility with modern web standards.