If you run a small business, you’ve probably seen two storage warnings that seem unrelated. Your mailbox is almost full, yet your cloud drive has plenty of space. Or the reverse: your file storage is maxed out while your inbox sits half empty. Most business platforms treat mailbox and file storage as two separate allowances, with separate limits and sometimes separate bills.
That isn’t an accident, and it isn’t only about pricing. Email and files grew up as different systems, built on different technology and managed by different rules.
This guide explains why mailbox and file storage are usually metered separately, what pooled storage changes, the trade-offs of each model, and how to reduce duplicated storage, especially the hidden cost of email attachments.
Quick Answer
Mailbox and file storage are usually metered separately for four reasons:
History: email servers and file servers began as separate products, often from separate vendors.
Architecture: mailboxes are stored and indexed differently from files, with their own protocols, retention rules, and performance limits.
Administration: organizations often want separate quotas, retention policies, and legal holds for email.
Pricing: separate allowances let vendors package and sell each product on its own.
Some providers now pool storage across email and files. That gives you one total to manage, but it also means a large file library and a busy inbox compete for the same space.
The Historical Reason: Two Different Systems
For decades, business email and file storage lived on different servers. A company might run a mail server for email and a separate file server, a set of network folders, for documents. Each had its own disks, backups, and administrator settings, so each naturally had its own quota.
When these systems moved to the cloud, many providers kept the separation. Email became a hosted mailbox service, and file shares became cloud drives. The products were often licensed and sold separately, and their storage limits followed the same split.
The Technical Reasons
Mailboxes are structured differently
A mailbox is not just a folder of files. It is a structured store of messages, folders, calendar items, contacts, and attachments, built so that messages can be searched, threaded, and synchronized quickly across devices. Email clients connect through protocols such as IMAP or proprietary sync methods, which expect a mailbox to behave in specific ways.
File storage is organized around documents and folders, with features such as previews, version history, sharing links, and in-browser editing. Because the two stores are optimized for different jobs, many providers measure and limit them separately.
Email has its own size limits
Email was never designed to move large files. Attachment limits commonly sit somewhere around 20–35 MB per message, depending on the provider. Encoding during transmission also makes attachments larger than the original files. Mailbox quotas, archiving tools, and retention policies were all designed around this message-based model.
Compliance applies differently to email
Many organizations must keep emails for set periods, place mailboxes on legal hold, or search them during investigations. Those obligations often differ from document retention rules. Separate storage makes it easier to apply email-specific policies without affecting the file library, and the reverse.
The Business Reason: Separate Products, Separate Pricing
Separate metering also suits how vendors sell. A provider can offer a fixed mailbox quota with an email plan and a separate drive allowance with a storage plan, then upsell either one independently.
For buyers, this has an awkward side effect: stranded capacity. A sales manager whose inbox is full can’t use the hundreds of gigabytes sitting unused in their cloud drive. Someone with a huge file archive can’t borrow space from a near-empty mailbox. You can end up paying for capacity in one place while running out in the other.
How Major Providers Approach It
Approaches vary, and plans change often. According to NevTan’s comparison, based on each provider’s plan pages in September 2026:
Provider | Storage model |
|---|---|
Microsoft 365 | Mailbox storage counted separately from OneDrive |
Google Workspace and Google One | One allowance shared across Drive, Gmail, and Photos |
Dropbox | File storage only, with no mailbox included |
NevTan Drive | One pool shared across Drive and NevTan Mail |
Microsoft’s separate model is the classic one, and NevTan’s comparison with Microsoft 365 covers it in more detail. Google is the best-known pooled model, which the NevTan Drive vs Google Drive comparison discusses alongside sharing and editing differences. Always check each provider’s current plan pages before deciding.
Separate vs Pooled Storage: Pros and Cons
Separate metering | Pooled storage | |
|---|---|---|
Predictability | Each service has a fixed limit | One total covers both |
Flexibility | Unused space in one service can’t help the other | Space goes wherever it’s needed |
Monitoring | Two meters to watch | One meter, ideally with a breakdown |
Risk when full | Only one service is affected | A full pool can affect both email and files |
Purchasing | Upgrades may be needed in two places | Buy additional room once |
Policy control | Easy to set email-specific limits | Requires more attention to who uses what |
Neither model is better for everyone. Separate metering suits organizations that need strict, independent control over mailbox sizes. Pooled storage suits small teams that would rather buy space once and use it wherever work happens.
How NevTan handles pooled storage
NevTan Drive has no subscription of its own. Your NevTan plan sets one storage pool shared between Drive and NevTan Mail, so you buy room once for both. The free plan includes 1 GB per user for up to 10 users, and paid plans range from 30 GB to 5 TB per user.
To avoid the main weakness of pooled storage, which is not knowing what is using the space, the storage meter breaks usage down between Drive files and Mail. When the pool fills, existing files stay readable, and nothing is deleted or locked. You’re warned at 85%, 90%, and 95%, and once the pool is full, NevTan Mail can’t send new attachments until you free space or add storage.
The Hidden Cost: Email Attachments Stored Again and Again
Whichever model you use, attachments are where storage quietly multiplies. Suppose you email a 10 MB PDF to five colleagues:
One copy sits in your Sent folder.
One copy lands in each of the five recipients’ inboxes.
Someone saves it to the shared drive.
Someone edits it and emails back “v2,” and the cycle repeats.
That one 10 MB file can easily use 70 MB or more across the organization within a day. With separate metering, the cost is spread across mailboxes and drives, so it’s harder to see. With pooled storage, it all comes from the same total, so it’s easier to notice.
Share links instead of attachments
The simplest fix is to store the file once and send a link. A link means one stored copy, and everyone sees the current version. In NevTan Drive, share links can carry an expiry date, a password, and download controls. Those controls are on every account, including free ones, so a link can be safer than an attachment as well as smaller.
Edit PDFs where they’re stored
PDFs cause particular duplication. People download the attachment, edit or sign it on their computer, then email it back as a new attachment. Every round adds more copies to more mailboxes.
Editing the PDF where it’s stored breaks that cycle. If you need a no-cost option, our step-by-step guide shows how to edit a PDF online free, without a converter or download. On NevTan’s paid plans, the built-in NevTan Drive PDF editor lets you change text, fill forms, annotate, and sign a PDF in the browser, then save it back to the same file in your Drive. Starter includes 20 PDF edits per user per month, Standard includes 100, and Plus and Enterprise are unlimited. Once the file is updated, share one link instead of sending another attachment.
How to Size Storage When Email and Files Are Pooled
If your provider pools mailbox and file storage, plan for both at once:
Measure current mailbox sizes for every user, not just the team average.
Measure current file storage, including shared folders.
Estimate monthly growth for both. Email tends to grow steadily, while file storage often grows in bursts around projects.
Plan 12 to 24 months ahead, then add 20–30% headroom.
Check per-file limits. NevTan Drive accepts single files up to 100 MB, as described in its guide to uploading and managing files.
With separate metering, do the same calculation twice, once per service. Make sure each allowance has enough headroom, because spare space in one can’t help the other.
Best Practices for Keeping Both Under Control
Empty Trash in both places. Deleted emails and files often still count until they’re permanently removed. In NevTan Drive, items stay in Trash, and count toward the shared pool, until you restore or permanently delete them.
Archive old mail deliberately. Decide which mail must be kept for compliance reasons, and move or delete the rest according to policy.
Search for large attachments. Most email clients can search or sort by message size. A few large threads often account for a surprising share of a mailbox.
Make links the default for internal sharing. Reserve attachments for recipients who genuinely need a standalone copy.
Review storage quarterly. A short review shows whether email or files are driving growth, which is especially useful with a pooled meter.
Common Mistakes
Counting only file storage when buying a pooled plan. The mailbox is part of the total.
Assuming free space in one service helps the other. With separate metering, it doesn’t.
Ignoring Sent folders. Every attachment you send is usually stored in your own mailbox as well as the recipients’.
Using email as a file archive. Mailboxes are poor document stores. Files are easier to find, version, and share from a drive.
Downloading and re-attaching edited PDFs. Every new version adds more copies. Edit in place and share a link.
Conclusion
Mailbox and file storage are usually metered separately because email and files began as separate systems, with different structures, size limits, compliance needs, and pricing models. Separation gives you control and isolation, but it can strand unused capacity. Pooled storage gives you flexibility and a single number to watch, provided you can see what’s using the space.
Whichever model you choose, the biggest savings come from habits: share links instead of attachments, edit files where they’re stored, and empty Trash regularly. To see how storage, sharing controls, and editing fit together in one workspace, explore the NevTan Drive feature overview.
