Why Tuta Doesn't Support IMAP (and What That Means for You)

Searching for Tuta IMAP settings, or trying to understand why does Tuta not support IMAP, leads to the same answer regardless of where you look: there are no settings to find. Tuta does not offer IMAP or SMTP access. Unlike Proton Mail — which provides a local bridge application for paid users — Tuta offers no supported path to connecting your account to a third-party email client.

This is not a missing feature awaiting a product update. It is a direct consequence of how Tuta's encryption model was designed. The same architecture that makes Tuta genuinely private is the reason Thunderbird, Apple Mail, and similar clients cannot connect to it.

This post explains the mechanism, maps out what access Tuta does offer across platforms, and is clear about one limit that applies to every third-party tool: no external email client — including AI Emaily — can connect to a Tuta account.

Why Tuta Has No IMAP or SMTP Server#

Most email providers store your messages in a format the server can read on demand. When a client connects via IMAP — the protocol defined in RFC 9051 — the server fetches the message, formats it, and sends it over the wire. The provider can do this because the mail sits in a readable form on their infrastructure.

Tuta was designed around the opposite model. Messages are encrypted on your device before they leave it, using keys that only you control. What arrives at Tuta's servers is ciphertext. Tuta goes further than most end-to-end encrypted providers: it encrypts not just message bodies, but also subject lines, contact names, and the full-text search index. The server cannot reconstruct the subject of a message, let alone its content.

Standard IMAP cannot work in this environment. RFC 9051 defines IMAP as a protocol for accessing and manipulating messages stored on a remote server. If the server cannot read the messages, it cannot serve them through IMAP. A real imap.tuta.com endpoint would require Tuta to hold decryption keys on their side — which would invalidate the core privacy guarantee at the product's foundation.

Proton Mail, which uses a similar end-to-end encryption model, addressed this with a different product decision: Proton built Bridge, a local desktop application. Bridge runs on the user's own machine, decrypts mail locally using the user's keys, and then exposes a private IMAP server that listens only on 127.0.0.1. Tuta has no equivalent. As of August 2026, Tuta does not offer or announce any Bridge-style workaround, and Tuta's own documentation does not indicate one is planned.

What You Can Actually Do With a Tuta Account#

Because IMAP and SMTP are unavailable, the only supported way to read and send Tuta mail is through Tuta's own applications. These cover every major platform, so access exists for each environment — just not through the client you may have hoped to use.

1. 1

   Use the Tuta web app

   The web interface at app.tuta.com works in any modern browser without installation. It is the most feature-complete version of the product and the fastest way to access your account from a shared or unfamiliar machine.

2. 2

   Install the Tuta desktop app

   Tuta publishes downloadable desktop applications for Windows, macOS, and Linux. These are Electron-based — the same web interface in an installable wrapper — available directly from tuta.com. They support system notifications and offline reading of previously cached messages.

3. 3

   Use the Tuta mobile app

   Tuta Mail is available on iOS via the App Store and on Android via the Play Store and F-Droid. The mobile apps support push notifications, offline access to synced messages, and end-to-end encrypted replies and composition.

4. 4

   Export your mail if you are migrating

   If the absence of IMAP is a hard blocker and you want to move to a provider that supports standard clients, Tuta's account settings include an export tool. It produces files you can import into another service. Note that exported mail loses its end-to-end encryption once it leaves Tuta's environment — this is expected and unavoidable, not a product bug.

Where Tuta Works and Where It Does Not#

The table below shows how Tuta access maps across platforms and client types. The third-party client column applies equally to desktop clients like Thunderbird, hosted email services, and any IMAP-based backup or archiving tool.

What to Do When the Lack of IMAP Is a Problem#

Most Tuta users accept the trade-off: strong privacy in exchange for using Tuta's own client on every platform. For some workflows, however, the absence of IMAP is a genuine blocker rather than an inconvenience.

The most common scenario is a unified inbox. If you manage several email accounts — a Tuta address alongside Gmail or Outlook accounts — there is no way to consolidate them in a single third-party client. You have to switch between the Tuta app and whatever client you use for the other accounts.

A second scenario is continuous backup and archiving. Many enterprise backup services and personal archiving tools sync mail via IMAP. They cannot reach a Tuta account. Tuta's export tool provides point-in-time snapshots, but continuous off-platform sync is unavailable.

The third scenario is inbox automation. Tools that read your inbox via IMAP to trigger workflows — certain Zapier integrations, for example — cannot connect to Tuta. Tuta does not expose a public API for third-party inbox access.

• Unified inbox across providers: not possible. Tuta mail stays inside the Tuta app and cannot be pulled into a multi-account client alongside other inboxes.
• IMAP-based backup or archiving: not possible as a continuous sync. Use Tuta's export function for periodic snapshots.
• Third-party automation that reads the inbox: not possible. Tuta has no publicly accessible inbox API for this purpose.
• Migration to another provider: possible via Tuta's built-in export tool. The exported mail can be imported into a new provider's inbox.
• Using Tuta alongside other accounts on the same device: possible by running the Tuta app and your other client side by side, but not in a unified view.

A Faster Way for Your Other Accounts#

Tuta cannot be added to a third-party client, and that limit is structural. We are not going to suggest a workaround that does not exist. But most people asking this question also manage at least one account on Gmail, Outlook, Fastmail, or another provider that uses standard IMAP. If that describes your setup, there is an option for those accounts.

We build AI Emaily. It is a hosted email client with an AI assistant that triages your inbox, drafts replies shaped by the voice and context you define in your Personal Context, and handles routine correspondence at the autonomy level you set — from manual approval through Copilot to Autopilot with undo and a full audit log. AI Emaily connects to Gmail, Outlook, and standard IMAP providers directly. It does not connect to Tuta, because no remote IMAP endpoint exists for Tuta accounts — that limit applies to us exactly as it applies to Thunderbird. What AI Emaily does is make the accounts on providers that do support standard protocols meaningfully easier to manage.