Fetch vs Push Mail on iPhone: Which Should You Use?

Fetch vs push mail on iPhone is one of the most-asked questions about the built-in Mail app, and most of the answers online are half right. Push is not a battery villain, Fetch is not always slow, and the setting you pick in Settings > Mail > Accounts > Fetch New Data does not always take effect the way the screen implies. Some account types silently ignore Push no matter what you choose.

This post walks through what each setting actually does in iOS 26, which accounts genuinely support Push (and which quietly fall back to Fetch), how the Automatic and Manual options work when your phone is locked or on cellular, and how to configure one behavior per account so the account that matters is instant and the rest do not wake the radio every fifteen minutes.

The verdict: push what actually matters, fetch the rest#

For most people the right answer is not global Push and not global Fetch. It is per-account. Turn Push on globally, set your primary account (the one you would want a notification for within thirty seconds) to Push if it supports it, set every low-priority account to Fetch on a schedule you actually want, and set anything you rarely check to Manual. The Fetch New Data screen is designed for exactly this — the schedule at the top is the default, and every account has its own override underneath.

Push does draw more battery than a light Fetch schedule, but the difference is small and it only applies to accounts that support Push in the first place. On a modern iPhone with a healthy battery, Push on one iCloud or Exchange account is not what runs your phone down. What actually costs battery is Fetch set to Every 15 Minutes on five accounts at once, because the radio wakes every three minutes on average and each wake burns more energy than a single push notification would.

The rest of this post is the detail behind that verdict — the account-by-account support matrix, what Automatic and Manual actually mean, and how to set it all in about two minutes.

Push vs Fetch at a glance#

The two mechanisms are opposite in direction. With Push, the server initiates — it opens a lightweight connection to your phone (via Apple Push Notification service for iCloud, or a persistent connection for Exchange ActiveSync and IMAP IDLE) and pings the moment a new message lands. With Fetch, your phone initiates — Mail wakes on a timer, opens a connection to the server, asks whether anything new has arrived, and closes.

Which iPhone Mail accounts actually get Push#

This is where most online guides get vague. The Fetch New Data screen shows a Push toggle at the top and lists your accounts underneath, and it is easy to assume every account gets Push if the toggle is on. That is not how it works. Whether an account supports Push depends on the mail protocol behind the account, not the toggle at the top of the screen.

The single most-searched question in this space is whether Gmail supports Push in the iPhone Mail app. It does not, and it has not for years. Google removed Exchange ActiveSync for consumer Gmail accounts in 2013, and Gmail's IMAP implementation is not one that iOS Mail treats as push-capable. If you add a Gmail account to Apple Mail on your iPhone, it will show up in Fetch New Data as a Push-capable account in some iOS versions, but new messages will not actually push. They arrive on your Fetch schedule.

