How the Airmail unified inbox works and when it helps

The search for the Airmail unified inbox usually comes from a specific kind of morning. There are three or four mail accounts on the Mac, each one belongs to a different part of life, and the message that mattered arrived in whichever mailbox was not selected. One list that holds everything sounds like the fix. It often is. It also quietly creates a second problem, which is that a single list makes it harder to see which identity a reply will go out under.

What follows is what the feature merges, what it deliberately leaves alone, the one setting that decides whether it stays usable after a few weeks, and the point at which the mail client is no longer the thing that needs changing.

What the unified inbox actually merges

Airmail is published by Bloop S.R.L. and listed for Mac as a free download with in-app purchases. The current Mac build requires macOS 14.6 or later, which rules out older machines that have stopped taking system updates. Account support is broad rather than selective. The product page states that any number of accounts of any type can be added, and names Gmail, GSuite, iCloud Mail, Exchange, Office 365, Microsoft Outlook, IMAP and POP3.

The unified inbox is described in one sentence on the same page, and the second half of that sentence matters as much as the first:

See all of the email in all of your inboxes at once with the unified inbox feature. You can even exclude accounts from this view if you want to.

So the merge is a read view built from the inbox folders of the accounts that have been allowed into it. That is narrower than it first sounds. Sending identity, signature, folder structure, filing rules and archive behaviour all stay attached to the account the message belongs to. A message read in the merged list is still a message in one specific mailbox, and acting on it acts inside that mailbox.

On the iPhone and iPad builds the merged view is the landing screen rather than an option. Airmail's help material states that the app opens directly in All Inboxes by default, and that the view is reachable at any time through the sidebar menu. Individual accounts remain selectable from the same sidebar, so the merged view and the per account view coexist instead of replacing each other. Anyone who prefers to start in a single mailbox has to change that default rather than turn something on.

Excluding accounts is the setting that decides everything

The exclusion option is usually treated as a footnote. In practice it is the difference between a merged inbox that lasts and one that gets abandoned after a fortnight.

Mail volume is not evenly distributed across accounts. One address typically carries conversations with people, and one or two others carry receipts, deployment notices, calendar invitations, billing alerts and password resets. Merging them puts the automated traffic in the same list as the conversations, at which point the merged list is noisier than any of the individual mailboxes were. The instinct after that is to stop trusting the merged view and go back to clicking through accounts, which returns the situation to where it started.

Airmail's own instructions for removing an account from the merged view, written for the iOS build, are short. Tap the menu icon in the top left corner, select the account to change, then tap the unified inbox toggle so that it turns grey. The grey state is the confirmation that the account has left the merged list. The account is still there and still receiving mail. It simply stops contributing to the combined view.

The useful default is to merge the accounts that carry conversations and leave out the accounts that carry notifications. That is a different lever from the Smart Inbox, which filters newsletters and similar distractions out of a view. Smart Inbox works on message type. Exclusion works on account. Problems caused by one account being structurally noisy are solved by exclusion, not by filtering.

Where a merged view is clearly the right answer

The case the unified inbox handles well is one person, one role, several addresses. A freelance address and a personal address. A current company address and an address from a domain that still receives mail. An iCloud account that holds family logistics and a Gmail account that holds everything older than 2015.

In that situation the cost of checking is the whole problem and the cost of mixing is close to zero. Nothing bad happens if a personal message sits above a work message in the same list, because both of them are going to be answered by the same person wearing the same hat. Reading becomes one pass instead of three, and the number of times the app is opened purely to check whether something arrived drops.

Several other Airmail features sit on the reading side of that line and compound with the merged view rather than fighting it. Snooze hides a message until a chosen time, which is the honest answer to mail that cannot be dealt with now but should not be marked as handled either. Send Later schedules delivery, which matters when correspondents sit in other time zones. Privacy Mode processes data locally on the device, blocks tracking pixels and stops images from loading automatically, which reduces how much a merged list of newsletters reveals to the senders.

None of those depend on how many accounts are merged. They are worth setting up first, because they change how much work the inbox creates, and that effect is easy to confuse with the effect of merging.

