Check disk space and bandwidth in cPanel

If your web hosting requires an unusually large amount of storage space or if you want to know how much data your website is transferring, you can find several tools for this directly in the CURIAWEB cPanel.

It is important in this regard, Not to be confused storage space and bandwidth. Storage space shows how much data is permanently stored in your hosting account. Bandwidth, on the other hand, shows how much data has been transferred between your hosting and visitors or other systems within a given period of time.

In this guide, we will show you how to check disk space and bandwidth in cPanel, find large directories, and systematically investigate unusually high usage.

Important: Never delete files just because a directory requires a lot of storage space. First, check which application uses the files and whether they are still needed.

Storage space and bandwidth briefly explained #

Both values describe completely different things.

Value	Meaning
Storage space	Data stored in your hosting account
bandwidth	Data transmitted between servers and other systems

Therefore, a website can require little storage space and still generate a lot of bandwidth.

Conversely, a hosting account can take up a lot of storage space even though the website has very few visitors.

What takes up storage space in web hosting? #

Different data can contribute to the storage consumption of a hosting account.

Typical examples are:

• Website files
• WordPress files
• Pictures and videos
• Email messages and attachments
• Databases
• Log files
• Cache files
• temporary files
• Backups and archives
• Test or staging websites

Therefore, if the used disk space suddenly increases sharply, you should first find out, which area has grown.

Check storage space directly in cPanel #

Depending on the view, various statistics or usage values of your account are already displayed on the cPanel overview page.

For a more detailed analysis, open:

Files → Storage usage

There you can see which directories within your hosting account are using a particularly large amount of disk space.

How to correctly read storage space usage #

The storage space overview helps you identify large directory areas.

You should not delete individual files immediately, but rather work your way step-by-step from the larger directory to the actual culprit.

Example:

Hosting-Account
└── public_html
    └── wp-content
        └── uploads

If public_html is very large, that initially only means that there is a lot of data within the website.

Only further analysis can show, for example, that a large part of it is under:

wp-content/uploads/

lies.

Examine large directories first #

If you are running out of storage space, look for the largest areas first.

This makes the analysis much more efficient than checking hundreds of small files individually.

Typical candidates include, for example:

public_html
mail
tmp

Which directories are particularly large on your end depends on the actual usage of the hosting account.

Use file manager for further analysis #

If you have found a conspicuously large website directory, you can then cPanel File Manager use.

There you can examine the directory structure in more detail and determine which files or subfolders are present.

Attention: You should not delete system and application files on suspicion. A single incorrect deletion can render a website or application unusable.

Website files as storage consumers #

On a standard website, media in particular can take up a large portion of the storage space.

This includes, for example:

• high-resolution photos
• Videos
• PDF files
• Download files
• multiple versions of the same media

WordPress may also contain automatically generated image sizes.

Depending on the theme, plugins, and WordPress configuration, a single uploaded image file can result in several additional image files being generated.

Find large ZIP files and archives #

A common and unnecessary use of storage space is caused by archives that were left behind on the web space after a migration or backup.

Typical file extensions are:

.zip
.tar
.tar.gz
.gz

Such files can be several gigabytes in size.

Always check before deleting what the archive was created for and whether it is still needed.

Check old manual backups #

If you backed up website files or databases yourself and then saved them in your hosting account, these copies can take up a significant amount of storage space.

Examples:

backup.zip
website-alt.zip
wordpress-backup.tar.gz
database-backup.sql

In particular, multiple older copies of the same website can quickly add up.

Important: Do not delete any backup until you have clarified whether it is still needed and whether another reliable backup exists.

Do not confuse JetBackup with manual backup files #

CURIAWEB also provides JetBackup 5 in cPanel.

A backup managed by the backup system is technically not the same as a ZIP or SQL file that you have saved yourself within your web space.

For example, if you in the file manager a large file named backup.zip find, therefore you should not automatically assume that it is a server-managed JetBackup.

Consider staging and test websites #

If you have cloned a website or created a staging environment, this can result in an almost exact copy of the original website.

For example:

Live website: 4 GB
Staging copy: 4 GB

This already requires approximately 8 GB of website data – not yet taking into account additional databases, emails, and other files.

Therefore, check whether older test or staging installations are still needed.

Check cache directories #

Caching systems temporarily store generated data to deliver websites faster.

Normally, the respective application manages this data itself.

However, in the event of a misconfiguration or unusual usage, cache directories can grow significantly.

Do not blindly delete cache directories via the file manager. If possible, use the dedicated cache function of the application in question.

Log files can grow significantly #

Applications can generate their own log files.

For example, if the same error is logged thousands of times, a log file can become unusually large.

Typical file names may include, for example:

error.log
debug.log
cron.log

The exact name depends on the application.

