Why I Switched from Proton Mail to Fastmail

I still care deeply about email privacy — but I recently moved my primary inbox from Proton Mail to Fastmail. Here’s why the trade-offs finally tipped.

Paul O'Brien
4 min read

I care deeply about email privacy. That hasn’t changed.

I’ve stopped treating my inbox as a privacy statement. These days, I care far more about whether my email actually works without getting in my way.

Recently, when my Proton Mail billing anniversary came around, I made a decision I’d been circling for a while: I moved my primary inbox from Proton Mail to Fastmail.

This wasn’t a dramatic break, and it wasn’t driven by a sudden loss of faith in privacy-first email. It was a reassessment — prompted by cost, constraints, and how my own usage has evolved.

Key TakeawaysThe Core Reason: Moving from a strict threat-model focus to daily operational efficiency, speed, and cross-client flexibility.The Cost Difference: Fastmail includes up to 100 custom domains and 600 aliases standard, whereas Proton gating required higher pricing tiers.The Hybrid Compromise: Primary day-to-day operations moved to Fastmail, while maintaining a @proton.me account for high-sensitivity signups.

This isn’t a reversal on privacy

Let’s be clear upfront: I haven’t suddenly decided that Gmail is “good enough,” or that advertising-funded inboxes are harmless. I still believe that free email funded by data extraction creates incentives that don’t work in the user’s favour. That hasn’t changed.

What has changed is my threat model.

For my own day-to-day use — newsletters, client emails, admin, domains, and long-term archiving — I’m balancing privacy with reliability, speed, and flexibility, and choosing a service that stays out of the way of how I actually work.

Where Proton Mail started to feel constrained

I’ve written at length about what Proton Mail gets right: zero-access encryption, reduced provider visibility, and a business model that doesn’t depend on advertising. I still respect that architecture, and I still think Proton is one of the most credible privacy-first email providers available.

But over time, friction crept in. Some of that was technical, some was structural, and some was simply about cost relative to what I actually need.

Feature / Metric Proton Mail Fastmail
Primary Philosophy Zero-access encryption & threat isolation Open standards & operational reliability
Protocol Support Proprietary API (Requires Proton Bridge for IMAP) Native IMAP, SMTP, CalDAV, CardDAV
Custom Domains Restricted / Gated by subscription tier Up to 100 custom domains included
Included Aliases Tiered limits Up to 600 aliases included
Search Engine Client-side indexing (slower on large archives) Fast server-side index (encrypted at rest)

Cost vs flexibility

As someone with multiple domain names, Proton’s pricing model became harder to justify. Adding more domains, more aliases, and more storage meant moving up tiers. I reached a point where I didn’t want to keep upgrading my Proton account just to accommodate how I already work.

Fastmail, by contrast, allows up to 100 custom domains and 600 aliases on a single account at no extra cost. For someone managing multiple identities and domains, that difference isn’t academic — it’s practical.

Workflow friction & protocol adapters

Proton Mail works best inside its own ecosystem. That’s not a flaw; it’s a design choice. But over time, it felt increasingly constrained.

Search is noticeably slower on encrypted content because indexing happens locally on client devices. While the Proton Bridge daemon works, it always feels like an adapter running in the background rather than a native experience.

Fastmail, by contrast, is unapologetically IMAP-native. It works naturally with Apple Mail and other standard desktop and mobile email clients, while offering fast, lightweight native apps across platforms.

Service quality and support started to matter more

Another factor — and one I didn’t expect to carry as much weight — was service responsiveness. Over the past year, I’ve seen increasing reports from Proton users about slow responses and stretched support:

  • Trustpilot sentiment on Fastmail: "Many reviewers praise the customer service, describing it as fast, helpful, and patient."
  • Trustpilot sentiment on Proton Mail: "Some reviewers mention that they did not receive a response from customer support..."

Separately from public user feedback, I experienced service delays myself — not with day-to-day email support, but through Proton’s partner channels. Recent communications went unanswered for months and still remain unanswered.

That gave me pause. If partners struggle to get timely responses, it becomes harder to confidently recommend the service or refer business without hesitation.

By contrast, Fastmail’s support has been consistently fast, human, and practical. When something needs clarification or breaks, you reach someone who understands email infrastructure — not a ticket that disappears into a queue. That reliability is part of the product.

What Fastmail gives me day to day

Fastmail doesn’t position itself as a privacy crusade. It positions itself as a fast, well-run email service that expects users to trust it — and then works hard not to betray that trust.

In practice, that looks like:

  • Instant Search: High-speed server-side indexing across large historical archives.
  • Calm Interface: Highly responsive web and mobile web/app interfaces.
  • Spam Filtering: Excellent filtering controls without delivery drama or false positives.
  • Generous Limits: 50 GB of mail storage and 10 GB of file storage standard.
  • Client Freedom: Seamless integration with Apple Mail, Thunderbird, and terminal tools.

How I handled the migration

The migration itself wasn’t entirely frictionless, but it was straightforward:

  1. Installed Proton Mail Bridge on macOS.
  2. Connected my Proton account to Apple Mail.
  3. Added my new Fastmail account via native IMAP.
  4. Dragged historical mail folders across folder-by-folder.

No vendor lock-in. No proprietary export formats. Just standard email behaving like email.

Step 1: Point Domain MX Records ──► Fastmail Infrastructure
Step 2: Connect Proton Bridge    ──► Drag-and-Drop Folders to Fastmail via IMAP
Result: Zero Downtime / Zero Address Changes Across Existing Accounts

Why having my own domain made the switch easier

One reason this move was relatively painless is that I don’t treat my email address as provider-owned.

By using my own custom domain names, my public-facing addresses don’t change when I change providers. I can move the infrastructure underneath without asking contacts or services to update their address books.

Owning your domain turns email providers into services you can swap — not identities you’re locked into.

A pragmatic split: I didn’t leave Proton entirely

I still keep my @proton.me address. When I want an extra layer of provider-isolated privacy — sensitive sign-ups, one-off communications, or high-risk scenarios — Proton is still there.

But for day-to-day email operations, Fastmail is now my primary provider.

This split just makes sense. I don't need one provider to solve every threat model. Fastmail won my daily workflow because it delivers what I actually use: lower domain costs, native app support, instant search, and dependable technical help.

Visit > Fastmail.com for more information.