Hostinger Business Shared Hosting Review: I Hosted 22 WordPress Websites and Found a Hidden Limit

Hello Dear Friend,

If you are planning to buy shared hosting and you are looking at plans that say “Host 50 Websites”, “Host 100 Websites” or even more, then I want you to read this article before making your decision.

Because I recently found something inside my own hosting dashboard that honestly made me look at hosting plans differently.

I am using a Hostinger Business Hosting plan, and one of the biggest reasons I liked this plan was simple.

It allowed me to host up to 100 websites.

For someone like me who works as a freelancer and designs/manages multiple websites, this looked like a very good deal.

I thought:

“Okay, 100 websites. I am not going to reach that limit anytime soon.”

And honestly, I was right.

Today, I am hosting only 22 websites on this hosting account.

Most of these websites are built on WordPress.

So naturally, I thought I still had plenty of hosting capacity left.

Then one day, I opened my hosting Resource Usage dashboard.

And this is where things became interesting.

My plan showed:

  • 200 GB total disk space
  • Only 17.27 GB used
  • Around 91% storage still free

Honestly, after seeing this, anyone would think:

“Perfect! There is no problem. I still have a huge amount of hosting space left.”

But then I looked at the next box.

And I saw this:

491,348 files and directories used out of 600,000.

That means my inode usage was already around:

82% USED

Wait.

My storage was only 9% used.

But another hosting limit was already at 82%.

And suddenly, I had one big question in my mind.

If my hosting plan allows me to host 100 websites, then why is one of my important hosting limits already 82% full with just 22 mostly WordPress websites?

That is exactly why I am writing this Hostinger Business Hosting review.

This is not going to be one of those articles where someone simply copies the features from the hosting company’s pricing page and says:

“Great hosting, fast servers, free SSL, 10 out of 10.”

No.

I am going to show you my real dashboard, real numbers and real experience.

And more importantly, I want to explain something I think many people, including me before this, don’t pay enough attention to when buying shared hosting.

The number of websites you can host is not the complete story.


My Real Hostinger Business Hosting Experience So Far

Let me first make my situation completely clear.

I use this hosting account for multiple websites.

At the moment:

  • My plan allows up to 100 websites
  • I am currently hosting 22 websites
  • Most of these are WordPress websites
  • My total storage is 200 GB
  • I have used only 17.27 GB
  • Around 91% disk storage is still free
  • But I have already used 491,348 out of 600,000 inodes
  • That means around 82% of my inode limit is already used

Now look at this situation carefully.

If I only checked my disk space, I would be completely relaxed.

I would think:

“Only 17 GB used out of 200 GB. I can easily add many more websites.”

But the inode number tells a completely different story.

This was my first lesson.

Free storage does not always mean you have unlimited hosting capacity left.

Because hosting has different limits.

You may have plenty of one resource available while another resource is slowly reaching its limit.

And in my case, that resource was inodes.


So, What Is an Inode in Hosting?

Before checking my own dashboard, I honestly never gave much attention to this word.

I was more interested in the things every normal hosting buyer looks at:

  • How many websites can I host?
  • How much storage will I get?
  • What is the price?
  • Is SSL free?
  • Will I get a free domain?
  • Is WordPress easy to install?

But then I saw:

491,348 out of 600,000.

So obviously, I had to understand what the hell was going on.

Let me explain it in the simplest way.

Imagine your hosting account is a big godown.

The total size of the godown is your disk space.

In my case, imagine I have a godown with space for 200 GB.

Now suppose I put one huge box inside it weighing 5 GB.

That one box uses a lot of space.

But it is still only one box.

Now imagine another situation.

Instead of one big box, I put 5 lakh small boxes inside the same godown.

Maybe all these small boxes together don’t use much physical space.

But I still have to manage 5 lakh different boxes.

This is roughly how I now understand the difference between:

Disk Space

and

Inodes.

In simple words, every file and directory on your hosting account adds to the inode count.

So you can have a lot of free disk space.

But if your account contains too many individual files and folders, you can still get close to your inode limit.

And this is exactly what happened to me.

Hostinger’s own documentation explains that each file or directory counts toward the inode limit, and reaching that limit can prevent additional files or directories from being created even when disk space remains available.


The First Thing That Confused Me: 100 Websites Means What Exactly?

This is the main reason I decided to write this article.

My plan allows me to host up to 100 websites.

But I currently have only 22.

So my simple calculation was:

100 – 22 = 78 websites still left.

Simple mathematics, right?

But hosting does not work like that.

Because all websites are not equal.

Let me give you an example.

Suppose I host one very simple HTML website.

It has:

  • 10 pages
  • 30 images
  • A few CSS files
  • A few JavaScript files

