B Signature Style Requirements: Your Complete Guide

Designing an email signature is the easy part. Making sure it actually renders correctly, complies with any applicable disclosure rules, and behaves consistently across the mess of email clients your recipients use — that's where most signatures quietly fail. This guide covers the practical requirements a signature needs to meet: technical constraints, cross-client compatibility, sizing rules, and the kinds of disclaimers or disclosures some businesses are required to include.

Want expert help putting this into practice? B-Signature Pro can guide you through it.

Technical Requirements: How Email Clients Actually Render HTML

Email signatures are built with HTML, but not the same HTML you'd use for a website. Most email clients strip out modern CSS, JavaScript, and even basic layout tools like flexbox or grid, because email rendering engines are built on older, more limited standards. The safest approach is to use simple table-based layouts, inline CSS styles rather than external stylesheets, and web-safe fonts. Anything relying on custom fonts, animations, or advanced CSS positioning is likely to break, particularly in Outlook, which uses Microsoft Word's rendering engine for HTML email rather than a standard browser engine.

This is the single biggest source of signature problems: a design built and tested only in a browser or a design tool often looks completely different once it's actually inserted into an email and rendered by the recipient's client. Requirements-driven design means building conservatively from the start rather than trying to fix a broken layout after the fact.

It's also worth remembering that many email clients strip out embedded style blocks entirely, which is why inline styling — applying formatting directly to each HTML element rather than referencing a separate stylesheet — is considered a requirement rather than a preference for signature design. A signature that depends on an external or embedded stylesheet is far more likely to lose its formatting somewhere along the delivery chain.

Image Requirements: Hosting, Sizing, and Format

Related: bsignature - Expert Advice for Business Success.

Images in a signature should be hosted on a reliable, publicly accessible URL rather than embedded as base64 data or attached as files. Embedded attachments can trigger security warnings or show up as a separate file the recipient has to open; hosted images load inline and look intentional. Use PNG format for logos with transparent backgrounds, and keep file sizes small — large images slow down load time and can cause a signature to appear broken or partially loaded, especially on mobile connections.

As a sizing guideline, logos generally work best between 40 and 100 pixels in height, and headshots in a similar range. Anything larger tends to overwhelm the text and looks disproportionate once actually viewed in an inbox rather than a design canvas.

Cross-Client Compatibility Requirements

There is no single email standard, which means a signature needs to be tested — not just designed — across the major clients your recipients actually use. Outlook (desktop), Gmail (web and app), and Apple Mail each render HTML differently enough that a signature which looks perfect in one can shift, break, or lose formatting entirely in another. Common problem areas include: spacing collapsing unexpectedly, background colors not displaying, custom fonts falling back to a generic typeface, and multi-column layouts stacking awkwardly.

A practical requirement for any business signature is a testing pass: send the finished signature to a handful of test accounts across different clients and devices before rolling it out. Catching a rendering issue in testing costs a few minutes; catching it after a hundred employees have already deployed it costs a lot more.

It's also worth checking how a signature behaves in reply chains and forwarded messages, not just in a fresh outgoing email. Some clients duplicate the signature at every reply in a thread, while others strip it after the first message. Neither behavior is something you control directly, but knowing how your recipients' clients typically handle it helps set realistic expectations for how consistently your signature will actually appear.

Mobile Rendering Requirements

See also: Master B Signature Style Best Practices: Expert Guide.

A large share of business email gets read on a phone, and mobile clients often compress or truncate signatures more aggressively than desktop. A requirement worth building into every signature from the start: it should degrade gracefully on a narrow screen. That means avoiding wide multi-column layouts that force horizontal scrolling, keeping text sizes legible without zooming, and making sure any linked buttons or icons remain tappable rather than shrinking into unusable targets.

Disclosure and Disclaimer Requirements

Depending on your industry and location, there may be specific information your business is expected or required to include in outgoing email communications. Common examples include company registration details for certain regulated industries, confidentiality notices for legal or financial correspondence, and unsubscribe or opt-out language if the email includes any marketing content. Requirements here vary significantly by jurisdiction and industry, so it's worth confirming with your legal or compliance team exactly what needs to appear rather than assuming a generic disclaimer covers you.

From a design standpoint, disclaimers and legal text should be visually de-emphasized — smaller font, lighter color, placed below the main contact block — so they don't compete with the actual signature content, while still remaining fully legible and complete.

Accessibility Requirements

Accessible signatures matter more than many businesses realize. Every image, including logos and icons, should include descriptive alt text so screen reader users understand what's being displayed even if images don't load. Text and background colors should maintain sufficient contrast to remain readable for users with visual impairments. Links should use descriptive anchor text rather than a bare, unreadable URL wherever practical. These are small additions during the build process but meaningful for recipients who rely on assistive technology.

Governance Requirements for Teams

For any business deploying a signature across more than a handful of employees, there's a governance requirement that's easy to overlook: a single source of truth for the approved template, and a controlled process for updating it. Without this, signatures drift — different employees end up with outdated logos, inconsistent formatting, or, worse, missing required disclaimers, simply because everyone maintains their own copy independently.

This is the exact problem a centralized signature platform is built to solve. B-Signature Pro lets a business lock a compliant, tested template and push updates centrally, so every employee's signature meets the same technical, branding, and disclosure requirements without relying on each person to manage it themselves.

Meeting these requirements up front — technical rendering, image handling, cross-client testing, mobile behavior, disclosures, and accessibility — is what separates a signature that looks fine in isolation from one that actually holds up across the full range of ways it will be seen.