Database Limits in Shared Hosting: Size, Tables and Performance Explained

Key highlights

• Learn what database limits are in shared hosting and why they exist to protect server performance.
• Understand how size caps and table limits work and what happens when your site reaches them.
• See how connection limits and shared resources affect your site’s load speed, checkout and search functionality.
• Spot the warning signs that show it’s time to upgrade your hosting plan.
• Get practical tips to optimize your database and stay within limits longer.

Database limits in shared hosting are caps your provider places on your databases. They set boundaries on how many databases you can create and how large each one can grow. They also govern how many tables your database can hold and how many simultaneous database connections your site can use.

These caps prevent any single account from hogging resources on a server that many customers share. Here’s what surprises most people: Many of these limits are set by your hosting provider, while technical limits can also depend on the database engine, server configuration and filesystem.

This guide walks through the database limits that matter most for your site and helps you plan for growth.

What are database limits in shared hosting?

Database limits in shared hosting are caps your provider sets to ensure everyone on the server gets fair access to resources. Common database limits include:

• Number of databases: How many separate databases your plan allows.
• Size per database or account: How much data each database can store, plus your total storage across all databases.
• Tables per database or account: How many tables your site can create before hitting the maximum.
• Concurrent MySQL connections: How many simultaneous connections your website can make to the database while processing requests.

Exact limits vary by hosting provider and plan. Check your plan’s current documentation rather than relying on a single industry-wide number.

Bluehost database limits at a glance:

Bluehost currently recommends staying within 5,000 tables or 10 GB of total database usage per hosting plan. A single database should remain within 5,000 tables or 5 GB. Check Bluehost’s current documentation for the latest limits and policies, as they may change over time.

Database limits are just one piece of the larger puzzle of shared hosting resource limits, which also include CPU, memory and storage.

Understanding these limits helps you plan capacity and spot bottlenecks before they affect your visitors. Now let’s look at the specific limits that shape how your database operates day to day.

Database size limits in shared hosting

Database size limits in shared hosting control how large each database can grow and how much total storage your account can use. Most providers set their own threshold based on the hosting plan and server environment.

1. Typical size caps on shared plans

Shared hosting providers may limit database usage per database, per account or both. The exact threshold depends on the provider and plan. Plans that advertise unlimited storage or databases still include fair-use policies and filesystem restrictions in their terms. In practice, unlimited plans usually have boundaries that become clear as your database grows.

2. Where size limits actually come from

MySQL does not set one universal maximum size for an entire database. In practice, database and table sizes can be limited by the storage engine, tablespace configuration, filesystem, operating system, available storage and your hosting provider’s policies.

On shared hosting, your provider may set limits well below these technical maximums to manage resources across accounts. That makes your hosting plan’s documented limits the ones that matter most in practice.

3. What happens when you exceed a database size limit

Exceeding your hosting provider’s recommended database limits can affect site performance and reliability. You may notice slower load times, database-related errors or downtime, depending on how your provider enforces its resource limits and how heavily your site uses the database.

Example: A growing WooCommerce store can accumulate product data, orders, customer information and plugin data over time. As the database becomes larger and more resource-intensive, performance issues may become more noticeable.

If your database exceeds your provider’s limits, check what is consuming space and remove or archive unnecessary data where appropriate. If your site consistently needs more resources than your shared hosting plan supports, consider moving to a hosting environment better suited to that workload.

4. How to check your current database size

Most hosting control panels show database size in the MySQL or phpMyAdmin section. In phpMyAdmin, the home screen lists each database with its current size. You can also run a simple SQL query to check size:

SELECT 
    table_schema AS "Database", 
    ROUND(SUM(data_length + index_length) / 1024 / 1024, 2) AS "Size (MB)"
FROM 
    information_schema.TABLES
GROUP BY 
    table_schema;

Checking database size regularly helps spot growth trends before hitting a cap. Set a reminder to review database size monthly, especially if running an eCommerce site or accepting user-generated content.

Keeping databases within their recommended size range and monitoring total usage helps avoid these disruptions. Size is only part of the picture, though. The number of tables your database can hold also plays a critical role in how your site operates.

Database table limits in shared hosting

Table limits cap how many tables your hosting account can create. The exact limit varies by hosting provider and plan. These caps exist to prevent filesystem strain and protect server performance, not because MySQL itself restricts table counts.

1. Why providers set table limits

Databases store data in files on the server’s filesystem, and those files consume inodes. An inode is a small record the system uses to track a file or folder. How many files a table uses depends on the storage engine and configuration, so a table does not always map to a single file.

Providers still enforce table caps for a practical reason. Accounts with very large numbers of tables and files can exhaust inode allowances and strain the server, even when disk space remains available.

2. What MySQL actually allows

MySQL and its InnoDB engine set no practical table-count restriction, and MySQL’s documentation notes InnoDB supports up to about 4 billion tables. That means the table limit you encounter on shared hosting is generally a hosting-level restriction rather than MySQL’s practical table ceiling.

3. Which sites hit table limits first

WordPress sites that use many plugins or extensions that create their own database tables may approach table limits sooner. Some plugins add custom tables to store specialized data, while others use existing WordPress tables.

Complex WooCommerce or membership sites may also accumulate additional tables when extensions introduce their own data structures. Checking which plugins create custom tables can help you understand and manage your database usage before you approach your hosting limit.

Understanding table limits helps you plan your site’s setup and identify unnecessary database usage before it becomes a problem.

Now that you know how size and table limits work, the next question is how they actually impact your visitors’ experience when your site is under load.

How database limits affect performance in shared hosting

