Expose disk size for each installed plugin

[maulikmakwana2008]

Currently, WordPress displays metadata such as Version, Author, and Details below each plugin name on the Plugins screen. However, there is no built-in way to view how much disk space an installed plugin consumes.

This enhancement proposes displaying the Plugin Size inline with existing metadata, improving transparency for administrators managing storage, backups, and performance—especially on shared or limited hosting environments.

Current Output
Version 5.6 | By Automattic – Anti-spam Team | View details

Proposed Output
Version 5.6 | Plugin Size 1.42 MB | By Automattic – Anti-spam Team | View details

Why This Belongs in Core

• No UI clutter (uses existing plugin meta row)
• Helps identify large plugins quickly
• No frontend impact
• No database schema changes
• Uses existing WordPress hooks
• Avoids need for third-party plugins

Technical Approach

• Hook into plugin_row_meta to append plugin size
• Calculate size from the plugin’s directory
• Cache size using transients to prevent repeated filesystem scans
• Clear cache on plugin update or deletion
• Admin-only execution

[westonruter]

I don't think this is appropriate for plugins list table. I would imagine plugin size is rarely if ever an issue when compared with the amount of storage taken up by uploaded images.

So if we do this, I think it would make more sense to add to Site Health info, to break down the current "Plugins directory size" entry into the sizes for individual plugins.

[maulikmakwana2008]

@westonruter
Patch attached.

This patch extends Site Health → Info → Directories and Sizes to expose
disk usage for each individual installed plugin.

It reuses existing filesystem logic via WP_Filesystem_Direct::dirsize(),
consistent with how core already calculates directory sizes, and adds
a new “Plugins (individual)” entry to the Site Health debug data.

The calculation runs only when viewing Site Health Info and does not
impact normal admin or front-end requests. No UI changes are introduced,
and no new public APIs are added.

Feedback welcome.

[westonruter]

The "version" field indicates when the issue was first introduced. It's not something newly in trunk, so this can be left blank.

Please open a pull request with the patch to facilitate review and testing. This is more helpful than attaching a patch file.

https://core.trac.wordpress.org/ticket/64445

[maulikmakwana2008]

@westonruter
you can review added PR request ​https://github.com/WordPress/wordpress-develop/pull/10671 and attached Updated64445.jpg

[westonruter]

Please leave the version blank, or else it could be set to back when the site info was added.

[maulikmakwana2008]

@westonruter
Thanks for the clarification. I don’t have permission to update the Version field, but I agree it should be left blank.

[westonruter]

@maulikmakwana2008 you set it to trunk again in your previous update.

[r1k0]

Test Report

Description

This report validates whether the indicated patch works as expected.

Patch tested: ​https://github.com/WordPress/wordpress-develop/pull/10671

Environment

• WordPress: 7.0-alpha-61215-src
• PHP: 8.2.29
• Server: nginx/1.29.4
• Database: mysqli (Server: 8.4.7 / Client: mysqlnd 8.2.29)
• Browser: Firefox 146.0
• OS: Ubuntu
• Theme: Twenty Twenty-Five 1.4
• MU Plugins: None activated
• Plugins:
  • Test Reports 1.2.1

Actual Results

1. ✅ Issue resolved with patch.

Before:

After:

[ozgursar]

Test Report

Description

This report validates whether the indicated patch works as expected.

Patch tested: ​https://github.com/WordPress/wordpress-develop/pull/10671

Environment

• WordPress: 7.0-alpha-61215-src
• PHP: 8.2.29
• Server: nginx/1.29.4
• Database: mysqli (Server: 8.4.7 / Client: mysqlnd 8.2.29)
• Browser: Chrome 143.0.0.0
• OS: macOS
• Theme: Twenty Twenty-Five 1.4
• MU Plugins: None activated
• Plugins:
  • Performance Lab 4.0.1
  • Test Reports 1.2.1

Actual Results

1. ✅ Issue resolved with patch.

Screenshots

Before	After

Additional Notes

• Plugins can create files/folders outside their base folder. For example, they usually store certain files in the /wp-content/uploads/[plugin-name] folder. Therefore, this patch doesn't calculate disk space usage for files created outside the plugin's base directory.

Trac ticket: https://core.trac.wordpress.org/ticket/64445

Raised a PR which adds Theme Sizes, Plugin Sizes and Upload Directory Content (except media) path sizes: