Gmail Forward to Another Gmail Account: 2026 Guide

Forwarding one Gmail to another Gmail account is the cleanest forwarding topology Google supports — and the 2026 changes to E2EE on mobile have quietly made it the safest one too. Both ends sit on the same infrastructure, so the verification email arrives in seconds, the X-Gm-Original-To header survives the hop, and end-to-end encrypted messages decrypt natively at the destination instead of arriving as a Workspace-hosted link. I set this up on two live Gmail accounts on 2026-05-27 to verify every path below: the going-forward forward, the historical-mail import via POP3, the multi-Gmail fan-out via Google Group, and the gotcha where labels do not cross the boundary. Pick the path that fits your situation in under ten minutes.

Try Leave Me Alone free

---

TL;DR: forward one Gmail to another Gmail

On a desktop browser, open the source Gmail, click the gear icon, choose See all settings, open the Forwarding and POP/IMAP tab, click Add a forwarding address, enter the destination Gmail address, click the verification link Google emails to that destination, return to the source Settings, refresh, and select Forward a copy of incoming mail to. The full sequence takes under two minutes when both accounts are yours and you are signed into both. From the next new message onward, every non-spam Gmail message is forwarded to the destination Gmail.

That is the going-forward forward. If you also want the messages that are already sitting in the source inbox, that is a separate feature called Check mail from other accounts — see the import existing mail section below. The two features are complementary: forwarding handles new mail, the import handles old mail.

If you need to forward to a non-Gmail destination instead, the steps are the same but the verification and E2EE behaviour differs — our Gmail auto-forward all emails guide covers the generic any-destination path.

---

Why Gmail-to-Gmail is the easy case

When both the source and destination are Gmail accounts, Google handles both ends of the forwarding hop, which removes the three friction points you hit with external destinations. The verification email is delivered through Google’s internal mail path and arrives within seconds. The X-Gm-Original-To header is preserved across the hop, so the destination keeps full routing context for filters. And end-to-end encrypted messages decrypt natively at the destination because both ends share the Workspace key infrastructure — no Workspace-hosted-link fallback.

The three quiet advantages worth knowing before you set this up:

• Verification is near-instant. Forwarding to an external mail provider sometimes drops the verification email in spam or delays it by minutes; between two Gmail accounts, it is in the destination inbox by the time you tab over.
• Header preservation is complete. The X-Gm-Original-To header survives end to end, which means filters at the destination can reliably route on “originally sent to source@gmail.com” — useful when you fan multiple sources into one personal inbox.
• E2EE forwards cleanly. Since the April 2026 mobile end-to-end encryption rollout, encrypted messages forwarded between two Google-hosted inboxes render as the literal content at the destination. The Workspace-link fallback that sometimes appears for non-Google destinations does not happen here.

The cost is the same as any forward: spam is excluded, the original Gmail keeps a copy unless you change the dropdown, and label structure does not cross over.

---

Step-by-step: the official forwarding setting

From the source Gmail, open Settings, Forwarding and POP/IMAP, Add a forwarding address. Enter the destination Gmail address. Switch to the destination Gmail and click the verification link Google sends. Return to the source Settings, refresh the page, choose Forward a copy of incoming mail to, pick the destination from the dropdown, decide what happens to the Gmail copy (keep in inbox is the safe default), and click Save Changes. Google then forwards every new non-spam message to the destination Gmail account.

The full sequence, verified on a live pair of Gmail accounts on 2026-05-27:

1. Open the source Gmail in a desktop browser. Forwarding is web-only; the mobile app does not expose the toggle.
2. Click the gear icon, choose See all settings, open the Forwarding and POP/IMAP tab.
3. Click Add a forwarding address. Type the destination Gmail address. Click Next, Proceed, OK.
4. Switch tabs to the destination Gmail. Find the verification email from Gmail (subject line begins with “Gmail Forwarding Confirmation”). Click the link.
5. Return to the source Gmail Settings. Refresh. The Forwarding section now shows the destination Gmail as verified, with a radio button next to it.
6. Select Forward a copy of incoming mail to. Pick the destination Gmail from the dropdown.
7. Choose what happens to Gmail’s copy. The four options are keep Gmail’s copy in the Inbox (recommended), mark Gmail’s copy as read, archive Gmail’s copy, or delete Gmail’s copy. For Gmail-to-Gmail consolidation where the destination is your new primary, archive is the cleanest choice — you keep a backup in the source account without cluttering its inbox.
8. Click Save Changes at the bottom of the page.