Now compare it with a WordPress website.

A WordPress website can have:

  • WordPress core files
  • Plugins
  • Themes
  • Child themes
  • Upload folders
  • Thousands of images
  • Image thumbnails
  • Cache files
  • Backup files
  • Temporary files
  • Log files
  • Staging websites

Both are called:

One website.

But both websites can have a completely different number of files.

So when a hosting company says you can host 100 websites, you should understand one thing.

It does not automatically mean every type of 100 websites will use the same resources.

One hundred simple websites and one hundred active WordPress websites with multiple plugins are two completely different situations.

And my 22 websites are proving this to me in real life.


Why Did Just 22 WordPress Websites Use Almost 5 Lakh Inodes?

Honestly, this was my next question.

I don’t have 5 lakh photos.

I don’t have 5 lakh documents.

I definitely did not manually upload 491,348 files.

So where did all these files come from?

The answer is probably not just one thing.

When you run multiple WordPress websites, files can come from many different places.

Let’s understand this.


1. WordPress Is Not Just One Website Folder With a Few Files

When you install WordPress, a complete file structure is installed.

Then you add:

  • Themes
  • Plugins
  • Images
  • Other website files

Now multiply that by 22 websites.

The number can start becoming big.

And this is before we even talk about cache, backups and image thumbnails.

In fact, this is not the first time managing multiple WordPress websites on my Hostinger account has created an unexpected technical situation. Earlier, I faced another strange issue where a website was working, but the WP Admin button had completely disappeared from Hostinger hPanel. You can read my complete real experience here: Hostinger WP Admin Button Missing? My WordPress Site Was Fine—Here’s What Actually Happened


2. Plugins Can Add a Huge Number of Files

As WordPress users, we usually see a plugin like this:

Click Install.

Click Activate.

Finished.

But inside the hosting account, a plugin may contain many different files.

For example:

  • PHP files
  • CSS files
  • JavaScript files
  • Images
  • Templates
  • Libraries
  • Language files
  • Configuration files

Now imagine you have 10, 15 or 20 plugins on different websites.

Then you have 22 WordPress websites.

Suddenly, you are not dealing with just:

22 websites.

You are dealing with thousands and thousands of individual files.


3. One Image Can Become Multiple Files

This is another interesting thing with WordPress.

You upload one image.

Naturally, you may think:

“I uploaded one image, so I added one file.”

But depending on WordPress settings, your theme and plugins, multiple image sizes can be generated.

For example:

  • Original image
  • Thumbnail
  • Medium image
  • Large image
  • Custom image sizes

Now think about it.

Suppose you upload hundreds of images across 22 websites.

One uploaded image can potentially create multiple files.

Again, your storage may still look perfectly fine.

But the number of files can keep increasing.


4. Cache Files May Be Quietly Growing

This is one area I am personally going to investigate on my account.

Because caching is useful for website speed.

I use WordPress, so obviously performance and caching are important.

But cache systems can create many files.

Depending on the website and tools being used, these can include:

  • Cached pages
  • Generated CSS
  • Generated JavaScript
  • Minified files
  • Temporary optimization files

One website may not look like a big problem.

But what about 22 websites?

That is why I don’t want to guess where my 491,348 files came from.

I want to check the actual folders.

And this is something I recommend you do too.

Don’t guess. Check the data.


My Biggest Lesson: Website Limit and Actual Hosting Capacity Are Not the Same Thing

This is probably the most important point of my entire review.

My plan says:

Up to 100 websites.

But my real experience is telling me something else.

I am only using 22 website slots.

However, my inode usage is already 82%.

So now I personally look at the number of websites differently.

I see it as:

The maximum number of websites the plan allows me to add.

But it is not a guarantee that I can add any random combination of 100 websites without reaching another resource limit first.

Because every website consumes resources differently.

One website may use:

  • Very little storage
  • Very few files
  • Very little CPU

Another may use much more.

The same applies to WordPress.

A simple five-page WordPress website and a large WooCommerce website are not going to behave the same way.

This is why, in my opinion, freelancers should never buy hosting based only on:

“How many websites can I host?”

Also ask:

What resources will those websites actually use?


91% Storage Was Free, So Why Was My Hosting Showing 82% Used?

This was the exact point where I understood the difference.

My dashboard had two different circles.

Disk Usage

Around 9% used.

Looks excellent.

Files and Directories/Inodes

Around 82% used.

Now the situation looks completely different.

Both numbers are correct.

There is no contradiction.

I simply had plenty of disk space but a much higher number of individual files and directories.

This is why I now believe every freelancer hosting multiple websites should regularly check both numbers.

Not just storage.


Is Hostinger Hiding the Inode Limit?

Now let me be fair.

I am writing a review based on my real experience.

