Best Practices13 min read

Outlook Signature Best Practices for 2026

Most Outlook signatures I see are either way too long, completely broken on mobile, or look like they were designed in 2008. The problem is that Outlook is genuinely harder to build for than Gmail or Apple Mail — it uses the Word rendering engine, which throws out half of modern CSS. Here are the rules that actually matter in 2026.

By the NeatStamp Team · Published March 2026 · 13 min read

The 12 golden rules of Outlook signatures

These aren’t opinions — they’re based on how Outlook actually renders HTML. Break any of these and you’ll see broken layouts, missing images, or deliverability problems. Follow them and your signature works everywhere.

Keep it under 4–5 lines of contact info

Less is more. A name, title, company, phone, and one social link is a complete signature. Everything beyond that competes with your actual email for attention. Most recipients spend about two seconds glancing at a signature — they're not reading it.

Use table-based HTML

Outlook renders email HTML using the Word engine, not a browser. That means flexbox, grid, and div-based layouts simply don't work. The only reliable layout system is HTML tables with inline styles. This is not elegant, but it works across Outlook 2016 through New Outlook and everything in between. See the full breakdown in the Outlook HTML guide.

Keep total HTML under 10KB

Deliverability matters. Email servers and spam filters start treating large signature blocks as suspicious. Some corporate mail gateways strip signatures over a certain size. Keep your HTML lean. If you're hitting 10KB, the culprit is almost certainly embedded images — which leads directly to rule 4. Deliverability guide has more on this.

Use hosted images, not embedded (base64 = attachment)

Base64-encoded images look convenient — no external hosting required — but they're a mistake. Outlook treats them as email attachments, so recipients see a paperclip icon. They also bloat your HTML file size significantly. Host all images on a public URL instead.

Keep images under 100KB total

Add up the file sizes of every image in your signature: logo, headshot, social icons, banner. That total should stay under 100KB. If you're over that, compress your JPEG photos (aim for under 25KB each) and run your PNGs through a tool like TinyPNG. Email signature size guide covers the exact numbers.

Use PNG for icons, JPEG for photos — never SVG

Outlook's Word renderer does not support SVG. It will show a broken image icon or nothing at all. Use PNG for logos and social icons (transparent background, sharp edges), and JPEG for headshots and photos (much smaller file size for photographic content).

Set explicit width and height on every image

Always set both the HTML width and height attributes directly on your img tag — not just in CSS. Without them, Outlook ignores your dimensions and renders images at their actual file size. A 400px logo file displayed without explicit dimensions will appear as 400px wide, breaking your layout.

Use inline CSS only

No CSS classes. No external stylesheets. No <style> blocks in the head. Outlook strips all of these. Every style property must be written directly on the element as a style attribute. This is tedious to write by hand, which is why signature generators exist.

Design for 500px width

A 500px maximum width works on desktop reading panes (which typically show at 600–800px) and scales down to mobile without horizontal scrollbars. It also leaves breathing room in Outlook's layout. Cap your outer table at 500px. Mobile-friendly signature guide has layout examples.

Test in dark mode

Outlook on Windows inverts colors that don't have explicit background declarations. If your text is dark on a white background but you haven't declared that white background inline, Outlook may flip it to dark — making dark text invisible on a dark background. Always set background-color: #ffffff on your outer table. Dark mode compatible signatures explains exactly which properties to declare.

Include a CTA, but keep it subtle

A scheduling link, a link to your latest blog post, or a one-line mention of a new product can all work well. The key word is subtle — a CTA that's bigger than your name looks desperate. One line, smaller font, below your contact details.

Don't use animated GIFs in Outlook

Classic Outlook (2016, 2019, 2021, and Outlook for Microsoft 365 on Windows) shows only the first frame of any animated GIF. It never plays. The animation you spent time on is completely invisible to the majority of corporate recipients. General email signature best practices covers more on multimedia in signatures.

Design tips: fonts, colors, and photos

The technical rules above keep your signature from breaking. These design guidelines keep it from looking bad. They’re not the same thing.

Font choices: stick to web-safe

Email is not a web page. Custom fonts from Google Fonts or your brand kit won’t load in Outlook — the client doesn’t fetch external CSS. Outlook will fall back to its own default (usually Times New Roman) if it can’t find your declared font. The safe choice is to use web-safe fonts as your primary declaration:

Arial

The most universally safe option. Clean, neutral, works at any size. Hard to go wrong.

Georgia

The best serif option. Authoritative feel without looking old-fashioned. Good for law, finance, academia.

Verdana

Designed specifically for screen readability. Slightly wider, very legible at 11–12px.

Trebuchet MS

A humanist sans-serif with a bit more character than Arial. Works well for creative fields.

Tahoma

Compact and clean. Windows staple. Renders particularly well in Outlook.

You can specify a brand font as your first choice with a web-safe fallback — for example: font-family: 'Lato', Arial, sans-serif. Recipients with Lato installed see it; everyone else sees Arial. The fallback is what matters. Keep body text at 12–13px minimum and your name at 14–16px bold.