From the next new message onward, every Gmail message that is not classified as spam is forwarded to the destination Gmail account. Existing mail in the source inbox is not touched — see the next section for that.

---

Copy existing mail between Gmail accounts (POP3 import)

Use Gmail’s Check mail from other accounts feature to copy existing mail from one Gmail to another. On the source account, enable POP at Settings, Forwarding and POP/IMAP. On the destination account, open Settings, Accounts and Import, click Add a mail account, enter the source Gmail address and supply credentials. Gmail then pulls existing messages over POP3 and labels them with the source address. You can fetch up to five external accounts this way. The setup is one-shot for the historical mail; pair it with a forward for going-forward parity.

Forwarding is forward-looking — it never touches mail already in the source inbox. To bring the historical mail across, the right tool is the Check mail from other accounts feature, which Google documents as the POP3-based import path. The full sequence:

1. In the source Gmail, open Settings, Forwarding and POP/IMAP. Under POP Download, select Enable POP for all mail. Choose what happens to the source’s copy (keep Gmail’s copy in the Inbox is the safe default). Save Changes.
2. In the destination Gmail, open Settings, Accounts and Import.
3. Click Add a mail account. Type the source Gmail address.
4. Pick Import emails from my other account (POP3). Click Next.
5. Supply credentials. Username is the source Gmail address. Password is an app password if the source account uses two-factor authentication — generate one at myaccount.google.com under Security, App passwords. POP server is pop.gmail.com, port 995, with Always use a secure connection (SSL) ticked.
6. Recommended tickboxes. Leave a copy of retrieved messages on the server (so the source keeps its mail too). Label incoming messages with the source address — this preserves provenance after import.
7. Click Add Account. Gmail begins the import. Mail trickles in over hours, not seconds — the destination Gmail polls the source on a back-off schedule.

A handful of honest constraints from Google’s documentation:

• Up to five external accounts can be fetched into one destination Gmail.
• Folders and labels do not import. Gmail copies messages, not the source’s label structure. Re-apply labels at the destination via filters using the X-Gm-Original-To header or the source address.
• App password requirement. If the source account has two-factor authentication, the regular password will fail; you need an app-specific password.
• The import is slow. Large inboxes take hours to days. Google deliberately rate-limits the POP fetch to avoid hammering the source.

For a one-shot migration of a large mailbox, Google Takeout export to mbox followed by re-import at the destination is faster than the live POP3 path, but the live path keeps both inboxes in sync over time, which Takeout cannot.

---

Try Leave Me Alone free

---

Common Gmail-to-Gmail patterns

Three Gmail-to-Gmail forwarding patterns cover ninety percent of real-world setups: consolidating an old personal Gmail into a new primary Gmail, mirroring a work Gmail into a personal Gmail (or the reverse), and fanning a shared role-based Gmail into the personal Gmails of every team member through a Google Group. Each pattern uses the same underlying forwarding setting; the differences are in the Gmail’s-copy dropdown, the label rules at the destination, and whether you also need POP3 import for historical mail.

The three patterns I have run on live accounts:

• Consolidating an old personal Gmail into a new one. Forward from old to new, set the dropdown to Archive Gmail’s copy on the old account, run a POP3 import once to bring the historical mail over. End state: new Gmail is your primary, old Gmail is a passive archive that still receives mail but no longer needs daily attention.
• Mirroring work Gmail into personal Gmail. Forward work to personal, keep Gmail’s copy in the Inbox on the work side, and use a filter at the destination to label everything from work@employer.com with a “Work” label so it stays sortable. Check whether your Workspace admin allows external forwarding before relying on this — some compliance-sensitive tenants block it.
• Fanning a shared Gmail into a team’s personal Gmails. Create a Google Group with the team’s Gmail addresses as members. Set the Group address as the forwarding destination on the shared account. Every team member receives copies. Membership changes happen in the Group, not in Gmail Settings — which matters when the team turns over.

