Yes — Salesforce caps the total number of Experience Cloud sites (communities) you can have in a single org. The published limit has historically been 100 sites per org, counting active, inactive, and preview sites together. This number can shift between releases and varies by edition, so the safe interview answer is “around 100, counting all states — verify the current number against Salesforce Help.”
What counts toward the limit
- Active communities — live, customer-facing.
- Inactive communities — built but not currently published.
- Preview communities — in builder, not yet published.
Deleting a community frees a slot. Communities count against the limit regardless of how many users they have.
Why the limit exists
Each community is a discrete configuration with its own URL, branding, security model, page metadata, navigation, and theme. Beyond a certain count the org becomes hard to maintain and the metadata store gets unwieldy. The cap is a guardrail.
Workarounds when you hit the cap
Real interview-grade answer if asked “what if we need more than 100?”:
- Multi-tenant patterns within one community. Use audience targeting, page variations, and dynamic branding to serve different sub-audiences from a single community — for example, brand-A and brand-B variations of one customer community.
- Consolidate stale ones. Most orgs that hit the cap have abandoned proof-of-concept communities. Audit and delete.
- Contact Salesforce Support. In rare cases Salesforce can raise the cap for enterprise customers with documented business need.
- Re-architect with sub-pages. A single community with deep page hierarchy can serve what previously was multiple shallow communities.
Edition matters
The default community count depends on edition (Enterprise, Performance, Unlimited, Developer). Developer Edition orgs have a small cap (typically a handful) for testing. Production caps are higher. Always check Salesforce Help for your edition’s current limit rather than memorizing a number that will change.
Quick interview answer
“Yes, there’s a per-org limit — historically around 100 Experience Cloud sites total, counting active, inactive, and preview sites. The number varies by edition and changes between releases, so the right way to quote it is to point to Salesforce Help. When orgs hit the limit, the answer is usually audit-and-delete stale sites or consolidate sub-audiences within fewer communities.”
Verified against: Salesforce Help — Experience Cloud Limits and Allocations. Last reviewed 2026-05-17.