MultiPHP INI Editor: Change PHP Limits in cPanel Without SSH
You need to raise upload_max_filesize or bump memory_limit, but you're on shared hosting with no SSH access and editing php.ini directly isn't an option. Good news: cPanel has a tool built exactly for this, and most people never notice it because it's easy to confuse with MultiPHP Manager, which does something completely different.
MultiPHP Manager vs MultiPHP INI Editor - they're not the same tool
This mix-up sends more tickets our way than almost anything else PHP-related. Here's the split:
- MultiPHP Manager switches which PHP version (7.4, 8.1, 8.2...) a domain runs on.
- MultiPHP INI Editor changes the configuration values inside whichever PHP version you're already running - things like memory limits, upload size caps, and execution timeouts.
If your site says PHP Fatal error: Allowed memory size exhausted or a file upload dies partway through, you don't need a version change. You need the INI Editor.
Symptom: the errors that mean you need this tool
You'll usually land here after seeing one of these:
Fatal error: Allowed memory size of 134217728 bytes exhausted- "The uploaded file exceeds the upload_max_filesize directive in php.ini"
- A large import (WooCommerce products, a big media file, a plugin's bulk uploader) times out with no clear error, just a blank page or a 500
- WordPress admin shows a notice: "Increase memory limit" or "Increase the PHP execution time limit"
All four map to a PHP directive you can raise yourself in about two minutes, no ticket required.
Cause: shared hosting defaults are deliberately conservative
Hosts set default PHP limits low on purpose. A single account with an unbounded memory_limit or no max_execution_time can hog CPU and RAM that hundreds of other accounts on the same server are sharing. The defaults protect everyone else - they're just not tuned for a WooCommerce store doing a 2,000-product CSV import or a photographer uploading 40MB RAW files.
The fix isn't to fight the platform, it's to raise your own account's limits within whatever ceiling your hosting plan allows.
Fix: raise the limits with MultiPHP INI Editor
- Log into cPanel and go to Software → MultiPHP INI Editor.
- At the top, choose Editor Mode, not Basic Mode - Basic Mode only exposes a handful of toggles and hides the directives you actually need.
- From the domain dropdown, select the domain you want to change (each domain under your account can have its own values).
- Find and update the directives that matter most (see table below), then click Save at the bottom of the page.
| Directive | What it controls | Typical safe bump |
|---|---|---|
memory_limit | Max RAM one PHP process can use | 256M for most WordPress sites, 512M for heavy WooCommerce stores |
upload_max_filesize | Largest single file you can upload | 64M or 128M depending on your media |
post_max_size | Total size of a form submission - must be equal to or larger than upload_max_filesize | Match or exceed upload_max_filesize |
max_execution_time | How long a single PHP script can run before it's killed | 120 or 300 seconds for imports/exports |
max_input_time | How long PHP waits to receive input data (relevant for large form posts) | Match max_execution_time |
Changes apply immediately - no restart, no propagation wait. Reload the page or retry the upload/import right away.
The one mistake that undoes everything
If post_max_size is smaller than upload_max_filesize, uploads still fail even after you raise the upload limit, because the form submission itself gets rejected before PHP even looks at the file size rule. Always raise both together, and keep post_max_size equal to or larger.
If a value won't save or reverts on its own
A few things cause this:
- Plan ceiling. Shared and reseller plans usually cap how high you can push memory_limit or execution time - CloudLinux LVE limits at the server level override anything you set in the INI Editor. If a value snaps back after saving, you've hit that ceiling; contact support to check your account's LVE limits.
- A conflicting override elsewhere. A
php_valueline in.htaccessor a.user.inifile in the site's root can override the MultiPHP INI Editor value. Check both if the setting isn't taking effect where you expect. - Wrong domain selected. If your account hosts multiple domains, double check you edited the one that's actually failing - each domain keeps its own separate PHP configuration.
Quick reference: which error maps to which directive
| What you're seeing | Directive to raise |
|---|---|
| "Allowed memory size exhausted" | memory_limit |
| "File exceeds upload_max_filesize" | upload_max_filesize and post_max_size together |
| Import/export stalls or times out with no error | max_execution_time and max_input_time |
| Large form submissions (checkout, multi-field forms) silently fail | post_max_size |
Keep this table handy the next time a support ticket just says "upload isn't working" - nine times out of ten it's one of these four rows, not a plugin bug.
Prevention: set sane defaults before you need them
If you run WooCommerce, a membership site, or anything with regular bulk imports, don't wait for the error. Set memory_limit to 256M and max_execution_time to 120 up front - it costs nothing when idle and saves you the mid-import panic later. For photography or video sites, bump upload_max_filesize and post_max_size together the same day you launch, not after the first failed upload from a client.
On a Getwebup VPS or dedicated plan you also have SSH access to edit php.ini directly if you need directives the INI Editor doesn't expose - but for shared and reseller hosting, MultiPHP INI Editor is the supported way to do this, and it's the one our support team will point you to first.
FAQ
Frequently asked questions
Why does MultiPHP INI Editor show different values than what I set in wp-config.php?
wp-config.php can only lower some PHP limits, never raise them past what the server allows. If you added define('WP_MEMORY_LIMIT', '512M') but the server's memory_limit is still 128M, WordPress is capped at 128M regardless of what wp-config.php says. Set the real ceiling in MultiPHP INI Editor first.
Can I edit php.ini directly instead of using this tool?
On shared and reseller hosting, no - there's no direct file access to the system php.ini, and creating your own in the wrong location gets ignored. MultiPHP INI Editor writes to the correct per-domain config for you. On a VPS with root access, you can edit php.ini directly if you prefer.
I raised memory_limit but I'm still getting the same fatal error. What's wrong?
Confirm you edited the correct domain from the dropdown - each domain has independent values. Also check for a .user.ini file in that site's document root or a php_value line in .htaccess, either of which can silently override the MultiPHP INI Editor setting.
Is there a maximum I can set these values to?
Yes, your hosting plan has a server-level ceiling (enforced through CloudLinux LVE on shared hosting) that MultiPHP INI Editor can't exceed. If a value reverts after saving, you've hit that ceiling - open a support ticket to check what your plan allows or to discuss upgrading.
Does changing these values affect other websites on my account?
No. MultiPHP INI Editor settings are per-domain, so raising memory_limit or upload_max_filesize for one site doesn't change the configuration for any other domain under the same cPanel account.