Hosting plan limits: reading disk and traffic usage and freeing space
By Datafex Engineering TeamPublished 4 min read
Running into a plan limit is usually noticed not through a warning but through the site failing to open one morning. Yet both the limit and the usage can be seen in advance, and most of what filled the space often does not even belong to the site. Below is where the limit is read on the web hosting plans, what happens when it is exceeded, and the right order for freeing space.
Your limits are visible in two places
Your plan's numeric limits are written on the service detail page in your customer panel: disk space, monthly traffic, and the number of domains, subdomains, databases, mailboxes and FTP accounts. Those values come from the plan definition — they answer "what am I entitled to".
How much of that entitlement you have used is shown on the statistics screen in Plesk. Putting the two pages side by side tells you where you stand without waiting for the end of the month. We do not print plan limits into articles, because plans change over time; the measure is always the value shown in the panel.
What happens when a limit is exceeded
Hosting subscriptions are configured with a blocking overuse policy. That means this: when the disk or traffic limit is passed, the subscription does not quietly carry on and grow the invoice — it is blocked on the panel side. In practice the site and the mail service become unreachable.
Annoying as that sounds, it is predictable: no surprise overage charge appears. But the predictability runs one way only — noticing that you are approaching the limit is your job.
The four things that fill a disk
When disk space runs out, the first place to look is almost never the site itself.
| Source | Why it grows | First check |
|---|---|---|
| Media files | Every image is generated in several sizes | List the largest directories |
| Mailboxes | Attachments pile up and nobody deletes them | Look at the size per mailbox |
| Backups | Backups held on the server multiply by the retention count | Open the backup list in the panel |
| Log and cache files | Error logs and plugin caches can grow without a ceiling | Search for files of abnormal size |
The third row is the sneakiest: taking backups is the right habit, but piling them up only on the server both fills the disk and fails to protect you. Where a backup belongs is covered in taking and restoring backups in Plesk.
The order for freeing space
- Sort directories by size in the panel's file manager and find the largest three. Do not start deleting on a hunch.
- Download the old backups sitting on the server and remove them from it; on most plans this step alone is enough.
- List mailboxes by size. It is common to find a single mailbox carrying ten years of attachments; setting a per-mailbox quota is the permanent fix.
- Clear out old log files and plugin caches.
- Weed out large unused images in the media library and set an upload size limit for new ones.
- Watch usage for a week after the cleanup. A disk that refills quickly is the sign of something that needs fixing rather than cleaning.
What the traffic limit counts
Monthly traffic is the data leaving the server: pages and images sent to visitors, downloaded files and outgoing email. Traffic jumping while visitor numbers stay flat usually has three causes — a large video or file added to the site, a rise in crawling other than search engines, and other sites linking straight to your images.
The first response is to shrink images and turn caching on. If most of the traffic comes from a single downloadable file, shared hosting was not the right home for that file to begin with.
When cleaning up is not enough
If you are still against the limit after the cleanup, you have reached a decision point with two options.
A larger plan. When the domain count, the disk or the traffic is what feels tight, moving up a plan is the cheapest answer and does not mean rebuilding the site; the new limits are applied to the existing subscription. You request it from your customer panel.
Your own server. The real limit of shared hosting is often not disk but privilege: if you need to run your own service, install an operating system package or change the web server configuration freely, a larger plan does not meet that need. At that threshold, how the limits and prices of the two compare puts numbers on the decision, and you can pick the resources you need and work out the monthly figure in the configurator.
Before you move to a server, know this: in solving the disk and traffic problem you also take on updates, security and the backup routine. If a full disk is your only problem, the right answer is usually the larger plan.