How to Create a Professional Email Signature
Learn how to create a professional email signature with clear contact details, restrained design, simple construction, and real-world testing.
Sophie Grant
Email Signature Specialist, Scribe

On this page
- Define the fallback-first contact path
- Lock the identity layer before adding extras
- Give each link one recipient job
- Keep the text layer readable without visuals
- Choose a format that preserves the fallback
- Make images optional and removable
- Build the text fallback before styling
- Run a fallback-first rendering check
- Seek professional evaluation when requirements remain unresolved
- Compare the received message across environments
- What should you check before using a professional email signature?
- Is a phone number required in a professional email signature?
- Should a professional email signature be plain text or HTML?
- How should I add a logo without making the signature dependent on images?
- What should a real email signature test message check?
- Sources
Define the fallback-first contact path
Use a fallback-first audit to create a professional email signature. Begin with the text a recipient needs when images, styling, or optional elements are unavailable, then add only the enhancements that preserve that contact path. Email signature etiquette is about presenting clear, useful contact information without creating clutter.
The audit has three layers: identity establishes your name and role; route provides a practical way to reach you or find one relevant professional destination; enhancement adds optional branding, imagery, or an action. Build the identity and route layers as text first. A logo, color, image, or call to action earns its place only when the underlying text remains clear without it.
The recipient’s next action should remain easy to see. Excess information can make a signature bulky and long, which can deter people from reading it or clicking its links. Images, colors, and random quotes can also make a signature feel cluttered and may undermine your credibility during a professional connection.
Use the contact path as your first review question: can someone identify you quickly, understand why you are contacting them, and find the most useful way to respond? If the answer is unclear, reduce the content before changing the styling.
Lock the identity layer before adding extras
Start the fallback-first audit with the identity layer. It should establish who you are, what you do, and how someone can reach you before any visual element is added:
- Your full name, written as you use it, so recipients know what to call you.
- Your job title and department, when those details give useful context about your role.
- A practical phone number; add a mobile number when it is pertinent to your work.
- Your professional email address when recipients may need to find or copy it.
A job title may be especially useful in a corporate setting because it gives recipients context without requiring them to look you up. Keep the identity layer as readable text and distinguish the name from the title and department. Leave out credentials or descriptors that do not help someone understand your role.
The contact method in your signature should match the way people are expected to reach you. A direct phone number is optional, so include it when a call is a useful route for your role rather than treating it as a compulsory field. Your email address can still be useful even when someone has just received a message from you: some email clients show your name rather than your address in the From field, making the actual address harder to find.
You can add your company name and logo, website, office address, relevant social profiles, and email address when they are useful. Treat those fields as supporting information, not as a second identity block. If an office address is not relevant to the people you contact, leave it out. If a social profile does not represent your professional role, leave that link out as well.

Give each link one recipient job
Give the route layer one clear destination. Include one relevant link, such as a professional social profile or a useful website page, when it adds context beyond your name and role. Use a short linked label instead of displaying a long URL in full.
Avoid too many links because they can confuse recipients and may trigger spam filters. Review each possible destination by asking what recipient need it serves and whether it duplicates another route. Remove social profiles, product pages, booking pages, campaign pages, or personal destinations that do not support the messages you send and the people who receive them.
The optional content in your signature should earn its space by helping recipients understand or continue the professional exchange. Remove large images, multiple fonts, bright colors, unnecessary disclaimers, promotional language, lengthy quotes, and personal social links unless they are relevant to your role.
A simple editing pass can separate useful context from decoration:
- Keep the company website when it helps someone understand the organization.
- Keep a professional social link when it represents your work and has a clear purpose.
- Remove quotes, slogans, and promotional copy that do not help the recipient respond.
- Remove duplicate ways to reach you when they add no practical choice.
- Keep a call to action only when it is relevant to the message and easy to ignore when it is not.
The result should feel complete without becoming a second marketing message.

