Using Proton Mail in a Different Client: What's Possible
The short answer
Yes, with caveats. Proton Mail does not offer standard IMAP. A third-party client must connect through Proton Mail Bridge, a local proxy available only on paid plans. Bridge runs on Windows, macOS and Linux, not on mobile. Mail decrypts on your machine, so Proton's zero-access-at-rest guarantee shifts to your local client.
Can I use Proton Mail in another email client? Only via Proton Bridge on a paid plan. Here's what actually works — and what E2E-encrypted promise breaks.
On this page
- 01What actually works, and what does not
- 02Before you set up Proton Mail Bridge
- 03How to add Proton Mail to a third-party client
- 04What breaks with a third-party client
- 05Rolling back to Proton's native apps
- 06Running Proton and a third-party client in parallel
- 07Where AI Emaily fits — and where it does not
Can I use Proton Mail in another email client? The short answer is yes, but not through the plain IMAP you're used to. Proton's whole point is that your mailbox is end-to-end encrypted at rest, so there is no server that speaks vanilla IMAP for a third-party client to log into. The path that exists is Proton Mail Bridge — a small application you run on your own machine that decrypts locally and exposes an IMAP endpoint on 127.0.0.1.
It works. It has real trade-offs. This guide walks through what those actually are before you commit an afternoon to setting it up, and where the third-party-client shape genuinely does not fit what you wanted from Proton in the first place. Everything below is verified against Proton's own live documentation as of August 2026.
What actually works, and what does not#
Bridge is a localhost proxy. Your third-party client talks to Bridge on 127.0.0.1; Bridge talks to Proton over Proton's authenticated protocol; the encryption and decryption happen on your machine. That single architecture decision decides most of what follows.
| Capability | With Proton Mail Bridge |
|---|---|
| Standard IMAP without Bridge | Not offered — Proton does not run an IMAP server for third-party clients on any tier. |
| Bridge on Windows, macOS, Linux | Available on all three, but only on paid Proton plans (Mail Plus, Unlimited, Duo, Family, Business). |
| Bridge on iOS or Android | Not available — Bridge is a desktop application only. Mobile stays on Proton's own app. |
| Mail read and send from a third-party client | Works — Bridge exposes IMAP for reading and SMTP for sending, using per-app credentials it generates for you. |
| End-to-end encrypted at rest on Proton's servers | Preserved. Bridge does not change what Proton stores — the server still sees only ciphertext. |
| Plaintext at rest on your local machine | Yes. Your third-party client caches decrypted messages in its own local store. |
| Proton Calendar and Contacts | Not carried by Bridge. Available separately over CalDAV and CardDAV on paid plans; third-party calendar support varies. |
| Server-side search across the archive | Not available — your third-party client indexes only what it has fetched locally. |
Two rows deserve real attention. First: no IMAP without Bridge, on any plan, ever. That is a design choice, not an oversight — a Proton mailbox is encrypted with keys Proton itself cannot use, so a standard IMAP server has nothing to serve. Second: your third-party client stores a plaintext cache. That is fine if your disk is fully encrypted and your client's data folder is not backed up to a cloud service; it is a real threat-model change if either of those is not true.
Before you set up Proton Mail Bridge#
Do this checklist first. Two of the items cost real time if you skip them and discover later.
- Confirm your Proton plan includes Bridge. Free Proton accounts do not — Bridge is a paid-tier feature. Check the current tier list on proton.me/mail/bridge rather than trusting a screenshot; Proton renames tiers periodically.
- Pick the machine Bridge will live on. Bridge has to be running on the same computer as the third-party client for mail to flow. A laptop that closes its lid is a laptop that stops receiving mail while it is closed.
- Decide whether you want a full third-party setup or a hybrid. Bridge on desktop plus Proton's own iOS or Android app on the phone is the most common shape — mobile stays on Proton because Bridge does not exist there.
- Have your two-factor method in reach. Bridge asks for the 2FA code during initial login. If you use a hardware key, plug it in before starting.
- Check disk space. Third-party clients that cache all mail locally (Apple Mail, Thunderbird, eM Client) will pull a decrypted copy of your archive. A 20 GB Proton mailbox becomes a 20 GB local folder.
- Note your keyboard-shortcut habits. The features people miss most after moving off Proton's app are its shortcut set and its unified sidebar — a new client is a new muscle memory, budget a week.
How to add Proton Mail to a third-party client#
The setup is a two-step operation: install and log in to Bridge, then point your client at the per-app credentials Bridge generates for you.
- 1
Install Proton Mail Bridge from Proton's download page
Grab the installer for Windows, macOS or Linux from proton.me/mail/bridge. On macOS, drag to Applications. On Windows, run the MSI. On Linux, use the deb, rpm or AppImage that matches your distribution. Bridge is signed and code-verified — do not install from mirrors.
- 2
Log in to Bridge with your Proton account
Open Bridge, enter your Proton email and password, and complete two-factor authentication if you have it enabled. The first sync downloads message metadata; full decryption happens on demand as your client requests each thread.
- 3
Copy the Bridge-generated IMAP and SMTP credentials
Bridge does not use your Proton password for IMAP. It creates a per-application password and shows the host (127.0.0.1), the ports (usually 1143 for IMAP and 1025 for SMTP), and the username to paste. These live in Bridge's account panel and can be regenerated per client.
- 4
Add the account to your third-party client
In Apple Mail, Thunderbird, Outlook, eM Client, Mailbird or any IMAP-capable client, add a new account using the Bridge-generated credentials. Use STARTTLS for both IMAP and SMTP — Bridge issues a self-signed certificate that your client will ask to trust the first time.
- 5
Verify with a round-trip test
Send an email from Proton's webmail to yourself, wait for it in the third-party client, reply from the third-party client, and check it appears in Proton's webmail Sent folder. If both directions work, Bridge is set up correctly.
- 6
Set up calendar and contacts separately if you want them
Bridge is mail-only. Proton Calendar (CalDAV) and Proton Contacts (CardDAV) are configured against Proton's servers directly, with credentials from your account's calendar and contacts sections — not through Bridge, and not on every third-party calendar client.
Bridge has to be running for mail to flow
What breaks with a third-party client#
This is the table to read before you commit. Some of what makes Proton feel like Proton is in the app, not the mailbox, and does not survive the move.
| Proton feature | What a third-party client sees |
|---|---|
| Zero-access encryption on Proton's servers | Preserved. Bridge decrypts locally; Proton still sees only ciphertext. |
| Zero-access encryption at rest on your device | Broken. Your third-party client caches decrypted plaintext in its own store — the machine is now the weak link, not the server. |
| Password-protected messages to non-Proton recipients | Not available from a third-party client. Composition happens only in Proton's own app or webmail. |
| Self-destructing messages | Not available from a third-party client. Composed only in Proton apps. |
| PGP to WKD contacts, key pinning, address verification | Bridge handles the crypto, but the client's UI shows a plain decrypted message. Trust decisions still have to be made in Proton's app. |
| Proton Sentinel anti-phishing warnings | Account-level protection stays on. The in-app UI cues do not translate; a third-party client will not show them. |
| Proton Calendar events and reminders | Not via Bridge. Set up separately with CalDAV; third-party support varies by client. |
| Proton Drive attachments | Not integrated. Attachments show as regular file links, not as inline Drive previews. |
| Server-side search of decrypted content | Not available. The client indexes only what it has fetched, so the first month of use has thin search results. |
| Sieve filters and folder routing | Still work. They run on Proton's server before Bridge sees the message; your client receives already-filtered mail. |
Two of these rows deserve a second read. The plaintext-cache row is the one that quietly changes your threat model — if your third-party client's data folder is backed up to iCloud or OneDrive, or if your laptop is not full-disk-encrypted, Proton's zero-access story now stops at the machine, not at the mailbox. The password-protected and self-destructing rows are the reason the pragmatic shape is a hybrid: compose the sensitive sends in Proton's app, live the rest of your workflow in the third-party client.
The concession, said plainly: **Proton's own apps are the only Proton client that keeps zero-access encryption end-to-end from Proton's servers all the way to the display, without decrypting to a third-party cache on your machine.** If verifiable at-rest encryption on every device is the reason you picked Proton, keep Proton's app for those threads and treat Bridge as a productivity layer over the less-sensitive part of your mail — not a wholesale replacement.
Rolling back to Proton's native apps#
Rollback is genuinely easy — the mail was never migrated, only mirrored. Bridge is a proxy, and turning it off leaves the Proton mailbox exactly as it was.
- 1
Quit and uninstall Bridge if you are done with it
Bridge stores encrypted local caches; uninstalling removes them along with the app. On macOS drag to Trash; on Windows use Add or Remove Programs; on Linux use your package manager to remove the deb, rpm or AppImage.
- 2
Remove the Proton account from your third-party client
In most clients, this deletes the local mail cache too — the plaintext copy on your machine. Verify by checking that the account's local storage folder is gone; on macOS Mail that is ~/Library/Mail, on Thunderbird it is the profile folder.
- 3
Confirm your Proton account is intact
Log in at proton.me and check inbox count, folder structure and labels. Nothing was ever changed server-side; there is nothing to restore. If read/unread state looks off, that is Bridge's IMAP session having marked things as it fetched them — Proton's own app will re-read the flags.
- 4
Reinstall Proton's app if you want it as your daily driver again
Proton Mail is a native app on macOS and Windows, plus web at proton.me. Password-protected composition, self-destructing messages and Sentinel's in-app phishing warnings return the moment you switch back — those never left the server, only the client.
Running Proton and a third-party client in parallel#
You do not have to pick. Bridge is happy to serve mail to one client while Proton's own app runs on a different machine or in the browser. The trade is that both stores now have their own view of read/unread, drafts and folder membership — and it is the Proton server that arbitrates via IMAP flags.
The clean version is a divided-use hybrid. Set Bridge up on your work laptop and point Apple Mail or Thunderbird at it for daily triage, keyboard shortcuts and third-party integrations. Keep the Proton app on your phone for sensitive threads, password-protected external sends and self-destructing messages. Both clients see the same server-side folders; changes made in one propagate to the other after the next IMAP sync, usually within a minute or two on IDLE-capable clients.
The one thing this hybrid does not solve: if you find yourself opening Proton every second reply to use the password-protected or self-destructing features, the third-party client is not the right shape. At that point the honest question is not "which client on top of Proton" but "which provider gives me both the encryption I need and the workflow I want" — and that is a provider move, not a client move.
Where AI Emaily fits — and where it does not#
We build AI Emaily. Being honest about this post: AI Emaily is a chief-of-staff agent that connects to Gmail, Outlook and IMAP mailboxes to triage, draft in your voice and close loops with approve-before-send. That shape does not marry with Proton Mail Bridge. Bridge is a same-machine localhost proxy — nothing outside your laptop can reach it — and our agent runs server-side, so the two do not meet in a way that keeps Proton's zero-access story intact.
If you are considering the third-party-client route because you have outgrown what Proton's native app does for triage and drafting, the real decision may be a provider move, not a client move. See [AI Emaily vs Proton](/compare/ai-emaily-vs-proton) for the honest side-by-side, the [Connect Proton](/docs/connect-proton) doc for the setup pathways we do support, or [AI Emaily pricing](/pricing) — 7-day trial, card required, $0 if cancelled before day 7.
Frequently asked
See it in AI Emaily
Keep reading
Sources
Written by
Nafiul HasanNafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.