File Upload Limit Problems on Shared Hosting: Why They Happen and How to Fix Them 

Key highlights 

• Recognize that shared hosting caps upload size to protect server resources split across hundreds of accounts. 

• Identify the smallest value among upload_max_filesize, post_max_size and memory_limit, since that one sets your real ceiling. 

• Check your current limit on the Media > Add New screen before you touch any setting. 

• Raise the limit yourself through your control panel’s PHP editor, no code or support ticket required. 

• Upgrade to a higher-resource plan once your control panel won’t raise the limit any further, since PHP edits can’t fix a plan-level ceiling. 

You’re uploading a product photo, a plugin or a client’s video file and WordPress stops you cold: “The uploaded file exceeds the upload_max_filesize directive in php.ini.” You bump the number in one setting, try again and the same error comes back. 

File upload limit problems on shared hosting rarely come down to one setting. Three PHP values interact, and your server or hosting plan can cap the ceiling no matter what you change inside WordPress. Fix the wrong one and you waste an afternoon guessing. 

This guide shows you which layer is actually blocking your upload, how to check it, how to raise it and when no PHP edit will help because you’ve hit a plan-level ceiling instead. 

Quick summary: What’s setting your upload limit 

Five layers can cap your upload, and the smallest value among them wins even if you raise the others. Scan this table before you change anything, then jump to the section that matches your situation. 

Layer	What it controls	Where you fix it
upload_max_filesize	Maximum size of one file	PHP configuration
post_max_size	Maximum size of the entire form submission	PHP configuration
memory_limit	Memory available to process the upload	PHP configuration
Server-level cap	Hard request-size ceiling set by Apache or nginx	Server configuration, host-controlled
Hosting plan ceiling	Maximum your account can be raised to	Plan-level, host-controlled

The next section breaks down why shared hosting sets these limits in the first place, then walks you through checking your current values and raising them one layer at a time. 

Why file upload limit problems happen on shared hosting 

Your shared hosting account sits on the same server as hundreds of other websites. All of you draw from one resource pool: 

• CPU capacity for processing requests 

• Memory for running scripts, including uploads 

• Disk I/O for reading and writing files 

A single unrestricted upload could tie up enough of that pool to slow down, or crash, every other site on the machine. That’s why your host caps upload_max_filesize, post_max_size and memory_limit at conservative defaults. 

The limit isn’t a WordPress rule. It’s a resource-protection measure built into the shared environment itself. WordPress can only work within whatever ceiling PHP allows it, which is why raising a setting inside WordPress sometimes changes nothing. 

VPS and dedicated hosting sidestep most of this problem. You get reserved resources instead of a shared pool, so your host can set the ceiling higher or hand you full control over it. Shared hosting trades that headroom for a lower price and keeps the limit tight to protect everyone else on the server. 

Once you know the cap exists to protect shared resources, not to restrict your site specifically, the next step is finding out exactly which PHP value is capping you right now. 

Check your current upload limit before you troubleshoot 

Before you touch any PHP setting, find out what your actual ceiling is right now. Guessing wastes time you don’t need to spend. 

To check it: 

• Log into your WordPress admin dashboard 

• Go to Media, then Add New 

• Look below the upload area for “Maximum upload file size” 

That number already reflects the smallest of upload_max_filesize, post_max_size and the memory available for the upload to process. WordPress doesn’t show you all three values separately here, only the effective result. 

If you need the individual values, not just the combined limit, check your hosting control panel’s PHP settings page or a plugin like Site Health under Tools. That breakdown tells you which specific value to raise, instead of adjusting all three and hoping one of them was the bottleneck. 

Fix the file upload limit exceeded error on shared hosting 

You have four ways to raise the limit, and which one works depends on how your hosting account is configured. Start with the control panel method. It requires no code and no file editing. 

1. Use the MultiPHP INI Editor in your control panel 

Most shared hosting control panels include a PHP settings editor built for exactly this. 

• Log into your hosting control panel 

• Open the Advanced tab, then MultiPHP INI Editor 

• Select your domain from the dropdown 

• Raise upload_max_filesize, post_max_size and memory_limit in Basic Mode 

• Click Apply 

This works for most accounts and takes under two minutes. 

2. Edit php.ini through File Manager 

If your account doesn’t expose these settings in Basic Mode, edit the php.ini file directly. 

• Open File Manager in your control panel 

• Locate php.ini in your site’s root directory 

• Right-click and select Edit 

• Update upload_max_filesize and post_max_size to your target value 

• Save the file 

Some accounts run FastCGI PHP, which ignores a root-directory php.ini entirely. If your changes don’t take effect after saving, check your PHP handler type before troubleshooting further. 

3. Add the limit through .htaccess (Apache only) 

This method only works on Apache servers with mod_php enabled. Add these lines to your .htaccess file: 

php_value upload_max_filesize 64M 
php_value post_max_size 64M 
php_value memory_limit 256M  

If your site returns a 500 error immediately after saving, your server isn’t running the PHP handler this method requires. Remove the lines and use the MultiPHP INI Editor instead. 

4. Set it in wp-config.php or functions.php 

This method works as a fallback, not a first choice, since many hosts block PHP from overriding server-level values this way. Add this near the top of wp-config.php: 

@ini_set('upload_max_filesize', '64M'); 
@ini_set('post_max_size', '64M');  

If the limit doesn’t change after adding this, your host has disabled runtime overrides and one of the first three methods is your only option. 

Pro tip: Set post_max_size and memory_limit higher than upload_max_filesize, not equal to it. WordPress needs headroom beyond the file itself to process the upload, so matching all three values exactly causes the upload to fail even though it looks like you raised the limit correctly. 

Also read: How to Increase PHP Limits 

When the fix doesn’t stick: hitting your host’s hard ceiling 

Sometimes none of the four methods change your upload limit, no matter how high you set the value. That’s not a mistake in your configuration. It means you’ve hit a ceiling your host controls at the plan level, one that individual account settings can’t override. 

A few signs point to this: 

• The MultiPHP INI Editor accepts your new value, but Media > Add New still shows the old limit 

• Every method in the previous section returns the same unchanged number 

• Support confirms the value you’re requesting exceeds what your plan allows 

This ceiling exists for the same reason the default limit does. Your host caps how far any single shared account can be raised, because uncapped accounts would let one site consume resources that hundreds of others depend on. No .htaccess trick or wp-config edit changes a limit enforced above the PHP layer. 

If you’ve confirmed this is your situation, a higher-resource hosting plan is the only real fix. Look for a plan built around dedicated or reserved resources rather than a shared pool, since that’s what actually raises the ceiling, not just a bigger number on the same shared infrastructure. 

Bluehost’s hosting lineup scales from shared plans into VPS and Dedicated hosting for this reason. You can move up without switching providers once your account genuinely needs more room. 

Final thoughts 

File upload limit problems on shared hosting look like a WordPress bug, but they’re a resource decision your host makes to protect every account on the server. Once you know which layer is actually capping you, whether it’s upload_max_filesize, post_max_size, memory_limit or a ceiling set above all three, the fix takes minutes, not guesswork. 

Start by checking your current limit, not by editing settings blind. Work through the four fix methods in order, beginning with the control panel editor, since it needs no code and resolves most cases on its own. If none of them move the number, you’ve found a plan-level ceiling, not a configuration mistake and no amount of file editing changes that. 

Ready to stop working around your host’s limits? Bluehost Web Hosting gives you control panel access to these PHP settings from day one, plus a scalable path to VPS or Dedicated hosting when your site genuinely outgrows a shared plan. 

FAQs