Comparison · generated on request
Default Post Content vs PostMeta Viewer – Custom Fields Inspector
Both plugins as this registry currently observes them. Figures come from the same daily snapshot, so they are directly comparable, which two separate wordpress.org pages, read minutes apart, are not.
| Default Post Content | PostMeta Viewer – Custom Fields Inspector | |
|---|---|---|
| What it does | Tired of typing in the same default content at the end of your post? Use the same custom fields for each new post? Make your WordPress install do it … | A powerful debugging tool for WordPress developers to inspect and analyze post meta (custom fields) across posts, pages, custom post types, taxonomy t … |
| Active installs | 70+ | 80+ |
| Rating | — | — |
| Last release | 16 years ago | 3 months ago |
| Current owner | Peter Butler | wpwebguru |
| Added to directory | 14 Apr 2009 | 12 Jan 2026 |
| Tested up to | WP 2.9.2 | WP 7.0.4 |
| Requires PHP | false | 7.4 |
Install figures are rounded by WordPress.org to one significant digit, so a gap smaller than a band step is not a difference. Nothing here ranks the two plugins or recommends either, and no link on this page earns anything.
Why this page is not in search results
There are roughly 1.8 billion possible pairs of WordPress plugins. Generating them would be scaled content abuse, so this registry does not: a comparison renders for anyone who asks for it, and is offered to search engines only once 25 different people have asked for that same pair within 60 days. This one has been requested by 0. Until it crosses, the page works normally but stays out of the index.
Records: Default Post Content · PostMeta Viewer – Custom Fields Inspector