Exchange EDB file too big even after users delete mail? Freed space stays inside the .edb as white space, so Windows still shows the full file size.
Check white space first, then create a new database, move all mailboxes into it and delete the old one. Offline defrag with eseutil /d is the other option. Both need free disk space.
Users deleted years of mail last month and your .edb file stayed the same size. Nothing is broken. Exchange reuses freed space for new mail instead of returning it to Windows.
Exchange EDB file too big comes down to white space or real mail. Below you measure free space, check your edition limit and choose between a mailbox move and an offline defrag.
Why will Deleted Mail Not Shrink an Exchange EDB File?
Deleted mail leaves free space inside your .edb file. Exchange reuses that space for new mail and does not return it to Windows.
Microsoft calls this free space white space. In Exchange 2010, Understanding Database Maintenance states that database compaction does not return unused space to the file system.
For Exchange 2010, Understanding Mailbox Database and Log Capacity Factors gives a sizing example. Take 100 mailboxes of 2 GB (200 GB in total) with 10 MB of mail per mailbox per day. White space then sits near 1 GB and grows past that figure when background maintenance cannot finish a full pass.
Four things keep a database large.
- Deleted items wait 14 days by default in Recoverable Items before Exchange removes them, per Set-MailboxDatabase.
- Disconnected mailboxes stay 30 days by default before Exchange purges them, per Disconnected mailboxes in Exchange Server.
- Former staff mailboxes stay until you remove them.
- Oversized mailboxes and archives use big blocks of space.
Recover Deleted Emails in Exchange Server explains how retention stages work.
How do You Check White Space in an Exchange Database?
Use Get-MailboxDatabase with the Status switch to see database size and free space inside it.
Get-MailboxDatabase -Status | Format-List Name,DatabaseSize,AvailableNewMailboxSpace
Get-MailboxDatabase lists Status for Exchange 2010 to SE. Microsoft's Q&A answer in Exchange database edb size says AvailableNewMailboxSpace is sometimes called white space.
When AvailableNewMailboxSpace is small next to DatabaseSize, mail fills your file and you need more disk or fewer mailboxes. When it is large, you can reclaim that space.
In Exchange 2007, How to Run Eseutil /D (Defragmentation) points to application event ID 1221 for free space inside a database file after online defragmentation.
What are the Exchange Database Size Limits by Edition and Version?
Exchange EDB file too big on Standard Edition can mean you hit the default 1,024 GB limit in Exchange 2010 to 2019. Enterprise Edition sets no default limit. Exchange 2007 Standard Edition RTM defaults to 50 GB.
| Exchange version | Standard Edition default | Enterprise Edition default | Best practice size |
|---|---|---|---|
| 2007 RTM | 50 GB | No default limit | 100 GB without continuous replication and 200 GB with it |
| 2010 | 1,024 GB | No default limit | 2 TB with several database copies |
| 2013, 2016 and 2019 | 1,024 GB | No default limit | 200 GB or less without high availability and 2 TB or less with it |
Limits for Exchange 2007 come from How to Modify a Database Size Limit. Exchange 2010 limits come from The current physical size of the database file is close to the maximum database size. Limits for Exchange 2013 to 2019 come from Exchange Server 2013, 2016 and 2019 Standard Edition can't mount databases that are larger than 1024 GB.
Best practice sizes come from Recommendations for Configuring Storage Groups and Databases for Exchange 2007 and Understanding Mailbox Database and Log Capacity Factors for Exchange 2010. Exchange 2013 storage configuration options covers Exchange 2013 and Exchange Server storage configuration options covers Exchange 2016 to SE.
Microsoft lists about 16 TB as supported database size in Exchange 2013 to SE. Plan for 120 percent of your calculated maximum size.
Exchange checks size limits periodically and dismounts a database that reaches its limit. Failover then fails too.
Microsoft's workaround raises the limit with a registry value named Database Size Limit in GB. Microsoft warns that a cumulative update can delete that key and names Enterprise Edition as the resolution.
Standard Edition servers cap you at five mounted databases from Exchange 2016 onward, as Exchange Server editions and versions lists. Count your databases before you add one. Exchange 2003 limits sit in Exchange 2003 priv1.edb.
How do You Shrink Exchange Database Files?
Exchange EDB file too big has two fixes. Move all mailboxes into a new database and delete the old one. Offline defrag is the other fix, with the database dismounted.
| Method | Downtime | Space needed | Result |
|---|---|---|---|
| Move all mailboxes into a new database | Users keep access unless you add ForceOffline | Disk for the new database | New file without the old white space |
| Offline defrag with eseutil /d | Database dismounted, users lose access | Spare drive space of 110 percent of the shrunken file | Smaller file that tends to grow back |
| Export and remove old mailboxes first | None | Room for PST files | Fewer mailboxes to move or defrag |
Microsoft's Exchange 2010 advice for a database with significant white space has three steps. Create a new database with its copies, move all mailboxes there and delete the original database with its copies.
Moving only some mailboxes does not shrink your old file. Exchange database edb size says a partial move only creates white space.
Keep a copy of your old .edb until users confirm their mail. Univik Software opens that copy offline if a mailbox looks incomplete.
“Moving mailboxes to a fresh database beats an offline defrag almost every time. Users keep working and you get a clean file at the end.”
How does an Exchange Offline Defrag Work?
Exchange offline defrag copies a dismounted database into a new file, so users lose access until it ends.
Dismount the database first. Microsoft's Exchange 2007 procedure in How to Run Eseutil /D (Defragmentation) sets the free space target at 110 percent of the finished database file.
eseutil /d "E:\Mailbox\Sales01\Sales01.edb" /t "G:\Scratch\Sales01-temp.edb"
Add /t to place the temporary database on another drive. Microsoft advises against a network drive, because a network error ends the defrag and you must start over.
By default the temporary database replaces the original file. Add /p to keep the original, which needs space for two more database copies. Back up your database before you start.
Under normal conditions an offline defrag does not permanently recover significant disk space, warns Eseutil /D Defragmentation Mode. Files tend to grow back to their earlier size.
Eseutil Commands Reference lists the eseutil switches. If an offline defrag stops with error -1605, Eseutil Illegal Duplicate Key explains the code.
Which Mailboxes should You Archive Before Shrinking?
Archive mailboxes for staff who left, closed projects and old test accounts first. Removing a mailbox means one fewer to move or defrag.
Exchange EDB Converter from Univik exports from a database copy. Export happens on a Windows PC from the copied .edb, so your Exchange server handles no extra work and users notice nothing.

