Signavique
Documentation

Designing signatures

Client rendering quirks: Outlook, Gmail and Apple Mail

Every generated signature is table-based HTML with inline styles, because that is the only thing all three render the same way.

Current service scope: HTML creation and guided installation are available. Transport stamping and on-premises agents are not available; directory connectivity does not deploy outgoing signatures. Review service limitations.

8 min read

Outlook for Windows

  1. 1Uses Word to render: no flexbox, no CSS grid, no background images.
  2. 2Adds spacing around images — we set display:block and border:0 to stop it.
  3. 3Rounded corners on buttons fall back to square. That is expected.

Gmail

  1. 1Strips <style> blocks, so everything must be inline.
  2. 2Clips messages over 102KB — keep signatures small.
  3. 3Rescales on mobile; avoid fixed widths above 600px.

Apple Mail

The most forgiving of the three, but it will override your font unless the user unticks “match my default message font” when creating the signature.

Next guideLocking fields so staff can't change them