Plugin Pulse
← Pulse
E

Edit Custom Fields

by Jay · Admin & Utilities

A simple interface to edit or delete Custom Fields.

⚠ Stale⚠ Likely abandoned
How scoring works →
50 Health · D
Maintenance 5/100
Rating quality 86/100
Support 70/100

50 health vs 54 average across 3,790 Admin & Utilities plugins

Removal-risk signals

53/100

Maintenance and integrity signals that tend to precede a WordPress.org removal. Not an official status, a heads-up to act.

  • Long abandoned. No update in 3+ years — the top precursor to removal once a vulnerability is found.
  • Falling behind WordPress. Tested up to WordPress 6.1.12.

Directory ranking optimization

How it's scored →

How well this listing is tuned to rank in WordPress.org search, on the factors an owner controls. Not popularity, optimization.

55 / 100

Room to improve

Biggest win: Update recency

Update recency 11/100
WP compatibility 46/100
Rating quality 73/100
Listing tuning 100/100

To rank higher: Last updated 1332 days ago — ship an update; wp.org decays a listing's search weight after ~180 days.

Get the full rank-higher report →

Daily downloads

Since 2023-01-07 · 1,331 days · wp.org + Plugin Pulse archive

+29% vs prior 30d
11Downloads · Aug 26

30-day downloads

Rolling 30-day volume · peaks are release surges

179

now · peak 898

18530d downloads · Aug 26

Directory rank vs rivals

wp.org popularity rank over time · higher is better · when a rival's line climbs above yours, they've overtaken you

Edit Custom Fields · #4537 you Advanced Custom Fiel · #448 Custom Post Types an · #1593 Advanced Custom Fiel · #7178

Rating trend

Star average over time · dips mark rough releases

4.8Stars · Aug 26

Update activity

How busy the existing users are, measured as downloads in the last 30 days for every 1,000 active sites. A spike means a new release everyone's pulling; a long, slow decline means an aging user base that updates less.

93per 1k installs · Aug 26

Release cadence

No release in a year
from wp.org release tags

How often this plugin actually ships. A steady rhythm is the maintenance signal a single "last updated" date can't show.

0

releases in the last 12 months

3.6y ago

latest release · v0.1.9

9

tagged releases on record

Recent releases

0.1.9 · 3.6y ago0.1.8 · 3.6y ago0.1.10 · 3.6y ago0.1.7 · 5.7y ago0.1.6 · 5.8y ago0.1.5 · 6.6y ago0.1.4 · 6.6y ago0.1.3 · 11.5y ago0.1.2 · 11.5y ago

What its installed base runs

via wordpress.org

Share of active installs on each version of this plugin · 100% run the current release. Green is the current release; a big slice on older versions is a user base that has stopped updating.

v0.1 100%

Estimated active installs

The public count shows “2K+”. Our estimate pins where the real number sits.

tracked estimate
2K–3K ≈2.9K

Refined from the date this plugin crossed into its current band.

Install history · since 2015-04-18 · 1,336 observations

2KInstalls · Aug 26

Estimated value

What this plugin might earn a year, and what it might sell for. Modeled from public signals; we don't see anyone's books.

Est. annual revenue

N/A

Est. acquisition value

N/A

No paid tier is visible, so we don't put a figure on revenue or sale value: that would be guessing. The install base is a real asset to an acquirer, just not one public data lets us price. A small install base leaves thin data to model from.

Details

Version
0.1.10
Last updated
3.6y ago
Added
2013-07-16 · 13 yrs old
Requires WP
3.5.1
Tested up to
6.1.12
Requires PHP

Recent reviews