Database limits impact how fast your site responds to visitors. However, it alone does not determine how fast a website performs. Query efficiency, indexing, database activity and the resources available to process those requests also matter.

1. Concurrent connection limits and traffic spikes

Your website may need multiple database connections as it handles dynamic requests. Hosting providers may limit the number of simultaneous database connections available to an account. Because providers do not always publish this figure, check your plan documentation or contact support for the limit that applies to your account.

If your site reaches this limit during a traffic spike, some database connections may fail and visitors may see errors or slow page loads.

2. Shared resource contention

On shared hosting, your database competes with other accounts for CPU, RAM and disk access. When neighbors run heavy queries, your site can show slow load times, sluggish checkout and occasional timeouts. Your database performance depends on both your own queries and how busy the rest of the server is.

A nearly full database does not slow queries by itself. Slowdowns come from connection limits, CPU and RAM pressure, and poorly optimized queries. Exceeding a storage limit may cause errors or affect database operations, depending on how your hosting provider enforces the limit.

3. Which sites feel the impact first

Sites that handle payments or heavy traffic generally feel these effects first, since they run more database queries per visit. eCommerce stores, membership sites and forums may reach database or resource limits sooner than simple blogs because they often handle more dynamic database activity.

Recognizing these performance patterns helps identify when your current plan no longer meets your needs. Before you react, it helps to match the symptom you are seeing to the limit behind it.

Which database limit are you actually hitting?

Different symptoms point to different limits, and the fix depends on which one you have reached. Use this table to move from what you see to what to check and what to do next.

Symptom	Possible cause	What to check	Next action
“Too many connections” during traffic spikes	Concurrent connection cap	Peak concurrent connections vs your plan’s limit	Review query efficiency and caching, then assess hosting resources if the issue keeps returning
Writes or updates fail, checkout or forms error out	Database size or storage quota	Current database size vs your hosting limit	Identify what is consuming storage before removing or archiving data
New tables fail to create	Table count limit	Current table count vs your hosting limit	Check and remove unused tables or plugins that created them, then review your hosting limits
Pages slow under normal traffic, high time to first byte	CPU, RAM or disk I/O contention	Resource usage graphs in your control panel	Optimize queries and indexes, then consider dedicated resources
Large database import fails partway	Import size or runtime limit	phpMyAdmin import cap and script runtime	Import over the command line or ask support

These symptoms can have several causes. Use them as starting points for investigation rather than proof that a particular database limit has been reached. Once you identify which limit is causing trouble, you can optimize your database and extend the life of your current plan.

How to optimize your database and stay within limits?

Extending the life of your shared hosting plan means keeping your database lean and efficient. A few regular maintenance tasks prevent bloat and help stay under caps longer.

1. Clean up old data regularly

Carefully check and remove expired temporary data, unnecessary post revisions and spam comments. WordPress can accumulate this data over time, increasing database size. However, before deleting orders, customer records or other important data, check your accounting, reporting, returns and legal retention requirements and create a backup first.

2. Optimize database tables

Tables can accumulate unused space over time as you add, update and delete records. Optimizing the tables can help reclaim this space and keep the database organized.

In phpMyAdmin, select a table and choose “Optimize table” from the dropdown. Make sure to run it after taking a backup and only when you notice fragmentation. Large tables may lock during optimization, so skip routine runs on your biggest tables.

3. Use caching to reduce queries

Page caching serves generated pages without running the full application, while object caching stores frequently requested database results. Both can reduce database activity and lower the number of queries your site needs to process. This can reduce database workload, especially during busy periods.

4. Limit plugin use

Some plugins add custom database tables or additional database queries. Review your plugins regularly and remove any you no longer use. Choose lightweight alternatives when possible, and avoid plugins that create dozens of tables or run heavy queries.

5. Archive old content carefully

Review old logs and other data that no longer needs to remain in your active database. For records such as orders or user data, only archive them using methods supported by your application or plugins that preserve data relationships. Before archiving or removing any data, check your retention and privacy requirements, create a backup and make sure you can restore the information if needed.

These optimization steps buy time and improve performance, but they are not a permanent fix. When your site consistently pushes limits even after optimization, it is time to consider an upgrade. Moving to VPS or dedicated hosting can provide more isolated or dedicated resources and greater control than shared hosting.

If you’re weighing an upgrade or starting fresh with a provider that understands database-driven sites, here’s what Bluehost Web Hosting offers to support your database needs from day one.

How Bluehost Web Hosting supports your database needs

Our web hosting includes MySQL databases that you can manage through phpMyAdmin. We currently recommend the following database limits:

• Up to 5,000 tables or 10 GB of total database usage per hosting plan.
• Up to 5,000 tables or 5 GB per individual database.

Our Web Hosting plans also include:

• NVMe SSD storage.
• Weekly website backups to help you restore your data if something goes wrong.
• phpMyAdmin access for direct database management and optimization.
• 24/7 chat support for hosting and database-related questions. Phone support varies by plan and international calling charges may apply.

If your database usage eventually outgrows a shared environment, we also offer VPS hosting and dedicated hosting with additional resources. The right next step depends on your site’s actual database and workload requirements.

Final thoughts

Database limits in shared hosting are provider policies that protect performance on a server shared with others. Once you know your database size, table and connection caps, you can optimize queries and storage, then upgrade when the warning signals keep returning.

Bluehost Web Hosting gives you a managed starting point with recommended database headroom and clear paths to advanced plans. It’s built to grow with your site, so you can start small and expand as your traffic and catalog do.

Ready to launch your site with reliable database support? Explore Bluehost Web Hosting plans and find the right fit for your site’s current needs.

FAQs