Choosing an email app when you have several accounts to watch

Most roundups of the best email app for multiple accounts answer a question the reader did not ask. They assume every address should pour into one unified inbox, rank a dozen clients on features, and stop. That works for a person with a personal address, an old address, and a newsletter address. It fails badly for a freelancer with four client identities, or for anyone who has to send from the right address without thinking about it, because merging is the opposite of what those situations need.

The useful first step is deciding which of two problems is actually on the table: consolidation, or separation. The tool that wins one loses the other.

Four situations hiding behind one phrase

The phrase "several accounts" covers arrangements with very different requirements.

The first is many addresses, one person. A personal Gmail, an old university address, an address used only for shopping. Nothing needs to stay apart, and a single inbox with good filtering is the right answer.

The second is separate identities that must not mix. Two clients, two employers, or a business and a personal life. Sending from the wrong address here is a real mistake, not an inconvenience, and the calendar, chat and drive that come with each account need the same separation.

The third is a shared inbox. Several people answering one address, where the question is assignment and avoiding duplicate replies rather than aggregation.

The fourth is different providers. Gmail plus a company Microsoft account plus an address on a domain with plain IMAP, where the practical constraint is what each provider allows a third-party client to do.

A tool recommendation only makes sense once the situation is named, so the sections below are organized by approach rather than by ranking.

The free route inside Gmail, and where it stops

Gmail can pull other mailboxes into itself, which is the cheapest version of consolidation and also the most limited. Google's documentation sets the ceiling at five email addresses added to one Gmail account through the accounts settings, using POP access on the other mailbox. Google also carries a notice on that page about upcoming changes to Gmailify and POP support, which is a reason not to build a long-term workflow on it without checking the current state first.

Two further constraints are worth knowing before choosing this route. An Outlook account cannot be added to Gmail on the desktop web, because Microsoft now requires modern authentication methods that the desktop flow does not offer, though the Gmail mobile app can do it. And messages import without folders or labels, so an organized archive arrives flattened.

Delegation is the other built-in mechanism, and it is designed for a different job. A personal Gmail account can add up to 10 delegates and a work or school account up to 1,000, with roughly 40 able to work in an account at the same time under typical use. Delegates can read, send and delete, but a long list of features is unavailable to them, including Chat, Smart Compose, Gemini in Gmail, and access to Google Account settings. Delegation answers the shared inbox case in a limited way, not the multi-identity case.

Desktop clients that merge accounts into one inbox

If consolidation is the goal, the client market is mature and the differences are mostly about price and about how much of a team product is being bought. Prices below were taken from each vendor's own pricing page on 23 September 2026.

App	Free tier	Paid	Platform notes
Apple Mail	Included with macOS	None	Ships with the system, unlimited accounts
Thunderbird	Free, open source, donation funded	None	Windows, Linux, macOS
Spark	Free, unlimited email accounts	Plus $10 per user monthly, $8.25 billed yearly. Pro $20, $16.58 billed yearly	Apple platforms, Android, Windows
Missive	30-day trial, no card	Starter $14, Productive $24, Business $36 per user monthly billed yearly	Team product, includes SMS and social accounts

Apple Mail and Thunderbird cost nothing and handle an arbitrary number of accounts, with unified inbox views built in. The reason people leave them is rarely the account handling; it is the surrounding features, such as scheduling, snoozing, or a shared view with colleagues.

Spark's free tier already allows unlimited email accounts, which makes it a reasonable place to test whether a merged inbox suits the way the work actually flows. Missive is priced per user because it is built around teams answering shared inboxes together, with internal discussion attached to threads, so it answers the third situation rather than the second.

The common limitation across all four is identity. A client renders mail from every account in one list, and the protection against sending from the wrong address is a dropdown and the reader's attention. For the second situation on the list above, that is exactly the wrong shape.

What to check before committing to a client

Four details decide whether a merged inbox stays pleasant after the first month, and none of them appear in a feature list as a single checkbox.

Search across accounts is the first. Some clients search the account currently selected and quietly exclude the others, which turns "find that invoice" into a tour of four mailboxes. Testing with a term that exists in two accounts takes a minute and settles it.

