Gmail Won’t Send | Fix It Fast

If Gmail won’t send, check connection, attachment size, account limits, and app settings, then retry or use Gmail on the web.

Email stuck on “Sending”? That’s frustrating, and it often has a simple cause. This guide walks you through the exact checks that clear most send failures on desktop, Android, and iPhone. You’ll find quick wins first, deeper fixes next, and two handy tables you can use as a checklist.

Gmail Not Sending Emails: Common Causes

Outgoing mail fails for a handful of practical reasons. The usual culprits are poor connectivity, attachments that exceed size limits, incorrect account settings, mailbox storage hitting the cap, or a send limit reached for the day. Sometimes an outdated app, a stuck Outbox, or a temporary service incident gets in the way too.

Quick Triage Before Anything Else

  • Send a plain text test mail to yourself. No images. No attachments.
  • Try gmail.com in a fresh private window. If that works, the issue sits with an app or extension.
  • Toggle airplane mode on/off (phone) or switch networks (desktop) to refresh the connection.
  • Remove large attachments or upload them to Drive and share the link.

Fast Fix Table

Use this early, broad table to zero in on the likely fix. Work top to bottom.

Symptom Most Likely Cause Quick Fix
“Sending…” never finishes Weak internet or stuck Outbox Reconnect, restart app, clear Outbox, resend
“Message not sent” on phone Background data or sync disabled Enable sync/data for Gmail, then resend
Instant bounce after Send Recipient address error or policy block Fix address, remove flagged content, try again
Attachment won’t upload Over 25 MB limit or flaky upload Use Drive link or compress the file
Everything fails in a mail app, works on web Corrupt cache or wrong settings Clear cache, re-add account, or update app
Works on phone, fails on work PC Extension, firewall, or VPN interference Disable add-ons/VPN, test a different browser
Send button greyed out No subject/body or no recipient Add a recipient and some body text
Temporary flood of errors Service incident Check status dashboard, wait, retry

Check Connection And Storage First

Open any site with images and scroll a bit. If loading stalls, switch Wi-Fi to mobile data or move closer to the router. On laptops, turn Wi-Fi off and on, or restart the adapter. On phones, toggle airplane mode, then try again. Next, glance at your Google storage. If the shared quota across Gmail, Drive, and Photos is full, sending can fail. Free up space by removing bulky Drive files or mail with large attachments from the Sent and Trash folders.

Clear A Stuck Outbox

On the Gmail mobile app, open the menu and tap Outbox. If messages sit there, open each draft, remove heavy attachments, and hit Send again. On desktop, switch to All Mail and look for drafts that show a paperclip and large size; edit and retry. If you see repeats of the same draft, delete the extras before resending.

Fix Attachment Problems The Right Way

Gmail sends attachments up to 25 MB per message. Larger files convert to a Drive link automatically. When that link can’t be shared due to permissions, recipients won’t get access, and you’ll think the mail never went through. Upload large files to Drive first, set link access for the recipient, then insert the link into the message.

Smart Tips For Large Files

  • Zip folders to shrink size before you add the file.
  • Share via Drive with “Anyone with the link” if the recipient’s domain blocks outside mail, then follow up with a direct link.
  • Avoid uncommon file types that might be blocked; use PDFs or common archives like .zip.

Confirm Send Limits And Status

If you sent a high volume of mail or many recipients in a short period, daily limits may pause sending for a while. Review limits here: Limits for sending & getting mail. If lots of users are seeing the same problem at once, scan the Workspace Status Dashboard for active incidents. If an incident shows, wait until the page marks it as resolved, then try again.

Update, Restart, And Re-Add The Account

Outdated apps or cached data often block sending. This quick cycle fixes many cases:

  1. Update the Gmail app (Android/iOS) or update your browser on desktop.
  2. Restart the phone or computer.
  3. Clear the Gmail app cache (Android) or remove and re-add the account in iOS Mail if you’re using Apple’s client.
  4. Test again with a small text-only message.

Turn Off Problem Add-Ons And VPN

Browser extensions that rewrite text, block scripts, or rewrite cookies can break the Send flow. Disable extensions for a minute, open a private window, and try again. If you use a VPN, disconnect and retest; some exit nodes trip spam defenses, which leads to blocks or delays.

Fix Send Errors On Android And iPhone

Phones ship with battery and data guards that can pause sync, which looks like a send failure. Here’s what to check.

Android Steps

  • Settings > Apps > Gmail > Battery: allow background activity.
  • Settings > Network & internet: disable Data Saver while sending.
  • Gmail app > Settings > your account: tick “Sync Gmail.”
  • Clear cache: Settings > Apps > Gmail > Storage & cache > Clear cache.

