---
title: "Limitations for Taxonomy"
description: "Understand the current limitations and behaviors of the taxonomy feature in Contentstack."
url: "https://www.contentstack.com/docs/headless-cms/limitations-for-taxonomy"
product: "Contentstack"
doc_type: "guide"
audience:
  - developers
  - admins
version: "current"
last_updated: "2026-06-23"
---

# Limitations for Taxonomy

*   The taxonomy feature is plan-based and accessible exclusively with the activation of the new CDA plan. Please contact the [support](mailto:support@contentstack.com) team to get this activated for your organization.
*   Taxonomy is a global module, and not specific to any branch.
*   The maximum number of taxonomies allowed per stack will depend on the product tier.
*   The maximum character length for a taxonomy name and UID is **50** characters.
*   The maximum character length for a taxonomy description is **255** characters.
*   The maximum number of terms allowed per taxonomy is **10000**.
*   The maximum number of terms allowed per entry is **25**.
*   The maximum depth of terms allowed is **10** levels.
*   The maximum character length for a term name and UID is **50** characters.
*   The taxonomy and term UIDs cannot be edited, once they are saved.
*   The UID for a term is unique within a taxonomy but not unique within a stack.
*   You can include and configure multiple taxonomies within a single taxonomy field in a content type. However, adding multiple taxonomy fields is not supported.
*   The taxonomy field cannot be added within modular blocks or group fields.
*   The UID for the taxonomy field is "taxonomies" within content types and is now a restricted keyword, which cannot be used for any other field.
*   Uncategorized entries (entries not assigned any term) will not be visible to users with taxonomy-based permissions.

## Publishing-related Limitations

*   **Publishing applies to the entire taxonomy**. You cannot publish individual terms.
*   **No versioning** or **rollback** is supported for taxonomy publishing.
*   Each publish action **overwrites** the previously published taxonomy for the selected environment and locale.
*   Only **published taxonomies** are available through the Content Delivery API (CDA).
*   Entries can reference **unpublished taxonomies**, but those references will not be resolved on delivery.
*   Although taxonomies are global, publishing requires **branch selection** to define locale availability and fallback hierarchy.