Your emails on a computer are stored in a local database file that your mail app reads, not as loose messages in a folder; if the app shows nothing, the file is either missing, locked by another process, filtered from view, or the account is configured for server-only access. In most desktop clients, that single data store — a .pst, .ost, .eml tree, or Maildir — lives under your user profile, so the messages usually still exist on disk even when the interface is empty. Finding them means knowing which storage model your client uses and where that model puts bytes.
How mail clients store messages on disk
Every desktop mail client is a database front end wearing an inbox costume. When a message arrives, the client either writes it to a local container or leaves it on the server and caches only headers. That distinction determines whether "my emails" are physically on this computer at all. Microsoft Outlook historically split the two roles: a .pst file for POP and archive data, an .ost file for Exchange and Microsoft 365 cached mode. Apple Mail uses an .emlx format — one file per message with a metadata plist — organized inside ~/Library/Mail. Thunderbird keeps a Maildir or mbox store under the profile directory, with an msf index file per folder. Windows Mail and newer Outlook for Windows moved toward a synchronized local cache with far less user-visible structure.
The mechanism matters because each client maintains two parallel records: the message body and an index that maps it to a folder view. The index can corrupt or rebuild while the bodies remain intact. That is why a search that returns zero results can coexist with a profile folder holding gigabytes of message data. Think of it as a library where the card catalog burned but the books are still on the shelves.
Local storage is also tiered. Cached mode keeps a sliding window of recent mail locally and pulls older items on demand. A 12-month cache setting on a large mailbox means the client may hold only a fraction of the total corpus. Set the cache slider to three months in a busy account and you can lose local access to thousands of messages without deleting anything. The mail is on the server; the computer simply was never told to keep it.
How much mail actually lives on a typical machine
A moderately used mailbox is larger than most people assume. A single plain-text email runs 5-50 KB; one with signatures, tracking pixels, and a small attachment runs 100 KB-1 MB. A 10 GB mailbox at 200 KB average per message holds roughly 50,000 messages. Outlook warns and eventually blocks when a .pst approaches its configured limit, historically 50 GB by default in recent builds, and a 2 GB ceiling applied to older ANSI-format files. Percentage-based warnings typically fire at 80% and 95% of whatever limit your organization sets.
Cache windows are the hidden multiplier. If your client caches one year and receives 150 messages a day, that local store grows by about 55,000 messages a year before attachments. A 5 GB cache cap with heavy attachments fills in months, not years. When the cap is hit, clients start evicting older cached items to make room, which looks like mail vanishing but is actually a rotation policy. On a laptop with a nearly full drive, the client may refuse to grow the cache at all and quietly serve everything from the server.
Search indexes add their own footprint. Windows Search, Spotlight, and client-native indexers typically consume 10-30% of the mail store size. A 60 GB Outlook profile can push a search index past 15 GB. When indexing is disabled or stalled, content search fails while folder browsing still works — a split-brain symptom that sends people hunting for deleted files that were never deleted.
Edge cases that mimic data loss
The most common false alarm is a view filter. Clients remember the last search or filter state per folder. An unread filter, a date range, a category filter, or a conversation-grouping toggle can hide 100% of messages in a folder that is fully populated. Clear all filters and the mail reappears instantly.
Account type is the second trap. An IMAP account with server-side folders shows only what the server exposes. If a rule on the server moved messages to a folder your client does not subscribe to, the inbox looks empty. POP accounts can be worse: a client configured to leave copies on the server versus remove them changes whether messages exist in one place or two. Windows Mail to Outlook migration and similar app transitions have repeatedly left users with two partial stores rather than one complete one.
Profile and permission problems rank third. A Windows user profile that failed to load properly can open the client against a fresh, empty profile directory, presenting a blank inbox while the old .ost sits untouched under a different SID folder. Fast Startup and hibernation can also leave the mail store file locked by a zombie process, so the client opens read-only or spawns a new empty store. Antivirus scanning that locks the .pst during a scheduled scan produces a "cannot open" or empty-folder state that resolves when the scan finishes.
Counterintuitive detail: deleting a message in a cached-mode client often deletes nothing on disk immediately. The message is moved to a Deleted Items tombstone and its space is reclaimed lazily during compaction. Between deletion and compaction, the original bytes may still be recoverable from the store file — but only until the client rewrites or compacts it, which can happen automatically within hours.
What people get wrong about missing mail
The biggest misconception is that a blank inbox means deleted mail. Deletion requires an affirmative action: emptying Deleted Items, running a destructive rule, or a server-side retention policy. A retention policy that permanently removes items older than 30 or 90 days is the most common silent cause of genuinely missing old mail. Organizations set these and users rarely notice until they search for a two-year-old thread.
The second misconception is that local search equals mailbox search. Local search only covers the local cache and index. If the cache window is 12 months, searches for older mail fail locally even though the server has everything. Searching from webmail or enabling server-side search in the client closes the gap. This discrepancy explains most "it's on my phone but not my computer" reports: phones often retain a different cache window than desktops.
The third is that file paths are stable. Outlook .ost files live under %LocalAppData%\Microsoft\Outlook and are tied to the account and profile. Recreating the Outlook profile generates a new file name and abandons the old one. Apple Mail's versioned library folders (~/Library/Mail/V10 and similar) change with OS upgrades, so a restored backup may place mail under a prior version directory the current app will not scan by default.
A professional caveat worth stating plainly: you should never hand-edit, move, or copy a live mail database file while the client is running. Doing so is the leading cause of genuine corruption and turns recoverable mail into an unreadable file. Close the client, confirm the process has exited in Task Manager or Activity Monitor, then copy the file to a safe location before touching anything.
Red flags to check before you panic
The client shows "Disconnected," "Working Offline," or a sync error banner; this is a connection state, not data loss. Your drive shows under 5% free space; clients throttle or stop caching when storage runs low. A rule, retention policy, or archive job ran in the last 24 hours and can move or delete large volumes quickly. You changed account type, migrated apps, or recreated the profile in the last two weeks. Multiple antivirus or backup tools are scanning the mail store folder; locked files present as empty mailboxes.
Side-by-side storage models and what they mean for finding mail
| Client / model | Typical on-disk location | Format | What a blank inbox usually means |
|---|---|---|---|
| Outlook (cached Exchange/M365) | %LocalAppData%\Microsoft\Outlook | .ost | Cache window or profile mismatch; server still has mail |
| Outlook (POP/archive) | User-chosen path, often Documents | .pst | File moved, locked, or opened read-only |
| Apple Mail | ~/Library/Mail/V# | .emlx per message | Versioned folder mismatch or index rebuild |
| Thunderbird | Profile folder (AppData or Application Support) | Maildir or mbox plus .msf index | Index corruption; bodies usually intact |
| Windows Mail / new Outlook | App-managed cache, not user-visible | Proprietary cache | Sync state or account subscription issue |
| Webmail in browser | Browser cache only | None persistent | Nothing is local; search the server |
Timeline of what happens to a message on disk
| Stage | Typical time | What changes on disk |
|---|---|---|
| Arrival and cache write | Seconds | Message body written to store; index entry created |
| Local indexing | Seconds to minutes | Search index updated; content becomes findable |
| Cache eviction (if over cap) | Ongoing | Oldest cached items removed; server copy remains |
| Delete action | Immediate | Item flagged deleted; moved to Deleted Items tombstone |
| Empty Deleted Items / retention expiry | 0-90 days depending on policy | Item marked for permanent removal |
| Store compaction | Hours to days, often automatic | Space reclaimed; deleted bytes may become unrecoverable |
| Backup snapshot | Nightly or weekly, per your schedule | Point-in-time copy captures whatever state existed |
Reconciling thresholds explicitly: the 30- and 90-day retention figures refer to server-side policy, measured from deletion, not from arrival. The 12-month cache window refers to local-only copies, measured from the newest message backward. The 80% and 95% warnings refer to store size against a configured cap, not to mailbox age. These are three independent clocks, and a message can be absent locally while fully present on the server, or present locally while already purged from the server. Confusing them produces most diagnostic dead ends.
Practical steps to locate your emails
Search the server first. Open the account in webmail and search there. If messages appear, the data exists and the problem is local cache, sync, or filters. This single step resolves the majority of cases. Clear all filters and search state in the desktop client, then toggle conversation view off. Verify the correct account and folder set are selected. Check account type and cache settings. Raise the local cache window and confirm the account is not set to headers-only or manual sync. Locate the store file. In Outlook, File > Account Settings > Data Files shows exact paths. For Apple Mail, hold Option and click Go > Library in Finder. Record file size and modification date — a recently modified multi-gigabyte file means data is present. Close the client fully, verify the process has ended, and copy the store file to an external drive before any repair attempt. Then use the client's built-in repair or rebuild tools, which are safe on a copy. Restore from backup if needed. Confirm the backup predates the loss and restore to a separate location first, never over the live store. Before moving or deleting anything permanently, set a 30-day pause and export a copy of critical folders to .eml or .mbox files, which are plain and portable.
If mail is genuinely gone from both server and local store, recovery depends on backups and on whether compaction has overwritten the bytes. Stop writing to that drive, and hand the file to professional recovery tools rather than consumer utilities that promise guaranteed restoration.
Limits of what this diagnosis can tell you
No guide can identify a specific missing message without examining your account settings, store files, and server logs. Client behavior also varies by version, organization policy, and platform, and vendors change defaults between releases. The mechanisms above are stable, but exact menu paths and file locations shift. If your organization manages the account, your IT administrator can query server-side retention, litigation hold, and audit logs that no local inspection can replicate. For email that carries legal, financial, or medical weight, treat any local recovery attempt as potentially destructive to evidence and consult your administrator or a qualified data-recovery professional before proceeding.
This article is general educational information about how mail clients store data; it is not a diagnosis of your specific system, a data-recovery service, or a guarantee that any message can be restored. It does not promise recovery outcomes. For accounts holding legal, financial, or regulated records, consult your IT administrator or a qualified data-recovery professional before modifying any mail store.