How to Send Encrypted Email Gmail: What Actually Works Today

If you need to send a sensitive message from your Gmail account right now, you deserve a straight answer about how to send encrypted email Gmail provides by default, what that protection actually covers, and where the real gaps are. Most guides conflate access controls with encryption. This one won't. You'll get the specific steps, the specific limits, and the one free tool that gives you genuine end-to-end encryption on a personal Gmail account today.

Key Takeaways

• Gmail encrypts messages in transit using TLS, but only if the recipient's mail provider also supports it. If it doesn't, Gmail sends the message in plain text.
• Confidential Mode is not encryption. It is an access-control feature. The email provider can still read the content, and screenshots defeat it trivially.
• True end-to-end encryption (S/MIME, client-side encryption) is restricted to paid enterprise Workspace accounts. Personal Gmail has no built-in E2EE option.
• The practical path for a free, personal Gmail account is a browser extension like FlowCrypt or Mailvelope, which layers OpenPGP encryption on top of Gmail's compose window.
• Even with body encryption, email metadata (sender, recipient, subject line, timestamps) remains visible to every server that touches the message. Keep subject lines vague.

What Encryption Does Gmail Actually Provide by Default?

Gmail uses TLS (Transport Layer Security) to encrypt messages while they travel between servers. That protection applies only during transit, and only if the recipient's email provider also supports TLS. If the other side doesn't, the message goes out unencrypted. You have no control over that decision and no notification before you hit send.

Once a message arrives, it sits on the provider's servers in a form the provider can read. TLS protects the pipe, not the contents at rest.

You can check the encryption status of any individual message by looking at the lock icon next to the recipient's name in the compose window. Gray means standard TLS. Green means S/MIME, which is only available on enterprise Workspace accounts. A red unlocked icon means the recipient's provider doesn't support TLS at all, and your message will travel in the clear.

Is Gmail Confidential Mode the Same as Encryption?

No. This is the single most common misunderstanding in every guide on this topic, and it is worth being precise about.

Confidential Mode lets you set an expiration date, revoke access after sending, and disable the forward button in the recipient's interface. Those are access controls. They are a form of data loss prevention. The content is stored on the provider's servers without a user-held encryption key, so the email provider retains access to it. There is no cryptographic barrier between the provider and your message.

The practical limits are worth spelling out:

• Nothing stops a recipient from screenshotting or photographing their screen. The provider itself acknowledges this.
• A recipient with malware on their device can still copy or download the content.
• The word "Confidential" in the feature name creates a gap between what users believe they are getting and what they are actually getting. A lock icon that means "we disabled the forward button" is not the same as a lock icon that means "only the intended recipient can decrypt this."

If you need to prevent interception by third parties or prevent the email provider from reading the content, Confidential Mode does neither.

How Do I Turn on Confidential Mode?

If access controls are sufficient for your use case (for instance, you want to set an expiration on a message to a trusted colleague), here are the steps:

1. Open a new compose window in Gmail.
2. Click the lock-and-clock icon at the bottom of the compose window (it may be labeled "Confidential mode" on hover).
3. Set an expiration date: 1 day, 1 week, 1 month, 3 months, or 5 years.
4. Optionally require an SMS passcode. The recipient will get a code via text message and must enter it to view the email. This adds a second factor but does not add encryption.
5. Click Save, then compose and send your message normally.

That is the entirety of it. Understand that you are controlling access, not encrypting content.

Why Is Real End-to-End Encryption Not Available on Free Gmail?

Because the provider has structured it that way. Client-side encryption launched for Gmail on the web in 2022, restricted to enterprise Workspace accounts. It reached general availability in 2025, still enterprise only. In April 2026, client-side E2EE extended to Gmail's mobile apps for the first time, still exclusively for enterprise/Workspace accounts.

The pattern has been consistent for over a decade. A Chrome extension called End to End was announced in 2014 that would have added PGP encryption to Gmail, but it was quietly abandoned. S/MIME, the other built-in encryption option, is also unavailable on personal accounts.

The result: if you are on a free Gmail account and you need to send a message that your email provider cannot read, there is no built-in way to do it. Advanced security is gated behind enterprise pricing tiers. Whether that is a reasonable business decision or a structural gap depends on your perspective, but the fact is plain.

What About Metadata?

This is the part almost every walkthrough skips.

Even if you encrypt the body of your email with the strongest available tool, the sender address, recipient address, subject line, and timestamps remain completely unencrypted and visible to every server that relays the message. Confidential Mode does not change this. TLS does not change this. PGP does not change this.

For many real threat models, metadata is the more actionable exposure. If someone can see that you emailed a specific lawyer at 2 AM on a Tuesday, the content of the message may not matter much. If a journalist's source is identifiable by the sender address alone, body encryption is necessary but not sufficient.

This is a structural limitation of email as a protocol. No Gmail feature, paid or free, addresses it. If metadata privacy matters to your situation, email may not be the right channel. Dedicated end-to-end encrypted messaging tools, or zero-knowledge file transfer services, handle this differently by design.

How Do I Actually Send an End-to-End Encrypted Email from a Personal Gmail Account?

You install a browser extension that adds OpenPGP encryption on top of Gmail's compose window. The two credible, free options are FlowCrypt and Mailvelope. Both work. Here is the step-by-step for each.

Option 1: FlowCrypt