All reviews on wp.org ↗
  1. KS
    7mo ago

    Taking over a site from another developer, there were a lot of old custom fields that were no longer in use after I rebuilt it, which made it hard to get an overview when adding new ones. This plugin worked very well – thanks!Worked fine for me on a WordPress version 6.9 site.

    Read on wp.org ↗
  2. cXD4931
    1.2y ago

    Installed and run on a WordPress working on version 6.8.1 with Php version 8.2 without major issues. The plugin moved fast and did the job in seconds. Highly recommended!

    Read on wp.org ↗
  3. phoenix36
    1.6y ago

    Very good and easy to use. Does what it should. Very nice, neatly under Tools menu!

    Read on wp.org ↗
  4. Manou Allou
    2.3y ago

    Although the plugin hasn’t been tested with the current WordPress release, it did the job for me. It cleaned up several unused CPT orphans and cleared them from my website’s database without causing any problems. Hope the developer will test and update the plugin with the current version of WordPress so it feels a bit more secure to use.

    Read on wp.org ↗
  5. Volker Forster
    2.9y ago

    Not impressed. Description says “This plugin offers a simple interface to edit or delete any Custom Field names/keys you may have created in the post/page editor. Deleting a Custom Field also deletes the associated content, so use with caution!”It only deleted the CONTENT from a custom field, but it definitely does NOT delete the field.I have so much meta-garbage collected over the years, and there is obviously no way to clean this mess up.

    Read on wp.org ↗
  6. Alex 六十 Karpov
    3.6y ago

    Time saver! Thank you

    Read on wp.org ↗
  7. Hitesh Bhasin
    5.2y ago

    Was thinking of deleting the custom fields one by one on a large site. Could delete them all in one go because of this plugin. Time Saver!

    Read on wp.org ↗
  8. THE CANDY TRAIL
    5.3y ago

    As others have said – does the job well for cleaning out junk from past themes + plug-ins. Deserves the praise. To have manually ‘cleaned’ 100s of posts from years of WP remodeling would have pushed me over the edge. THANK YOU for this plug-in!

    Read on wp.org ↗

Latest updates

via wp.org changelog

Recent releases and news for this plugin

  1. Version 0.1.10 Update text domain 0.1.10
  2. Version 0.1.9 More sanitiziation and hardening 0.1.9
  3. Version 0.1.8 Use wp_verify_nonce to protect against CSRF Use sprintf for translations. 0.1.8
  4. Version 0.1.7 Use $wpdb->prepare 0.1.7
  5. Version 0.1.6 Add nonce checks 0.1.6
  6. Version 0.1.4 Fixed regression from 0.1.2 onward that broke plugin when custom field key was used in multiple posts. 0.1.4

Behavioral tests

via WP Hive

Automated install-time checks, tested on PHP 8.1.12 · WP 6.2

Low memory footprint
Low page-speed impact
Runs on latest PHP + WP
No PHP errors
No JS errors
Activates cleanly
No resource errors
No external HTTP errors
Optimized database use
Frequently updated

Growth timeline

Install-tier crossings we have observed, and how long each tier took to outgrow

  1. 2025-04-25 3K+ → 2K+ down after 7 days in tier
  2. 2025-04-18 2K+ → 3K+ up after 1 days in tier
  3. 2025-04-17 3K+ → 2K+ down after 2 days in tier
  4. 2025-04-15 2K+ → 3K+ up after 5 days in tier
  5. 2025-04-10 3K+ → 2K+ down after 3 days in tier
  6. 2025-04-07 2K+ → 3K+ up after 6 days in tier
  7. 2025-04-01 3K+ → 2K+ down after 2 days in tier
  8. 2025-03-30 2K+ → 3K+ up after 1 days in tier

Competes with

The plugins that solve the same job, ranked by shared tags then reach, closest match first. The letter on the right is each plugin's health grade (A best, F worst).

Compare head to head →

Embed this report card

Drop a live Pulse card for Edit Custom Fields into a readme, a review or a deck. It updates itself.

<iframe src="https://plugins.wpmayor.com/embed/edit-custom-fields" width="480" height="300" style="border:0" loading="lazy" title="Edit Custom Fields — Plugin Pulse"></iframe>
Preview card ↗

Edit Custom Fields: 2K+ active installs, 4.8★ (16 reviews). Plugin Pulse (WP Mayor), as of 2026-08-29. https://plugins.wpmayor.com/plugin/edit-custom-fields