Skip to content

Why Does Gmail Say "Sending..." Before Your Email Is Actually Sent?

Gmail acknowledges your email before it leaves the building. Why accepting work first and processing it later makes systems feel instant and stay reliable.

By 2 min read
  • System Design Explained
  • Reliability
  • System Design
  • Software Architecture

Have you ever noticed what happens after you click Send in Gmail? The email doesn't instantly become "Sent." For a brief moment, you see: Sending...

That tiny status tells a much bigger story about distributed systems. When you press Send, Gmail doesn't just forward your email and hope for the best.

Why Does Gmail Say "Sending..." Before Your Email Is Actually Sent?

A simplified flow looks like this:

  1. πŸ“§ You click Send
  2. βœ… Gmail stores the email safely.
  3. πŸ“© A background service takes responsibility for delivering it.
  4. 🌐 It attempts to contact the recipient's mail server.
  5. ❌ If the destination is temporarily unavailable, Gmail doesn't immediately fail.

It retries. Sometimes minutes later. Sometimes longer.

Only after repeated failures does it give up and notify you.

Why? Because temporary failures happen all the time.

  • Networks become unavailable.
  • Mail servers restart.
  • Connections time out.

A successful email system isn't one that never encounters failures. It's one that recovers from them without asking the user to press Send again.

That's one of my favorite principles in system design: Reliable systems don't assume success.

They assume failure, plan for recovery, and make that complexity invisible to users.

The next time you see "Sending...", remember: You're watching resilience in action.

Keep reading