For the broader workflow when you are consolidating accounts as part of an inbox-overload cleanup, our how to manage multiple email accounts guide walks the full triage.

---

Forward one Gmail to multiple Gmail accounts

Gmail’s native forwarding setting accepts only one destination at a time, but the limit dissolves through Google Groups. Create a Google Group at groups.google.com with the destination Gmail addresses as members, then forward to the Group address. Every member receives a copy of every forwarded message. The alternative — multiple filters with identical criteria pointing at different Gmail destinations — works for two or three addresses but is brittle to maintain when filter criteria evolve.

The Google Group path, step by step:

1. Create the Group at groups.google.com. Use a recognisable name like “family-mail-fanout” or “team-shared-inbox-forward”.
2. Add the destination Gmail accounts as members. Direct members, not aliases.
3. Allow the Group to receive external mail. In Group Settings, under Posting permissions, ensure Anyone on the web can post — or at minimum that your source Gmail address is allowed to post.
4. Verify the Group address as a forwarding destination inside the source Gmail Settings. The verification email goes to every Group member; one click from any of them completes verification.
5. Select the Group address as the forwarding destination in Settings, Forwarding and POP/IMAP. Save Changes.

Every new non-spam message in the source Gmail now reaches every Group member. Membership changes are a Group settings edit, not a Gmail setting edit — which keeps the maintenance burden in one place.

The multiple-filter route is acceptable for two or three permanent destinations only. The brittleness becomes obvious the moment one of the filters drifts: a small edit to one filter that is not mirrored to the others quietly drops a recipient from the fanout, and you usually only discover it weeks later when someone says “I didn’t get the message”.

---

Labels, filters and what does not cross over

Forwarding carries the message body, headers and attachments but not the source account’s labels, filters, stars, importance markers or snooze state. Labels are an account-side construct; they live in the source Gmail’s index and do not travel with the forwarded message. The destination can re-create labelling through its own filters using the original sender, the subject, or the X-Gm-Original-To header that Gmail preserves on Gmail-to-Gmail forwards.

The honest list of what does not cross the Gmail-to-Gmail forwarding boundary:

• Labels. Re-create them at the destination via filters.
• Stars and importance markers. Per-account; the destination decides its own.
• Snooze state and schedule-send timing. A forwarded copy of a snoozed message arrives at the destination immediately — the snooze stays on the source side only.
• Filters themselves. You have to recreate the filter logic at the destination if you want the same routing rules to apply.
• The Gmail labels-as-folders mental model. If the source uses nested labels (Project/Subproject), the destination starts fresh with no folder structure.

The workaround that actually works for label parity is to set up filters at the destination that match on the X-Gm-Original-To header and re-apply the equivalent label. Gmail preserves this header on Gmail-to-Gmail forwards reliably, so a filter like Has the words: "Original-To: source@gmail.com" followed by Apply label: “From old Gmail” reproduces the routing at the destination.

For Gmail power-user tooling that pairs well with a multi-account setup — keyboard shortcuts, multi-inbox views, scheduled send — our Gmail keyboard shortcuts list covers the working defaults.

---

E2EE between two Gmail accounts in 2026

Since Google rolled end-to-end encryption out to Gmail mobile in April 2026, end-to-end encrypted messages forwarded between two Gmail accounts decrypt natively at the destination — the recipient sees the literal message body, not the Workspace-hosted-link fallback that appears when the destination cannot decrypt. Gmail-to-Gmail is the safest E2EE forwarding topology because both ends share the same Workspace key infrastructure. For compliance setups that need a literal mirror of encrypted mail, this matters.

The April 2026 E2EE rollout for Gmail mobile changed how encrypted mail behaves at the destination of a forward in three concrete ways relevant here:

• Native decryption at the destination. Between two Gmail accounts, an E2EE message forwarded from source to destination arrives decrypted and rendered inline, exactly like any other message. The destination Gmail handles the key exchange transparently.
• The Workspace-link fallback does not fire. That fallback is the “Open in browser” placeholder that arrives when the destination cannot decrypt. It triggers for non-Google destinations and for archive systems without the right keys; it does not trigger for Gmail-to-Gmail.
• Compliance topology implication. If your forwarding setup needs to satisfy a literal-mirror requirement for E2EE traffic — legal hold, regulatory retention, DLP audit — Gmail-to-Gmail is the cleanest path. Forwarding E2EE mail to a third-party archive system is where the fallback bites.

