Outlook signature or server-side signature: which is better?

What differs between a signature set in Outlook and one added by Exchange on the server, and the trade-offs of each.

Updated 16 November 2026

An email signature can be added in two places: in the mail program while the person writes (a client-side signature), or by the mail system after the message is sent (a server-side signature). Each has strengths.

Client-side: set in Outlook

  • Visible while writing. The sender sees exactly what goes out, and it is in their Sent Items.
  • Sits where the person puts it. On a reply it can appear directly under the new text.
  • Per device and per app. Outlook on Windows, Mac, the web and a phone each have their own signature setting. Gaps are common.
  • Hard to keep consistent. People edit, delete or paste in their own version.

Server-side: added by Exchange

  • The same on every device. Added as the message passes through Microsoft 365, including mail sent from phones.
  • Consistent and current. One change updates everyone; staff cannot remove it.
  • Added at the end. It goes after the whole conversation on replies and forwards, not under the latest text.
  • Not visible to the sender while writing, and not in their Sent Items copy.
  • Images are linked. See the limits to plan for.

How to decide

If brand consistency, legal wording or mobile coverage matter, server-side wins. If a sender needs to see and position the signature in long threads, client-side is friendlier. Many organizations use a server-side signature for external mail and keep it short, so the trade-offs stay small.

LlamaSig is server-side: it does not run in Outlook and does not show the signature while composing. How signatures are applied.

More guides