Free Gmail Signature Generator

Why Gmail signatures need their own tool

Gmail is not a normal HTML email client. It strips parts of the HTML you paste into its signature editor, it limits the signature to 10,000 characters, and it renders differently on Gmail web, Gmail dark mode, the Gmail iOS app, and the Gmail Android app. A signature built without any of those quirks in mind shows up clipped, broken, or invisible depending on where the recipient opens it.

This generator targets those quirks directly. The canonical Email Signature Generator handles the broad case — Outlook, Apple Mail, Yahoo, all of them. This page is for the situation where you sign in to Gmail every morning and want your signature to look right there specifically.

Gmail's 10,000-character signature limit, explained

Gmail caps each signature at 10,000 characters of HTML — confirmed in the official Gmail help docs. When you exceed it, Gmail rejects the save and shows the "The signature is too long" error.

A few things to know about how Gmail counts:

• It counts the full HTML, not the visible text. A signature that reads as 200 words of plain text often hits 2,000–3,000 characters of HTML because of the wrapping tags, inline styles, and `<table>` markup that survives the editor.
• Pasting from Microsoft Word or Google Docs almost always exceeds it. Word inserts ~6,000 characters of MS-Office-specific markup around the visible text alone. The same signature pasted from a proper HTML editor will be 5× lighter.
• Embedded base64 images can blow past the limit on their own. A 50 KB photo embedded as base64 is ~67,000 characters. Always host the image externally (our tool does this automatically via imgbb) so only the URL counts toward your 10,000.

How to add a signature in Gmail on desktop

Gmail moved the signature settings into the modern UI around 2018 and they have stayed in roughly the same place since. The path:

1. Open Gmail in any browser. Click the gear icon in the top right.
2. Pick "See all settings" from the panel that slides out.
3. Stay on the General tab. Scroll until you reach Signature.
4. Click "Create new", give the signature a name (e.g. "Work full"), then paste the signature into the editor.
5. Below the editor, find Signature defaults. Set "FOR NEW EMAILS USE" and "ON REPLY/FORWARD USE" — these are the two dropdowns that decide which signature appears where.
6. Scroll to the very bottom of the General tab and hit Save Changes. Gmail throws away everything if you skip this step.

How signatures work in the Gmail mobile apps (iOS and Android)

Mobile is the place Gmail signatures break most often. The two apps behave differently:

Gmail iOS

The Gmail iOS app does not render HTML in signatures composed on the device. It supports plain text only. If you want an HTML signature to appear on iOS, you have to set it from the desktop web app — the iOS app will then pull and use the desktop-set signature when sending from the same account. Signatures composed inside the iOS app are plain text on the wire, even if the message body is HTML.

Gmail Android

Android historically had the same plain-text-only restriction. As of March 2025, the Android Gmail app honors HTML signatures that were set on the desktop and synced via the account. Signatures composed directly in the Android app are still plain text. So the rule is the same: set the HTML version on desktop, and Android will follow.

Setting up multiple signatures (one per identity)

Gmail supports multiple signatures per account. The use case is people who send from more than one address (work + personal, founder + customer-support, "Send mail as" linked accounts). To set one up:

1. In Gmail Settings → General → Signature, click "Create new" once for each signature you want.
2. Under "Signature defaults", the dropdowns let you pick a different signature per "Send as" identity. So an email sent from your personal address can use one signature, and an email sent from your business address can use another, automatically.
3. You can also pick "No signature" for some identities — useful for transactional accounts (notifications@, no-reply@) where a signature would be weird.

Setting up a company-wide signature in Google Workspace

If you're an IT admin rolling out signatures across an organization, Google Workspace lets you append a footer to every outgoing message from a given organizational unit. This is different from per-user signatures — Google calls it an append footer and it stamps after the user's individual signature, regardless of what they have set personally.

1. Open the Google Workspace Admin console. Sign in with a super-admin account.
2. Apps → Google Workspace → Gmail → Compliance → Append footer.
3. Pick the organizational unit (everyone, a department, a single user group), then click Configure.
4. Paste the HTML footer into the editor. Keep it short — Google's append-footer feature is HTML but more aggressively sanitized than the user-facing signature editor. Stick to a single `<table>` with inline styles.
5. Save. The footer applies to every message sent from accounts in that OU within a few hours.

The append footer is the right tool for legal disclaimers and address blocks that must appear on every message uniformly. It's the wrong tool for per-user signatures with names and photos — those should stay in each user's personal Gmail settings. Many orgs run both: a personal signature for branding and a compliance footer below it.

Adding images and logos without breaking them

About half of the Gmail signature support requests on the internet are some flavor of "my signature image is broken." There are three common causes and one root fix.

The causes:

• Private image URL. You uploaded the image to Google Drive but the link permission is "Restricted." Gmail can serve it to you but not to the recipient. Switch the Drive sharing to "Anyone with the link can view" — or better, host the image somewhere else.
• Plain-text composition mode. If you switch the email composer to plain-text mode, your HTML signature is replaced by its plain-text fallback for that message. The image cannot exist in plain text, so it shows up as a broken filename instead.
• Recipient blocked images. Gmail and many corporate inboxes block external images by default until the recipient clicks Show Images. The signature looks "broken" until they do. You cannot fix this from the sender side — it is a recipient-side setting.

The fix: host the image on a public CDN that always returns a 200 OK without authentication. Our tool does this automatically via imgbb when you upload through the Photo or Logo section. The resulting URL is short, public, and stable.

Designing for Gmail dark mode

Gmail mobile flips a lot of users into dark mode by default. Gmail desktop has a dark theme too. Signatures designed for white-on-white can become invisible when the client inverts the background but leaves the text color untouched.

Three rules that keep a signature legible in both modes:

1. Specify both color and background-color on every text node. Leaving background unset and only setting `color: #000` leaves the text black on whatever color the client picks. Set both.
2. Use transparent PNGs for logos and photos. A logo on a white background looks fine in light mode and like a white rectangle floating in space in dark mode. Transparent backgrounds work in both.
3. Avoid pure black (#000) and pure white (#fff). Most clients aggressively invert these. A near-black (#222) or near-white (#f7f7f7) survives the inversion intact.

The Quoted-Printable corruption issue

A lesser-known Gmail problem: when your signature contains long lines of HTML and the recipient's mail server transcodes the message into Quoted-Printable encoding (per RFC 2045), the encoder inserts soft line breaks every 76 characters. Those breaks turn URLs and CSS values into broken tokens — `https://exa=` followed by `mple.com/path` on the next line.

For the original recipient, modern mail clients re-fold the soft breaks back into one line and the signature renders fine. For someone forwarding or replying inside an older or unusual client, the soft breaks stay literal and the HTML breaks. The fix on our end: short attribute values, no inline base64 (already enforced via imgbb hosting), no comment-only `<!--…-->` blocks that the encoder mangles. Our generator follows these rules automatically.

Troubleshooting: signature not showing, image broken, error messages

Gmail signature vs. Gmail "vacation responder" — not the same thing

Worth clearing up because it confuses new Gmail users: a signature is a block appended to every outgoing email. A vacation responder is an auto-reply that fires when an email arrives while the responder is on. They live in different parts of Gmail Settings and serve different purposes.

If you want an auto-reply for time off, that is the "Vacation responder" section further down the General tab. If you want every email to carry a consistent branded sign-off, that is the Signature section we have been covering.