How to Install WordPress Beta, RC and Nightly Builds (2026)

Want to try new WordPress features before they are released? You can install a WordPress beta, release candidate (RC) or nightly build in a few clicks. When we first wrote this in 2011, the Beta Tester plugin confused us by offering an alpha of the current version instead of the beta. The plugin is still the official way to test, and in 2026 you also have WordPress Playground and WP-CLI. Here is how each works.

Quick answer: On a test site, install the official WordPress Beta Tester plugin, go to Tools > Beta Testing, choose Bleeding edge for the next major version (or Point release for the next minor one), pick the Beta/RC or Nightlies stream, save, then go to Dashboard > Updates and update. For zero risk, open WordPress Playground in your browser with ?wp=beta or ?wp=nightly.

Alpha, beta, RC and nightly: what’s the difference?

• Nightly (alpha/trunk): the latest development code, rebuilt every day. Newest features, most bugs.
• Beta: features are mostly complete and ready for wider testing.
• Release candidate (RC): the team thinks it is ready; final bug fixes only.

Before you start

• Never test on your live site. Use a staging copy, a local install or Playground.
• Back up files and the database. Database changes in a new version can make downgrading difficult.
• Expect some plugins or themes to break; that’s what testing is for.

Method 1: WordPress Beta Tester plugin

1. Install and activate WordPress Beta Tester (on multisite, find it under Settings).
2. Go to Tools > Beta Testing.
3. Choose a channel: Point release (the next minor update) or Bleeding edge (the next major version, like the beta we wanted in 2011).
4. Choose a stream: Beta/RC only for milestone releases, or Nightlies for daily builds.
5. Save, then open Dashboard > Updates and click the update button. Your site now shows a version like “7.x-beta1”.
6. Keep updating to get fixes until the final release.

Method 2: WordPress Playground (no install)

WordPress Playground runs a full WordPress site in your browser. Add ?wp=beta or ?wp=nightly to the Playground URL to load a test version, then install your plugins and theme to check compatibility. Nothing touches your real site.

Method 3: WP-CLI

If your test server has WP-CLI, update from the command line:

wp core update --version=nightly

You can also pass a specific beta or RC version number or a download URL from the release announcement on the WordPress News blog.

Report what you find

Found a bug? Search the Alpha/Beta support forum and report it there or on WordPress Trac. Plugin and theme developers should test early so their users aren’t surprised on release day.

When the final version arrives, see how to update WordPress safely and use maintenance mode during big upgrades.

FAQ

Can I go back to the stable version after a beta?

Switch the plugin back to Point release and wait for the final release, or restore your backup. Downgrading directly can fail if the database changed.

Is it safe to run WordPress beta on a live site?

No. Betas and nightlies can have serious bugs. Always use a test site.

When are WordPress betas released?

Betas usually appear several weeks before each major release, followed by release candidates.