But I don’t want to create fake controversy.

So no, I am not saying:

“Hostinger secretly created a fake limit.”

That would not be correct.

Hostinger provides information about inode limits and resource limits in its support documentation and dashboard. The important lesson from my experience is something different: many buyers may focus mainly on website count and disk space without understanding how separate limits can affect real-world capacity. Hostinger also advises users above 80% usage to investigate and reduce unnecessary inode usage where possible.

My issue is more about how beginners think while buying hosting.

When you see:

HOST 100 WEBSITES

that is a big and easy number to understand.

When you see:

600,000 INODES

many beginners may not even know what it means.

I didn’t give it much attention before this experience either.

Now I do.


Can Hostinger Business Hosting Really Handle 100 WordPress Websites?

Now this is where I want to be very careful.

I cannot say:

“No, it cannot handle 100 WordPress websites.”

Because websites are different.

I also cannot say:

“Yes, every person can easily host 100 WordPress websites.”

That would also be wrong.

My own experience shows why.

I am currently hosting 22 mostly WordPress websites.

My inode usage is already around 82%.

But another person may have 22 completely different websites with a different number of files.

Their usage may be lower.

So my answer is:

It depends on the type of websites.

You need to consider:

  • How many files each website has
  • How many plugins you use
  • How many images are uploaded
  • Whether image thumbnails are generated
  • Cache files
  • Old backups
  • Staging websites
  • CPU usage
  • RAM usage
  • Database usage
  • Traffic

The website limit alone cannot answer the full question.


My Real Verdict on Hostinger Business Shared Hosting for Multiple WordPress Websites

Now let me give you my honest opinion.

I am not going to say Hostinger is bad because I discovered an inode limit.

Every hosting environment has resource limits.

The important thing is understanding them.

For me, Hostinger has been useful because I manage multiple websites from one account.

The dashboard makes it possible to check important resource usage.

And in my case, checking that dashboard is exactly how I discovered this problem before reaching 100%.

But if you are a freelancer like me and your plan is to keep adding client WordPress websites, then I strongly recommend checking more than the number of website slots.

Before buying or upgrading, look at:

  • Website limit
  • Disk space
  • Inodes
  • CPU
  • RAM
  • I/O
  • Database limits
  • Backup options
  • Upgrade options

Because your first limit may not be the one you expect.

For me, it was not disk space.

It was inodes.


What Happens If You Reach the Inode Limit?

This is another reason I decided to investigate my account now.

I don’t want to wait until my inode usage reaches 100%.

According to Hostinger’s documentation, once the inode limit is reached, the account can be unable to create additional files or directories even if disk space is still available, and websites may not work properly. Their guidance for high inode usage includes checking unnecessary files, old backups, staging environments, unused plugins/themes and cache or redundant files.

That means I need to understand what is consuming my files before I reach the limit.

And this brings me to my next experiment.


My Next Step: I Am Going to Find Where My 491,348 Files Are Actually Hiding

This article is based on a real discovery.

But I don’t want to make up the next part.

I want real proof.

My next job is to find out exactly which folders are consuming the highest number of inodes.

I want to check:

  • Which WordPress websites have the most files?
  • Are cache folders responsible?
  • Are old backups responsible?
  • Are image uploads creating a huge number of files?
  • Are unused websites still sitting on my hosting?
  • Are there old staging websites?
  • Are unused plugins or themes adding unnecessary files?

Once I find the answer, I will update this article.

And honestly, I think that update will be even more interesting.

Because anyone can explain:

“What is an inode?”

But finding out where 491,348 real files on 22 WordPress websites are actually coming from is a real case study.

That is something I want to investigate properly.


How I Am Going to Reduce My Inode Usage

I am not going to randomly enter File Manager and start deleting folders.

Please don’t do that either.

My plan is simple.

First:

Find the folders with the highest number of files.

Then:

Understand what those files actually do.

Then:

Check whether they are still needed.

I will specifically look for things like:

  • Old backups
  • Unused websites
  • Test websites
  • Old staging environments
  • Cache files
  • Unused themes
  • Unused plugins
  • Redundant files

Hostinger also recommends identifying unnecessary backups, old staging environments, unused plugins/themes, cache and redundant files when inode usage is high, rather than deleting important files blindly.

If I can safely reduce unnecessary files, great.

If I genuinely need all those files because my business has grown, then upgrading later may make more sense.

But first:

Understand the problem.

Then:

Choose the solution.


Is Hostinger Good for Freelancers and Web Designers?

From my own experience, I would say this depends on how you work.

If you are a freelancer managing a few websites, a good shared hosting plan can be a very practical starting point.

If you manage many WordPress websites like me, then it becomes even more important to monitor your resources.