When a log file is very large, you should not only look at the file, but also clarify, why so many entries are created.

Check WordPress debug.log #

With WordPress debugging enabled, for example, the following file may be present:

wp-content/debug.log

If a website constantly generates warnings or errors, this file can grow significantly.

We cover WordPress error logging under Using WordPress debugging and error logs.

Fix the error instead of just deleting the log file #

Assuming a log file is 2 GB in size and continues to grow daily.

Simply deleting the file does not solve the actual problem.

The more sensible procedure is:

detect large log file
        ↓
identify recurring error message
        ↓
fix the cause
        ↓
subsequently clean up the log file in a controlled manner

We explain how to analyze typical web server error messages at Read cPanel Error Log and find website errors.

Emails can take up a lot of storage space #

In heavily used mailboxes, emails can consume a significant portion of the hosting storage.

Of particular relevance are:

• large attachments
• messages stored for years
• extensive Sent folder
• Recycle Bin
• Spam folder
• several large mailboxes

With IMAP, messages are generally stored on the mail server as long as they are not deleted or moved accordingly.

Analyze email storage separately #

cPanel provides a dedicated feature for email mailboxes:

Email → Email storage usage

There you can investigate more specifically which email accounts or mail folders are taking up storage space.

We explain the exact procedure under Check and clean up email storage in cPanel.

Don't forget the trash and spam folders #

A message is not necessarily deleted from the server just because it was removed from the inbox.

Depending on the email client and configuration, it may then be located in the trash, for example.

Even spam folders can fill up over time.

Therefore, if a mailbox is unusually large, you should look at the individual mail folders and not just the inbox.

Databases also require storage space #

MySQL databases also contribute to the memory usage of a hosting account.

In data-intensive applications, they can grow considerably.

Typical causes include, for example:

• large online stores
• extensive log or statistics tables
• Session data
• Plugin data
• Import data
• uncleaned temporary records

A database should not be cleaned directly in phpMyAdmin if you do not know the function of the tables in question.

You can find the basics of database management under Use phpMyAdmin in cPanel.

Attention: Never delete unknown database tables on suspicion. A supposedly old or large table may be required for the website to function.

SQL backups can take up additional storage space #

A database itself and an exported database backup are two different storage consumers.

For example, if you export a large database and the generated .sql- then leaves the file on the web space, both data sets exist simultaneously.

Check storage space again after deleting #

Once you have securely removed unnecessary files, check the storage space usage again.

Note that, depending on the system, usage statistics do not necessarily need to be updated to the exact second in every view.

If a display still shows the previous value immediately after a deletion, this does not automatically mean that the file is still present.

Include hidden files #

Certain files under Linux start with a dot and may be hidden in a normal file view.

Examples:

.htaccess
.user.ini

We explain how to make such files visible at Show hidden files like .htaccess in cPanel.

Storage full: What can happen? #

If a hosting account no longer has sufficient free storage space available, various functions can be impaired.

Depending on the application, problems may arise, for example, with:

• Upload new files
• Saving new data
• Receiving emails
• Creating temporary files
• Performing updates
• Generating cache or log files

Therefore, a full storage space should not only be investigated when the website is already showing errors.

Do not start updates first when storage is full #

A software update may require additional temporary storage space.

If the hosting account is already completely full, an update may fail or remain incomplete as a result.

First, create sufficient free disk space in a controlled manner, and then start the update.

What is bandwidth? #

The bandwidth display in cPanel shows the traffic generated by the use of your hosting account.

Simplified:

Visitor loads website
→ Server transfers HTML, CSS, JavaScript, and images
→ Data traffic is generated

Other services can also generate traffic.

Storage space and bandwidth are therefore two separate metrics.

Check bandwidth in cPanel #

Open in CURIAWEB-cPanel:

Measured values → Bandwidth

There you can view the bandwidth usage or data traffic of your hosting account.

Why is the bandwidth increasing? #

More bandwidth does not automatically mean a problem.

An increase can occur, for example, due to:

• more website visitors
• large images or downloads
• frequently accessed files
• Bots and crawlers
• Downloads of large files
• certain automated accesses

Therefore, a successful article or a heavily visited website can naturally generate more traffic.

Large files increase data traffic #

Assuming a publicly accessible file is 100 MB in size and is downloaded completely 100 times.

Then, just from that, it creates approximately:

100 MB × 100
= 10,000 MB
≈ 10 GB data transfer

The example shows why individual large files can have a significant impact on data traffic.

Many small page views can also generate a lot of bandwidth #

Not only downloads are relevant.

When a website transfers several megabytes of images, CSS, JavaScript, and other resources per full page view, this adds up accordingly with many visitors.

Bandwidth and website speed are not the same thing #

High bandwidth usage does not automatically mean the website is slow.

