Read and Draft Email Offline on a Flight: Setup Checklist

The honest version of how to read email offline on a plane is that almost none of it happens on the plane. It happens in the twenty minutes before boarding, on airport Wi-Fi, and it is mostly about forcing content onto the device rather than flipping one switch.

Every app-specific guide tells you which toggle to enable. Far fewer cover the four things that decide whether the next six hours are useful: how much mail lands on the device, whether the attachments came with it, whether search still works, and what happens to everything you wrote when the wheels touch down.

This guide assumes no connectivity at all — airplane mode, or onboard Wi-Fi you have decided not to buy. Below: the criteria, a scored comparison of the common setups, a ten-minute gate-side checklist, and the reconnect behaviour that catches people out.

The short answer: what to do before you board#

Run this while you still have a real connection. Every step is something you cannot do once the cabin door closes.

1. 1

   Widen the sync window

   Push out the setting that controls how many days of mail your app stores locally. The Gmail Android app calls it Days of mail to sync, and Gmail Help is blunt that any message outside that window will not be available offline. New Outlook for Windows offers 7, 30, 90 or 180 days under Settings, General, Offline — and defaults to 30.

2. 2

   Turn on attachment downloading

   This is a separate setting from the sync window, and it is the one people miss. In the Gmail Android app, Download attachments only auto-downloads on Wi-Fi; with it off, attachments stay server-side until you fetch them by hand. Gmail's browser offline mode has its own Download attachments checkbox.

3. 3

   Open every thread you plan to work

   A sync window makes a thread eligible for offline access. Opening it is what reliably materialises the full message body and inline images on the device. Ten taps at the gate costs a minute and removes most of the risk.

4. 4

   Open the attachments too — actually open them

   Tap each PDF or deck until it renders. A file listed on a message is not the same as a file stored on the phone, and the difference only shows up when you are somewhere you cannot fix it.

5. 5

   Test search in the terminal, with the radio off

   Switch on airplane mode while you are still at the gate and search for something you know is in the synced window. If it returns nothing, you have learned that on the ground rather than at hour three.

6. 6

   Decide what you want to happen on reconnect

   If you would rather review a batch of replies before they go, write them as drafts and do not hit send. Queued sends do not wait for you to be paying attention.

Why 'synced' and 'on the device' are not the same thing#

Almost every offline complaint traces back to one gap. A sync window defines which messages the app is allowed to keep. It does not guarantee that every part of those messages has been fetched.

Headers, subjects and snippets are cheap, so they come down in bulk. Full HTML bodies, embedded images and attachments are expensive, so most clients fetch them lazily — when you open the thing. Microsoft states this outright for Outlook on the web: attachments are not available when offline.

So the inbox looks complete at 35,000 feet, and then one message opens to a blank body or a greyed-out file. Nothing is broken. The app never had a reason to download that part, and now it cannot.

Criteria that actually matter at 35,000 feet#

Five things decide whether an offline setup earns its place. Everything else — themes, swipe gestures, snooze — is irrelevant once the radio is off.

How the common setups score#

Scored against vendor documentation as of August 2026, not a bench test. Where a vendor does not document a behaviour, this table says so rather than guessing — the honest answer is 'do not rely on it until you have checked your own build'.

Worked example: a six-hour flight, planned at the gate#

Boarding at 16:40. The job in the air: close a client proposal, review two contracts, clear forty low-stakes messages. Here is the ten-minute routine on gate Wi-Fi.

1. 1

   16:15 — widen and wait

   Push the sync window to the deepest option offered, then leave the app open and the screen on. Backgrounding the app on a phone can pause the sync. Two or three minutes of visible progress is normal.

2. 2

   16:20 — open the six threads that matter

   The proposal thread, both contract threads, and the three internal threads you will quote from. Scroll each to the bottom so older messages render, not just the newest.

3. 3

   16:25 — open all nine attachments

   Two contracts, a pricing sheet, four reference PDFs, two images. Each gets a tap until it displays. This is the step that fails silently if you skip it.

4. 4

   16:30 — airplane mode on, dry run

   Still at the gate: open one contract, run one search, start one reply. Anything broken is now a thirty-second fix on terminal Wi-Fi instead of unfixable for six hours.

5. 5

   16:35 — decide the send policy

   The forty low-stakes replies can queue and fire on landing. The proposal reply stays a draft, because you want to reread it on the ground first.

Do queued emails send automatically when I reconnect?#

Yes, and that is the part worth planning for. Google documents that mail sent from Gmail's offline mode lands in an Outbox folder and goes out when the connection returns. Microsoft describes the same shape for Outlook: messages sit in the Outbox until you are back online, and offline actions upload on reconnect.

None of that is a bug. The problem is timing. Your phone finds a tower while you are still taxiing, device in your pocket and attention on the overhead bin, and everything you wrote across six hours leaves in one burst.

That burst has no review step. The reply you wrote at hour two and quietly regretted at hour five goes out with the rest, and any undo-send window expires while the aircraft is still moving.

Red flags to check before you rely on any of this#

Five failure modes account for most ruined flights. Four are checkable in the terminal.

• Cloud links are not attachments. A Google Drive or SharePoint link inside a message is a URL, and no amount of caching makes it resolve at altitude. Download those files separately before you board.
• Search that returns nothing instead of an error. An empty result looks identical to 'no matching mail', so you conclude the thread does not exist rather than that search is offline. Test it on the ground.
• Onboard Wi-Fi that authenticates but does not route. The device reports a connection, so the client starts syncing and drains the outbox against a network that goes nowhere. If you have not paid the portal, keep airplane mode fully on.
• Sync that pauses when you background the app. Widening the window and immediately locking the phone often means nothing downloads. Keep the app in the foreground until it settles.
• Battery. A stalled sync loop against dead onboard Wi-Fi is the fastest way to lose the last two hours of a charger-less flight.

What we'd pick, and who we're wrong for#

For a long-haul flight where the job is searching a deep archive and opening files you did not anticipate needing, classic Outlook for Windows in Cached Exchange Mode is the better answer, and it is not close. The slider goes to All, the local cache carries attachments, and search runs against that cache rather than the server. If that is your flight, take a laptop.

For the more common case — a two-to-six-hour flight, threads you already know about, and mail spread across a work Google account, a personal Outlook account and an IMAP domain — the constraint is accounts rather than archive depth, and that is where we fit. AI Emaily puts Gmail, Outlook and IMAP in one inbox, ships a native iOS app, downloadable Mac and Windows apps and an installable PWA on Android, and keeps recently synced mail readable and repliable when the network drops. Replies queue locally and send when connectivity returns.

The limits, plainly. Our offline mode is partial by design: it is not a cached-mode client with a complete local archive, so an attachment you never opened will not be there, and neither will mail outside the recent sync window. There is no Linux build. On Android we are a PWA rather than a native app, which matters if your device suspends background web apps aggressively. We build AI Emaily, so check that paragraph against your own flight rather than taking it on trust.

What is different is the reconnect story. The agent proposes; it does not send on its own while you are in the air, and every action lands in an audit log you can undo. What fires on landing is the list you approved, not a surprise.