How to Save Emails to Google Drive as .EML Files (2026)

Saving selected emails to Google Drive is useful when you want the original message file outside the mailbox. Mailsink gives a Drive folder its own forwarding address and saves each received message as an .eml file.

This guide explains the exact workflow and its limits. It is not a compliance archive, legal-hold system, or historical mailbox migration.

What the Google Drive destination saves

For each message sent to the Mailsink inbox, the Drive destination uploads the original RFC 822 email as a file with the .eml extension. That format keeps the message's MIME structure, including its headers, body parts, and encoded attachments.

The file is stored in the Google Drive folder created for that inbox. The generated filename uses the message date and subject so files are easier to recognize.

An .eml file is not the same as saving each attachment as a separate Drive document. Download and open the message with a compatible mail client when you need to inspect its complete contents.

When Google Drive is the right destination

Choose Drive when you want:

• selected original messages stored as portable files;
• a folder of invoices, contracts, or project correspondence for reference;
• message files that can be downloaded and opened outside Mailsink;
• a simple handoff folder for a narrow workflow.

Choose Google Sheets when you need one structured row per email. Choose Notion or Airtable when people need to assign, categorize, or work with each message as a record.

Do not describe a Drive folder as a regulated archive without independently validating retention, access controls, deletion behavior, monitoring, and the rules that apply to your organization.

Step 1: connect your Google account

1. Create a Mailsink account.
2. Open Connections and connect Google.
3. Review Google's authorization screen and allow the access required to create and write to the destination folder.
4. Return to Mailsink after authorization.

Use the Google account that should own the folder. Google Workspace administrators can restrict third-party app access, so organization approval may be required.

Step 2: create a Google Drive inbox

1. Open Inboxes and choose Create.
2. Select Custom Setup as the workflow.
3. Select Google Drive as the destination.
4. Choose the connected Google account.
5. Optionally name the folder, then create the inbox.
6. Copy the private address ending in @in.mailsink.app.

Mailsink creates a new folder for the inbox and provides a link to it. Treat the forwarding address as an ingestion endpoint: anyone able to send to it may create a file in the folder.

Step 3: test one message

Manually forward a safe, representative email to the generated address. Include an attachment only if attachments matter to the workflow.

Open the Drive folder and verify:

• one .eml file appeared;
• the filename is recognizable;
• the file downloads successfully;
• a compatible mail client opens the message;
• the body, headers, and test attachment are present;
• the folder's sharing permissions are appropriate.

Keep the source message until you have validated the result. If no file appears, inspect the Mailsink activity state, Google connection, folder availability, and account limits.

Step 4: choose manual or automatic routing

Manual forwarding is often appropriate for contracts, important receipts, or other messages selected by a person. Use BCC when your provider and policy permit a copy to be sent during normal correspondence.

For automatic capture, begin with a narrow sender, recipient, or subject rule.

Gmail

Google sends a verification message to a new forwarding address before automatic forwarding can start. The current Mailsink beta does not reliably surface that message in-app, so manual forwarding or BCC is the dependable starting path.

If you can complete verification, use Google's current forwarding instructions and test the exact filter before expanding it.

Outlook and Microsoft 365

Some Microsoft 365 organizations block automatic external forwarding. An administrator controls that policy, and blocked attempts may return 5.7.520. Use an approved rule, manual forwarding, or BCC rather than trying to work around the tenant policy.

See Microsoft's external forwarding policy.

Useful Drive workflows

Contract correspondence

Save selected messages associated with a signed agreement or negotiation. The .eml retains the original message structure, but your legal retention process still needs separate ownership and controls.

Invoice and receipt files

Route invoices or receipts into a dedicated folder and verify that the .eml opens with the expected attachment. If the team needs vendor, amount, due date, and review status as fields, use the receipt and invoice workflow instead.

Client or project handoff

Create a folder for a narrow set of important communications. Use Google Drive permissions to limit access, and avoid mixing unrelated clients in one inbox.

Messages for downstream processing

An .eml file can be consumed by tools that understand RFC 822 email. Validate the downstream parser with representative HTML messages, attachments, and unusual encodings before depending on it.

How to open an .eml file

Drive stores the file, but the most reliable viewing path is to download it and use an email client that supports .eml, such as Outlook, Apple Mail, or Thunderbird. Viewer behavior varies by browser, device, and installed applications.

Do not upload sensitive messages to an unknown online conversion service merely to view or convert them.

Keep the folder reliable

• Use one inbox for one folder purpose.
• Restrict the Drive folder to the people who need it.
• Test representative attachments instead of assuming every file behaves identically.
• Monitor failed messages and expired Google authorization.
• Document who can delete files and how long they should remain.
• Keep a separate retention or backup strategy when the workflow is business-critical.

Common questions

Does Mailsink save attachments as separate Drive files?

No. The Drive destination saves the original email as one .eml file. Attachments remain encoded inside the message.

Can I use an existing Drive folder?

The current setup creates a new folder for the inbox. You can name it during creation and manage its sharing permissions in Drive.

Can multiple senders use the same folder?

Yes, when they send or forward to the same Mailsink address. Separate sensitive clients or unrelated workflows into different inboxes and folders.

Is this a backup or compliance archive?

It can create an additional copy of selected new messages, but Mailsink does not claim the controls required for backup, legal hold, or regulatory compliance. Validate those requirements separately.

Start with one file

Forward one message, open the resulting .eml, and check the folder permissions. Only then decide whether a provider rule is worth adding.

Create a Google Drive inbox →

If you need fields and filters instead of original message files, use the email-to-Google-Sheets guide.

Last updated: September 1, 2026