Where a merged view creates a new problem

The case it handles badly is one person, several roles. Two employers. An agency and a client whose mail must not be visible during a screen share. A company account governed by a retention policy and a personal account that is not.

The failure mode here is not clutter, it is attribution. In a per account view, the mailbox is on screen before the reply is written, so the sending identity is established by where the reading happened. In a merged view that cue is gone, and the sending identity becomes something to notice in a field rather than something implied by context. A reply that leaves under the wrong address is a small technical event and a large social one, and it is the kind of mistake that gets more likely as the merged list gets busier.

Airmail offers a partial countermeasure. Accounts can be assigned colours so that each one is identifiable at a glance in the message list, and the message preview can be customised. Colour is a real improvement over no signal at all. It is still a visual convention that has to be read correctly while moving quickly, which is a weaker guarantee than simply not having the two mailboxes in the same list.

For strict separation, the answer is to exclude the sensitive account from the merged view and keep it as its own entry in the sidebar. That costs one extra click per check and removes the class of mistake entirely. Trading a click for a category of error is usually the right trade.

Mail is rarely the only account that doubled

There is a reason the merged inbox often feels like it solved less than expected. Mail is the account that doubled first and the one that is most visible, but it is seldom the only one.

The same person with two mail addresses generally has two Slack workspaces, two Notion logins, two GitHub accounts, two calendars, and separate billing on a handful of web tools. A mail client, however good, is scoped to mail. Everything else lives in a browser, where the unit of identity is the cookie jar, and a single browser profile can only hold one signed in session per service at a time.

That difference is what makes the options genuinely different rather than better and worse.

Approach	Solves	Leaves open
One mail client, accounts merged	Checking several mailboxes in one pass	Web app logins, sending identity cues
One mail client, accounts separate	Sending identity, retention boundaries	The number of places to check
Two browser profiles	One signed in session per service, per profile	Two identical icons, notifications and extensions configured twice
A browser that keeps each web app in its own window	Sessions per app and per account, in one place	Mail that is only read in a native client

The last row is the category that exists specifically because the browser's own limit is one session per service. Tools in that category load each service in its own container, which is why the same web application can be signed in twice at once. A feature by feature view of what that involves is on the Features page, and the way containers get grouped by role rather than by service is covered under Workspaces. Which services load cleanly in a container, including mail, is listed on Supported apps.

A short test for whether the merge is helping

Two counts settle the question faster than any feature comparison, and both take a single day.

Count the number of times the mail app gets opened to check whether something arrived, as distinct from opening it to read or write a specific message. Checking is the cost that a merged inbox removes. If that count was high before merging and is now low, the feature is doing its job and nothing else needs to change.

Then count the near misses on sending identity. Any moment spent verifying which address a reply is about to leave from, any message recalled or corrected, any hesitation before hitting send. If that count went up after merging, the merge is trading a solved problem for an unsolved one, and the fix is exclusion rather than a different mail client.

If the first count stayed high despite merging, the cause is usually outside the mail client. Checking has not reduced because the checking was never mostly about mail. It was about Slack, the shared drive, the issue tracker and the two dashboards, each of which still needs a session of its own.

One more distinction is worth drawing before changing tools again. A merged inbox reduces how many places have to be looked at. It does not reduce how much mail arrives, and it does not decide anything about what to do with a message. Airmail's Snooze and rules address the second question, and the Smart Inbox addresses the third by keeping newsletters out of the way. Expecting the merge alone to make the mailbox feel lighter usually leads to a search for a different mail client, when the missing piece was a filing decision that no client can make on anyone's behalf.

What to change first

Start inside Airmail: exclude the noisiest account from the merged view, assign a colour to each remaining account, and leave the defaults alone for a week. That is free and it settles whether mail was the bottleneck.

If the checking continues because the other half of the workday is also signed in twice, the unit that needs to change is the window rather than the mailbox, and SpaceDeck is built around that unit. The Pricing page is the fastest way to judge whether that step is worth taking at all.