Email basics
Email subject line length: what Gmail actually shows
September 6, 2026 · 2 min read · Inbox Wingman
You wrote a clear subject line, hit send, and on your recipient's phone it reads "Quick question about the invoice fo…". The part that mattered got cut.
There is no single "maximum subject line length" — the limit that matters is not what email allows, but what inboxes display. This short guide covers what the major clients show, and how to write subjects that survive the cut.
The technical limit is not the real limit
The email standard (RFC 5322) recommends keeping each header line under 78 characters and allows up to 998. In practice you could send a 500-character subject and it would deliver fine.
But nobody reads subjects in raw form. They read them in an inbox list, squeezed between a sender name and a timestamp. That's where the real limit lives.
What Gmail and other clients typically display
Exact numbers depend on screen width, font settings, and whether a preview snippet is shown, so treat these as working ranges rather than hard rules:
| Client | Approximate visible characters |
|---|---|
| Gmail desktop (list view) | ~60–70 |
| Gmail app (phone) | ~30–40 |
| Apple Mail (phone) | ~35–45 |
| Outlook desktop | ~50–70 |
Two things follow from the table:
- Mobile is the constraint. A large share of email is opened on phones, and phones show roughly half of what desktop shows.
- The first ~40 characters are the only part you control. Everything after that may or may not be seen.
How to write subjects that survive truncation
Front-load the point. Put the noun that matters first: "Invoice #218 — payment due Friday" beats "Just following up regarding the outstanding invoice #218".
One subject, one topic. If you need two topics, send two emails. Combined subjects are the first to become meaningless when truncated.
Skip the filler openers. "Quick question about…", "Following up on…", "Checking in re:…" burn 20+ characters before saying anything. Cut straight to the content.
Use numbers and names. "Staging deploy blocked by failing auth test" is specific and scannable. "Problem with the deployment" is not.
Don't shout. All caps and stacked punctuation ("URGENT!!!") don't buy attention in 2026 — they pattern-match to spam, for both filters and humans.
You can check any subject against these rules with our free subject line tester — it shows live desktop and mobile previews and flags common issues.
When the subject line isn't the problem
If you're optimizing subject lines because your own inbox is unmanageable — clients buried under newsletters, bots, and notification noise — the fix usually isn't better subjects, it's better triage on the receiving side. That's the problem Inbox Wingman solves: it classifies every incoming email inside Gmail, drafts replies in your voice, and sends one daily brief with everything you owe an answer to.