1. Install FlowCrypt from the Chrome Web Store. It also has a mobile app for Android.
2. Open Gmail. FlowCrypt will prompt you to set up or import a PGP key. If you don't have one, it generates a new key pair in a few clicks.
3. A new "Secure Compose" button appears in your Gmail interface. Click it.
4. Compose your message. If your recipient also uses PGP (FlowCrypt, Mailvelope, or any PGP-compatible tool), the message is encrypted end-to-end using their public key.
5. If your recipient does not have a PGP key, FlowCrypt can send a password-protected message instead. You share the password with the recipient through a separate channel (a phone call, a text message, anything that is not the same email thread).

The password-protected fallback is the most practical option for sending one encrypted message to someone who has never heard of PGP. They receive a link, enter the password, and read the message in their browser. No software installation required on their end.

Option 2: Mailvelope

1. Install Mailvelope from the Chrome Web Store.
2. Generate a PGP key pair through the Mailvelope setup wizard. This takes about thirty seconds.
3. Exchange public keys with your recipient. Mailvelope can search public key servers, or you can manually import your recipient's public key.
4. When composing in Gmail, click the Mailvelope overlay icon to open the encrypted editor. Write your message, select your recipient's key, and send.

Mailvelope is open-source and works across most webmail providers, not just Gmail. The trade-off compared to FlowCrypt: Mailvelope does not have a built-in password-protected message option for recipients without PGP keys, so both parties generally need compatible setups.

What Should I Put in the Subject Line?

As little as possible. Subject lines are not encrypted in PGP emails. Write something generic: "Follow-up" or "Document" or nothing at all. Do not put the substance of the communication in the subject line.

How Do These Solutions Compare?

Here is the honest landscape for a personal Gmail user in mid-2026:

• TLS (default): Encrypts in transit only, and only if the recipient's provider cooperates. The email provider reads the content at rest. Metadata exposed.
• Confidential Mode (built-in): Access controls. Not encryption. Provider reads the content. Screenshots defeat it. Metadata exposed.
• S/MIME (built-in, enterprise only): Real encryption, but requires paid Workspace. Both parties need S/MIME certificates. Not available to you on a free account.
• Client-Side Encryption (built-in, enterprise only): Genuine E2EE where the provider cannot read the content. Available on web and mobile as of April 2026, but restricted to Enterprise Plus-level plans.
• FlowCrypt / Mailvelope (free, third-party): Real end-to-end encryption via OpenPGP. Works on personal Gmail. Requires a browser extension. FlowCrypt can send to recipients without PGP via password-protected messages.

If you need to send one encrypted email today from a personal Gmail account, FlowCrypt's password-protected message is the lowest-friction path. Install the extension, generate a key, compose in Secure Compose, set a message password, and share that password with your recipient through a different channel.

What Are the Limits of the PGP Approach?

PGP browser extensions solve the body-encryption problem. They do not solve the metadata problem. They do not protect attachments separately from the message body (the attachment is encrypted along with the message, but if you need to share a large file, email is often the wrong tool regardless). And they add friction: you are installing software, managing keys, and asking your recipient to do something slightly unfamiliar.

There are also newer, lighter-weight projects emerging. An open-source PGP layer for Gmail appeared in early 2026 with one-click key generation aimed at non-technical users. GmailKrypt is another recent entry. These are newer, less battle-tested, and worth evaluating on their own merits, but the trend is clear: people want simpler encrypted-email UX outside of enterprise tools, and the tooling is catching up.

Why Does This Matter Beyond One Email?

The gap between what labels promise and what crypto delivers is a thing we think about constantly. When you build an encrypted system, debugging is different. You cannot just query the database and read a content column to verify what a user sees. In an encrypted-at-rest architecture, a content column can read as empty and still decrypt to perfect data through the application's own decrypt path. The source of truth is the decrypt path on the specific rows, not the raw storage. That is a small operational detail, but it shapes how you think about the relationship between storage and truth. Labels on a UI ("Confidential," "Encrypted," "Secure") are not the same as the cryptographic reality underneath them.

This is the core problem with Confidential Mode. The label says confidential. The system says access-controlled. Those are different things, and the difference matters precisely when you need it most: when the stakes are real.

When Should I Not Use Email at All?

If your threat model includes metadata surveillance (who you are communicating with, when, and how often), email is structurally the wrong tool. No amount of body encryption fixes the fact that email headers are visible to every relay server.

If you need to transfer a file with true zero-knowledge encryption, where the service itself cannot access the content, dedicated encrypted transfer tools exist for that purpose. If you need ongoing private conversation, an end-to-end encrypted messaging platform is a better fit than email.

Email is good for what it is good for: asynchronous, interoperable communication across organizational boundaries. For a single sensitive message where you need body-level encryption and your recipient is on any email provider, the PGP-extension approach described above is the best option available on a personal Gmail account today. Just understand the boundaries.

The Steps, Compressed

If you skimmed here, the short version:

1. Install FlowCrypt in your browser.
2. Generate a PGP key (FlowCrypt walks you through it).
3. Click "Secure Compose" in Gmail.
4. Write your message. Set a message password if your recipient doesn't use PGP.
5. Send the email. Share the password via a different channel (phone, text, Signal).
6. Keep the subject line vague. It is not encrypted.

That is the whole thing. It takes about five minutes the first time and about thirty seconds every time after.

If you want encrypted communication that handles memory, context, and file transfers without routing through email at all, start a free 7-day trial, no card required.

Michael C.

Founder & Principal Engineer, Selina Labs

Michael builds Selina, a privacy-first AI that remembers you across conversations. He ships security-sensitive AI in production — real attacks, real fixes, measured in minutes and dollars — and writes about privacy, security, and LLMs from that seat. Top Rated Plus and expert-verified on Upwork.

• www.upwork.com
• x.com
• medium.com
• selinalabs.io