The reliable way to reduce memory use across several WordPress sites is to measure the requests that fail, remove the code and jobs that create peaks, then set WordPress limits below the PHP limit enforced by your server. Raising WP_MEMORY_LIMIT alone cannot give PHP more memory than the host allows.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
There is no honest “RAM per site” number. A lightly used brochure site with a lean theme may consume far less than a store, page builder, multilingual network or import job. Plan from observed peak usage, PHP-FPM worker concurrency, database load and cache size, and increase capacity in small, tested steps.
As an Amazon Associate I earn from qualifying purchases.
What memory is being exhausted?
Most WordPress memory errors refer to PHP’s per-request limit, not directly to the total RAM installed in the machine. A front-end page, an administration screen, a scheduled task and an image import can all use different amounts of PHP memory. Several PHP-FPM workers may run at the same time, so a server can run out of physical RAM even when each individual request is below its limit.
Keep four resources distinct when diagnosing a failure:
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
- PHP request memory: the amount one PHP request may allocate before it triggers an “allowed memory size exhausted” fatal error.
- Worker concurrency: the number of PHP-FPM or equivalent workers that can be active simultaneously. Multiplying a realistic per-request peak by active workers gives a better view of PHP’s possible total than a per-site guess.
- Database memory: buffers, connections and query work needed by MySQL or MariaDB.
- Cache and operating-system memory: persistent object caches, opcode caches, the web server and the OS also need room.
A useful capacity model is therefore: peak PHP memory per worker multiplied by possible concurrent workers, plus the database, cache, web server and OS, with safety headroom. Measure those components rather than assigning a fixed RAM allowance to every domain.
WordPress’s documented starting limits
WordPress defines separate constants for visitor-facing requests and administration or other intensive operations. The official documentation describes WP_MEMORY_LIMIT as the maximum memory PHP may consume for ordinary WordPress requests. The Hosting Handbook notes that whether a request succeeds is ultimately controlled by the server.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →| Request type | WordPress default or guidance | How to interpret it |
|---|---|---|
| Single-site front end | 40 MB default WP_MEMORY_LIMIT |
A baseline for normal front-end requests, not a promise that every plugin combination fits. |
| Multisite front end | 64 MB default WP_MEMORY_LIMIT |
A higher default because network requests can load more shared functionality. |
| Administration and backend operations | 256 MB default WP_MAX_MEMORY_LIMIT |
Used for wp-admin and other operations that need more memory than a normal page view. |
| Hosting Handbook starting tiers | 128 MB minimum, 256 MB recommended default, 512 MB or more for resource-intensive sites | Starting points only; actual needs depend on installed plugins, themes and workloads. |
These values are per PHP request. They do not mean that a server with 256 MB of RAM can safely run one 256 MB worker, a database and a cache. Nor does a 512 MB request limit guarantee that a badly behaved plugin will complete successfully.
Measure the failing workload before changing a limit
Start with evidence from the exact site and request that fails. A front-end error may have a different cause from a media-regeneration task or a network-wide update.
- Capture the fatal error. Record the timestamp, domain, URL or command, PHP version, and the “allowed memory size” and “tried to allocate” figures. Check the PHP-FPM, web-server and WordPress debug logs, not only the browser message.
- Classify the request. Separate front-end traffic, wp-admin screens, AJAX requests, cron jobs, WP-CLI commands, image regeneration, imports and bulk updates. Note whether the failure affects one site or the whole network.
- Compare peaks. Use your host’s PHP-FPM status, process metrics or an application monitor to identify peak worker memory and concurrency. A single successful page load is not a capacity test.
- Reproduce safely. Repeat the same import, editor action or command in a staging copy or during a quiet period. Record memory before and after changing one variable so you can identify the component that altered the peak.
WordPress’s Site Health screen can reveal the active PHP memory limit and related environment information, but host-level logs are needed to determine whether a server policy prevented a runtime change. If the fatal log names a plugin file, hook or importer, treat that component as the first suspect rather than immediately raising every limit.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
Remove avoidable allocations from every site
Inventory plugins and themes across the installation
Build a list for each site and, if applicable, for network-activated extensions. WP-CLI can expose the inventory without loading a browser session:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
wp plugin listlists plugins for a single installation.wp plugin list --networklists network-activated plugins in a multisite network.wp theme listshows installed themes, including inactive ones.wp site listenumerates sites in a multisite network; add--url=example.comto target a particular site with other commands.
Remove unused plugins and themes rather than merely deactivating them when they are no longer needed. Replace extensions that load large libraries on every request, duplicate the same feature, or perform expensive remote calls. Check update notes and compatibility before removing a component, and take a backup so you can restore configuration and data.
Keep admin-only code off the front end
Some plugins register reports, editors, or migration tools on every request even though visitors never use them. Prefer components that load those classes only in wp-admin, on a specific REST route, or during a command-line job. If you maintain custom code, guard administration hooks with an appropriate context check and avoid constructing large data sets until the relevant screen or command actually needs them.
Control page-builder, media and import peaks
Visual editors, large product catalogs, multilingual indexes and image-processing libraries can create much higher peaks than ordinary page views. Resize or compress source images before upload where possible. Run thumbnail regeneration and catalog imports in batches, and pause between batches if worker or database utilization remains high. A smaller batch that completes reliably is preferable to a single request that approaches the limit and can be terminated halfway through.
Separate heavy jobs from visitor traffic
Do not make a visitor’s page request perform a network-wide migration, thousands of scheduled events or a full media scan. Move intensive work to WP-CLI or a scheduler with controlled concurrency:
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsRank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
- Choose a maintenance window or a staging environment and create a current backup.
- Target one site at a time with
--url=site.example, or iterate through the output ofwp site listinstead of launching every site simultaneously. - Use bounded batches for imports, updates and image regeneration. Log the last successful item so a failed batch can resume without duplicating work.
- Run due cron tasks deliberately with
wp cron event run --due-nowwhen testing, rather than allowing an uncontrolled backlog to collide with peak visitor traffic. - Watch PHP worker memory, database connections, execution time and disk space while the job runs. Stop the batch if any resource approaches its limit.
WP-CLI’s multisite targeting and cache commands are useful for operational work, but commands can still consume substantial memory. A command-line process is not automatically lightweight; measure the same way you would measure a web request.
Set WordPress constants only after checking the host limit
First determine the server’s PHP memory_limit for the affected SAPI (web, PHP-FPM and command line can differ). A WordPress constant cannot exceed a host-enforced value. Some managed or shared hosts ignore attempts to change it in wp-config.php or prevent runtime changes entirely.
- Ask the host or inspect the relevant PHP information to confirm the effective
memory_limitfor the failing request. - In the site’s
wp-config.php, place the constants before the line that says to stop editing, and use values justified by your measurements. For example:define('WP_MEMORY_LIMIT', '128M');for front-end requests anddefine('WP_MAX_MEMORY_LIMIT', '256M');for administration. - Keep the front-end and backend values purposeful. Raising both to an arbitrarily large number can let one request consume memory needed by other sites, workers or the database.
- Clear any relevant opcode or application cache, then repeat the exact failing request and compare the peak and log output.
If the effective PHP limit is lower than the value you need, request a server-side change or move to a plan that permits an appropriate limit. If the host refuses, reduce the workload or run the operation through a controlled worker instead of repeatedly overriding WordPress settings.
Use persistent object caching for repeated database work
A persistent object cache stores frequently reused WordPress objects between requests. Memcached or a compatible Redis service can reduce repeated database queries and latency when the same options, user data or query results are requested often. This is a performance and database-load improvement, not a way to make PHP allocations disappear.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute- Confirm that your host supports a persistent cache service and that the service is isolated from other customers or protected with the required authentication.
- Install a cache integration that matches the service and your WordPress version. Enable it for one low-risk site first.
- Verify that the integration reports a persistent backend rather than the default in-process cache. Test logins, updates, carts and other stateful features.
- Monitor cache size, hit rate, evictions, connection errors and latency. Set a size that leaves room for PHP workers and the database.
- Flush the cache after major code or schema changes, and use WP-CLI cache commands only when you understand the effect on all sites sharing that backend.
Object caching consumes memory of its own. An undersized cache can evict entries constantly; an oversized cache can starve PHP or the database. Treat cache memory as part of the capacity model, not as free RAM.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
Enable opcode caching, but budget for it
PHP opcode caching, commonly provided by OPcache, keeps compiled PHP bytecode so workers do not repeatedly compile the same files. This reduces CPU work and can improve response consistency, especially when many sites share common WordPress code. The compiled scripts occupy shared memory, and the cache needs monitoring for capacity, restarts and invalidation after deployments.
Use the host’s supported OPcache configuration rather than adding conflicting settings in application files. Confirm that the cache is active for the web SAPI, observe its utilization and restart or invalidate it safely after deploying changed PHP files. Opcode caching complements, but does not replace, removing a memory-heavy plugin or controlling an import peak.
Choose between separate installations and Multisite deliberately
Running many domains as separate WordPress installations and running them in one Multisite network have different memory and failure characteristics. Neither architecture has a universal RAM-per-site benchmark.
Recommended Free Tools
| Decision area | Separate installations | WordPress Multisite |
|---|---|---|
| Isolation | A fatal error or incompatible plugin is more likely to remain confined to one installation, provided resources are separated. | Shared code and network services mean a faulty plugin, update or overloaded worker can affect several sites. |
| Code and cache efficiency | Each installation loads its own copy of WordPress and may duplicate opcode and object-cache entries. | Shared core and network-activated code can improve reuse, although site-specific data and requests still consume resources. |
| Per-site customization | Independent plugin, theme and PHP configuration choices are straightforward. | Network rules and plugin compatibility can limit per-site choices; a network-wide component must suit every site. |
| Operations | Backups, updates and monitoring are repeated per installation. | Centralized updates and site targeting simplify some tasks but increase the blast radius of mistakes. |
| Resource pooling | PHP workers and database resources can be separated or pooled depending on hosting design. | PHP workers, database connections and caches are commonly shared across the network, so concurrency must be planned globally. |
Choose Multisite for governance, shared code and coordinated administration—not as a promise of lower memory use. Choose separate installations when isolation, independent release schedules or incompatible extensions matter more. Whichever model you use, measure the busiest sites and jobs rather than averaging them away.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Stage capacity increases and verify each change
After removing avoidable work and controlling jobs, increase resources incrementally:
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
- Establish a baseline for normal traffic and the heaviest repeatable operation.
- Change one item—plugin, batch size, cache allocation, PHP limit, worker count or hosting tier—at a time.
- Run the same workload again and record peak PHP memory, worker saturation, database load, cache evictions, response time and error logs.
- Keep the change only if the workload completes with headroom under realistic concurrency. Revert it if it merely moves failures from PHP into system swapping, database timeouts or other sites becoming slow.
- Document the tested limit and the workload that justified it. Re-test after adding a plugin, changing a theme, enabling a new site or upgrading PHP.
Headroom matters because traffic is concurrent and workloads are uneven. A setting that succeeds for one import in isolation may fail when cron, visitors and an editor session run together.
Troubleshoot an “allowed memory size exhausted” error
The error appears on one front-end URL
Check the named plugin or theme file, disable the suspected component in staging, and compare the request with a minimal theme. Look for related widgets, shortcodes, REST callbacks or queries that load large result sets. If the host limit is already reached, raising a WordPress constant will not help until the workload is reduced or the server limit changes.
Free tools Windows power users keep installed
One-click scans. No signup required.
Only wp-admin, the editor or an importer fails
Use the backend constant only after confirming the host limit, then reduce the operation’s scope: split the import, lower image dimensions, update fewer records per batch, or run the job through WP-CLI during a quiet window. Keep visitor traffic on its normal path while the controlled job runs.
Failures occur across several sites at once
Inspect shared PHP-FPM worker limits, database connections, object-cache health and network-activated plugins. A network-wide extension or simultaneous cron backlog can create a concurrency spike even when each site looks healthy alone. Stagger jobs and test one site before re-enabling the broader operation.
The limit was raised but errors continue
Verify the effective PHP setting for the actual SAPI and request; command-line PHP and PHP-FPM may read different configuration files. Check for a host policy that caps runtime changes, then inspect logs for a different failure such as execution time, disk space, database timeout or an out-of-memory kill by the operating system.
A repeatable maintenance checklist
- Keep PHP, WordPress, themes and plugins supported and remove unused extensions.
- Review logs for memory fatals by site, URL, command and time of day.
- Measure peak per-request memory and concurrent workers before changing limits.
- Separate front-end traffic from imports, image work, bulk updates and cron.
- Target multisite jobs site by site and use resumable batches.
- Confirm the host-level PHP limit before setting WordPress constants.
- Use persistent object caching when repeated database work is the bottleneck, and monitor evictions and memory.
- Use opcode caching where supported and monitor its shared-memory utilization.
- Retest after every major plugin, theme, cache or hosting change.
The practical rule is simple: find the request that peaks, make that request smaller or less concurrent, then give it only the additional limit your measured workload and server can safely support. This approach reduces failures without sacrificing the memory needed by other sites, PHP workers or the database.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
