Follow these recommendations to ensure optimal Sitecore Content Hub performance.



Data model

Keep the number of relation definitions assigned to any single entity definition below 50. Use aggregates.


Keep the number of members assigned to any single entity definition below 100.


Remove unused portal languages.

Page design

Keep the number of page components per page below 200. Use tabs so that data is loaded when a tab is selected and not all at once. Remove unused components. Use React components, and avoid having React and Knockout components on the same page.

Product content

Set the allow_navigation flag to false by default to avoid performance issues.


Do not use self-referencing relations that inherit taxonomies if there are already more than 50 taxonomy relations on an entity definition.


Turn off the Inherits security switch when there are more than two levels of inheritance. You can find this switch in the Technical group on the entity detail page.


The Upload API is intended for day-to-day activities and not for the bulk upload of assets. A typical use for the Upload API is to build third-party upload UIs, which can be useful for connector plugins. For integrations, bulk uploads, or large blobs, use fetch jobs instead of the Upload API. Fetch jobs are executed through back-end services and do not impact the UI performance. You could also use an Excel import.


Pre-calculated permissions in Content Hub are evaluated each time an entity is created or updated. The number of user groups, and the number of policies they contain, have an impact on performance; for this reason, ensure you have no more than 100 user groups, each containing fewer than 100 policies.

Do you have some feedback for us?

If you have suggestions for improving this article,