Email deliverability Q&A

Why did my email get clipped in Gmail?

Samuel Chenard

By Samuel Chenard · CEO & Co-Founder, Palisade · Reviewed July 20, 2026

Gmail clipped your email because its HTML weighed more than roughly 102KB. Everything past that point hides behind [Message clipped] and a View entire message link. Only the code counts, not image file sizes. Google does not publish the threshold; Mailchimp, Litmus, and Klaviyo all document it at about 102KB. Trim the HTML and the clip disappears.

At a glance
The thresholdAbout 102KB of HTML, per Mailchimp, Litmus, and Klaviyo docs
Google's own numberNot published anywhere in Gmail Help (checked 2026-07-20)
What countsHTML and CSS markup only; image file sizes do not count
Mobile is stricterKlaviyo documents roughly 20KB on iOS and roughly 75KB on other mobile devices
What it is notNot a spam filter, not a block, and not an authentication failure
Who fixes itThe sender. The fix is a lighter template, nothing else.

Clipping is Gmail truncating the rendered message. When the HTML of an email crosses a size threshold, Gmail shows the first chunk, then replaces the rest with [Message clipped] and a View entire message link that opens the full email in a browser tab. The message was delivered and it landed in the inbox; Gmail simply declined to render all of it.

The threshold is the part everyone gets wrong. Google does not document a clipping limit anywhere in Gmail Help; the only Gmail size limit Google publishes is the 25MB attachment cap, which is a different thing entirely. The ~102KB figure comes from ESP documentation: Mailchimp states Gmail clips messages larger than 102KB, and Litmus and Klaviyo document the same number. Klaviyo adds that mobile clients clip earlier, at roughly 20KB on iOS and 75KB on other mobile devices.

What counts toward the limit is the raw HTML: text, inline styles, <style> blocks, tracking parameters, and every URL. Litmus is explicit that image file sizes do not count, only the code. That is why an email with three huge photos can render fine while a text-heavy newsletter with a bloated template gets cut in half.

Gmail clipping triage flow: the Message clipped notice means the sent HTML is too heavy, files over about 102KB need the delivered HTML measured, mobile clients clip earlier at roughly 20KB on iOS, and the fix is stripping duplicate CSS and retesting until the sent HTML clears the budget

What the documentation actually says

SourceDocumented behaviorNotes
Mailchimp (Help)Gmail clips emails with a message size larger than 102KB; hidden content sits behind a View entire message linkAlso warns that open tracking breaks, since the tracking code is in the clipped portion
Litmus (guide)Clips over 102kb of code; the limit excludes images and counts only the markup itselfNotes clipping can cut mid-tag and break the layout of what still renders
Klaviyo (Help Center)About 102KB on desktop; roughly 20KB on iOS and 75KB on other mobile devicesDocuments that the clipped tracking pixel stops opens from recording
Google (Gmail Help)Publishes no clipping threshold; documented size limits cover attachments (25MB), not renderingThe ~102KB figure is ESP-observed, not Google-stated

Treat 102KB as a reliable working number, not an official one. Three major ESPs independently document it and it has held for years, but since Google has never published it, build in margin: aim for well under 100KB rather than engineering to the line. All four sources checked 2026-07-20; links in Sources below.

Why clipping costs more than a truncated footer

The direct damage lands on the two things senders keep at the bottom of an email. The unsubscribe link lives in the footer, so a clipped message hides it unless the reader clicks through to the web view; frustrated readers who cannot find unsubscribe reach for the spam button instead, and spam complaints hurt where clipping itself does not. The open-tracking pixel also usually sits at the bottom, and Klaviyo and Mailchimp both document the consequence: the pixel is in the clipped portion, it never loads, and the open never records. Your open rate under-reports on exactly the sends that are heaviest.

Under-reported opens then cascade. Campaigns look weaker than they are, engagement-based segments (people who opened in the last 90 days) silently shed subscribers who did open, and any automation keyed on opens misfires. If your open rate stepped down right after a template redesign, check a test send in Gmail for the clip before you blame the content.

There is also a rendering hazard: Litmus notes the cut can land mid-tag, so an unclosed table or div can break the layout of the part of the email that did render. A clipped email can arrive looking broken, on top of being shorter.

Clipping is a size problem, not an authentication problem

Worth saying plainly: SPF, DKIM, and DMARC have nothing to do with clipping. An email can pass every authentication check and still get clipped, and fixing your DNS will not shave a single kilobyte off your template. If your problem is [Message clipped], the fix is in your HTML, full stop.

The two problems just share a failure mode, which is why they get confused: both quietly suppress engagement metrics. Authentication failures keep mail from reaching the inbox normally: Google's sender guidelines state that unauthenticated messages might be marked as spam or rejected with a 5.7.26 error (rejection codes are covered in the SMTP error-code reference at /learning/smtp-error-codes). Clipping lets the mail in and then hides part of it. If opens dropped, it is worth ruling out both, but they are separate diagnoses with separate fixes, and this page only solves the second one.

What made the HTML heavy: cause and fix

