Supercharge Your WordPress Sites: WP Cloud Unveils PHP Memory Limit Pricing

We’re excited to announce a significant enhancement to the WP Cloud platform: configurable RAM per PHP Worker with our new PHP memory limit-based pricing model. This feature empowers our partners to fine-tune performance for memory-intensive WordPress sites without compromising reliability.

Understanding PHP Memory Limits

The PHP memory limit setting controls how much memory a single PHP script can consume. This acts as a crucial safeguard against poorly coded scripts that might otherwise drain server resources. However, for sophisticated WordPress implementations, standard memory limits can become a constraint rather than a protection.

When a site hits its PHP memory limit, site owners encounter the dreaded “Allowed memory size exhausted” error. This happens frequently with:

• Memory-heavy page builders
• Resource-intensive import/export processes
• Media processing operations

While most WordPress installations will function with WP Cloud’s default memory (64MB), some WordPress sites require at least 256MB. Complex sites with page builders, membership functionality, or e-commerce features can need 512MB or more to function properly.

The Power of Flexible Memory Allocation

Starting today, WP Cloud partners can adjust memory limits per PHP Worker through our API in increments of 512MB up to 2048MB. This flexibility directly addresses the challenges faced by complex WordPress implementations using resource-intensive builders.

Upgraded memory limits means more reliable site editing, and improved overall performance for memory-intensive operations like bulk product imports or complex page rendering.

What’s Driving This Change?

At WP Cloud, partner feedback is mission-critical, and like many of our features and enhancements, this request came directly from a partner. Tom Fanelli, CEO of Convesio, our soft-launch partner for this feature, identified memory constraints as a limiting factor for sophisticated WordPress sites. When memory-heavy backend pages failed to load, the traditional solutions were often costly and time-consuming:

• Optimizing autoload tables
• Convincing clients to remove certain plugins
• Rebuilding sites with lighter frameworks

None of these options was ideal from a business perspective. Rather than forcing our partners to compromise, we listened and developed a solution that maintains the performance our platform is known for while adding the flexibility these complex sites require.

“What WP Cloud added seems simple, but the business impact is huge. Without this, we were delaying launches and losing time troubleshooting memory-related errors. Now we can instantly accommodate higher-memory needs, especially for clients with heavy plugins, custom APIs, or complex dashboards. It improves time to value, reduces support burden, and increases platform retention”

– Tom Fanelli, Convesio CEO

How It Works: RAM Units and Pricing

We’re introducing the concept of “Units of RAM,” with each unit representing 512MB of memory. Partners can select from four memory configurations per PHP Worker:

• 512MB (1 unit – our default setting)
• 1024MB (2 units)
• 1536MB (3 units)
• 2048MB (4 units)

WP Cloud partners who want to review pricing information can find that information in their Partner Portal page. This keeps things transparent and tailored to your partner agreement.

Getting Started

Current partners can access this feature immediately through our API using the new php_memory_limit site meta.

php_memory_limit may be used to set the per-request PHP memory limit to a value between 512MB and 2048MB. Allowed values are 512, 1024, 1536, 2048. The default if not set is 512.

Positioning Memory Upgrades: Insurance, Not A Necessity

It’s important to stress that for most sites, the default 512MB is plenty, and higher tiers are for specific, demanding needs, not a baseline requirement. These memory upgrades provide hosts with an immediate solution for rare memory-exhaustion issues, potentially reducing support tickets while creating a natural upsell opportunity. The default 512MB tier will comfortably support even heavy sites for the foreseeable future. Higher tiers offer valuable peace of mind and accommodate workloads with genuinely demanding requirements.

Sites experiencing memory exhaustion errors will benefit most from upgrades. For others, this is optional headroom rather than necessities. End customers shouldn’t feel pressured to upgrade nor should the default 512MB be positioned as a baseline requirement. We can confidently offer these upgrades as insurance for those who want additional capacity. This approach generates revenue with minimal operational overhead.

The key is striking the right balance: we don’t want to create unnecessary urgency that might concern end users, but we also shouldn’t hide a valuable feature that can meaningfully contribute to revenue growth.

When to Consider Higher Memory Allocations

Based on industry standards and our experience, here are some guidelines for when to consider upgrading your memory allocation:

• 512MB (Default): Sufficient for most WordPress sites
• 1024MB: Recommended for some sites using page builders, or membership plugins or mid-size ecommerce
• 1536MB: Ideal for complex sites with multiple resource-intensive plugins, large product catalogs, or extensive custom functionality
• 2048MB: Best for enterprise-level implementations with heavy backend processing needs, large-scale e-commerce, or sites handling significant media processing

What’s Next?

This PHP memory limit-based pricing model represents another step in our commitment to building the most flexible, powerful cloud-based WordPress hosting platform available. We’ll continue monitoring usage patterns and partner feedback to ensure our offerings evolve with your needs.

Have questions about implementing configurable RAM for your sites? Are you a current WP Cloud and have a feature request? We want to hear it. Contact our team today using your partner portal form to discuss how this new feature can enhance your WordPress hosting capabilities.