Free · No signup · Gmail & Outlook ready

Email Signature Generator

Build a professional email signature in seconds and copy the HTML. Works with Gmail, Outlook, and Apple Mail — no account, no watermark.

Template
Personal Details
Contact
Branding
Legal (optional)
Live Preview

Hi there,

Thanks for reaching out. I'll get back to you shortly.

Best regards,

  1. Click Copy HTML above
  2. Open Gmail → Settings (gear icon) → See all settings
  3. In the General tab, scroll to Signature
  4. Click Create new, give it a name
  5. In the signature editor, press Ctrl+Shift+V (Win) or ⌘+Shift+V (Mac) to paste without formatting
  1. Click Copy HTML above
  2. Open Outlook → File → Options → Mail → Signatures
  3. Click New, name your signature
  4. In the editor, right-click and choose Paste Special → HTML
  5. Click OK and set as default
  1. Click Copy HTML above
  2. Open a text editor (TextEdit), paste and save as signature.html
  3. In Apple Mail → Mail → Settings → Signatures
  4. Create a new signature, then quit Mail
  5. Replace the signature file in ~/Library/Mail/V*/MailData/Signatures/ with your HTML file

Why every competitor requires a login

HubSpot, MySignature, and Canva all require an account to export your email signature. This tool generates the HTML entirely in your browser — nothing is sent to any server. Your signature data stays private.

Instant copy

The HTML is generated live as you type. Click "Copy HTML" and paste directly into Gmail, Outlook, or Apple Mail settings.

🖼

Photo support

Upload a profile photo and it's embedded as a base64 data URI — no external image hosting required, which means it loads in all email clients.

🎨

Three templates

Modern (accent bar + horizontal layout), Classic (centered with divider), and Minimal (inline text, no images) — all tested in major email clients.

Email HTML is not web HTML

Email clients render HTML with engines that range from a decade behind the web to genuinely idiosyncratic. Outlook on Windows uses Microsoft Word's rendering engine, which has no meaningful support for flexbox, grid, or float-based layout, and handles padding inconsistently.

Consequently, signatures must be built with nested tables and inline styles — the technique the web abandoned twenty years ago. External stylesheets are stripped by most clients, and <style> blocks in the head are removed by several, so every declaration belongs in a style attribute on the element itself.

Use table cell padding rather than CSS margins, specify widths in pixels rather than percentages where precision matters, and avoid background images, which Outlook ignores. Web fonts do not load in most clients, so specify a font stack ending in a system font and accept that many recipients see the fallback.

Images, tracking and the blocked-images case

Most clients block remote images by default until the recipient chooses to load them, so a signature that is entirely one image arrives as an empty box with a broken-image icon. Anything essential — your name, role and contact details — must be live text, not baked into a graphic.

Every image needs meaningful alt text and explicit width and height attributes, so the layout does not collapse when images are blocked. Serve images from a stable, publicly reachable HTTPS URL: signatures are forwarded and archived for years, and a broken image in a signature looks worse than no image.

Keep logos small. A signature adds its weight to every message in a thread, and a large logo repeated through a long conversation is both wasteful and visually noisy. Around 150 pixels wide, at twice that in actual pixels for high-density screens, is generally ample. Note also that Apple Mail's privacy protection and similar features now pre-load images for many recipients, so image loads are not a reliable indication that anyone read the message.

Content, legal requirements and restraint

A signature should carry name, role, organisation and one or two reliable ways to reach you. The common failure is including everything — five phone numbers, six social links, a quotation, a legal disclaimer and an environmental appeal — which buries the useful information and looks unprofessional.

Some elements are legally required in some jurisdictions. UK companies must state the registered company name, registration number, place of registration and registered office address in business emails under the Companies Act; Germany and several other EU states have comparable requirements. Regulated professions often have their own obligations. Confidentiality notices, by contrast, have very little legal effect and are largely ritual.

Consider accessibility and plain text. Colour should not be the only way information is conveyed, contrast should meet the usual thresholds, and a plain-text alternative should carry the same details, since some recipients read mail as text. Test the finished signature in Outlook on Windows, Gmail on the web, and Apple Mail on iOS at minimum — those three cover most recipients and fail in different ways.

Frequently Asked Questions

Is my information uploaded anywhere?

No. Everything runs in your browser. Your name, contact details, and photo are never sent to a server.

Will it work in all email clients?

The generated HTML uses table-based layout which is the most widely compatible approach for email clients, including older versions of Outlook which use Word's rendering engine.

Why embed the photo as base64?

External image URLs in signatures are often blocked by corporate email filters. Embedding as base64 means the image is part of the HTML and always loads correctly.

Can I use a company logo instead of a photo?

Yes — the photo upload accepts any image. Upload your company logo and it will appear in the signature in place of a profile photo.

Why does my signature look broken in Outlook?

Outlook on Windows renders with Microsoft Word's engine, which does not support flexbox, grid or floats and handles padding inconsistently. Build with nested tables and inline styles, and use cell padding rather than CSS margins.

Can I use an image for my whole signature?

No. Most clients block remote images by default, so it would arrive as an empty box. Keep name, role and contact details as live text, and give every image alt text plus explicit width and height.