The fastest check takes about 20 seconds: sign in to your WordPress dashboard and look at Dashboard > Updates, or the "At a Glance" widget on the Dashboard home screen. It shows the version you are running plus whether an update is waiting.
If you cannot log in, you can still find the version from the public page source, an RSS feed, the version.php file over FTP, or WP-CLI if your host offers it. This guide gives you that method matrix, explains how to read a release number, and ends with a simple decision rule so you know when to update right away, when to test first, and when to wait.
The path in 6 steps
The steps of this page, in order.
-
01 Find your version Use the method that fits what access you have: dashboard, browser, file system, or command line.
-
02 Read the number Decide whether the release is major, maintenance, security, or beta, it changes everything.
-
03 Check compatibility Confirm your plugins and theme work with the target version before you touch core.
-
04 Back up first Take a timestamped backup of files and database you can restore from.
-
05 Update in order Update core and extensions in the right sequence, then test on the live front end.
-
06 Roll back if broken Know how to restore the previous version and where to get it before you need it.
01 / 11
What WordPress version am I running?
If you can log in, the dashboard tells you in seconds; if you cannot, the page source, RSS feed, version.php file, and WP-CLI are your four fallbacks. For the full picture, from hosting and themes to security and SEO basics, see our WordPress guide.
If you can log in, the Updates screen (Dashboard → Updates) and the At a Glance widget on the home screen both display the current WordPress version. Updates also flags whether a newer one is pending.
The number appears in three parts (for example 7.1.4): the first tells you which branch, the others how far along the cycle you are. Every method below works without installing anything; the difference is whether you need a login, file access, or a terminal.
Check methods: what each one needs and what it reveals
| Method | Login required | Reliability | Exposes version publicly? |
|---|---|---|---|
| Dashboard → Updates | Yes | High | No |
| Home screen 'At a Glance' widget | Yes | High | No |
| Front-end page source (Generator meta tag) | No | Medium | Yes, visible to anyone |
| RSS feed | No | Low, Medium | Yes, when the feed includes it |
| version.php file via FTP/SSH | No (file access only) | High | No |
| WP-CLI (`wp core version`) | No (terminal/SSH only) | High | No |
Reliability here means how consistently the method returns the real core version. Front-end and RSS checks depend on the site not stripping or caching the information, and they make the version visible to visitors and bots alike.
02 / 11
How do I check the version without logging in?
Four login-free routes exist, and they differ in reliability and how much they leak to strangers.
The public-facing route is the generator meta tag: a line in the HTML source that can reveal your WordPress version to anyone. Open the page source and search for "generator". The RSS feed often carries the same line, but it may be cached, so refresh the source first if the numbers disagree. For the most authoritative answer without admin access, open wp-includes/version.php over FTP and read the $wp_version value.
Reliability runs from the database to the public page. version.php is the source of truth, the generator tag is a copy that can go stale, and the RSS line is a cached copy of that copy. A security plugin or theme change can remove the tag entirely. None of these routes require a login, and only the file route hides the number from strangers.
Can you reach the dashboard?
If yes, read the version at the bottom of every admin screen; if no, skip to the next route.
Can you view the public page source?
Search for a generator meta tag. If it is present, it names the version; if it is absent, move on.
Can you view or fetch the RSS feed?
The generator line usually appears there too. Clear the cache or refresh the source first if it disagrees with the page.
Do you have FTP or a file manager?
Open wp-includes/version.php and read $wp_version. This works even when the dashboard is unreachable, and it does not expose the number publicly.
Do you have command-line access?
WP-CLI can report the version in one command. It is the fastest route for multiple sites, but it needs shell access, which many hosts restrict.
Going further
Show me why
Concept
Why the page source sometimes hides the version
The generator tag is a convenience, not a guarantee, so its absence tells you nothing about whether your site is current.
A security plugin can strip the generator meta tag, and a custom theme can simply omit it. In both cases the version is still there; it is just no longer printed in the public HTML. That is why a missing tag is not evidence of an updated site.
If the tag is gone, the RSS feed may still carry the same line, and the file route always works if you have FTP. The takeaway: treat the public page as a quick signal and version.php as the answer. If you want to keep the number private, removing the tag is a reasonable step, and it does not break update checks, which use WordPress.org APIs, not the tag.
- Page source shows no generator tagCheck whether a security plugin or theme removed it; the version still exists in version.php.
- RSS and page source disagreeClear caches and refresh the page source; a cached feed can show an older version.
- You have FTP but not the dashboardOpen wp-includes/version.php and read the $wp_version line for the exact number.
- You want to stop leaking the versionRemoving the generator tag is safe and does not affect WordPress.org update checks.
03 / 11
What do the numbers in the version mean?
The three numbers tell you how big the release is and how urgently you should treat it.
A version like 6.7.1 breaks into three signals. The first number is the major branch (6.x, 7.x): it can change behavior, so test it before deploying widely. The middle number is a minor release within that branch, adding features or smaller changes; the third is a maintenance or security patch, usually the smallest and safest to apply quickly.
A label such as beta or release candidate means the build is not production-ready. The official release notes warn against installing betas on live or mission-critical sites, so treat any pre-release tag as a testing-only build.
Major release
A new first number, like the jump from 6.x to 7.x. It can change behavior, so test it before deploying widely.
- Example
- 6.x → 7.x
- Risk
- Higher
Key pointTest on a staging site first, then update.
Minor release
A new middle number, like 6.7 → 6.8. It adds features or smaller changes within the same major branch.
- Example
- 6.7 → 6.8
- Risk
- Moderate
Key pointReview the changelog, then update after a quick check.
Maintenance release
A new third number, like 6.7.0 → 6.7.1, for small fixes and tweaks. Usually the smallest and safest to apply quickly.
- Example
- 6.7.0 → 6.7.1
- Risk
- Low
Key pointApply soon; it rarely breaks anything.
Security release
A version shipped mainly to fix a vulnerability, a security release, meant to be applied quickly.
- Example
- 6.7.2 (security)
- Risk
- Low but urgent
Key pointApply as soon as possible, after a backup.
04 / 11
How do I check plugin and theme versions?
Plugin and theme versions live beside core in the same dashboard, and compatibility there causes most failed updates.
Open Dashboard > Plugins and Dashboard > Appearance > Themes. Each row shows the installed version, and the Updates screens list everything with a pending update. Inactive plugins and unused themes still count as update surface, so delete what you do not use.
Check what the release touched before you click Update All. If it changed menus, the REST API (the interface other software uses to read and write your site's content), or the editor, test the plugins that hook into those areas first.
What to test first, by plugin category
| Plugin category | A release that touches menus, REST API, or the editor | A maintenance or security release |
|---|---|---|
| Page builders and block plugins | Test first | Low risk |
| Forms and e-commerce | Test first | Moderate risk |
| SEO and caching | Test second | Low risk |
| Backup and security | Test last, after a backup | Low risk |
A decision aid, not a rule: the release notes on wordpress.org tell you what actually changed.
05 / 11
What is the safest order to update things?
Back up, stage if you can, update core and extensions in a deliberate order, then verify on the live site.
Start with a fresh backup of files and database within the hour before you touch anything. If an update breaks the site, that backup is your rollback point, a copy from yesterday may already be missing orders or posts.
On a staging site (a private copy where you test updates before pushing them live), update core first, then plugins, then themes. If something breaks, that order tells you which layer caused it. Once live, verify pages, login, and a test order, then delete unused themes and plugins.
-
Back up now, not yesterday
Export the full database and file system immediately before updating. Confirm the backup opens or restores on a test path.
-
Stage the update
On a staging copy, update core first, then plugins, then themes. Test each layer before moving on.
-
Push to live, then verify
Check the front page, logging in, and one form or test order. Clear caches and confirm the site loads.
-
Clean up
Delete themes and plugins you no longer use. Inactive code still needs updating and can be a security risk.
06 / 11
What if I cannot access my dashboard?
You can still find and update the version from the file system, but you lose the safety net of the dashboard's notices.
Start with your host's control panel, not the login page. Many panels display the installed WordPress version and run a one-click update with a snapshot you can restore. If you have FTP or SFTP, core, the WordPress software itself, separate from plugins and themes, stores its authoritative version in wp-includes/version.php. Open that file as plain text and read the number.
That same file path also tells you whether files were partially replaced: if the dashboard broke during an update, rename the folders under wp-content/plugins to disable them, then confirm the version again before choosing your next move. Files first, plugins second, database last.
Open your host control panel
Most panels show the installed version and an update button with a snapshot; use that before touching files.
Read version.php over FTP or SFTP
Download wp-includes/version.php as plain text and read the number; it is the authoritative core version.
Inspect the plugins folder
Each subfolder in wp-content/plugins represents an installed plugin; map them before disabling anything.
Rename plugin folders to disable
Renaming a plugin folder disables that plugin without deleting it, so you can restore it if the site recovers.
Confirm the version, then decide
After any file change, check version.php again before updating, rolling back, or asking for help.
Going further
Dashboard is down
Special case
Recovering a broken dashboard
Recover a broken dashboard in three ordered layers: files, plugins, then the database.
Work from the outside in. Your host panel and version.php tell you what is actually installed; a mismatch between the two usually means an update stopped halfway. Fix the file layer first, because everything else depends on a complete core.
Plugins come second. Renaming folders in wp-content/plugins disables them cleanly; restore one at a time to find the trigger. Only if the site still fails after all plugin folders are renamed should you look at the database, and then only through your host's tools or a known-good backup.
- Files firstRead version.php and compare it to what your host panel reports; resolve any mismatch before moving on.
- Plugins secondRename plugin folders to disable them, then restore one at a time to isolate the cause.
- Database lastOnly touch the database after files and plugins are ruled out, and only via host tools or a backup.
07 / 11
How do I roll back if an update breaks my site?
A rollback is a restore: you need a backup or the official download of the older version ready before you update.
A rollback means going back to the version that worked before the update broke something. Write down the exact version you were on before you start, so you know what to restore. Restore your database and files from the backup you took right before updating, then, if needed, replace the core files with that older version from the official WordPress release archive at wordpress.org/download/releases.
Do not learn this during an outage. Run the steps once on a staging copy so the restore path is familiar. Keep the checklist where you can find it without a working dashboard.
Version noted
Write down the exact WordPress version before updating. You need it to know what to restore to.
Fresh backup taken
Back up database and files immediately before the update, so the restore point is current.
Restore path known
Confirm how your host restores a backup, or where the official older version lives on wordpress.org/download/releases.
Rollback steps written down
Keep the steps on paper or in a note outside the dashboard, reachable even if the site is down.
Tested once on staging
Run the restore once on a staging copy, so you are not learning it live during an outage.
08 / 11
Can I hide my version without breaking updates?
Yes, you can remove the public generator tag without touching how updates work, but understand what it does and does not protect.
The version shows up in the generator meta tag, an HTML line in your page source that tells anyone who looks which WordPress release you run. Removing it means the core files stay exactly where they are; update checks still talk to wordpress.org from inside the dashboard. You are hiding a sign, not locking a door.
Core, the WordPress software itself, keeps its version number internally no matter what the front end prints. Test any generator-tag change on a staging copy first, because some themes and plugins read that tag for their own output.
What hiding changes
Trims one visible version string from your public HTML. Useful as a small cleanup, often bundled with a security plugin you already run.
- Protection level
- Low, cosmetic signal only
Key pointTreat it as tidiness, not as security.
What hiding does not change
Your core files, your update pipeline and the dashboard's own version checks all keep working. Scanners can still infer versions from asset query strings, readme files and headers.
- Blocker for
- Automated, low-effort scans only
Key pointPatch on time instead of relying on obscurity.
Where to test it
Themes and plugins sometimes parse the generator tag. Change it on staging first, then check that feeds, sitemaps and any custom templates still render.
- Rollback
- Backup restore or revert the snippet
Key pointChange one site at a time, then re-check the page source.
09 / 11
Should I update now, wait, or test first?
Three inputs decide it: the release type, your backup status, and whether your plugins are known to be compatible.
Start with the release type. A security release, a version shipped mainly to fix a vulnerability, is meant to be applied quickly, and WordPress's own guidance is to install security releases promptly. A major release deserves more caution: put it on a staging site, a private copy of your site where you test updates before pushing them live, and check your key flows first.
Backup status is the second input. If your last backup is older than a day, take a fresh one before touching anything. The table below turns those three signals into a single next action.
Update now, test first, or hold: one decision table
| Release type | Backup status | Plugin compatibility | Next action |
|---|---|---|---|
| Security release | Backup from the last 24 hours | Core plugins not known to conflict | Update now, then re-check the front end and login |
| Security release | No backup, or older than 24 hours | Any | Back up first, then update the same day |
| Major release | Recent backup | Unverified | Test on staging, then push live |
| Major release | No recent backup | Unverified | Back up, stage it, test, then push live |
| Minor or maintenance release | Recent backup | Known compatible | Update now during a low-traffic window |
| Any release | Any | A plugin you cannot afford to lose | Back up, then test on staging before going live |
Version numbers and release types are dated at the time of writing; confirm the current release type on the official WordPress releases page before you act.
10 / 11
When should I get help instead of doing it myself?
Bring in a developer when the site is revenue-critical, when the update is a major release, or when the dashboard is already broken.
Two cases justify outside help. First, a major release, a change to a whole new version branch, not a small fix, on a site with custom code, a member area, or e-commerce. Put that on a staging site, a private copy you test on before pushing changes live. Second, a dashboard you cannot open after file-level checks: a developer preserves evidence and restores the last good state.
Everything else is usually DIY territory. Small brochure or blog sites with a fresh backup and compatible plugins can click the dashboard's update button. A rollback, restoring the previous working version, is always your fallback.
Do it yourself
You manage a small brochure or blog site, keep a fresh backup, and the update is a minor or maintenance release with compatible plugins.
- Best for
- Small sites, low traffic, recent backup
- Time
- 15, 30 minutes
Key pointClick update, test the homepage, then log out.
Ask your host
Your host often runs automatic backups and can restore a previous version if a routine update breaks something. Start a support ticket before you touch anything.
- Best for
- Managed hosting plans with backup tools
- Time
- Support ticket turnaround
Key pointOpen a ticket and confirm the last good restore point.
Hire a developer
Your site earns revenue, runs custom code, a member area, or e-commerce, or the dashboard is already down. A developer stages the migration and handles rollback.
- Best for
- Revenue-critical or broken sites
- Time
- Project-based engagement
Key pointAsk for a staging environment and a rollback plan before work starts.
11 / 11










