Exclaimer Email Signatures: Previewing and Using Your Logo
How a logo works in an Exclaimer email signature: why recipients see a raster image rather than vector artwork, how to prepare it from your vector master, and what a preview can and cannot confirm.
Contents
The short answer
When you add a logo to an email signature managed through Exclaimer, the version recipients see is a raster image, not your editable vector artwork. Your vector file stays the master. You export a raster copy from it, and that copy goes into the signature. The preview shows how that image is placed in the signature design. It cannot guarantee how every recipient's email client will display it.
Exclaimer is a service for centrally managing email signatures across an organization. This article covers the logo itself: which file belongs in the signature, how it relates to your vector source, and how to read a preview. Specific Exclaimer details, such as accepted upload formats, file size limits, preview tools and plan features, were not part of the available evidence. Check those against Exclaimer's current documentation before you finalize anything.
Three different things called "the logo"
Much of the confusion about signature logos comes from treating three separate assets as one. Keeping them apart makes the workflow much clearer.
| Asset | What it is | Role in an email signature |
| Vector master (for example SVG, AI, EPS or PDF) | Artwork made of paths and shapes that can scale without losing quality, if it truly contains vector data | Source file for producing signature images; not normally the file recipients receive |
| Raster export (for example PNG, JPG or GIF) | A fixed grid of pixels produced from the master | The image that actually appears in the signature |
| Preview | A rendered view of the signature inside an editor or test message | A check on layout and appearance, limited to the environment it is shown in |
Why the vector file doesn't go into the signature
Email clients differ widely in what they render, and SVG support in email is limited and inconsistent across commonly used clients. A vector logo that looks sharp in a browser or design tool may fail to appear, or may be replaced by a blank box, when it arrives in someone's inbox. This is why raster formats are the conventional choice for signature logos. If you are considering an SVG for an Exclaimer signature, confirm what the platform currently accepts and test it in your recipients' clients. Don't assume it will work.
Also, a file extension doesn't prove that a file contains editable vector paths. An SVG, EPS or PDF can simply wrap an embedded raster image. Before you treat a file as your scalable master, open it in a vector editor and confirm that the logo is built from paths. If the "vector" file only holds pixels, exporting from it gives you no quality advantage.
Preparing the logo from your vector master
- Export from the confirmed vector master, not from a screenshot or a previously compressed image, so the raster copy starts as clean as possible.
- Export at a higher pixel size than the logo's intended display size, then constrain the displayed dimensions in the signature. This helps the logo stay crisp on high-density screens. Check Exclaimer's guidance for recommended dimensions, since none were available here.
- Choose the format to fit the artwork: PNG suits flat logos and transparency, while JPG suits photographic content and does not support transparency.
- Consider dark backgrounds. Some email clients display messages in dark mode, so a transparent logo with dark artwork can become hard to see. A version with a subtle background or outline may read more reliably.
- Keep the file size modest. Signature images appear on every message, so an oversized file adds weight to each email.
What a preview can and cannot tell you
An editor preview is useful for checking placement, proportions, spacing against the text, and whether the logo looks blurry or stretched at its displayed size. It reflects one rendering environment. Recipients may use desktop clients, webmail, or mobile apps, each with its own handling of images, scaling, dark mode and image blocking. Some clients don't load images until the recipient allows it, in which case alternative text may be all they see.
The reliable check is to send test messages and view them in the clients your recipients actually use. Look at the logo on light and dark backgrounds and on a high-density display. Whether Exclaimer offers built-in multi-client previews or test sends is not established by the available evidence, so verify which preview features your setup includes.
Rights to the artwork
Being able to download or upload a logo is not the same as having permission to use or modify it. If the logo belongs to your organization, follow its brand guidelines on color variants, minimum sizes and clear space. If the signature includes other marks, such as partner logos, certification badges or awards, confirm that you may use them and in what form. Recoloring, cropping or redrawing someone else's trademark, or using its fonts, may require separate permission.
Gaps to resolve before rollout
- Which image formats Exclaimer currently accepts for signature logos, and whether SVG is among them.
- Any file size or dimension limits for uploaded images.
- Whether images are hosted and linked or embedded in the message, which affects image blocking and display.
- Which preview and test-send options are available in your plan or configuration.