Per-account signatures and default sending address are the second. A client that allows one signature per identity, and that picks the sending address from the account a thread belongs to rather than from a global default, removes most wrong-address replies. A client that does not will produce them.

Notification granularity is the third. Being alerted for every message in every account is how people end up muting mail entirely. Per-account notification settings, so that a client account rings and a newsletter account does not, is the setting that keeps alerts trustworthy.

Provider support is the fourth, and it is where the two approaches genuinely diverge. Google's own documentation notes that Microsoft now requires non-Microsoft email users to use modern authentication methods, which is why the desktop route of adding an Outlook account to Gmail is closed while the mobile app route stays open. Provider rules change on the provider's schedule, and every native client has to follow them. An arrangement built on each provider's own web interface inherits those changes automatically instead.

The other approach: keep the web apps, separate the sessions

The alternative is to stop treating mail as a single application at all. Each account stays in its own web session, signed in permanently, with the rest of that account's tools beside it. Nothing merges, so nothing can be sent from the wrong identity, and a client's mail, calendar and drive travel together.

This is what the category of app-aggregation browsers on macOS is built for, and the relevant pricing was checked on the same date.

Product	Free tier	Paid
Wavebox	2 groups, 2 apps in each, 1 extension	$8.33 per month, paid annually
Shift	5 spaces, 10 apps per space	$199.99 billed annually
Ferdium	No limits, open source	None

The trade-off against a native client is real and runs both ways. A web session is heavier than a native inbox and depends on a connection. In exchange, every provider works the same way, because the web interface is the provider's own, and the mail client's support for a given provider stops being a question. Gmail's keyboard shortcuts, Workspace admin controls and Microsoft's security policies all behave exactly as the vendor intended, which is not always true through IMAP.

Notifications are where this approach can go wrong or go right. Ten signed-in web apps produce ten sources of alerts, which is worse than one client, unless the browser collects them into a single notification center with a schedule for quiet hours. That is the difference between a tidy setup and a noisy one, and it is worth checking before committing. The feature list of any candidate should be read for exactly this.

When the answer is both

Plenty of setups end up mixed, and that is not a failure. A native client handles the low-stakes personal addresses in one merged inbox, while each client or employer identity lives in its own isolated workspace with its mail, calendar and files together. The rule that keeps it coherent: merge the accounts whose mistakes cost nothing, isolate the accounts whose mistakes cost something.

The hidden cost is switching, not features

Feature comparisons dominate this topic because features are easy to tabulate. The thing that actually consumes the day is switching, and it shows up in three forms.

The first is re-authentication. Every sign-out and sign-in costs a password lookup and a second factor, and two-factor prompts are the reason people leave accounts signed in somewhere they should not. A setup where every account is always signed in, in a place that survives a restart, eliminates that cost entirely.

The second is context reassembly. Answering a client message often needs the thread, the shared document, the calendar and the invoice, and those live behind the same identity. When mail has been merged into a client but the rest of the account's tools are scattered across browser tabs, each reply becomes a small scavenger hunt. Grouping the tools of one identity together is what removes it.

The third is verification. Confirming which account a window belongs to, before hitting send, is a small tax paid dozens of times a day. Color-coded spaces, or a client that shows the account prominently on every message, converts that check into something peripheral rather than deliberate.

None of these are features in the usual sense, which is why they rarely decide a roundup and almost always decide whether a setup survives.

Four questions that settle the choice

Does sending from the wrong address matter? If it does, separation beats consolidation, and a unified inbox is a liability rather than a feature.

Is there anything beyond mail attached to each account? A Google or Microsoft identity brings a calendar, a drive and a chat. Merging the mail while leaving the rest scattered across browser tabs solves a fifth of the problem.

Will anyone else need to see these messages? If yes, that is a shared inbox requirement, and it points at a team product with assignment and internal comments rather than at a personal client.

How many accounts are there really? Two or three personal addresses fit comfortably in Apple Mail at no cost. Six identities that each carry a full set of tools do not, and forcing them into one client usually produces a second problem to solve later.

What to change first

Count the accounts, then split the list into the ones that can safely merge and the ones that must not. Point the first group at a free client that is already installed, and give each account in the second group its own permanently signed-in session, which is what a browser like SpaceDeck is organized around. That single split does more for daily calm than any ranking of email clients.