If real-time Gmail notifications matter to you, the practical options are: install the Gmail app itself (which uses Google's own push channel), install a third-party mail client whose server watches your Gmail on your behalf and pushes to your phone, or accept a Fetch schedule and pick an interval you can live with.

Where Push wins#

Push wins on latency and it wins on total battery across a busy inbox. If you receive fewer than a hundred messages a day on your primary account, one Push connection is cheaper than fetching every fifteen minutes, because the radio wakes far less often. A push notification is a short exchange initiated when there is something to deliver; a scheduled fetch is a full connection every interval whether the server has anything or not.

Push also wins on the situations that matter most: an incoming reply to a message you sent five minutes ago, a two-factor code you asked for right now, a meeting change the moment your colleague clicks send. On Fetch the same message can sit on the server for the entire interval before your phone knows about it — Every 15 Minutes means an average delay of about seven and a half minutes and a worst case of fifteen. If you have ever missed a code because the fetch had just run, you know the cost.

The battery arithmetic changes as account count grows. One iCloud account on Push draws less power over a day than the same account on Fetch every fifteen minutes, because Fetch keeps waking the modem even when nothing is happening. Five accounts on Fetch every fifteen minutes is significantly worse than one account on Push and four on Hourly, for the same reason — the total number of radio wakes is what determines the cost.

Where Fetch wins#

Fetch wins when the account is one you genuinely do not need to hear about immediately. A newsletter-only address, a receipts-only address, a legacy account you check once a day out of habit — none of these need to interrupt you the moment a message arrives, and putting them on Push burns a persistent connection you get no value from. Setting them to Hourly or Manually reclaims that cost.

Fetch also wins when a protocol does not actually support Push. Gmail is the obvious case: since the account is going to fetch regardless, setting it to Push in the UI is worse than setting it to Fetch, because you keep the label without the behavior and you have no idea what schedule the account is actually on. Setting it to Fetch, with a specific interval, means you know how stale your inbox can be — you chose the number.

The Manual option deserves a mention here too. Manual means the account never checks in the background. It only refreshes when you open Mail and pull down the message list, or open that specific mailbox. For an archive account you consult twice a month, Manual is correct — the account exists, mail is retrievable when you want it, and it costs zero background power.

What each setting costs you#

iOS 26's Fetch schedule offers five choices for accounts that fall back to Fetch or that you explicitly set to Fetch: Automatically, Every 15 Minutes, Every 30 Minutes, Hourly, and Manually. The trade-offs are real and measurable, and the cost you pay is a mix of battery, cellular data, and delivery delay.

The Automatic option is misunderstood almost universally. It does not mean iOS picks a smart interval based on how often you use the account. It means fetch runs only when the phone is connected to Wi-Fi and plugged in. On cellular, or on Wi-Fi while running on battery, an account set to Automatically does not fetch at all in the background — new mail arrives only when you open the Mail app. This is deliberate: it is Apple's most conservative option, designed for accounts you want kept fresh overnight on your charger but never on the go.

If Automatically is your global default and you have wondered why your email seems fine at home but goes stale during the day, this is why. Change the schedule to Hourly and the behavior becomes what most people expect from Automatically.

How to configure it per account#

1. 1

   Open Settings and go to Mail

   On iOS 26, open the Settings app, scroll down to Apps, tap Mail, then tap Mail Accounts. On earlier iOS versions the same screen lives at Settings > Mail > Accounts.

2. 2

   Tap Fetch New Data

   This is the master screen for Push, per-account overrides, and the global fetch schedule. Everything you need is on this one screen.

3. 3

   Turn Push on globally

   Toggle Push on at the top. This does not force every account to Push — it just permits Push for the accounts that support it. Leaving it off disables Push everywhere even for accounts that would otherwise use it.

4. 4

   Set each account individually

   Tap each account in the list and choose Push, Fetch, or Manually. Push is only visible as an option for accounts whose protocol supports it — if you do not see Push under an account, that account does not push (Gmail is the common case). For a primary account you want real-time, choose Push. For accounts you check periodically, choose Fetch. For accounts you consult on demand, choose Manually.

5. 5

   Pick the global fetch schedule

   At the bottom of the Fetch New Data screen, choose Automatically, Every 15 Minutes, Every 30 Minutes, Hourly, or Manually. This schedule applies to any account whose per-account setting is Fetch. Hourly is the pragmatic default; Every 15 Minutes is worth it only if you have exactly one Fetch account that matters.

6. 6

   Handle Gmail deliberately

   If you have a Gmail account added to Apple Mail and you have accepted that it will not push, set it explicitly to Fetch and pick an interval you can live with. Do not leave it on Push — the label is inaccurate and it is easier to reason about the schedule if the screen matches reality.

A third option: use a mail client with its own push#

The whole Push vs Fetch question exists because Apple Mail is downstream of whatever protocol your provider offers. When the provider does not push (Gmail), Apple Mail cannot invent it. The client that can push a Gmail message to you in seconds is one that watches the Gmail account on its own servers and forwards the notification to your phone through Apple Push Notification service — the same channel iCloud uses.

We build AI Emaily, an AI-native email client with a native iOS app and a server-side sync layer. The sync worker holds an IMAP IDLE connection to Gmail, Outlook, iCloud, and any IMAP host on our servers, and pushes new-message notifications to the iOS app via APNs. Gmail on our app behaves like iCloud on Apple Mail: the message arrives, the notification appears, no fetch interval involved. The trade-off is honest — you are trusting our servers to hold that connection, which is the same trade any hosted push-notification service makes.

Beyond notifications, the app runs an approval-first agent that triages the inbox, drafts replies in your set voice, and surfaces the messages that need you. Everything sends only on your approval in Copilot mode, with a gated Autopilot for routine replies if you turn it on. There is a 7-day free trial on the Pro and Autopilot plans, no permanent free tier — worth trying only if the notification and triage story is the reason you were looking at the Fetch screen in the first place.