Color contrast

Use dark text on a light background — not pure black (#000000), but a dark grey like #333333 or #1a1a2e. Pure black can cause inversion issues in some dark mode implementations. Your text needs to pass a 4.5:1 contrast ratio for normal text sizes. Common failures I see:

Light grey (#999999) on white — fails WCAG AA at normal text sizes
Brand colors that are too light (yellow, pale blue, mint green) as text
White text without an explicit background declaration — disappears in dark mode

Stick to a maximum of three colors in total: one primary brand color for accent elements (a divider line, your name, a CTA button), one dark neutral for body text, and white or very light grey for the background.

White space and photo shape

Cramped signatures look unprofessional. Give elements breathing room with cell padding in your tables — at least 4–6px between rows. Don’t stack seven lines of text with no visual separation.

For headshots: a circular crop looks modern and friendly. A square crop is more neutral. Either works — just apply the crop before you upload the image, not in CSS (CSS border-radius on images is unreliable in Outlook). Keep headshots at 80×80px or 100×100px display size. Anything larger and it starts to dominate the signature.

What to include vs what to skip

There’s no universal answer — it depends on your role, industry, and country. Here’s a clear breakdown.

Always include

Full name — as you’d appear on a business card
Job title — specific beats vague ("Senior Account Manager" vs "Sales")
Company name — linked to your company website
One phone number — direct line preferred
Email address — yes, even though they have it; it gets copied into forwards and calendar invites

Include if relevant to your role

Company logo — reinforces trust for client-facing roles
LinkedIn link — nearly universally appropriate
Headshot — strong for sales, consulting, coaching, real estate
Scheduling link — only if recipients actually book meetings with you
Pronouns — increasingly common in progressive industries and companies
Certifications or credentials — valuable in regulated fields (healthcare, finance, legal)

Legal disclaimer requirements by country

This catches people out. Some countries have actual legal requirements for what must appear in business emails, not just best practice suggestions:

UK: Limited companies must include full company name, registered number, registered office address, and country of registration in all business correspondence — including email. This is the Companies Act 2006.
Germany: Similar requirements under the GmbH-Gesetz and AG-Gesetz — company name, legal form, registered office, and registration court must appear.
EU generally: VAT numbers required in some B2B contexts.
US healthcare: HIPAA requires a confidentiality notice on emails that may contain protected health information.
US financial services: FINRA and SEC-registered firms need regulatory disclosures.

Check with your legal team or company secretary for your specific obligations. NeatStamp’s team signature management lets you add required legal text as a locked field that employees can’t accidentally delete.

Leave these out

"Sent from my iPhone" or "Sent from my Android" — turn this off immediately
"Please consider the environment before printing" — accomplishes nothing
Inspirational quotes — unless thought leadership is your specific positioning
Animated GIFs — broken in classic Outlook, distracting everywhere else
More than 3 social media icons — two or three platforms you’re actually active on
Your full mailing address — unless legally required or you run a physical location business

For a detailed breakdown of every element and whether it earns its spot, the Outlook signature guide covers this with specific examples by industry. You can also see what clean, minimal signatures look like in the template library.

Company-wide best practices for teams

One person following these rules is good. Your whole company following them consistently is significantly better. A uniform signature policy creates brand consistency and makes legal compliance manageable. Here’s how to do it right.

Define a signature policy first

Before you build anything, decide what’s mandatory and what’s optional. A good policy covers: required fields (name, title, phone, email), brand elements (approved logo, approved colors), what employees can personalize (maybe their pronouns or a personal LinkedIn link), and what’s prohibited (personal quotes, non-brand images, custom fonts).

Write this down. An unwritten policy gets ignored as soon as someone joins and sets up their signature based on a colleague’s six-year-old example.

Centralized deployment options

Exchange / Microsoft 365 transport rules

Microsoft 365 lets IT admins apply server-side signatures via transport rules (also called mail flow rules). These append HTML to every outgoing email automatically, regardless of what signature the user has locally. The downside: they apply after the email leaves Outlook, so the sender doesn't see the signature in their sent copy.

Active Directory + signature template tools

Tools like CodeTwo, Exclaimer, and Crossware pull employee data from Active Directory (name, title, department, phone) and auto-populate signature templates. Good for larger organizations where keeping 200 signatures updated manually is impractical.

Managed signature platforms

NeatStamp's team plan lets you create a master template, lock brand elements that can't be changed, and let employees fill in their personal details. Everyone gets a consistent, correctly coded signature without involving IT for every update.

Update management

Signatures go stale fast. Phone numbers change, people get promoted, offices move. Set a quarterly reminder to audit signatures across your team. With a centralized tool, you change the template once and everyone’s signature updates. Without one, you’re chasing 30 people to re-install theirs.

The email signature for teams guide covers deployment options in much more detail, including the Microsoft 365 transport rule setup step by step.

Testing checklist before you deploy

Building a signature is step one. Testing it is step two — and most people skip it. Here’s what to check before you roll anything out.

Outlook desktop (Windows)

Images display at the correct size (not at full file resolution)
Layout doesn't collapse — columns stay side by side
Text renders in the correct font (Arial, not Times New Roman)
Links are clickable (phone number, email, website, social icons)
No images show as email attachments

Dark mode (Outlook + other clients)

Text is visible on dark backgrounds
Background is explicitly declared white (#ffffff) in inline style
No text or icon disappears
Logo is legible (consider a dark-mode version if your logo is white)

Mobile (iOS Mail + Gmail + Outlook mobile)

No horizontal scrollbars
Text is at least 11px and readable without zooming
Phone number is a tappable tel: link
Social icons are at least 24×24px (tappable)
Images scale proportionally

Gmail and Apple Mail

Images load from external URLs (not broken)
Colors are correct
Spacing looks right (Gmail sometimes adds margins)

Content

All links go to the right URLs (easy to make a typo)
Phone number is correct and includes country code for international contacts
Company website link works
No outdated job title or company name

If you want to test properly without sending test emails to your team, use a service like Litmus or Email on Acid for multi-client preview rendering. For quick checks, send to yourself across a Gmail account, an Outlook.com account, and your work email — that covers the most common rendering paths. The Outlook-compatible signature guide goes deeper on testing in specific Outlook versions.

How NeatStamp handles this for you

Every rule in this guide is built into NeatStamp’s output. When you build a signature in the NeatStamp editor, the generated HTML automatically:

Uses table-based layout compatible with Outlook 2016 through New Outlook
Applies all styles inline (no classes, no external CSS)
Sets explicit width and height on every image
Uses only web-safe fonts with appropriate fallbacks
Declares background colors explicitly to prevent dark mode inversions
Keeps the HTML well under 10KB
Hosts your images on a CDN (Pro plan) so they never appear as attachments
Generates mobile-responsive code within a 500px max-width structure

You don’t need to know any HTML to build a correctly coded signature. The editor gives you a visual interface; the output is production-ready code you can paste directly into Outlook. If you want to inspect or customize the HTML, you can — but you don’t have to.

For teams, NeatStamp lets you create a master template, lock the elements that must stay consistent (logo, colors, legal text), and let each team member fill in their own name, title, and photo. One click updates the template across everyone. The team features page has the full details.

Frequently asked questions

Why does my Outlook signature look different on the recipient's end?

Outlook uses the Word rendering engine to display HTML, which ignores many standard CSS properties. The most common culprits are CSS classes (Outlook strips them), non-table layouts (Word doesn't understand div-based layout), and custom fonts that aren't installed on the recipient's machine. Build your signature with table-based HTML and inline styles only.

What's the maximum size for an Outlook signature HTML file?

Keep the total HTML under 10KB. Beyond that, some mail servers and spam filters start treating the signature as suspicious content. Base64-encoded images are the fastest way to blow this limit — a single 20KB logo becomes 27KB of base64 text. Use externally hosted images instead.

Can I use animated GIFs in my Outlook signature?

Classic Outlook (2016, 2019, 2021, and Outlook for Microsoft 365 on Windows) only renders the first frame of an animated GIF — it never plays. New Outlook and Outlook on the web do support animation. Since most corporate users are still on classic Outlook, it's safest to avoid animated GIFs altogether unless you know your audience.

How do I make my Outlook signature work on mobile?

Design for 500–600px maximum width. Use a single-column layout that scales down gracefully. Set explicit width and height attributes on all images. Keep text at 11px minimum. Wrap phone numbers in tel: links so they're tappable. Outlook mobile renders signatures fairly faithfully if the HTML is clean table-based code.

Do I legally need a disclaimer in my Outlook signature?

It depends on your country and industry. In the UK, limited companies must include their company registration number, registered office, and place of registration in business emails — that's a legal requirement. In the US, HIPAA requires disclaimers for healthcare communications. Financial services firms in most countries need regulatory body references. For most other businesses, a confidentiality disclaimer is optional but common.

Should I use PNG or JPEG for my logo in Outlook?

PNG for logos — it supports transparent backgrounds and renders sharp edges without artifacts. JPEG for headshots and photos — the file size is significantly smaller for photographic content. Never use SVG in Outlook signatures. Outlook's Word renderer does not support SVG and will either show a broken image icon or nothing at all.

How do I deploy one Outlook signature across my whole team?

There are three common approaches: Exchange/Microsoft 365 transport rules (server-side, no user involvement required), Active Directory-linked templates via third-party tools, or a managed signature tool like NeatStamp that lets you push consistent signatures to everyone from a single dashboard. The right choice depends on your IT setup and how much control you need.

Why does Outlook show my image as an attachment?

This almost always happens when images are embedded as base64 data URIs rather than hosted externally. Outlook treats embedded images as email attachments. Host your images on a public URL (your company website, a CDN, or NeatStamp's hosting) and reference them with a standard img src tag.

Build a signature that follows every rule on this page

NeatStamp generates Outlook-compatible HTML automatically. No code required. Free to try, takes about 60 seconds.

Create My Signature — Free Browse Templates