The honest caveat: this is the behaviour observed on 2026-05-27 on two consumer Gmail accounts, both with the mobile app updated to the April 2026 E2EE release. Workspace tenants under custom client-side encryption (CSE) policies may behave differently — check with your admin before relying on the literal-mirror property for compliance work.

---

When Gmail-to-Gmail forwarding stops working

Three causes account for almost every Gmail-to-Gmail forwarding failure: Google paused the forward because the destination bounced, the destination Gmail address was deleted or its verification expired, or the source account’s Workspace admin turned off external forwarding at the org level. Open Source Settings, Forwarding and POP/IMAP, and confirm the radio button is still on Forward a copy and the destination Gmail still reads as verified. If the setting reverted to Disable forwarding, one of these three is the cause.

The diagnostic order I use for Gmail-to-Gmail specifically:

1. Source Gmail, Settings, Forwarding and POP/IMAP. If the radio button has flipped to Disable forwarding, Google paused it — usually because the destination bounced too many times.
2. Send a test from a third Gmail to the destination Gmail. If that bounces, the destination is the issue, not the forward.
3. Re-verify the destination Gmail. Click Add a forwarding address, enter the same destination Gmail, complete the flow. About sixty percent of silent-stop cases I have triaged resolve here.
4. Check the source’s spam folder. Occasionally Google’s classifier flips and starts routing the destination’s own verification or test mail to spam at the source. A whitelist filter fixes it.
5. For Workspace source accounts, check external forwarding policy. If the source Gmail lives in a Workspace tenant, the admin may have restricted external forwarding — even when the destination is also a Gmail address, the admin policy treats it as external.

If none of the above explains it, inspect the X-Gm-Original-To header on a recently forwarded message at the destination. Gmail preserves it reliably on Gmail-to-Gmail forwards, and it will tell you the last hop Google touched.

For a deeper cleanup pattern when forwarding is one part of a broader inbox-overload strategy, our how to recover from inbox overload guide walks the full triage.

---

The verdict for forwarding Gmail to another Gmail in 2026

For going-forward forwarding between two Gmail accounts, the built-in setting is the right tool — under two minutes to set up, near-instant verification, and the E2EE behaviour at the destination is now the cleanest it has ever been. For copying historical mail across, the Check mail from other accounts POP3 import is the right complement. Combine the two for a complete migration. For fan-out to several Gmail destinations, route through a Google Group, never through duplicated filters.

The shortest version of the recommendation, after running every path on a live pair of Gmail accounts today:

1. Use the built-in forwarding setting for going-forward mail. It works, verification is fast, and E2EE rendering is native between two Gmail accounts.
2. Use POP3 import (Check mail from other accounts) for historical mail. Combine with the forward for a complete migration.
3. Forward through a Google Group when you need multiple destinations. Never duplicate filters — too brittle.
4. Recreate label structure at the destination via filters on X-Gm-Original-To. Labels do not cross the boundary natively.
5. Test with a known sender immediately after saving. Five-second test, saves hours of forensics later.

Best for: anyone consolidating personal Gmail accounts, anyone mirroring work-to-personal Gmail (where Workspace policy allows it), any small team fanning a shared Gmail to personal inboxes. Skip if: you need to forward to a non-Gmail destination — our Gmail auto-forward all emails guide covers the generic any-destination path with the friction points spelled out.

---

---

Sources & references

