Increase WordPress Max Upload File Size: Full Guide

Why Does WordPress Limit Your Upload File Size in the First Place?

Here’s the short answer: WordPress isn’t actually the one blocking your upload. The limit you’re hitting lives on your server, set by PHP, and WordPress simply inherits it. That’s why you can’t fix it from inside WordPress alone — you have to go one layer deeper.

This analysis is informed by hands-on experience designing and operating production systems, including web hosting platforms, AI-driven automation workflows, and high-traffic digital services used by real businesses across multiple markets.

What Exactly Is ‘upload_max_filesize’?

upload_max_filesize is a PHP directive that caps how large a single file can be when uploaded through your site — whether that’s a product image, a PDF invoice, or a video for your portfolio. If you’ve ever tried uploading a large file in your WordPress Media Library and got a vague “file exceeds the maximum upload size” error, this setting is almost always the culprit. There’s a related setting called post_max_size that also needs adjusting alongside it, which is where a lot of guides confuse people.

Who Sets This Limit — WordPress or Your Host?

Your hosting provider sets the default value, not WordPress. On shared hosting especially, providers keep this number conservative — usually just a couple of MB — because one account uploading huge files can eat up server memory and disk I/O that’s shared with hundreds of other websites on the same box. It’s resource protection, not laziness.

If you’re a freelancer, blogger, or small business owner in Pakistan running your first self-hosted site, this is worth understanding early. Some hosts lock these settings down tight with no easy way to change them. Others, like HostBreak.com, make it straightforward to adjust via cPanel or support — which matters a lot once you’re uploading high-res portfolios, podcast files, or product catalogs.

How Do You Check Your Current Max Upload Size in WordPress?

The fastest way is to open Media > Add New in your WordPress dashboard — the number you’re working with is printed right there, under the upload box, as “Maximum upload file size.” No plugins, no guesswork, no digging through files. That single line tells you exactly what your server will currently accept before you even try uploading anything.

Checking via Media > Add New

1. Log in to your WordPress admin dashboard.
2. Go to Media > Add New.
3. Look just below the drag-and-drop upload area — you’ll see something like “Maximum upload file size: 2 MB” or “64 MB.”

That’s your real-world ceiling, as enforced by your server, right now.

Checking via Site Health Tool

If you want more detail — or you’re troubleshooting why a theme or plugin is complaining about upload limits — use WordPress’s built-in diagnostics instead.

1. Go to Tools > Site Health.
2. Click the Info tab.
3. Expand the Server section.
4. Scroll to find upload_max_filesize and post_max_size listed together.

This view is handy because it shows both values side by side, which matters more than most tutorials let on.

What the Numbers Actually Mean (MB vs post_max_size)

Here’s the part that trips people up: upload_max_filesize controls the size of one individual file, while post_max_size controls the total size of everything submitted in that request — including the file, plus any form data riding along with it. If post_max_size is set lower than upload_max_filesize, your upload will still fail even though the file itself is technically “small enough.”

As a rule of thumb, post_max_size should always be equal to or slightly larger than upload_max_filesize. Mismatched values are one of the most common reasons people raise one setting, still get an error, and assume nothing worked.

If you’re on shared hosting and can’t see these values changing even after editing files yourself, that’s usually a hosting restriction — not a WordPress problem. HostBreak.com’s support team can check and adjust these PHP limits for you directly, which saves a lot of back-and-forth guessing on your end.

What Are All the Ways to Increase the Upload Limit in WordPress?

There are four real ways to raise WordPress’s upload limit: editing functions.php, editing .htaccess, creating or editing php.ini, and using a plugin. None of them is guaranteed to work on its own — if your host has set a hard server-level cap, some of these methods will quietly do nothing, no matter how correctly you’ve written them. Let’s go through all four so you know exactly which one applies to your situation.

Editing functions.php

This is the method most tutorials lead with, so it’s worth trying first since it needs no server access — just your theme files.

1. Go to Appearance > Theme File Editor (or connect via FTP) and open your active theme’s functions.php.
2. Add this near the top: @ini_set( 'upload_max_size', '64M' ); @ini_set( 'post_max_size', '64M' ); @ini_set( 'max_execution_time', '300' );
3. Save the file and re-check the limit under Media > Add New.

The catch: ini_set() can only change PHP settings that are allowed to be modified at runtime. Many hosts lock upload_max_filesize and post_max_size at the server level, which means this snippet runs without error but simply has no effect. If the number doesn’t change, your host has a hard cap — move to the next methods, or contact support.

Editing .htaccess (Apache)

This works only if your server runs Apache — it does nothing on Nginx or LiteSpeed, so check with your host first.

