Troubleshooting “Empty Message” Errors in UI

The “Empty Message” error occurs in the Gmail web interface when the application attempts to process or send an email that it perceives as lacking required content. Users encounter this either as a pre-send confirmation alert (“Send this message without a subject or text in the body?”), an interface dialog preventing the send action entirely, or an incoming email that opens as a blank white canvas despite headers indicating a payload exists. This issue is typically caused by browser extension interference, corrupted rich text editor DOM trees, clipboard formatting artifacts, or broken multipart MIME boundaries.

How to Resolve Gmail “Empty Message” UI Errors

To fix an “Empty message” error in the Gmail web interface, test sending in an incognito or private browser window with all extensions disabled. If the error clears, turn off third-party ad blockers, translation tools, or grammar extensions that modify Gmail’s composer. If reading a blank incoming message, switch your display to plain-text mode or clear your browser’s site data cache.

Diagnosing the Two Types of Empty Message Errors

Before applying technical fixes, determine where the failure happens:

                  "Empty Message" Anomaly Detected
                                 │
         ┌───────────────────────┴───────────────────────┐
         ▼                                               ▼
Outbound Composition Failure                    Inbound Display Failure
  • Pop-up blocks sending                         • Email opens completely blank
  • Text is visible, but Gmail sees null          • Size indicators show data exists
  • Editor DOM tree desynchronized                • Multipart MIME parsing failure
  • Outbound Composition Glitches: You have typed text or pasted images into the compose window, but clicking “Send” yields a warning that the body is empty, or the interface rejects the request.
  • Inbound Display Failures: An email arrives in your inbox with a valid subject line and sender, but opening the message displays no text. The headers show a size of 50 KB or more, but the rendering window shows nothing.

Resolving Outbound Composition Errors

Step 1: Isolate Browser Extensions (DOM Injection Interference)

Gmail’s web composer operates within an internal iframe structure. Third-party extensions that interact with page elements—such as grammar checkers (Grammarly), translation tools, ad blockers (uBlock Origin), and custom CSS dark-mode plugins—modify the Document Object Model (DOM) directly.

When an extension modifies the compose box, it can break the link between what you see on the screen and what Gmail’s background JavaScript tracks in memory. When you click Send, the script checks its internal draft object, finds no text, and halts.

  1. Open an Incognito window (Chrome) or Private Window (Firefox/Safari).
  2. Log in to Gmail and attempt to send the exact same text.
  3. If the message sends without an empty message warning, return to your normal browser profile.
  4. Disable extensions one by one under chrome://extensions to identify the conflicting tool.

Step 2: Strip Hidden Characters and Broken HTML Formatting

Copying content from word processors, spreadsheets, or web pages can pull invisible artifacts into the compose box. These include:

  • Zero-width spaces (U+200B)
  • Unclosed HTML formatting tags
  • Malformed tables and high-density SVG wrappers

If the composer cannot resolve these elements, it may drop the text during the final parsing step. To clean the text:

  1. Select all content in the compose window (Ctrl+A or Cmd+A).
  2. Click the Remove Formatting button (the Tx icon) in the bottom formatting toolbar.
  3. Alternatively, paste raw text into the composer using Ctrl+Shift+V (Windows) or Cmd+Shift+V (macOS).
  4. If you frequently encounter clipboard issues, review Resolving “Formatting lost” on Copy-Paste.

Step 3: Switch to Plain Text Mode

If the rich text editor continues to fail:

  1. Click the More options menu (three vertical dots) in the lower-right corner of the compose window.
  2. Check Plain text mode.
  3. Gmail will convert the draft to raw text, stripping out all background HTML wrappers. Click Send.

If drafts fail to retain text during this process or disappear unexpectedly, see How to Fix “Drafts not saving” in Browser.

Resolving Inbound Blank Message Failures

If you receive an email that appears blank even though the sender confirms they wrote a message, use these steps to isolate the issue:

Step 1: Inspect the Raw MIME Structure

  1. Open the blank message in Gmail.
  2. Click the More options menu (three vertical dots) next to the Reply button.
  3. Select Show original.
  4. Scroll down to inspect the raw message body.

Check the Content-Type headers:

Content-Type: multipart/alternative; boundary="----=_Part_12345"

Look for the text between the boundary markers.

  • If you see readable text inside text/plain or text/html sections in the raw view, the message contains data, but your browser is failing to render it.
  • If the raw view shows empty boundaries, the sending mail client transmitted a corrupt, empty payload.

Step 2: Identify CSS Display Errors

Some automated marketing platforms send poorly formatted emails where the root <div> contains bad styling:

<div style="display:none;">Message Content</div>

Alternatively, an unclosed comment tag (<!--) can cause the browser’s rendering engine to treat the entire email body as hidden code. When this happens, view the original message source to read the text.

Step 3: Clear Corrupted Service Workers and Local Cache

A corrupted local cache can prevent Gmail’s web application from loading message bodies:

  1. In Google Chrome, go to chrome://settings/siteData.
  2. Search for mail.google.com.
  3. Click the trash can icon to remove local cached site data.
  4. Navigate to chrome://serviceworker-internals.
  5. Locate the scope for https://mail.google.com and click Unregister.
  6. Restart the browser, log back in to Gmail, and open the message.

If sending issues persist across your browser session, verify that your interface is not encountering cancellation loops by reviewing Fix: Gmail “Undo Send” Not Working.