Personally, I would not reject a hosting company simply because there is an inode limit.

Instead, I would compare the complete resources offered by the plan.

For example:

How many websites?

Okay.

But what about:

How many inodes?

What about:

CPU?

What about:

RAM?

What happens when my client websites grow?

Can I upgrade?

These questions are more important to me now than they were before I discovered my own 82% inode usage.

If you are checking current plans, prices or resource limits, don’t rely only on my older dashboard because hosting plans can change over time. Check the current details directly on Hostinger’s official hosting plans and compare them with your actual needs. Hostinger’s support documentation also says the most up-to-date plan information should be checked in hPanel because limits can change.


My Personal Affiliate Disclosure

Some links on this website may be affiliate links.

That means if you purchase through my link, I may earn a commission at no extra cost to you.

But I want to make one thing clear.

This article was not written because someone paid me to create a fake review.

I am actually using this hosting account.

The numbers shown in this article came from my own dashboard.

22 websites.

17.27 GB storage used out of 200 GB.

491,348 inodes used out of 600,000.

Around 82% inode usage.

This is my real experience.

And in my opinion, if I am recommending a hosting plan through an affiliate link, then I should also talk about the limitations and things I discover while actually using it.

Otherwise, what is the point of calling it a review?

Want to check the current Hostinger plans yourself?

Get additional 10% Discount . – Apply Coupan Code DOSGROUP

Don’t just check the price.

Before purchasing, also check the current technical limits and choose according to the number and type of websites you actually plan to run.


Frequently Asked Questions

Is Hostinger Business Hosting shared hosting?

Yes, the Business hosting plan discussed in this article is part of a shared web-hosting environment rather than a dedicated server where all server resources belong exclusively to one user. The exact current plan names and limits can change, so check Hostinger’s current plan details before purchasing.


How many WordPress websites can I host on Hostinger Business Hosting?

There is no single answer for every user.

My own plan allowed up to 100 websites, but I discovered that another resource—inodes—was already around 82% used with 22 mostly WordPress websites.

The actual number you can comfortably host depends on how heavy your websites are and how many resources they use.


What is the inode limit in Hostinger?

An inode is associated with a file or directory on the hosting account. Each file and directory counts toward the inode limit. If the limit is reached, new files or directories may not be created even if disk space is still available.


Can I have free hosting storage but still reach the inode limit?

Yes.

My own dashboard is the example.

I had around 91% disk storage free, but my inode usage was already around 82%.

Disk space and inode usage measure different things.


Why do WordPress websites use so many inodes?

WordPress websites contain core files, themes, plugins, uploads and other generated files. Image sizes, cache, backups, staging websites and additional installations can further increase the total number of files.

The actual cause should be checked folder by folder instead of assuming one reason for every website.


Is 82% inode usage dangerous?

It does not automatically mean your hosting account will stop working immediately.

But I personally consider it a warning worth investigating, especially when I am planning to add more WordPress websites.

I would rather understand the reason at 82% than wait until I reach 100%.


How can I reduce inode usage in shared hosting?

First identify which directories contain the most files.

Then check whether there are unnecessary:

  • Backups
  • Cache files
  • Old staging websites
  • Unused websites
  • Unused plugins
  • Unused themes
  • Redundant files

Don’t randomly delete WordPress files without understanding what they do.


Final Thoughts: The Number “100 Websites” Does Not Tell You the Whole Story

When I purchased this hosting plan, one of the biggest numbers I noticed was:

Host Up to 100 Websites

As a freelancer, I liked that.

I thought I had plenty of room to grow.

And technically, I still have only 22 websites.

But then I opened my Resource Usage dashboard.

And I discovered something I had never really thought about before.

My disk usage:

Only 9%.

My inode usage:

Already 82%.

That’s when I understood something important.

A hosting account does not have only one limit.

You may have:

  • Plenty of storage left
  • But high inode usage

Or you may have:

  • Plenty of inode capacity
  • But another resource reaching its limit

So next time you buy hosting, don’t simply ask:

“How many websites can I host?”

Ask:

“How many websites like mine can this hosting plan realistically handle?”

Because those are two completely different questions.

My Hostinger Business Hosting plan allowed me to host up to 100 websites.

But my real experience with 22 mostly WordPress websites showed me that I needed to watch another limit much earlier than expected.

And honestly, this is why I like checking real dashboards more than reading marketing numbers.

Marketing tells you what a plan can offer.

Real usage tells you what happens when you actually start using it.

I am now going to investigate exactly where my 491,348 files are coming from.

When I find the answer, I will update this article with my actual folder data and screenshots.

And maybe the next lesson will be even bigger.

Because right now, I have discovered the limit.

My next job is to find the real culprit.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top