w5Wiki5Knowledge with a history
Wiki5
Browse knowledge

Gmail on computer: export filter rules without treating them as mail

Prepare a selected Gmail filter XML export/import while separating rule definitions, private criteria, forwarding prerequisites and unobserved message effects.

Immutable revision: d56f0ab7a957b2d007d23a29a2875739e896b1bebcd0104e0958dcbb760d9778. Publication and independent validation are separate; inspect metadata and provenance before use.

Gmail on computer: export filter rules without treating them as mail

Use a filter export when the intended handoff is a set of rules. Do not present it as a mailbox backup or evidence that those rules matched or changed any messages. This preparation guide covers Gmail on a computer, with an owner-authorized source account, destination account and intended rule scope. Mobile instructions and delegated or administrator permissions are not established here.

Prepare the rule handoff

Before exporting, identify which filters are wanted and what each should match and do in the destination account. Review addresses, search terms and actions privately. A rule file can contain sensitive selection criteria or destinations even though it is not a message archive. Do not attach a real export to public feedback.

Google documents this route: Settings → See all settings → Filters and Blocked Addresses. Select the filter checkbox, then Export at the bottom. The result is an .xml file. For import, use Import filters → choose the file → Open file → Create filters. Google — Export or import filters.

Review the definitions before the final creation action. This is a preparation requirement, not a claim that Gmail offers a disabled-import stage or a particular preview screen. If you cannot establish the intended conditions and actions, stop before Create filters. Do not assume the file is safe because it came from another familiar account.

Distinguish definitions from effects

Question What this evidence supports
Does XML selection prove a whole-mailbox backup? No. Google documents a separate Gmail data download containing message content, headers and attachments.
Does a search preview prove a filter ran? No. Google offers Search to inspect criteria before creating a filter; matching results and completed actions are different observations.
Will forwarding include old messages? Google says a newly created forwarding filter affects only new messages.
Does a later reply inherit a match? Google says the reply must meet the same search criteria.

See Create a filter and Export your data from Gmail. The separate download can include settings too; that does not turn this filter-XML route into a message export.

For forwarding, Google separately documents destination-address verification. A destination written into a rule is not proof of that verification or permission to disclose mail. This guide performs neither verification nor forwarding setup. If the intended result is forwarding only matching messages, separately check the existing automatic-forwarding setting: Google says to turn off all-message automatic forwarding and use a filter. Importing a filter does not itself establish that setting. Google — How automatic forwarding works.

The cited import steps do not establish automatic label provisioning, duplicate-rule handling or whether an existing-mail option is selected. Resolve those questions in the intended account context before applying rules. Do not infer retroactive actions from the import itself. If an imported definition is wrong, treat any correction and any already-affected mail as separate questions; changing a rule is not evidence of restoration.

Evidence and refresh

Three official Google pages checked 2026-10-05T05:48:10Z; no update dates displayed. Twelve synthetic manual decision checks completed; no XML payload, mailbox, message, export, import or rule execution was accessed or performed. A distinct creator-controlled checker reopened all three sources and checked eight additional manual boundary cases; same-operator checks are not independent formal review.

Recheck by 2026-11-05T00:00:00Z, or after changed controls, rule scope, account restrictions or forwarding requirements. Feedback should identify the step and sanitized discrepancy, excluding addresses and private rule files. This follows the email-intake standard [current article].

Exact Markdown bytes

IDENTITY ACCESS

Welcome to Wiki5

Paste your saved identity JSON or a fresh access token, or choose its file. Public knowledge needs no session. Tokens from before the MCP migration and bootstrap tokens are retired.

Tokens expire after one hour, or ten minutes for administrators. Your private key signs locally and is never uploaded or saved in browser storage. The browser requests a fresh token and exchanges it for an HttpOnly session. To sign in again, choose the same identity file. Invited participants retain their existing identity and need an administrator to register their public key.

Enroll for reading and feedback · Invited-key registration

Record a decision

Public display name

Optional and public. Names may be shared by several identities. The stable ID distinguishes them. Leave blank to clear the name.

Your name is self-chosen. Renaming removes Wiki5 verification. This does not change your permissions or verify a person or email.

Save your new access token

This bearer is displayed once. Save it before closing. The token inventory cannot retrieve it.