iPhone Steps

  • Settings > Mail > Accounts: open your Google account and toggle Mail off, then on.
  • Settings > Mail > Accounts > Fetch New Data: set Push/Fetch as needed.
  • If you use the Gmail app, update it in the App Store and restart the phone.

Check Address, Content, And Attachments For Blocks

A single typo in the recipient field can bounce a message. If the address looks fine, scan the message body for things that trigger filters—mass links, suspicious attachments, short link redirects, or malformed HTML pasted from a page builder. Send a plain text version with no links to test. If that works, add elements back one at a time.

What To Do With Bounces

When a message bounces, Gmail shows an error line in the returned mail. Read the code and wording. If the bounce says the recipient inbox is full, wait or contact them through another channel. If it says “user not found,” ask for an updated address. If it says a policy blocked the content, remove the flagged attachment or links and resend.

Desktop Client And SMTP Settings

If you send mail through Outlook, Apple Mail, or another client with Gmail added, misconfigured SMTP details can block sending. Use OAuth if offered; it handles token-based sign-in. If you must enter server details, use smtp.gmail.com on port 465 (SSL) or 587 (TLS), and correct account credentials. Re-authenticate if you recently changed your Google password.

Two-Step Verification And App Passwords

With 2-Step Verification enabled, some older clients need an app password. Generate one in your Google account’s security settings, then paste it into the client. If the client supports OAuth, prefer that route and skip app passwords.

When You Hit Attachment Size Limits

Gmail allows up to 25 MB of attachments per message; beyond that it converts to a Drive link. If recipients can’t open the link, fix Drive sharing and resend from the message draft. Steps that help:

  • Change Drive link access to the recipient’s domain or “Anyone with the link.”
  • Convert images to efficient formats (PNG or JPG) and trim resolution.
  • Export large slide decks to PDF with reduced image size.

Details on file size and how the Drive link handoff works live here: Send attachments with Gmail.

Service Health And Outage Clues

If send errors appear across devices, and coworkers see the same, a platform incident may be in progress. Check the Workspace Status Dashboard for a green check next to Gmail. Yellow or red markers show a disruption or outage. Open the item to read the latest note, then retry after the page marks it resolved.

Second Reference Table: Error Clues And Actions

Keep this next table handy once you’re past the midway point of troubleshooting. Match the clue to the next step.

Error Or Clue What It Usually Means Action To Take
“Message not sent – tap to retry” Phone sync paused or weak data Enable sync, switch networks, resend
“Size exceeds limit” Attachments over 25 MB Use Drive link or compress files
“You have reached a limit for sending mail” Daily send cap reached Wait for reset; send fewer recipients
Bounce with “user not found” Recipient address invalid Confirm address with recipient
Bounce with “mailbox full” Recipient storage full Try later or contact via chat/call
Browser Send unresponsive Extension or cache issue Private window, disable add-ons
App works; client fails SMTP or auth mismatch Use OAuth or correct ports
Send fails only on big emails Network timeout during upload Stable Wi-Fi or wired connection

Prevent Send Failures Next Time

Keep The App And Browser Fresh

Update the Gmail app and your browser every few weeks. New releases patch bugs and reduce odd send behavior. If you rely on desktop clients, schedule updates there too.

Build “Safe Send” Habits

  • Attach, then wait a beat to see the upload complete before clicking Send.
  • Use Drive for anything heavy or collaborative.
  • Limit bulk sends; spread messages across the day to avoid caps noted in the send limits page linked above.
  • Keep inbox size healthy; archive old threads and empty Trash regularly.

Document The Setup That Works

Once everything runs smoothly, jot down your working SMTP or client settings. If you switch phones or laptops, you’ll be back up in minutes.

When You’ve Tried Everything

If webmail and the mobile app both fail, and the status page shows green, try a different network or hotspot to rule out local filtering. If your account belongs to a workplace or school, ask the admin if new policies were added. Some orgs block certain file types or external links. For personal accounts, leave the message in Drafts, wait an hour, and send again after limits reset.

Recap: The Fix Flow That Works

  1. Test a plain text message to yourself on the web.
  2. Switch networks and clear or resend from Outbox.
  3. Trim attachments or share via Drive with correct link access.
  4. Update app/browser, disable extensions, restart the device.
  5. Check send caps and service status with the two links above.
  6. Re-add the account in the client or use OAuth.

Why This Guide Works

Most send failures come down to size, settings, or service state. By starting with quick tests, you isolate the exact barrier fast. The two linked pages cover official size behavior and platform health, and the rest gives you a clean path to a successful Send.