Gmail clipping hides the rest of an email behind “View entire message” when the message code is too large. Around 102 KB is the familiar desktop threshold, not a guarantee for every device. Check a fresh delivered test, reduce unnecessary code, then verify the full offer, action and footer remain visible. Compressing hosted images alone does not solve code weight.
A customer should not have to expand the email to discover the part you intended them to act on. Before cutting the copy, establish whether the problem is the delivered message, a particular version of its content, or your repeated test thread.
What does Gmail clipping actually hide?
Mailchimp’s clipping guide puts the cutoff at 102 KB of message code, with the rest hidden behind the full-message link. Klaviyo’s guide treats that as a general desktop figure and says limits vary by device. The relevant weight includes text, HTML, styling and link code.
Hosted image files are separate from that code. Making a hosted photograph smaller does not remove the markup around it. Deleting an unnecessary image block can reduce the code, because the block itself disappears.
Use the symptom to choose the investigation:
| What you see | What to check |
|---|---|
| A clipping notice followed by a full-message link | Compare the initial view with the expanded message; record where content disappears |
| The bottom layout looks broken near that notice | Review the code at the cut as well as the total message size |
| Only a chain of repeated tests appears clipped | Send a fresh test with a unique subject before changing the template |
| Colours change but the content remains present | Follow the dark-mode diagnosis |
| The email never arrives | Start with delivery troubleshooting |
The layout check matters: Litmus explains that clipping can interrupt a table or other structure before its closing code, potentially breaking the displayed layout.
Why does a test pass while another version gets clipped?
The delivered version can include added markup or different personalised content. A passing test does not clear a version with different content or a different Gmail client. Check the delivered result for the combinations you intend to cover.
Also isolate the test thread. UPC university IT’s newsletter guidance notes that same-subject tests can be grouped and appear clipped. Give the next controlled test a unique subject. If only the old thread shows the problem, that observation alone does not establish a failure across the campaign audience.
Next, check what was actually sent. The code in the editor is only part of the investigation: the Litmus guide recommends checking for markup the sending platform adds on send.
For a concrete example, Klaviyo’s documented size check is email editor → Preview & test → Email Size. Put the template in a campaign or flow first so the estimate includes UTM parameters. Preview several profiles where substantial dynamic content is involved; the estimate can vary with the content included for each person.
The same guide describes the desktop limit as generally 102 KB and warns that limits vary by device. Treat the displayed size as an estimate, then check the Gmail clients relevant to your send.
For a technical handoff, keep the received original alongside the screenshot. Google documents the browser path: open the message, choose More beside Reply → Show original. Ask the person investigating size to identify which HTML they measured. Record the tool and its reading; an unexplained file-size number is not a demonstrated Gmail cutoff.
What should you remove first?
Start with a copy, clear unnecessary pasted formatting, and investigate code-heavy modules before cutting essential content. Preserve the original so you can compare both the content and the displayed result.
- Clear unnecessary pasted formatting. UPC recommends plain-text paste when external content brings hidden formatting. Restore the styles you actually need in the email editor.
- Find expensive modules. In a duplicate, remove one suspected block at a time and compare the estimate. Klaviyo documents this isolation method and notes that device-only blocks still add code to every send, including where they are hidden.
- Review the structure. Have the template owner inspect nested tables, unnecessary comments and obsolete fixes. The Litmus procedure calls for rendering tests after structural changes; do not treat every compatibility fix as disposable.
- Reduce secondary content. If the message still needs shortening, move an optional explanation or additional catalogue content to a clearly labelled destination. Keep the email’s essential offer, action and required footer content.
Choose the next edit from what the comparison shows. If deleting a decorative module barely changes the estimate, that test has not identified a useful source of savings. If a repeated block makes the difference, repair that part before rewriting the whole message.
How do you know the repair worked?
Check the delivered message for clipping, essential content and working links in each selected profile and Gmail client. Record those combinations and keep untested ones explicit. Save a compact record:
| Record | What to put in it |
|---|---|
| Message | Template version, send route and unique test subject |
| Content | Selected profile and the dynamic content it includes |
| Viewer | Gmail app or browser, device and test date |
| Size | Estimate or measured HTML size, clearly labelled with its method |
| Initial view | Whether clipping appears; last visible content if it does |
| Reader’s task | Offer and action visible, required footer present, relevant links checked |
Consider an invented test comparison: a short personalised version displays fully, while a version with a longer product block gets clipped. The first result does not clear the template. Investigate the longer version, make the repair, then repeat both checks.
A useful acceptance statement is “the revised template displayed fully for these profiles in these Gmail clients,” followed by the record. Repeat the check after material template or dynamic-content changes.
Does fixing open tracking also fix the email?
No. Moving a tracking pixel above the cut does not restore hidden content. Check the offer, action and footer separately. A pixel hidden below the cut can interfere with measured opens; UPC’s guidance describes end-of-message tracking code being hidden along with the content.
Klaviyo suggests moving the pixel to the top when clipping threatens tracking. A changed open rate after that move is not evidence of more reading; the open-rate reliability guide covers that broader measurement limit.
Frequently asked questions
Will compressing images stop Gmail clipping?
For externally hosted images, the image file’s weight is separate from the message code involved in clipping. Removing an unnecessary image block can reduce its associated code; compressing the hosted file alone does not remove that markup.
Is staying below 102 KB enough for every Gmail user?
Treat 102 KB as a general desktop reference. The size-check documentation above notes device differences and labels its preview reading an estimate. Verify the delivered content in the Gmail clients relevant to your audience rather than promising a universal safe size.
Why does Gmail clip only my repeated test emails?
Same-subject tests can be grouped and appear clipped. Try a unique test subject in a controlled inbox, then compare the delivered result. That helps isolate the test-thread explanation without assuming the campaign is clear for every profile or device.
Should you move the tracking pixel instead of shortening the email?
Moving the pixel may address tracking affected by its position, but leaves clipped content hidden. Check the reader’s initial view and essential content separately before accepting the repair.