Memory Limit Manager documentation for a smoother setup and safer updates.
This guide covers installation, recommended preset values, how the plugin updates memory limits, how automatic backups work, and what to do when your hosting environment will not allow automatic writes.
Install the plugin, then open Settings → Memory Manager.
You can install Memory Limit Manager the standard WordPress way or by uploading the ZIP file manually.
Automatic installation
- Log in to your WordPress admin area.
- Go to Plugins → Add New.
- Search for Memory Limit Manager.
- Click Install Now, then activate the plugin.
Manual installation
- Download the plugin ZIP file from WordPress.org.
- Go to Plugins → Add New → Upload Plugin.
- Select the ZIP file and click Install Now.
- Activate the plugin after installation completes.
A simple workflow from status check to updated limits.
The plugin is built to keep the process short and understandable, even if you rarely work with configuration files.
Review current status
Start by checking the current WordPress memory values, PHP memory limit, file location, and whether the configuration file is writable.
Choose preset or custom values
Use the quick presets for common site sizes or enter your own frontend and admin memory values manually.
Apply the change
Click Update Memory Limits. The plugin backs up the file, writes the new values, and clears opcode cache so the update can take effect immediately.
Reasonable starting points for different site sizes.
These are practical starting values, not absolute rules. If your host enforces lower limits, hosting-level settings may still override them.
128M / 256M for blogs, brochure sites, and simpler installs.
256M / 512M for many production WordPress sites with a normal plugin mix.
512M / 1G for heavier e-commerce, media, or plugin-intensive setups.
1G / 2G when the environment and hosting plan are built to support it.
Higher memory helps, but it does not replace diagnosis.
- If the site is throwing memory exhausted errors, higher limits can be an immediate fix.
- If the site is slow or unstable, raising limits may help but should not replace performance troubleshooting.
- If your host enforces strict PHP limits, WordPress constants may not be able to exceed those values.
- If another plugin, mu-plugin, or server rule defines the constants elsewhere, the plugin’s conflict detection will help you spot that first.
Every update is protected by an automatic wp-config.php backup.
The plugin does not back up your whole site. It specifically protects the file it changes.
Backup format
Backups are saved beside wp-config.php using a timestamped format similar to wp-config.php.backup-YYYY-MM-DD-HHMMSS.
Retention policy
The plugin keeps the five most recent backups and automatically removes older ones to avoid clutter.
Restore path
If a write fails, the plugin can restore automatically. You can also restore manually through FTP or your hosting file manager if needed.
What to do when automatic updates do not go through.
Most issues come down to permissions, hosting rules, or limits being defined somewhere else already.
If wp-config.php is not writable
The plugin cannot safely update the file directly. Use the manual fallback code it provides, then paste that code into wp-config.php using FTP, cPanel File Manager, or your host’s file tools.
define( 'WP_MEMORY_LIMIT', '256M' );
define( 'WP_MAX_MEMORY_LIMIT', '512M' );
If values are defined elsewhere
Some sites define memory constants in another plugin, theme, must-use plugin, or server-level configuration. Use the plugin’s conflict detection warning as your signal to review those sources before assuming the change failed.
Common questions before changing memory limits.
These are the questions most site owners ask before they touch a configuration file for the first time.
Is Memory Limit Manager free?
Yes. The plugin is free and available on WordPress.org.
Can I undo changes later?
Yes. Each update creates a backup of wp-config.php, so you have a clean recovery point for the file the plugin changed.
What if my host blocks the automatic update?
Use the manual fallback snippet provided by the plugin. Some environments do not allow direct writes, and the manual method is there for exactly that situation.
Will increasing memory fix every performance problem?
No. It can solve memory-related failures and reduce pressure in heavier admin workflows, but it does not replace profiling, cleanup, caching work, or better plugin choices.
Does the plugin work on multisite?
Yes. The official plugin listing notes multisite compatibility.
Need the plugin or want direct support?
Start with the official WordPress.org listing for downloads and support, or get in touch directly if you want help diagnosing whether memory limits are the real issue on your site.