About This Project

A reference tool built by a WordPress developer, for WordPress developers — because this resource didn't exist and it should have.

Who built this

I've been building WordPress sites for over 15 years — from simple blogs to complex multi-site networks with custom plugins. Over that time I've written plugins that create their own database tables, debugged orphaned tables left behind by uninstalled plugins, and spent more time than I'd like to admit running SHOW TABLES and cross-referencing forum posts to figure out what created what.

This site was built to solve that problem for myself — and then open-sourced because it seemed like something the community should have access to.

Why this exists

When you uninstall a WordPress plugin, it usually leaves its database tables behind. Those tables take up space, can slow down queries, and for sites that have installed and removed dozens of plugins over the years, they accumulate fast.

The question "is it safe to drop this table?" used to require Googling the table name, hoping someone had mentioned it in a forum post, or digging through plugin source code. There was no single reference.

This is that reference. Every table in the index is tied to a specific plugin (or WordPress core), with schema information, version data, and safe-to-delete guidance.

How tables are detected

Each plugin in the index is analyzed using two methods:

STATIC

Static analysis scans the plugin's PHP source code for CREATE TABLE statements, $wpdb->prefix patterns, and schema definitions. High confidence — the table structure is read directly from source.

LIVE

Live detection installs the plugin in a sandboxed WordPress environment and compares the database before and after activation. Catches tables created dynamically at runtime that static analysis would miss.

Both methods are cross-referenced where possible. The "Confidence" field on each table page reflects how certain the detection is. When in doubt, we say so.

Open source & transparency

The crawler, analysis pipeline, and this website are open source. If a table is missing, a schema is wrong, or a plugin association is incorrect — you can file an issue or submit a PR.

There are no affiliate links. No sponsored listings. No paid placements. Just a reference tool that tries to be accurate and useful.

JSON API

Every table and plugin page has a corresponding JSON endpoint. You can use it to integrate this data into your own tools:

GET /api/v1/table/{table_name}
GET /api/v1/plugin/{plugin_slug}

No authentication required. Please be reasonable with request rates.