Drupal is a registered trademark of Dries Buytaert
cms 2.1.2 — Update released for Drupal core (2.1.2)! drupal 11.1.10 — Update released for Drupal core (11.1.10)! drupal 10.5.10 — Update released for Drupal core (10.5.10)! drupal 10.4.10 — Update released for Drupal core (10.4.10)! drupal 11.2.12 — Update released for Drupal core (11.2.12)! drupal 11.3.10 — Update released for Drupal core (11.3.10)! drupal 10.6.9 — Update released for Drupal core (10.6.9)! drupal 10.6.8 — Update released for Drupal core (10.6.8)! drupal 11.3.9 — Update released for Drupal core (11.3.9)! drupal 11.3.8 — Update released for Drupal core (11.3.8)! drupal 11.3.7 — Update released for Drupal core (11.3.7)! drupal 11.2.11 — Update released for Drupal core (11.2.11)! drupal 10.6.7 — Update released for Drupal core (10.6.7)! drupal 10.5.9 — Update released for Drupal core (10.5.9)! cms 2.1.1 — Update released for Drupal core (2.1.1)! drupal 11.3.6 — Update released for Drupal core (11.3.6)! drupal 10.6.6 — Update released for Drupal core (10.6.6)! cms 2.1.0 — Update released for Drupal core (2.1.0)! linkit 7.0.15 — Minor update available for module linkit (7.0.15). views_data_export 8.x-1.10 — Minor update available for module views_data_export (8.x-1.10).
← All modules

field_usage_display

3 sites Security covered
View on drupal.org

The problem

Drupal fields are reusable within the same entity type. The same field storage (for example, body) can be attached to multiple bundles — for example, the Article and Basic page content types can both share the same body field storage. Before modifying or deleting a field, an administrator needs to know where else it is used.

The existing global field report at /admin/reports/fields provides this information, but only as a site-wide table that must be scanned manually and is disconnected from the page where field decisions are made.

The solution

Field Usage Display adds a single "Also used in" column directly to the Manage Fields table — right where administrators are already working. The column is blank for fields used only in the current bundle (no noise), and lists the human-readable labels of other bundles for shared fields (immediate context before editing or deleting).

Example (Article content type)

Field Field type Also used in Operations Body body Text (formatted…) Basic page Edit Image field_image Image Edit Tags field_tags Entity reference Blog post, Event Edit

Features

  • Works on all fieldable entity types: content types, media types, taxonomy vocabularies, block types, user accounts, and any other entity type that uses Field UI. Within each entity type, all bundles sharing a field storage are listed.
  • Displays human-readable bundle labels, not machine names.
  • Optional integration with ctools_entity_mask: when that submodule is installed, cross-entity-type borrowed fields are also listed, with the entity type name shown in parentheses for clarity.
  • No configuration required — the column appears automatically.
  • No new pages, routes, or permissions — purely additive to existing UI.

Requirements

  • Drupal 11
  • Core modules: field, field_ui (both enabled by default on most sites)

Activity

Total releases
3
First release
Apr 2026
Latest release
1 month ago
Release cadence
4 days
Stability
67% stable

Release Timeline

Releases

Version Type Release date
1.1.0 Stable Apr 14, 2026
1.0.0 Stable Apr 7, 2026
1.0.x-dev Dev Apr 7, 2026