1. Open .htaccess in your site’s root folder via FTP or File Manager.
2. Add these lines at the bottom: php_value upload_max_filesize 64M
php_value post_max_size 64M
php_value max_execution_time 300
php_value max_input_time 300
3. Save, reload the site, and confirm it still loads normally — a wrong directive here can trigger a 500 error, so keep a backup of the original file.

Same limitation applies: if your hosting plan enforces a fixed PHP ceiling, .htaccess directives get ignored or throw an “unable to set” error.

Creating or Editing php.ini

This is the most reliable of the DIY methods, but it depends entirely on whether your host permits custom php.ini files for your account — shared hosting plans often don’t.

1. Check if a php.ini already exists in your root directory. If not, create a blank file named php.ini.
2. Add: upload_max_filesize = 64M
post_max_size = 64M
max_execution_time = 300
3. Upload it to your root directory and refresh Media > Add New to see if it took effect.

On many shared setups this file is ignored entirely because the hosting environment doesn’t read custom php.ini per account. This is precisely the kind of limit HostBreak.com’s support team can adjust directly from the server side — no guessing which method your stack even supports.

Using a Plugin (and Why It’s a Last Resort)

Plugins like “Increase Upload Max Filesize” give you a dashboard slider instead of editing code, but they work by calling the exact same ini_set() functions under the hood.

1. Install and activate the plugin from Plugins > Add New.
2. Go to its settings page, usually under Media or Settings, and set your desired limit.
3. Save and verify the new value on the upload screen.

If functions.php couldn’t override the limit, the plugin won’t either — it’s hitting the same server wall, just with a nicer interface. Treat it as a convenience for environments that do allow runtime changes, not a fix for a hard cap.

If you’ve tried all four and the number refuses to budge, that’s not a WordPress issue — it’s a hosting configuration issue. HostBreak.com’s support team can raise these PHP limits for you directly on the server, and with local billing through JazzCash and EasyPaisa, sorting out a hosting-level fix doesn’t have to mean a long, confusing support ticket.

Why Does the Fix Not Work Even After Editing the Files?

Most failed fixes happen because your shared hosting plan enforces a server-wide hard cap that no amount of code editing can override. You can edit functions.php, .htaccess, and php.ini all you want — if the hosting environment itself has the limit locked, WordPress has no way around it. Here’s how to confirm that’s what’s actually happening to you.

Hard Limits Set at the Server/Hosting Level

Shared servers host hundreds of accounts on the same machine, so hosts often cap upload_max_filesize and post_max_size at the server config level to keep resources fair for everyone. When that’s the case, your overrides get silently ignored — no error, no warning, just no change. The fastest way to check: create a file called info.php with <?php phpinfo(); ?>, upload it to your root folder, and visit it in your browser. Look for “Loaded Configuration File” and the actual upload_max_filesize value. If it still shows the old number after all your edits, that’s your host’s hard ceiling, not a mistake in your code.

Caching and CDN Interference

If you’re running a caching plugin or a CDN like Cloudflare in front of your site, you might be looking at a cached version of the Media > Add New screen or an old PHP info snapshot. Clear your site cache, purge the CDN cache, and hard-refresh the browser (Ctrl+Shift+R) before you conclude the fix didn’t work. It’s a small thing, but it wastes a lot of people’s time chasing a “bug” that’s really just a stale cache.

Wrong File Being Edited (Multiple php.ini Locations)

Servers can have several php.ini files — one for the server globally, one per PHP version, one per domain in some control panels. If you edited a copy that isn’t the one actually loaded for your site, nothing changes. The phpinfo() trick above tells you exactly which file is loaded, so you’re not guessing.

If you’ve checked all three and the number still won’t move, it’s time to stop troubleshooting code and start asking your host directly — or consider whether your current host is giving you enough control in the first place. That’s exactly where we’re headed next.

Is Your Hosting Provider the Real Reason You’re Stuck? (What Most Tutorials Don’t Tell You)

Yes — in most cases, if your upload fix isn’t sticking, it’s because your hosting plan was built to cap uploads low on purpose, not by accident. Nobody tells you this upfront because it doesn’t sound great in a sales pitch, but understanding it saves you hours of wasted troubleshooting.

Why Shared Hosting Often Hard-Caps Uploads Deliberately

On a shared server, your WordPress site sits alongside hundreds of other accounts pulling from the same CPU, RAM, and disk I/O pool. A handful of users uploading huge video files or running bulk media imports can slow things down for everyone else on that box. So hosts set conservative server-wide limits — often somewhere in the 2MB to 32MB range — as a blunt but effective way to prevent abuse and keep the shared environment stable. It’s a legitimate resource-management decision. The problem is most budget hosts don’t disclose it clearly when you sign up, so you only discover the ceiling exists when your upload fails and your own code edits mysteriously do nothing.

