What Are Bandwidth and Inode? How They Affect Your Website

When choosing a hosting plan, you will always encounter the terms bandwidth and inode in the specifications. Many site owners ignore these numbers until something goes wrong. Understanding what they mean — and how to manage them — can prevent site outages and keep your hosting running smoothly.

What Is Bandwidth?

Bandwidth (also called data transfer) is the total amount of data your website sends and receives each month. Every time a visitor loads your site, the server transmits files — HTML, images, CSS, JavaScript, and any downloadable content — to their browser. The sum of all that data transfer is your bandwidth consumption.

Bandwidth Usage Examples

• A 2 MB page × 1,000 visitors/day × 30 days = 60 GB per month
• A 5 MB high-resolution image loaded 10,000 times = 50 GB per month
• A 100 MB video viewed 1,000 times = 100 GB per month

A typical business website or blog usually consumes 5–20 GB per month. Sites with heavy images, video, or high traffic will use considerably more.

What Happens When You Exceed Bandwidth?

Depending on your hosting provider's policy, one of two things typically occurs:

• Site suspension: Your website is taken offline until the next billing cycle or until you upgrade your plan
• Overage charges: Some providers charge a fee for every GB used beyond your limit

AsiaGB designs bandwidth allocations to comfortably cover typical website needs. If you require more, contact Support to discuss options.

What Is an Inode?

An inode (information node) is a counter for the total number of files and folders stored in your hosting account. Every single file and every folder — regardless of size — consumes exactly one inode. Even a 1-byte file uses the same inode count as a 1 GB file.

Where Inodes Come From

• WordPress core files: approximately 2,000–3,000 inodes
• Each plugin: 100–500 inodes depending on complexity
• Each theme: 200–1,000 inodes
• Uploaded media with generated thumbnails: each image creates 4–6 files (original + multiple sizes), which can easily exceed 20,000+ inodes on media-heavy sites
• Each email in a mailbox: 1 inode per message
• Plugin-generated cache files: can create thousands of files per day

What Happens When Inodes Are Full?

When your inode limit is reached, the server cannot create any new files. The effects are immediate and serious:

• WordPress may display errors in the admin dashboard and frontend
• Incoming emails may bounce because the server cannot write new mail files
• Backup processes fail silently
• Plugin caching systems stop working properly

Bandwidth vs Disk Space — What Is the Difference?

These two resources are often confused because both are measured in gigabytes. The distinction is simple:

• Disk space is how much data you can store on the server — your files, database, email, and code all live here.
• Bandwidth is how much data the server sends out to visitors each month. Even if you store a 5 MB image once, loading it 1,000 times costs you 5 GB of bandwidth.

Both resources need attention. A site with huge images stored locally will consume disk space and bandwidth rapidly. Moving static assets to a CDN reduces bandwidth consumption from the origin server without shrinking your actual file storage usage.

A Note on "Unlimited Bandwidth" Plans

Some hosting providers advertise unlimited bandwidth. In practice, these plans almost always include a fair-use policy that throttles or suspends accounts that generate unusually high traffic — typically because such accounts impact other users sharing the same server. Always read the Terms of Service carefully before choosing such a plan.

AsiaGB specifies bandwidth per plan transparently, sized to comfortably cover typical usage at each tier. If your site grows beyond the plan's allocation, upgrading is straightforward without migrating servers.

Bandwidth and Inode Estimates by Site Type

Use this table as a starting point when choosing a plan or deciding whether to upgrade:

E-commerce stores and news sites with large media libraries are most at risk of hitting the 50,000 inode ceiling. Every product image upload generates multiple thumbnail sizes automatically, multiplying inode consumption quickly.

How to Check Your Inode Usage

You can check your current inode count directly from DirectAdmin:

1. Log in to DirectAdmin
2. On the main dashboard, look for Usage Statistics
3. You will see current inode usage alongside your total limit

You can also browse directories in File Manager to count files per folder and identify which directories are consuming the most inodes.

Finding Inode-Heavy Directories via SSH

If you have SSH access to your server, these commands quickly identify which directories are consuming the most inodes:

# List the 10 directories with the most files inside public_html
find ~/public_html -type d | while read d; do
  echo "$(find "$d" -maxdepth 1 -type f | wc -l) $d"
done | sort -rn | head -10

# Count total inodes used in public_html
find ~/public_html | wc -l

# Count WordPress cache files specifically
find ~/public_html/wp-content/cache -type f | wc -l

The output almost always points to one of two culprits: the WordPress cache directory or the wp-content/uploads tree filled with thumbnail variants. Knowing which folder is the offender tells you exactly where to start cleaning.

How to Reduce Inode Usage

High inode counts typically result from years of file accumulation that was never cleaned up. Here are effective strategies to bring your count down:

1. Clear WordPress Cache

Caching plugins like W3 Total Cache and WP Super Cache generate thousands of temporary files. Clear the cache regularly from within the plugin settings, or configure automatic cache purging on a schedule.

2. Delete Unused Plugins and Themes

Deactivated plugins and themes that are not deleted still consume inodes. Remove every plugin and theme you are not actively using.

3. Delete WordPress Post Revisions

WordPress automatically saves a revision every time a post is updated. After years of editing, thousands of revisions can accumulate in your database. Use a plugin like WP-Optimize to purge old revisions in bulk.

4. Remove Unused Media

Every image you upload to WordPress generates multiple thumbnail sizes automatically (thumbnail, medium, large, and theme-specific sizes) — meaning one upload creates 4–6 files. Use a plugin like Media Cleaner to identify and remove media files that are no longer used anywhere on the site.

5. Clean Out Old Emails

Every email in your mailbox counts as one inode. Years of accumulated spam, sent mail, and old messages can add up to thousands of inodes. Regularly empty Spam, Trash, and Sent folders.

6. Limit WordPress Revisions

Add this line to wp-config.php to cap how many revisions WordPress stores:

define('WP_POST_REVISIONS', 3);

This keeps only the three most recent revisions of each post instead of storing every version indefinitely.

Recommended Tools for Monitoring Inode and Bandwidth

Proactive monitoring prevents resource problems before they become site outages. Here are the tools that work best in practice.

WordPress Plugins for Inode Control

• WP-Optimize — Cleans up revisions, transients, and table overhead. Supports scheduled automatic cleanup.
• Media Cleaner — Scans for uploaded files that are not referenced anywhere in your content and queues them for deletion.
• Query Monitor — Surfaces slow queries and PHP warnings that can be caused by a full filesystem, helping you diagnose inode-related errors in WordPress.

Bandwidth Monitoring via DirectAdmin

DirectAdmin includes a Bandwidth Summary page that displays daily and monthly usage with a graph. Access it from:

DirectAdmin → Extra Features → Bandwidth Summary

For more detail, the Log Viewer in DirectAdmin shows individual request logs so you can identify which files are being downloaded most frequently and consuming the most bandwidth. This data helps you decide whether to offload large assets to a CDN.

Using a CDN to Reduce Origin Bandwidth

If your site serves many images, videos, or downloadable files, integrating a CDN such as Cloudflare significantly reduces bandwidth consumed by your origin hosting server. The CDN caches static assets at edge locations closest to each visitor, so those assets are not fetched from your server on every request. This is the most effective single step for high-traffic sites with large media libraries.