SymptomLikely causeThe fix
Every campaign clips, even short onesTemplate bloat: deep nested tables, per-block repeated styles, old client hacksRebuild or minify the base template; audit what your editor generates per block
Clipping started after switching editors or ESPsThe new tool injects duplicate CSS or extra wrapper markup on every elementCompare sent-message source before and after; enable embedded styles or a cleaner output mode
Only test sends clipGmail threads same-subject tests into one conversation and counts the combined sizeChange the subject line on each test send, or delete the earlier tests from the thread
Long newsletters clip near the endGenuinely too much content in one send: every article in full, plus footer blocksExcerpt each story with a read-more link to the site; keep the email a table of contents
Sent size is far larger than your draftLink tracking rewrites every URL into a long redirect, inflating the markupShorten heavily linked sections and drop decorative links; retest the sent size
Clips on phones but not desktopMobile thresholds are lower (Klaviyo: roughly 20KB on iOS, 75KB on other devices)Design to the mobile budget, not the 102KB desktop one

In every row the lever is the same: less markup in the sent message. Measure the sent version, not your draft; the ESP's wrapper, injected styles, and rewritten tracking links are all added after you hit send.

Gmail clipping triage flow: the Message clipped notice means the sent HTML is too heavy, files over about 102KB need the delivered HTML measured, mobile clients clip earlier at roughly 20KB on iOS, and the fix is stripping duplicate CSS and retesting until the sent HTML clears the budget

How to fix it

  1. Reproduce the clip and rule out a delivery problem

    Send the campaign to a Gmail address you control and look for [Message clipped] at the bottom. While you are testing, run your sending domain through the free check below: it will not fix clipping (nothing DNS-side will), but it checks your authentication records and common blocklists so you can rule those out as the cause, leaving size as the remaining suspect.

    Run the check now

    Enter your sending domain and the check runs instantly on the next page. Free, no signup.

  2. Measure the sent HTML, not the draft

    Open the delivered message's source in Gmail (Show original) and check its size. ESPs add wrapper markup, inject styles, and rewrite every link for tracking after you hit send, so the delivered file is always heavier than the one in your editor.

  3. Strip duplicate and dead CSS

    Drag-and-drop editors repeat the same inline styles on every block, and old templates carry fixes for email clients that no longer need them. Remove HTML comments, collapse repeated styles, and run the result through a minifier; Litmus's guidance is to keep exactly as much markup as you need and no more.

  4. Cut content, not quality

    If the template is clean and it still clips, the email is carrying too much. Excerpt long articles with a link to the full piece, drop decorative sections, and remember only the code counts: one good image costs less markup than four paragraphs of styled text.

  5. Retest against the mobile budget and make it routine

    Confirm the fix on a phone as well as desktop, since mobile clients clip far earlier than 102KB. Then add a sent-size check to your pre-send checklist with margin built in; a template that ships at 95KB will clip the week someone adds a banner.

Related free tools: Email header analyzer · DMARC checker

Frequently asked questions

Get the sent HTML under roughly 102KB. Strip duplicate inline styles and HTML comments, flatten nested tables, excerpt long articles instead of including them in full, and minify before sending. Measure the delivered message via Show original in Gmail, since ESP wrappers and rewritten tracking links inflate it past your draft.

Yes, directly. Klaviyo and Mailchimp both document that the open-tracking pixel usually sits at the bottom of the email, inside the clipped portion, so it never loads and the open never records. Heavy sends under-report opens, which then distorts engagement segments and any automation triggered by opening.

No. Litmus and Klaviyo are both explicit that the limit covers only the code: HTML, CSS, text, and URLs, including image URLs. The image files themselves load separately and do not count. A photo-heavy email with lean markup renders fine; a text-heavy one with a bloated template gets clipped.

No. Clipping happens to delivered mail, wherever it lands; it is a rendering behavior, not a filtering verdict. The indirect risk is real though: a clipped footer hides the unsubscribe link, and readers who cannot find it tend to hit the spam button, and those complaints do affect future placement.

No. Clipping is purely about HTML size; authentication has no bearing on it, and a fully authenticated email clips at the same threshold as an unauthenticated one. They only feel similar because both quietly depress engagement numbers. Fix clipping in the template; fix authentication in DNS. They never share a fix.

Gmail threads messages with the same subject into one conversation and evaluates the combined size, so five test sends of a 30KB email can clip as a thread even though each send is fine alone. Change the subject on each test, or delete earlier tests from the conversation before judging.

Google has never published one; Gmail Help documents attachment limits (25MB) but says nothing about clipping. The working number comes from ESP documentation: Mailchimp, Litmus, and Klaviyo all state about 102KB of HTML on desktop, and Klaviyo documents lower mobile thresholds. Engineer to well under 100KB for margin.

Sources

Every benchmark above was verified against the vendor's own documentation on the date shown.

Related reading

Email deliverability, fixed: the full guide

Not sure this is your only problem?

Run a free email security score: every authentication and deliverability gap for your domain, in one pass.