Jason Bahl

Tyler

David Levine

Ryan Kanner

Geoff Taylor

Edwin Cromley

WPGraphQL is a free, open-source WordPress plugin that provides an extendable GraphQL schema and API for any WordPress site.
Get Started
<ol>
<li>Install WPGraphQL: <code>wp plugin install wp-graphql --activate</code></li>
<li>Try it out: <a href="https://repl.wpgraphql.com" rel="nofollow ugc">Live Demo</a></li>
<li>Read the <a href="https://wpgraphql.com/docs/quick-start" rel="nofollow ugc">Quick Start Guide</a>.</li>
<li>Join the <a href="https://discord.gg/AGVBqqyaUY" rel="nofollow ugc">Community on Discord</a> and <a href="https://github.com/wp-graphql/wp-graphql" rel="nofollow ugc">Star the Repo</a>!</li>
</ol>
Key Features
<ul>
<li>Flexible API: Query posts, pages, custom post types, taxonomies, users, and more.</li>
<li>Extendable Schema: Easily add functionality with WPGraphQL’s API, enabling custom integrations.</li>
<li>Compatible with Modern Frameworks: Works seamlessly with <a href="https://vercel.com/guides/wordpress-with-vercel" rel="nofollow ugc">Next.js</a>, <a href="https://docs.astro.build/en/guides/cms/wordpress/" rel="nofollow ugc">Astro</a>, <a href="https://www.okupter.com/blog/headless-wordpress-graphql-sveltekit" rel="nofollow ugc">SvelteKit</a>, and more.</li>
<li>Optimized Performance: Fetch exactly the data you need in a single query. Boost performance with <a href="https://github.com/wp-graphql/wp-graphql-smart-cache" rel="nofollow ugc">WPGraphQL Smart Cache</a>.</li>
</ul>
WPGraphQL is becoming a <a href="https://wordpress.org/news/2024/10/wpgraphql/" rel="ugc">Canonical Plugin</a> on WordPress.org, ensuring long-term support and a growing community of users and contributors.
<h4>Upgrading</h4>
It is recommended that anytime you want to update WPGraphQL that you get familiar with what’s changed in the release.
WPGraphQL publishes <a href="https://github.com/wp-graphql/wp-graphql/releases" rel="nofollow ugc">release notes on Github</a>.
WPGraphQL has been following Semver practices for a few years. We will continue to follow Semver and let version numbers communicate meaning. The summary of Semver versioning is as follows:
<ul>
<li>MAJOR version when you make incompatible API changes,</li>
<li>MINOR version when you add functionality in a backwards compatible manner, and</li>
<li>PATCH version when you make backwards compatible bug fixes.</li>
</ul>
You can read more about the details of Semver at semver.org
<h3>Privacy Policy</h3>
WPGraphQL uses <a href="https://appsero.com" rel="nofollow ugc">Appsero</a> SDK to collect some telemetry data upon user’s confirmation. This helps us to troubleshoot problems faster and make product improvements.
Appsero SDK does not gather any data by default. The SDK starts gathering basic telemetry data only when a user allows it via the admin notice.
Learn more about how <a href="https://appsero.com/privacy-policy/" rel="nofollow ugc">Appsero collects and uses this data</a>.
Learn more about how <a href="https://appsero.com/privacy-policy/" rel="nofollow ugc">Appsero collects and uses this data</a>.

WPGraphQL


I operate a large blog that uses WordPress as a headless CMS with a Next.JS frontend, which is largely enabled by this plugin. Let me just say first that creating an entire alternative third-party data API is an ambitious undertaking and I appreciate all the work the authors have put into it.



But as a developer I have to throw out a word of caution that this plugin often has major bugs that can have critical impact on your production website. For example after a recent minor update  we discovered a bug where any URL with a special character in it started returning a 404, causing several of our pages to suddenly become unavailable to users and delisted from Google, and this went on for many months before we realized it.



There have been many similar instances. My general approach is to lean more on WordPress's REST API over time which is more reliable since it's maintained by the WordPress team, and only use WPGraphQL when it's necessary.



Also recommend turning off auto-updates and test your website extremely thoroughly after any upgrade.


Unreliable

GraphQL vs. REST API
  10    :     0

Thank you for this plugin. Building my headless application with WPGraphQL is fun. 
The repl interface to test queries is A+.

Speedy

WPGraphQL adds a flexible and powerful GraphQL API to WordPress, enabling efficient querying and interaction with your site's data.

WP Engine

Chris Wiegman

John Parris

Nick C

Joseph Fusco

Anthony Burchell

rfmeier

markkelnar

Matthew Wright

Andrew Matthews

claygriffiths

Jason Konen

Teresa Gobble

Theo

blakewpe

Colin Murphy

In conjunction with the <a href="https://www.npmjs.com/search?q=%40faustwp" rel="nofollow ugc">Faust.js™ NPM packages</a>, the Faust.js™ WordPress plugin enables a decoupled front-end to authenticate with WordPress through GraphQL mutations and REST API endpoints. It is the bridge between a Faust.js™ powered front-end application, and a WordPress backend.
The plugin also provides useful options for headless sites, such as the ability to:
<ul>
<li>Hide “theme” admin pages.</li>
<li>Redirect public route requests to the front-end application.</li>
<li>Rewrite WordPress URLs to front-end URLs in queried content.</li>
</ul>

Faust.js

The future of headless WP


Reduces the complexity of building headless WordPress frontends for the web tenfold. Addition of Apollo helps the user flexibly perform declarative queries to manipulate and structure data too. 


Comprehensive

Faust.js™ transforms your traditional WordPress installation into a flexible headless CMS.

WPGraphQL vs Faust.js