An email backup is an independent copy of mailbox contents held apart from the live provider account, and it remains usable even when that account changes. The copy stays readable after deletion, locking, or hacking of the account. Gmail, Outlook, and Apple Mail each offer a separate export route, and each route produces a file that can be stored separately from the live account. The exported copy becomes a backup only in a second location, after a test confirms that it opens. Exporting leaves the live mailbox intact. The backup therefore adds to the account, and it does not replace the account itself.
Provider sync and email backup
Sync and backup perform different jobs. Sync holds an identical mailbox state on a phone, a computer, and a webmail page. A deletion on one device then vanishes from the other synced copies. A locked or deleted account also removes access to the server copy, because the mailbox on the server is no longer reachable from any synced device. A backup severs that connection. The exported file remains readable after a change to the live account. The 3-2-1 backup rule gives the pattern in plain terms: three copies, two storage types, and one copy offsite. The same point appears in the offline backup analysis and in the 321 backup strategy overview, both of which treat a disconnected copy as the protection against a failure that affects the live account.
Sync mirrors the live account, while a backup is a separate copy stored outside that account.
Google states that a recently deleted Google Account may still be recoverable. Successful recovery restores access to the account and its data. Older deletions may not be recoverable. The same Google recovery page states a further limit. Google reserves the right to delete an inactive Google Account and its data after at least two years of inactivity across Google. A secondary deleted Gmail recovery guide repeats the warning that recovery is not guaranteed. It gives no fixed window. The conclusion stays narrow. An export made before loss is the only copy under the account holder's control.
Gmail export through Google Takeout
Gmail backup begins at Google Takeout, the export tool for Google Account data. The documented flow picks Mail from the product list. Other products stay deselected for a mail-only export. Google then delivers the created export as a download link by email. Secondary guides describe the same steps. They deselect all products, select Mail, and use the Mail options for all messages or selected labels. They then choose a delivery method and file type, and create the export. See the Gmail to MBOX export guide, the Gmail export before deletion guide, the Google Takeout step guide, and the Gmail MBOX export guide.
The export holds mail in MBOX format. User settings sit in JSON, according to the same guides. Export timing shifts with mailbox size. Secondary guides report minutes for small accounts. They report hours or days for large accounts, with the wait growing as the mailbox grows. No fixed delivery time appears in the sources for this piece. The archive downloads in full, including every split part. Storage uses a dated folder name such as gmail-backup-2026-10-24, which keeps each export identifiable by the date it was created, and which separates that export from later exports in the same archive. Takeout produces files to keep and open. It does not provide a button that puts mail back into the account.
Outlook export through desktop Outlook
Outlook backup uses desktop Outlook. Outlook on the web does not provide this route. Microsoft states that an Outlook.com mailbox can move to a .pst file through new Outlook for Windows or classic Outlook for Windows. Legacy Outlook for Mac produces a .olm file instead. The completed file holds a copy of email, contacts, and calendar up to the creation date. See the Microsoft Outlook.com export page. The same page states that desktop Outlook is required. Classic Outlook for Windows can export in Reduced Functionality Mode. That mode needs no Microsoft 365 subscription or free trial.
For classic Outlook, Microsoft lists a menu sequence. The sequence runs File, Open and Export, Import/Export, Export to a file, then Outlook Data File (.pst). The final steps select the email address, choose a save folder, and select Finish. See the Microsoft Outlook backup page. A secondary guide notes a gap in new Outlook. New Outlook lacks the classic path. Some Microsoft 365 and Outlook.com accounts show a server-side export option under Settings. Availability varies by account type. See the Outlook PST and CSV export guide. A second secondary guide sets the new Outlook export flow beside the classic wizard. See the Outlook mailbox export guide.
Two limits apply to PST export. First, the classic wizard flow covers one account at a time. Folder properties, rules, and blocked sender lists fall outside the exported mail data in secondary guides. Second, an organisation account may block local PST creation by policy. The account administrator or IT team then holds the approved export route, and that route is the one to use when local PST creation is blocked. The PST file moves to a second location after creation. A PST file left only in the same Documents folder as the live Outlook profile is not an offsite copy.
Apple Mail export and Time Machine
Apple Mail backup uses the mailbox export function in the Mail app on a Mac. Apple states Mail exports mailboxes in mbox format. The steps select one or more mailboxes and choose Mailbox, Export Mailbox. Mail then exports the mailboxes as .mbox packages. See the Apple Mail import and export page. The same page states a rule for repeat exports. A repeat export does not overwrite an earlier export. It creates a new .mbox file, such as My Mailbox 3.mbox. Dated repeat exports therefore stay safe from accidental overwrite, because each new export is a separate file rather than a replacement for the previous one. Import runs in the other direction through File, Import Mailboxes. Imported messages land in a mailbox called Import.
Mailboxes under On My Mac exist only on that Mac. Mail moved to a local mailbox leaves the server. The Mac itself then becomes the only copy, unless an export or a system backup exists. Secondary guides repeat the same warning. They recommend Time Machine or an export for On My Mac mail. See the Mac Mail archiving guide, the Apple Mail external drive backup guide, the Mac email archiving guide, and the Mac Mail archive guide.
Time Machine covers the whole Mac, including local mail, on an automatic schedule. Apple states that Time Machine makes hourly backups for the past 24 hours. It makes daily backups for the past month. It makes weekly backups for all previous months. The oldest backups disappear when the backup disk fills. See the Apple Time Machine page. The same page recommends a backup disk with at least twice the storage capacity of the Mac. It states that an encrypted backup requires a backup password for later restore. Time Machine is a system backup, not a mail-only export. A mailbox export is the portable copy that can move to another mail client, because the exported file is separate from the system backup. Time Machine is the recovery copy for the whole Mac.
Local mail clients and Thunderbird
A local mail client adds a second route to the same goal. Mail synced by IMAP to a desktop client can leave through that client. This route works even when the provider web interface offers no full export, because the desktop client already holds a synced copy of the mailbox. Thunderbird keeps mail on the local machine inside a profile folder. That profile copy covers the whole client. Folder export covers single folders as portable files. The two routes therefore serve different restore needs, since a whole-client copy and a single-folder file are not interchangeable. See the Thunderbird backup guide. The ImportExportTools NG add-on exports folders as MBOX. It exports messages as EML and other formats, depending on the export option chosen in the add-on. It also imports MBOX files back into Thunderbird. See the ImportExportTools NG guide and the Thunderbird MBOX export guide.
Profile copies and folder exports serve different restore cases. A profile copy restores the client setup, accounts, and folders together on a replacement machine. That restore depends on the client version reading the profile, because a profile created in one version may not open cleanly in a different version. A folder export in MBOX or EML form moves messages between clients. It loses client-specific settings in the process. Either route requires the client to finish syncing first, before the copy is taken.
Backup formats
The format decides where the backup can open later. The table below states that choice.
| Format | Produced by | Opens in | Limit |
|---|---|---|---|
| MBOX | Google Takeout, Apple Mail, Thunderbird | Apple Mail, Thunderbird, MBOX readers | Outlook on Windows needs conversion |
| PST | Outlook for Windows | Outlook for Windows | Does not open directly in Apple Mail |
| OLM | Outlook for Mac, legacy | Outlook for Mac | Not a Windows PST file |
| EML | Single message save, Thunderbird export | Most mail clients | One file per message, no folder structure on its own |
| Single message export | Any PDF reader | Search and import are weaker than a mailbox file |
Backup storage
Storage follows the same rule as the format choice. One copy is not a backup. A workable routine starts with a dated export on an external drive. The drive disconnects after the copy. A second copy sits in a different location. That location can be a second drive kept elsewhere. It can also be an encrypted cloud folder on an account separate from the mail account. Cloud sync alone does not meet the test. A sync service mirrors deletions and changes to every device.
File names carry the date and the account label in plain form. Examples include gmail-2026-10-24, outlook-2026-10-24, and apple-mail-2026-10-24. An older export is therefore never mistaken for a current one. Large exports split by the export tool size setting. They do not split by manual partial downloads. No part is missed as a result.
Encryption and access control
A mail backup holds the same sensitive material as the mailbox. That material includes private correspondence, attachments, password reset messages, and financial statements. An unencrypted backup on a portable drive gives full access to anyone holding the drive. Encryption of the backup drive or the archive itself removes that access, because the contents stay unreadable without the password or key that unlocks them. It adds a cost. The password or key must survive separately from the backup. Apple states the same trade-off for Time Machine. An encrypted backup asks for a backup password needed for later restore.
The password or recovery key sits in a password manager or written record kept apart from the backup drive. It does not sit in a text file on the same drive. A backup that cannot be unlocked is not a backup, because the archive cannot be opened for a restore without the password or key. The same rule applies to cloud copies. The cloud account needs its own strong password and two-step sign-in. That sign-in stays separate from the mail account password where possible.
Email aliases and email backups
Aliases and backups protect different assets. An alias is a separate forwarding address given to a website instead of the real inbox address. A leak of that website database then exposes the alias rather than the real address. The alias can pause or disable after the leak. AliasFleet provides aliases as managed, persistent identities, with one alias per website and forwarding to a chosen inbox, and that forwarding arrangement is the mechanism described in this section. AliasFleet is not a disposable email service. The alias mechanism does not store or restore a mailbox history. An alias that is disabled stops future mail to that address. Past messages already in the inbox still need their own backup.
The combined setup is two separate controls, one for the addresses websites hold and one for the message history outside the provider. Aliases limit which address each website holds. That limit reduces the spread of the real address after a breach. Exports limit the loss when an account is locked, hacked, or deleted. The message history then exists outside the provider. A check of breach exposure on Have I Been Pwned still leaves the same two questions. The first question is which address was exposed. The second question is whether the messages tied to that address exist anywhere else. The alias answers the first question. The backup answers the second.
Restore testing and backup schedule
A backup test runs before the backup is needed. It does not run during an account crisis. The test imports a copy of the export into a separate test folder. It opens sample messages across the date range. It opens an attachment. A test that only checks file size or folder presence does not confirm readability. A truncated archive can report a plausible size while containing broken messages. When the test import succeeds, the test folder can be deleted. The archive stays as the verified copy.
A schedule keeps the backup current without daily manual work. A monthly full export suits most personal accounts. A local client copy or a Time Machine schedule fills the gap between exports for Mac users. Accounts with daily critical mail need a shorter cycle and a dated archive per cycle. A single corrupted export then never becomes the only copy. Old exports stay until the next two exports have passed a restore test, so a new export is verified before the older copies are removed. They are then deleted to limit the amount of sensitive mail stored on portable media.
Top comments (0)