Base64 Image in an Email Signature

Will a Base64 image actually show in your signature?

The idea is appealing: a logo embedded directly in the signature HTML cannot be blocked the way a hosted image can, because there is no external request to block. That part is true. The catch is that most major email clients strip data URIs from received mail anyway — so the Base64 approach works in some clients and silently fails in others. Here is the honest picture.

Client behavior changes over time — always send a test to your own accounts in each client before relying on any embedding method.

What actually works, client by client

• Gmail signature: use Gmail's own signature editor and upload the image there. Gmail hosts it for you, which is why Gmail-to-Gmail signature logos display even though Gmail strips your hand-made data URIs.
• Outlook signature: build the signature in Outlook's editor with an inserted picture; Outlook embeds it as an attachment referenced by CID on send.
• Apple Mail signature: data URIs genuinely work here — the encoder above plus the HTML snippet is a valid route.
• Email you generate yourself (transactional mail, newsletters): prefer a CID-embedded image for broad compatibility; keep a Base64 variant only where your audience measurement says Apple clients dominate.

Where the encoder above is useful

• Apple Mail and Thunderbird signatures — the clients that render data URIs.
• Testing and previews — paste the snippet into a test HTML email and see exactly how the logo renders before you upload it to a signature platform.
• Single-file assets — any context where the signature HTML must travel as one self-contained file.

Keep the source logo small — around 150-320 px wide and under 10 KB. Base64 adds about 33%, so a 10 KB logo becomes a ~13.7 KB string repeated inside every message you send. If the file is larger, shrink it first with the PNG compressor + encoder and check the final size with the Base64 size calculator.

Base64 is not a workaround for image blocking

Email clients block hosted images for privacy reasons — hosted images leak open-tracking data. A data URI avoids that leak, but the same clients strip it anyway, so Base64 is not a reliable way to force images into everyone's inbox. Treat it as a compatibility feature for the clients that support it, not a bypass.