Keep the text layer readable without visuals
Review the identity and route layers as plain text before applying visual hierarchy. The name and role should be easiest to scan, with contact methods and links arranged underneath in a consistent order. Keep the block concise enough that the message remains visible on a phone; remove optional content before shrinking necessary text.
Use one clear typeface family, a readable size, and a modest distinction between your name and supporting details. Limit graphic elements to 1-2 to help avoid a cluttered design. A horizontal rule, small logo, or restrained color accent may provide structure, but multiple decorative elements can make the block feel like an advertisement. If the text becomes difficult to read when the image or color is removed, simplify the enhancement layer.
The brand layer of your signature can use your company’s color palette, logo, and fonts, while still needing to remain readable on phones. Use brand color for a limited emphasis rather than coloring every line. Keep the main contact information understandable if color is removed or displayed differently.
A call to action or promotional banner is optional. Add one subtle, relevant action only when it serves the recipient, such as following a company account or visiting a page connected to the conversation. Do not let the action appear more prominent than your identity details. The contact path should remain useful even when the action is ignored, blocked, or removed from a particular email view.

Choose a format that preserves the fallback
Choose the construction format by asking whether it preserves the identity and route layers when the enhancement layer changes. Plain text is suitable when clarity and broad simplicity matter most. HTML supports clickable links and styled layouts when you need a more structured block, but the text should remain understandable without its styling.
Most email platforms offer built-in tools for creating and customizing signatures. A signature maker can create formatted HTML from your contact details, imagery, template, and brand colors, producing ready-to-use signature code. A reusable generator or approved template can save repeated formatting work, but review its output against the text fallback rather than judging the visual block alone.
The layout complexity of your signature affects how confidently you can move it between tools. When a signature is built in Word and copied into Outlook, greater complexity makes it less likely to look good. Use a small number of text styles, straightforward spacing, and links that can be checked individually.
For image insertion, avoid dragging and dropping images into a signature because most clients may strip embedded files or block them for security. Use the insertion method provided by the relevant signature editor, then inspect the result instead of assuming the pasted version is intact. Keep a clean source version of the approved content so you can make a controlled change rather than rebuilding the entire block from a visual copy.
Make images optional and removable
Treat the image layer as removable enhancement, not as part of the fallback. A small company logo can be included in JPG or PNG format when it adds useful branding, but the name, role, contact details, and links should remain available as text. Recipients may not see a logo when images are turned off, and using an image can increase the likelihood of spam filtering.
Do not rely on text inside a logo to communicate essential information because logos with text are not accessible to people with vision impairments. Add descriptive alt text to an image and use a descriptive filename so a blocked image has a meaningful fallback. Remove the image from the audit and confirm that the identity and route layers still stand on their own.
The image hosting choice affects whether recipients can load the asset. Use an absolute HTTPS URL for a signature image, not a relative path or an HTTP URL, and host the file on a secure, publicly accessible server or CDN. Email clients may block images from non-secure or private domains.
Do not place the image in a password-protected or private folder because external email clients may not be able to authenticate to that location. Keep the asset visually quiet: overly bright, flashing, or animated images may be flagged by enterprise spam filters, and some clients may strip GIFs completely.
For the image dimensions and file method, use a maximum width of 600px because wider images are often resized or cropped. Many email clients, including Outlook and Yahoo, may strip or reject inline base64 content, especially for images larger than 50KB. These limits describe the image asset, not the length of the text block, so review both separately.
Build the text fallback before styling
Build the reusable block in two passes. First write the text fallback with the identity and route layers: name, role, practical contact method, and one useful link. Then add optional branding, imagery, or a relevant action without moving essential information into those elements.
If an image is used, keep it small and simple, add descriptive alt text, and use an absolute HTTPS URL from a secure, publicly accessible host. Keep one version of the text fallback beside the styled version. Later checks can then show whether a change affects the contact path or only the removable enhancement layer.
Keep the contact details as text outside the image so they remain available when images are blocked. If you use a transparent PNG logo, use a width of 150-200px. Add the block through the relevant email client or approved organizational process, then compare the received message with the intended version at representative mobile, desktop, webmail, and native-app contexts. A difference in wrapping, spacing, image loading, or readability is a reason to simplify the block before using it.
Run a fallback-first rendering check
Use the rendering check to compare the styled version with its text fallback. Email clients can display the same signature differently because they use different HTML rendering engines. A signature that looks good on a desktop can appear oversized or broken on a phone, and the reverse can also happen. Test across relevant clients and devices because rendering can vary by client, device, and mobile operating system, which are regularly updated.
Preview the signature on both mobile and desktop before you adopt it. Look for horizontal scrolling, text that is difficult to read without zooming, links or phone numbers that are hard to tap, styles that disappear, and images that change the spacing around the text. The key check is whether the identity and route layers remain usable when a visual element changes or disappears; a preview should be followed by a real message.
The test message should use realistic data and the intended sending identity. Use this short validation sequence:
- Insert the approved signature into the intended email identity.
- Compose a real message with realistic sender details and ordinary body text.
- Send the message to a test address or representative recipient environments.
- Open it in supported desktop, mobile, webmail, and native-app contexts.
- Check the layout, images, links, wrapping, spacing, and text readability.
- Check that phone numbers and links are easy to tap and that any action remains visible without taking over the message.
- Correct the source block, then send the test again after a material change.
The test should expose the conditions recipients will actually encounter. A saved signature that has not traveled through a real message has not completed this check.
The acceptance check for your signature should be specific enough to produce a correction, not just a general impression. Confirm that the name and role remain clear, the contact path stays in order, links open the intended destinations, images load or fail without damaging the text, and the block does not crowd the message on a small screen.
Check fixed-width layouts, font readability, tap-target size, inline styles, and live phone and desktop rendering when previewing the signature. If a client changes the spacing or removes an image, decide whether the text version still works. If it does not, simplify the construction or remove the dependent visual element before use.
Seek professional evaluation when requirements remain unresolved
Organization-specific requirements can change the acceptable signature content or review path. If a legal, accessibility, compliance, or brand requirement remains unclear after you have assembled and tested the block, pause the rollout and route that question to the responsible reviewer in your organization.
Use the same boundary for a material unresolved failure: an image that will not load, a link that reaches the wrong destination, a layout that obscures the message, or text that cannot be read comfortably on a supported device. Record the issue, the environment where it appeared, and the correction needed. Do not approve the signature until the responsible requirement or failure has a clear disposition.
A review is also appropriate when several teams need different fields or actions. Resolve the shared identity and contact requirements first, then document which variation is allowed for each role. That keeps a necessary variation distinct from an accidental inconsistency.
Compare the received message across environments
Use a real message to evaluate the signature in the environments that matter to recipients. Populate it with realistic user data, send it, and open it in representative mobile, desktop, webmail, and native-app contexts. Check links, image loading and fallbacks, wrapping, spacing, and readability. If a check exposes a problem, return to the text, image, or layout choice and simplify it before use.
Repeat the comparison after changing a link, image, layout, or optional action. Keep the source block available so the same checks can be run on the next revision. For teams that need a reusable, approved email signature format without making IT the bottleneck for routine updates, see Scribe on a 30-minute call with our team.
What should you check before using a professional email signature?
Is a phone number required in a professional email signature?
Not always. Some guidance treats a phone number as a core field, while other guidance treats a direct number as optional. Include one when calling is a practical contact route for your role or when your organization requires it; otherwise, make sure recipients still have a useful way to reach you.
Should a professional email signature be plain text or HTML?
Use plain text when maximum simplicity and portability matter. Choose HTML when you need clickable links or a styled layout, but keep the structure simple because email clients can render the same HTML differently. In either format, test the version that recipients will receive.
How should I add a logo without making the signature dependent on images?
Keep your name, role, contact details, and links as live text, and use the logo only as supporting branding. If you include an image, use a small JPG or PNG with descriptive alt text, an absolute HTTPS URL, and publicly accessible hosting. Do not put essential information only inside the logo, because recipients may not see images and text inside logos is not accessible to people with vision impairments.
What should a real email signature test message check?
Send a message using realistic details from the intended email identity, then open it in representative desktop, mobile, webmail, and native-app environments. Check the links, images, wrapping, spacing, readability, phone-number and link tap targets, and whether the signature still works when an image is blocked. Repeat the test after any material change to the source block.
Get started with Scribe
Create your signature in minutes
Free 14-day trial — no credit card.






