Drupal is a registered trademark of Dries Buytaert
Protected Pages 3.0.0 Major update available for module protected_pages (3.0.0). Commerce Core 3.3.8 Minor update available for module commerce (3.3.8). Layout Builder Reorder 2.0.1 Minor update available for module layout_builder_reorder (2.0.1). Ban 1.1.0 Minor update available for module ban (1.1.0). Field Formatter Range 2.0.0 Major update available for module field_formatter_range (2.0.0). Field Formatter Range 8.x-1.8 Minor update available for module field_formatter_range (8.x-1.8). UI Patterns (SDC in Drupal UI) 2.0.18 Minor update available for module ui_patterns (2.0.18). Varbase FAQs 9.2.1 Minor update available for module varbase_faqs (9.2.1). Search API Solr 4.3.11 Module search_api_solr updated after 14 months of inactivity (4.3.11). Provus Mega Menu Module provus_mega_menu crossed 1,000 active installs.

Field Usage Tracker

12 sites No security coverage
View on drupal.org

This module provides a report that tracks where fields are utilized across your Drupal site, including content types, Views, and custom code. It's valuable for site audits and refactoring by showing field usage in one centralized location.

Track and display where fields are used across content types, Views, and custom code. Useful for site audits, field cleanup, and refactoring.

Features

The Field Usage Tracker module provides a report listing all fields (field storages) used across your Drupal site. It helps developers, site builders, and auditors understand:

  • Which fields are attached to which content types (or other entities)
  • If those fields are used in any Views
  • If those fields are referenced in custom PHP code (e.g., inside custom modules)

This module is especially useful when refactoring content types, removing unused fields, or performing site audits.

Post-Installation

  1. Install and enable the module as usual via Extend page or using Drush: drush en field_usage_tracker
  2. Navigate to /admin/reports/field-usage
  3. Review the report that shows all fields, their target entity and bundle, and usage status.

There is no additional configuration required. The module scans Views via the Views config and detects field usage in code by searching within custom module folders for field machine names.

Additional Requirements

No additional modules or libraries are required. This module works with Drupal core APIs and Views configuration.

  • Devel – for inspecting field info and entity structure.
  • Views – although optional, field usage in Views can only be detected if Views module is enabled.

Similar projects

  • Field Audit – focuses on listing field usage per bundle but does not check usage in Views or code.
  • Unused Modules or Fields (custom scripts) – often need manual database queries; this module offers a UI-based solution.

This module is distinct in its combined focus on Views, custom code, and entity field mapping — all in a single report page.

Supporting this Module

If you find this module useful and would like to support its development or request new features, feel free to open an issue or contribute via the issue queue.

Community Documentation

Activity

Total releases
2
First release
May 2025
Latest release
1 year ago
Releases (12 mo)
0 ▼ from 2
Maintenance
Dormant

Releases

Version Type Release date
1.0.x-dev Dev May 26, 2025
1.0.0 Stable May 14, 2025