Compatibility methodology

How we design signatures for real email clients.

A signature that looks correct in a browser can change after it is pasted into Gmail or Outlook. Our templates prioritize stable information and predictable layout over fragile visual effects.

Structure

Core layouts use HTML tables, explicit cell dimensions, inline styles, and email-safe font stacks. We avoid relying on flexbox, grid, pseudo-elements, CSS variables, or remote fonts in copied signature HTML.

Images

Signature images and icons use public static URLs rather than embedded data URLs. Dimensions are declared explicitly, and essential identity and contact information remains real text so a signature is still understandable when remote images are blocked.

Verification

  1. Render the default template and verify its expected geometry in a browser.
  2. Copy the formatted HTML using the same product flow as a user.
  3. Paste into supported client settings and send a real test message.
  4. Check links, images, spacing, alignment, replies, and mobile reading.

Gmail and Outlook versions, company security policies, and recipient settings can still modify HTML. Always send your own test message before adopting a signature.

Corrections

If a documented layout fails in a current email client, send the client version and a screenshot to intmainwjj@gmail.com.