RFC 2047 encoded-word

Client

Email header encoding near quoted-printable cluster.

Build =?UTF-8?B?...?= MIME encoded-word headers.

About RFC 2047 encoded-word

Build =?UTF-8?B?...?= MIME encoded-word headers. Processing runs in your browser—Toolcore does not need your paste for the core operation on this page.

Transforms UTF-8 text in your browser; confirm byte semantics before using output on the wire.

How to use

Paste or type in the main field, then read the output below. Use Load example when available, or open the page with ?q= / ?qb= so tickets and agents share the same input.

=?UTF-8?B?Q2Fmw6kgcsOpc3Vtw6k=?=

Common use cases

  • Transform sample text with rfc 2047 encoded-word while debugging legacy email, Usenet, or protocol payloads.
  • Compare output size and alphabet against Base64, Z85, or hex dumps on the same input without leaving the encoding hub.
  • Email header encoding near quoted-printable cluster.
  • When the payload also needs a sibling encoding, open the related encoding-quoted-printable page from More tools below.

Common mistakes to avoid

  • Treating UTF-8 paste as raw binary

    These tools encode the UTF-8 bytes of your text unless the page states otherwise. For arbitrary byte arrays, convert from hex first.

  • Mixing alphabets between encodings

    Base91, Z85, uuencode, and Base64 use different symbol sets—decode with the matching tool before re-encoding.

  • Pasting secrets into shareable prefill links

    URL query parameters may appear in browser history. Use Load example for demos; avoid ?q= links for production keys.

FAQ

Where does encoding run?

In your browser. Toolcore does not need your paste for the transform.

Is there a payload size limit?

Very large pastes may slow the tab. Split huge files locally before encoding samples on the page.

Can agents prefill this page?

Yes. Use ?q= for short text or ?qb= for base64 payloads on the tool URL.

More tools

Related utilities you can open in another tab—mostly client-side.