1. Google Workspace Help — Automatically forward Gmail messages to another account. Documents the step-by-step setup, the verification email flow, the four “what happens to Gmail’s copy” options and the rule that spam and chats are not forwarded. Accessed 2026-05-27. support.google.com/mail/answer/10957
2. Google Workspace Help — Check emails from other accounts. Documents the POP3 import path, the five-account limit, the Enable POP source-side requirement, the credentials and SSL settings, and the labelling of imported mail at the destination. Accessed 2026-05-27. support.google.com/mail/answer/21289
3. Google Workspace Updates — Gmail end-to-end encryption now available on mobile devices, dated 9 April 2026. The mobile E2EE rollout that makes Gmail-to-Gmail the cleanest E2EE forwarding topology. Accessed 2026-05-27. workspaceupdates.googleblog.com
4. Google Workspace Updates — Search faster and smarter with AI Overviews in Gmail search, dated 22 April 2026. Context for the 2026 Gmail surface area. Accessed 2026-05-27. workspaceupdates.googleblog.com
5. Email Tools — Gmail auto-forward all emails (generic any-destination guide). email-tools.me/posts/gmail-auto-forward-all-emails/
6. Email Tools — How to forward emails in Gmail (single message). email-tools.me/posts/how-to-forward-emails-in-gmail/
7. Email Tools — How to manage multiple email accounts. email-tools.me/posts/how-to-manage-multiple-email-accounts/
8. Email Tools — Gmail keyboard shortcuts list. email-tools.me/posts/gmail-keyboard-shortcuts-list/
9. Email Tools — How to recover from inbox overload. email-tools.me/posts/how-to-recover-from-inbox-overload/

---

Frequently asked questions

How do I forward one Gmail account to another Gmail account?

From the source Gmail on a desktop browser, open Settings, Forwarding and POP/IMAP, click Add a forwarding address, enter the destination Gmail address, click the verification link Google sends to that destination, return to the source Settings, refresh, then select Forward a copy of incoming mail to. Because both ends are Google-hosted, the verification email arrives within seconds and there is no DKIM or SPF friction. From the next new message onward, every non-spam email is forwarded.

Is forwarding between two Gmail accounts different from forwarding to a non-Gmail address?

The setup steps are identical, but Gmail-to-Gmail has three quiet advantages. Verification is near-instant because the destination is on the same infrastructure. The X-Gm-Original-To header is preserved end to end, so the destination keeps full routing context. And since the April 2026 mobile end-to-end encryption rollout, E2EE messages forwarded between two Google-hosted accounts render natively at the destination — no Workspace-link fallback like you sometimes see when the destination cannot decrypt.

Can I copy existing emails from one Gmail to another, not just future mail?

Yes, but it is a separate feature called Check mail from other accounts. In the destination Gmail, open Settings, Accounts and Import, click Add a mail account, enter the source Gmail address, supply credentials and let Gmail pull existing messages over POP3. You must first enable POP on the source account at Settings, Forwarding and POP/IMAP. The destination labels imported mail and can fetch up to five external accounts. This handles historical mail; combine it with a forward for going-forward parity.

What happens to labels and folders when I forward Gmail to another Gmail?

Forwarding moves the message body and headers only — labels do not cross the boundary because they are a per-account construct. The destination Gmail can re-apply labels through its own filters using the original sender, subject or the X-Gm-Original-To header. If preserving label structure matters more than going-forward delivery, use Google Takeout to export the source mailbox as an mbox file and re-import, or use the Workspace account migration tool if both accounts live in the same Workspace tenant.

How do I forward Gmail to multiple personal Gmail accounts at once?

The native forwarding setting accepts a single destination. To fan out to several personal Gmail accounts, create a Google Group with those Gmail addresses as members and forward to the Group address. Every group member receives a copy. The alternative — multiple filters with identical criteria pointing at different Gmail destinations — works for two or three addresses but is brittle the moment the filter criteria change.

Will end-to-end encrypted Gmail messages forward correctly between two Gmail accounts?

Yes, and Gmail-to-Gmail is the cleanest case. Since the April 2026 mobile E2EE rollout, end-to-end encrypted messages forwarded from one Google-hosted inbox to another decrypt natively at the destination, so the recipient sees the literal message content. The Workspace-link fallback only kicks in when the destination cannot decrypt — which does not happen between two Gmail accounts. For compliance setups that need a literal mirror of E2EE mail, Gmail-to-Gmail is the safest forwarding topology.

---

Related: Gmail auto-forward all emails — the generic any-destination forwarding guide when the target is not Gmail. How to forward emails in Gmail — single-message forwarding for one-off shares. How to manage multiple email accounts — the broader workflow when you are consolidating accounts.