Increasing WordPress Real-Time Collaboration Limits (WP 7 – Tested Guide)

TL;DR

• WordPress 7 brings real-time collaboration (like Google Docs)
• Default limit is low (~3 users)
• PHP-based overrides don’t work
• You need a client-side JavaScript hook
• Performance depends heavily on your server resources

---

Introduction

WordPress 7 introduces real-time collaboration, allowing multiple users to edit the same post or page at the same time—similar to Google Docs.

While testing this feature in real environments, I ran into a strict user limit that can quickly become a blocker for teams working on staging or production sites.

In this guide, I’ll walk through:

• What the default limit is
• Why it exists
• How to increase it (the right way)
• What happens to performance when you do

---

The Problem

When testing with multiple users, the editor stopped allowing new participants after 3 concurrent users.

Instead, it showed this message:

“Real-time collaboration has reached its connection limit. Try again later or contact your site administrator.”

Naturally, the first instinct is to increase the limit via configuration.

I tried this constant (commonly suggested online):

define( 'WP_COLLABORATION_MAX_USERS', 20 );

But it had no effect at all.

---

Why This Happens

The key thing to understand is:

This limit is not controlled by PHP alone.

WordPress real-time collaboration runs on a client-side sync system, where limits are enforced using JavaScript.

So even if you increase limits in PHP:

• The backend accepts it
• But the browser still blocks additional users

In short:

• PHP cannot override this limit
• The restriction lives in JavaScript

---

Working Solution (Client-Side Override)

To actually increase the limit, you need to hook into the JavaScript layer using wp.hooks.

MU Plugin Setup

Create this file:

wp-content/mu-plugins/increase-collab-limit.php

Add the following code:

<?php
/**
 * Plugin Author: Aditya Shah
 * Plugin Name: Increase Collaboration Client Limit
 * Description: Overrides max clients per room for WordPress real-time collaboration.
 */

add_action( 'admin_enqueue_scripts', function() {
	wp_add_inline_script(
		'wp-hooks',
		"document.addEventListener('DOMContentLoaded', function() {
			if (window.wp && wp.hooks) {
				wp.hooks.addFilter(
					'sync.pollingProvider.maxClientsPerRoom',
					'custom/increase-limit',
					function(value, room) {
						return 20;
					}
				);
			}
		});"
	);
}, 20 );

This overrides the client-side limit and allows up to 20 concurrent users.

---

Important: Why PHP Filters Don’t Work

You might also try something like this:

add_filter( 'sync.pollingProvider.maxClientsPerRoom', function( $limit, $room ) {
    return 50;
}, 10, 2 );

This looks correct—but it won’t work.

Here’s why:

• The filter exists only in JavaScript
• It’s defined in the sync layer (e.g. sync.js)
• PHP has no control over that layer

The only reliable solution is injecting a JavaScript filter using wp_add_inline_script().

---

Performance Testing Results

Test Setup

• 4 users editing at the same time
• Tested across different hosting plans
• Monitoring done via htop and custom logs

What I Observed

Standard Plans (0.5–1 CPU)

• Clear CPU and memory spikes
• Increased load during editing sessions
• Occasional lag in syncing changes

Higher-Tier Plans (2+ CPU)

• Much more stable performance
• Minimal resource impact
• Smooth real-time collaboration with 4 users

Key takeaway:

Increasing the limit is easy.

Handling the load is the real challenge.

---

Additional Findings

No Core Constants (Yet)

While digging through the code, I didn’t find any working backend constants for:

• WP_COLLABORATION_MAX_USERS
• WP_COLLABORATION_POLL_INTERVAL
• wp_max_concurrent_users

This suggests the feature is still evolving and not fully configurable from the backend yet.

---

Compatibility Notes

Metabox Conflicts

There are currently issues with metabox-based plugins.

For example:

• SmartCrawl Pro caused conflicts during testing

Workaround:
Disable conflicting plugins while testing collaboration.

---

When Should You Increase the Limit?

You’ll benefit from this if you:

• Have multiple editors working together
• Run content teams or editorial workflows
• Need collaborative staging environments
• Are testing WordPress 7 features at scale

---

Final Thoughts

Real-time collaboration is a big step forward for WordPress.

But it also introduces a new layer of complexity.

• The default limit is intentionally conservative
• You can increase it with a client-side override
• But performance depends entirely on your infrastructure

Before increasing limits in production, make sure your server can handle the extra load.

---

FAQ

What is WordPress real-time collaboration?

It allows multiple users to edit the same content at the same time with live syncing.

Can you increase collaboration limits in WordPress?

Yes, but only using a client-side JavaScript hook—not PHP.

Why doesn’t WP_COLLABORATION_MAX_USERS work?

Because the limit is enforced in JavaScript, not in PHP.

How many users can collaborate safely?

In most cases, 5–20 users depending on server resources.

Does increasing limits affect performance?

Yes. It increases CPU usage, memory usage, and request load significantly.