Likewise, low bandwidth usage does not prove that a website is fast.

Website performance depends on numerous other factors, for example:

• PHP processing
• Database queries
• Caching
• Size of individual resources
• external services
• Hosting resources

Do not confuse bandwidth and CloudLinux resources #

These values also describe different technical levels.

measured value	What is being considered?
Storage space	stored data
bandwidth	transmitted data
CloudLinux resources	for example, CPU, memory, and processes

We will cover the CloudLinux evaluation in the next article under Understanding CloudLinux Resource Usage in cPanel.

Investigate unusually high bandwidth #

If traffic increases sharply for no apparent reason, you should first narrow down the time period.

Then check whether the increase coincides with a known change.

Examples:

• new marketing campaign
• new download
• heavily visited blog post
• Bot activity
• new application
• external inclusion of a file

Hotlinking can generate traffic #

If an external website embeds a file directly from your hosting, the file is still served from your server.

For example, a third-party site could load an image directly via your URL.

This generates traffic on your hosting for every corresponding call.

cPanel provides for this under Security → Hotlink Protection provides a corresponding function.

Important: Do not activate hotlink protection rashly. External services, feeds, or other legitimate integrations may also need to access files on your website.

Distinguish between visitors and bots #

An increase in traffic does not necessarily have to come from human visitors.

Search engines, monitoring services, and other bots also retrieve websites and files.

For a more detailed analysis, in the cPanel area Measurements for example, access and statistical tools can be helpful.

Use AWStats for further analysis #

With Metrics → AWStats can you view additional statistics on visits to your website.

Such statistics can help to better classify unusual access patterns or frequently accessed content.

Note that web server statistics and modern analytics systems may use different measurement methods. Their numbers therefore do not have to be identical.

Storage issue or resource issue? #

If a website is slow or showing errors, you should not automatically blame the storage space.

First, check what kind of problem it is.

Observation	Meaningful first checkpoin
Files can no longer be saved	Storage space
Mailbox is full	Email storage space
An unusually large amount of data is being transferred	Bandwidth / Traffic
Website is slow under load	CloudLinux Resources and Application
Website shows PHP errors	Error Log
Resource Limit Is Reached	CloudLinux resources

Systematically clean up storage space #

If you need to free up storage space, proceed in a controlled manner:

1. Open Files → Storage usage.
2. Identify the largest directories.
3. Distinguish between website, email, database, and other data.
4. Examine large website directories with the file manager.
5. Check old ZIP, SQL, and other manually created backup files.
6. Check unneeded test and staging websites.
7. Check unusually large log files.
8. Analyze email storage separately.
9. Only delete data whose purpose you clearly know.
10. Then check the disk space usage again.

What you shouldn't delete on suspicion #

In particular, do not randomly remove:

• unknown system directories
• WordPress core files
• Plugin or theme files
• Database files
• Configuration files
• hidden files
• Mail directories directly via the file manager

If you do not know what a file or directory is needed for, clarify this before deleting it.

Basic rule: Cleaning up storage space doesn't mean „deleting large files,“ but rather finding out first which data is no longer needed.

If the displayed memory consumption remains unclear #

If the storage space display shows high usage, but you cannot clearly identify the corresponding data, you should not experiment by randomly deleting things.

Document instead:

• displayed total consumption
• largest directories
• suspicious files
• approximate file sizes
• whether the consumption has increased suddenly or slowly

When should you contact CURIAWEB support? #

If your hosting storage is growing unexpectedly rapidly, cannot be allocated, or an application is no longer functioning correctly due to a lack of disk space, a technical review may be advisable.

Particularly helpful are:

• affected domain
• current memory usage
• conspicuously large directories
• point in time since which consumption has increased
• recent changes
• any visible error messages

In the case of unusually high bandwidth, the affected time period and known changes in traffic are also helpful.

Summary #

Storage space and bandwidth are two different metrics. Storage space describes the data that is permanently stored in your hosting account. Bandwidth, on the other hand, describes the data traffic between your hosting and other systems.

You can analyze the memory usage in cPanel under Files → Storage usage. Work your way from large directories down to the actual files and do not delete any unknown data on suspicion.

Typical storage consumers are website files, media, emails, databases, manual backups, staging websites, cache files, and significantly grown logs.

For emails, you should additionally Email → Email storage usage use, as it allows individual mailboxes and mail folders to be examined more specifically.

You can find the bandwidth usage under Measured values → Bandwidth. A high value can be caused by many visitors, large downloads, bots, or other frequently accessed resources, and is not automatically an error.

When a website is slow, you should not confuse storage space and bandwidth with CPU, RAM, or process limits. These values belong to CloudLinux resource usage and are evaluated separately.

The most important rule is: First determine which area is causing the consumption – and only then clean it up or optimize it in a targeted manner.