Gmail blocks email signatures over 10,000 characters. Here's how the limit really works, why your signature blew past it, and how to slim the HTML down without losing the design.
The MailSigCraft Team
MailSigCraft
You designed a clean signature, pasted it into Gmail, and Gmail either refused to save it ("This signature is too long") or — worse — saved a truncated copy that quietly dropped the last social icon, logo, or disclaimer. This is the 10,000-character limit, and the frustrating part is that the limit applies to HTML characters, not visible text. A signature that looks like one short line can easily blow past it.
This post explains exactly what counts toward the 10K budget, the three things that almost always push you over it, and how to slim the HTML down without losing the design.
When Gmail says "10,000 characters," it means 10,000 characters of the raw HTML stored on Google's servers — not the visible text length. A signature that reads "Jane Doe — CEO, Acme Inc" can balloon to 6,000+ characters of HTML once you add a logo, social icons, formatting, and inline styles.
Three culprits, in order.
This is the #1 reason. A single 5KB logo encoded inline takes up roughly 6,800 characters of HTML on its own. Two icons plus a logo and you've spent most of your budget before the text starts.
Host images on a CDN and use <img src="https://..."> instead of data:image/png;base64,.... That one change typically cuts a signature's HTML size by 80%. The MailSigCraft editor does this for every image you upload by default.
Email HTML needs inline CSS (no <style> blocks), but most signature generators are sloppy about it — every <td> carries the same 200-character style="font-family: ...; font-size: ...; line-height: ...; color: ...; padding: ...;" block, repeated across 20+ cells.
Consolidate common styles onto parent cells, use shorthand properties (font: 14px/1.4 Arial beats two separate declarations), and strip whitespace from the rendered HTML. A well-inlined signature uses 30–40% less CSS than a generated one.
Some signature tools append ?utm_source=email&utm_medium=signature&utm_campaign=q2-launch to every social link. Across six social platforms, that's 600+ characters of pure overhead.
Use shorter UTM params (?u=sig) or move tracking to a server-side redirect — that's exactly what MailSigCraft's click-tracking does, swapping every long link for a short /go/... URL.
Open your signature in the MailSigCraft editor.
Click Copy HTML (the option labeled "Copy HTML," not "Copy Signature").
Paste the HTML into any character counter, or in your browser's DevTools console run copy(prompt('paste:')) and check the length.
Anything under 8,000 leaves headroom. 8,000–10,000 will work but is risky. Over 10,000 will be rejected or truncated. The 10K ceiling hasn't moved in years, so designing to an 8,000 cap gives you a 20% safety margin against future shrinkage or admin-injected disclaimers.
Switch every image from base64 to a hosted URL. This alone solves most "too long" errors.
Drop logos that don't earn their pixels. A 200×200 logo displayed at 32px is wasting 3× the bytes it needs. Re-export at 2× the display size (so 64×64 for a 32px logo) and the file shrinks proportionally.
Cut social icons you don't actually need. Each icon costs roughly 800 characters of HTML. Six icons = 4,800 characters; three icons = 2,400. Pick the channels that matter for inbound replies, not every account you've ever opened.
Build the signature in the MailSigCraft editor — CDN-hosted images and minified output by default.
Copy with Copy Signature (rich clipboard, not raw HTML).
Paste into Gmail's signature field.
If you still get "too long," remove one social icon or shrink your logo and re-paste.
The 10K limit is rarely the real problem — image weight is. Switch images to hosted URLs, drop the icons you don't need, and you'll never see "This signature is too long" again.
No — the 10,000-character cap applies the same way to both account types. It's a per-signature storage limit on Gmail's own signature field, not a plan-tier restriction, so a free personal account and a paid Workspace seat hit the exact same wall at the exact same size.
Yes, if that text lives inside the same signature field. Anything you paste into Gmail's signature box — visible text, disclaimer paragraphs, and all the surrounding HTML — counts toward the same 10,000-character budget. A long legal disclaimer appended after your signature can be exactly what pushes an otherwise-reasonable design over the limit; if your company requires one, budget for it before you finalize the logo and social icon sizes, not after.
No — Gmail's signature editor doesn't show a running character count anywhere in the interface. That's exactly why the error only shows up after you've already built the whole thing and tried to save. Checking the HTML weight yourself before pasting, as described above, is the only way to know you're safe in advance instead of finding out from an error message.
Yes. Gmail's "Send mail as" aliases each carry their own signature, and each of those signatures is checked against the 10,000-character limit independently. If you run a personal brand alias alongside a work alias from the same inbox, going over the limit on one doesn't affect the other — but it also means you have to slim down each oversized signature separately rather than fixing it once for the whole account.
Shorten link tracking. Replace verbose UTM params with a short redirect, or drop UTM entirely if you're not measuring signature click-through.
Strip whitespace from the HTML. Indented, human-readable HTML is 10–20% larger than minified HTML and renders identically. MailSigCraft minifies on copy automatically.