Univik Software names PST files after original mailboxes and splits them above a size you choose. Split size defaults to 50 GB. Step by step export instructions sit in How to Convert EDB to PST.
Disconnected mailboxes need a separate export, covered in Export a Disconnected Mailbox to PST. Single mailboxes in a mounted database export through PowerShell, as New-MailboxExportRequest Guide shows.
- Exchange EDB file too big means free space inside the file, not extra mail.
- AvailableNewMailboxSpace shows how much space you can reclaim.
- Standard Edition stops at 1,024 GB per database from Exchange 2010 on and at 50 GB in Exchange 2007 RTM.
- Microsoft's Exchange 2010 advice is a new database and a move of all mailboxes. Offline defrag needs a dismount and 110 percent free space.
- Archive old mailboxes and remove them before a move or defrag.
Export leavers and closed projects from a database copy to PST with Univik Software. Trial edition saves 10 messages per folder. Licences start at $99 for 2 PCs.
Free Download See all featuresQuestions About Large Exchange Databases
Why is my Exchange EDB file too big after I delete mail?
Deleted mail becomes white space inside the file. Exchange reuses that space for new mail instead of returning it to Windows.
Does deleting mail make the EDB file smaller?
No. Freed space stays inside your file as white space. Space comes back only after all mailboxes move to a new database or you defrag offline.
Does moving some mailboxes shrink the old database?
No. Exchange database edb size says a partial move only creates white space. Move all mailboxes and delete the old database to get the space back.
What happens to the space after an offline defrag?
In Exchange 2007, Eseutil /D Defragmentation Mode says an offline defrag does not permanently recover significant disk space under normal conditions. Files tend to grow back. For a database with significant white space, Microsoft's Exchange 2010 advice is a new database and a move of all mailboxes.
Will removing log files shrink the database?
No. Log files sit outside the .edb, so deleting them leaves the file at the same size. In Exchange 2013, Microsoft says a successful full or incremental backup truncates logs that recovery no longer needs, per Backup, restore, and disaster recovery.
What is the maximum size of an Exchange database?
Microsoft puts supported database size at about 16 TB from Exchange 2016 to SE, per Exchange Server storage configuration options. Standard Edition stops at 1,024 GB by default and Enterprise Edition has no default limit.
Can I raise the 1,024 GB limit on Standard Edition?
Yes, with a workaround. For Exchange 2013 to 2019, Microsoft lists the registry value Database Size Limit in GB but says a cumulative update can delete it. Enterprise Edition has no default limit, per Exchange Server 2013, 2016 and 2019 Standard Edition can't mount databases that are larger than 1024 GB.
Can users keep working during a mailbox move?
Yes. New-MoveRequest starts an asynchronous move and describes ForceOffline as the switch that blocks user access, so skip that switch.
Can Univik Software open my old .edb after the move?
Yes. Univik Software opens the dismounted .edb copy you moved off the full volume without Exchange Server and supports Windows 11 and 10. You confirm mailbox content before you remove the old files. Trial edition saves 10 messages per folder.