← Compare

ACF to WP-API vs WPGraphQL for ACF

Head-to-head on the signals that matter, from the public WordPress.org data.

WPGraphQL for ACF is the safest pick: health B · 83 against 47 for ACF to WP-API, led by lower removal risk.

Active-install trajectory

ACF to WP-API moved down one install band, 500+ to 400+. That's a single step across the whole window, so there's no trajectory to draw. The download trend below moves daily.

Metric	ACF to WP-API	WPGraphQL for ACF
Active installs Modeled from the public "N+" band and recent downloads.	400–500	10K–20K ✓
Active installs, change over ~6 months Compares the public install bands. One band step shows as the band change, not a percentage.	-20%	Stable ✓
Overall health	D · 47	B · 83 ✓
Maintenance How recently the plugin was updated.	3/100	100/100 ✓
Rating quality Volume-adjusted review quality.	81/100 ✓	74/100
Support Share of forum threads marked resolved.	70/100	70/100
Rating (weighted for review count)	4.2★ ✓	4.0★
Reviews	5 ✓	1
Ranking optimization How well the listing is tuned to rank on wp.org.	34/100	88/100 ✓
Removal risk Maintenance signals that precede a wp.org closure. Not an official status.	High	Low ✓
Last updated	9.6y ago	yesterday ✓
Downloads, last 30d	238	18.8K ✓
Download momentum, last 30d vs prior 30d Dips that follow a release spike are normal: wp.org counts every update as a download, so the weeks after a release run lower.	+13%	+23%
Install conversion Active installs over lifetime downloads. Downloads include every update, so older and more frequently released plugins read lower.	0.8%	4.5% ✓
Category	Developer Tools	Developer Tools

✓ marks the stronger plugin on each row. Rows where they're level show no marker.

Release activity

ACF to WP-APIWPGraphQL for ACF

7-day average daily downloads. Downloads spike for about a week after each release as the install base re-downloads, so read this as release cadence, not growth.