Package limits explained (disk, inodes, bandwidth, email)
On this page
Each package sets limits for the accounts on it. In every field, 0 means unlimited. This page explains what each limit counts and what happens when an account reaches it. Processor, memory and process limits have their own page.
Disk quota (MB)
- Counts website files, email and databases together. Customers see the split in Resource Usage.
- Usage is measured every 10 minutes.
- At 90% and at 100%, the customer gets an email (once a month each) and you get a copy at the Contact email of Server Settings.
- When disk quotas are on (Server Settings → Limits → Disk quotas shows Enforced), the filesystem also stops the account's website files from growing past the quota. If it shows Measured only, click Enable disk quotas. If it shows Not available, the server's kernel or filesystem does not support quotas and accounts are only warned by email.
Max files and folders (inodes)
- Limits how many files and folders the account's home folder can hold. It needs disk quotas enforced.
- Customers see the count under Files and folders in Resource Usage, with a warning from 90%.
- At the limit, new files fail: uploads, cache files, sessions.
Monthly bandwidth (MB)
- Counts the website traffic of the account from the 1st of the month. It is read from the web server logs every minute.
- At 80% and 100% the customer gets an email. What happens at 100% depends on Server Settings → When an account uses up its monthly bandwidth. See bandwidth limit reached.
Domains
- Max addon domains — extra websites with their own domain.
- Max subdomains — for example
shop.example.com. - Max parked domains (aliases) — other domains that show the same website.
Email, databases and other counts
- Max email accounts — mailboxes.
- Max databases — MySQL and PostgreSQL databases count together. Installing WordPress or another application also uses one.
- Max cron jobs, Max FTP accounts, Max mailing lists.
When a count is reached, creating one more is refused with You have reached your … limit (N). See limit reached errors.
Emails per hour
- How many emails the account may send per hour. Each recipient counts.
- 0 uses the server default: Default emails per hour, per account in Mail Queue & Spam (section Email) → Sending limits. That default is 500; setting it to 0 means no limit.
- Over the limit, messages wait and go out later. The customer and you are told.
Good to know
- Lowering a limit below what an account already uses does not delete anything. The account just cannot add more until it is under the limit again.
- The package list shows only the main limits; open a package with Edit to see all of them.
Thank you — this helps us improve the article.
Still stuck?
Ask the AI about your exact situation — it answers from this knowledge base — or contact us.
Related articles
- How to create a hosting package (plan) and its limits
Create a package with disk, bandwidth, email, database and resource limits, a feature list and a PHP version, then put hosting accounts on it.
- CPU, memory and process limits per hosting account
How the processor, memory and process limits of a package work, what happens when an account reaches them, and where you and the customer see it.
- Website shows "Bandwidth limit reached" page
The site shows "Bandwidth limit reached" because the account used its monthly traffic. How traffic is counted, when it returns and how to fix it now.
- Error "You have reached your … limit" in the control panel
Why the control panel refuses a new mailbox, database, domain, cron job or FTP account with "You have reached your limit", and how to fix it.