# Gmail clipping of emails

## Understanding and Avoiding Gmail Clipping

Gmail “clipping” happens when an email exceeds Gmail’s size limit and part of the message is hidden behind a **“\[Message clipped] View entire message”** link.

Clipped emails can negatively affect marketing performance, and in some cases, prevent tracking pixels from firing—leading to inaccurate open rate data.

This guide explains how clipping works, how to check your email’s size, and practical ways to reduce it.

### About Gmail Clipping

When Gmail clips an email:

* The recipient only sees part of the message unless they click **“View entire message”**.
* The tracking pixel (used for measuring opens) may be hidden, causing underreported open rates.
* The clipping threshold varies by device:
  * **Desktop Gmail**: \~102 KB
  * **Mobile Gmail**:
    * iOS Gmail app: as low as \~20 KB (inconsistently applied)
    * Other mobile devices: \~75 KB

Note: Large image file sizes don’t cause clipping—clipping is based on the HTML code size (including text, links, and styles).

### How to Check Your Email’s Size

Bird platform offers an email size checker under the Preview section in the email editor, use it while building:

1. Open your email in the editor.
2. Click **Preview**
3. Look for the **Email Size** section.
4. Review the clipping risk level:
   * **<85 KB:** Not at risk
   * **85–95 KB:** Might be at risk
   * **>95 KB:** Likely to be clipped
5. If using dynamic content, preview with multiple profiles—final size can vary per recipient.

<figure><img src="https://3861485111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FU9kiDiTGVD8kkbnKKyEn%2Fuploads%2FfLywlGtqUliLnD9AbunB%2FScreenshot%202025-08-14%20at%207.26.18%E2%80%AFPM.png?alt=media&#x26;token=e1aa4293-49b5-4310-afbf-6d86332668de" alt=""><figcaption></figcaption></figure>

### What Gmail Clipping Looks Like

In Gmail, clipped emails display:

<figure><img src="https://3861485111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FU9kiDiTGVD8kkbnKKyEn%2Fuploads%2FNsWywiBAVjZUtLMBYD7V%2FScreenshot%202025-08-14%20at%207.24.54%E2%80%AFPM.png?alt=media&#x26;token=8b3032c3-adcc-4c1d-a94f-afb4b4ffbfe3" alt=""><figcaption></figcaption></figure>

Clicking the link opens the full message in a new window.

### Understanding Clipping Risk

| Size Range | Risk Level | Recommended Action                        |
| ---------- | ---------- | ----------------------------------------- |
| <85 KB     | Low        | No changes needed                         |
| 85–95 KB   | Medium     | Consider reducing size                    |
| >95 KB     | High       | Reduce size immediately to avoid clipping |

### How to Reduce Email Size

You can reduce HTML size without removing valuable content:

1. Minimize desktop- or mobile-only blocks
   * These add extra code even if hidden. Use blocks that show on both desktop and mobile when possible.
2. Avoid header/link bar blocks
   * Replace with a simple logo image + text links to reduce heavy responsive styling.
3. Remove section background images
   * Use solid colors or patterns instead.
4. Clean up unnecessary styles
   * Pasting from Google Docs or Word can add hidden formatting. Use **Ctrl+Shift+V** (Windows) or **Cmd+Shift+V** (Mac) to paste plain text.
5. Consolidate blocks and sections
   * Merge similar sections into fewer blocks.
   * Combine multiple columns or text blocks with the same styling.
6. Test block impact
   * Clone your email, delete one block at a time, and preview to see which changes reduce size most.

### Key Takeaways

* Keep HTML under **102 KB** for desktop Gmail and **75 KB (or lower)** for mobile Gmail.
* Clipping is about **code size**, not image file size.
* Regularly preview and test for size as you build.
* Optimize code by consolidating blocks, cleaning styles, and simplifying structure.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bird.com/applications/content/email-templates/concepts/gmail-clipping-of-emails.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