How to Tell If It’s a Hosting Limit vs a Plugin Conflict

Run the phpinfo() check from earlier in this guide first — that tells you the actual loaded value, not what you think you set. If the number refuses to budge no matter what you change in functions.php, .htaccess, or php.ini, that’s a host-level lock. A plugin conflict looks different: uploads might fail inconsistently, throw a specific error from a security or media plugin, or work fine in one browser/theme but not another. If disabling plugins one by one changes the behavior, it’s a plugin. If nothing you touch in WordPress changes the phpinfo() number, it’s your hosting environment, full stop.

What a Pakistani Site Owner Should Actually Ask Their Host

Don’t waste time explaining your whole backstory to support — ask a direct, specific question and get a direct answer. Use this script:

• “What is my current upload_max_filesize and post_max_size?”
• “Can these be raised on my current plan, and if so, by how much?”
• “If not, is this a hard limit tied to my plan tier, or is it adjustable with a support ticket?”

A host that answers this clearly and quickly — without pushing you straight into an upgrade — is one worth staying with. If you’re currently on a host that stonewalls this or takes days to reply over a support ticket, that’s a real signal. At HostBreak.com, our support team answers this kind of question directly over chat or ticket, in plain terms, with PKR billing and local payment options like JazzCash and EasyPaisa so you’re not stuck waiting on international payment processing just to upgrade a plan.

How Does HostBreak.com Make This Easier for Pakistani WordPress Users?

HostBreak.com fixes the upload-limit headache by giving you direct, click-based control over upload_max_filesize and post_max_size through cPanel — no editing php.ini by hand, no guessing which file actually takes effect, and no waiting days for a ticket reply if you get stuck. That’s really the whole thing most tutorials skip: you shouldn’t need to be a developer to raise a file upload cap on your own WordPress site.

Adjustable PHP Limits via cPanel (No Code Needed)

Every HostBreak.com hosting plan gives you access to cPanel’s MultiPHP INI Editor, which is the cleanest way to raise these limits without touching code at all.

1. Log in to your HostBreak.com cPanel account.
2. Open MultiPHP INI Editor under the Software section.
3. Select your domain from the dropdown.
4. Switch to the Editor Mode view for full control.
5. Find upload_max_filesize and post_max_size, and raise both — keep post_max_size equal to or slightly higher than upload_max_filesize, since it needs to cover the whole request, not just the file.
6. Click Save and re-run the phpinfo() check on your WordPress site to confirm the new values actually loaded.

Tip: if your plan’s dashboard doesn’t expose the field you need, that’s exactly the kind of thing to raise with support rather than fight with for an hour on your own.

Local Support in Urdu/English for Pakistani Site Owners

If the MultiPHP editor doesn’t show the option you need, or the value still won’t stick after saving, HostBreak.com’s support team will walk you through it over chat or ticket — in Urdu or English, whichever you’re comfortable with. You’re not describing your problem to someone in a different time zone who doesn’t get the context; you’re talking to a team that deals with WordPress media-upload issues for Pakistani businesses every day.

PKR Pricing with JazzCash, EasyPaisa, and Bank Transfer

Upgrading a plan to get more server headroom shouldn’t mean fighting with an international card gateway. HostBreak.com bills in PKR and accepts JazzCash, EasyPaisa, and direct bank transfer, so moving from a capped entry-level plan to something like the Standard Plan (PKR 800/mo) or Pro Plan (PKR 1,000/mo) is a two-minute payment, not a currency-conversion ordeal. If you’re currently stuck on a host that only takes foreign cards and routes every support question through a slow ticket queue, that friction alone is worth switching over.

This conclusion reflects patterns I have observed repeatedly while building and scaling real-world digital systems, where theoretical best practices often diverge from what is operationally sustainable at scale.

Final Thoughts: Choosing the Right Fix for Your Site

A functions.php snippet or a plugin can get you past an upload error today, but it won’t stop the problem coming back the next time you install a theme, switch hosts, or hit a bigger file. The real fix is having a hosting environment where you can open MultiPHP INI Editor, change upload_max_filesize and post_max_size yourself, and have it just work — no guesswork about whether your server will even honor a code-level override.

That’s really the whole point of this guide: code fixes are fine as a quick patch, but a WordPress hosting plan with proper cPanel access and support that picks up the phone is what prevents you from googling this same error six months from now. If you’re still stuck after trying everything here, that’s usually a sign your current host is restricting settings at the server level — and no snippet will get around that.