Choose a language

Man checking his website settings on a laptop at his desk

How to Check Your WordPress Version (and Update It Safely)

Published November 5, 2026 · Mis à jour le November 16, 2026 · 16 min read

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.

  1. 01 Find your version Use the method that fits what access you have: dashboard, browser, file system, or command line.
  2. 02 Read the number Decide whether the release is major, maintenance, security, or beta, it changes everything.
  3. 03 Check compatibility Confirm your plugins and theme work with the target version before you touch core.
  4. 04 Back up first Take a timestamped backup of files and database you can restore from.
  5. 05 Update in order Update core and extensions in the right sequence, then test on the live front end.
  6. 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

MethodLogin requiredReliabilityExposes version publicly?
Dashboard → UpdatesYesHighNo
Home screen 'At a Glance' widgetYesHighNo
Front-end page source (Generator meta tag)NoMediumYes, visible to anyone
RSS feedNoLow, MediumYes, when the feed includes it
version.php file via FTP/SSHNo (file access only)HighNo
WP-CLI (`wp core version`)No (terminal/SSH only)HighNo

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.

Store owner checking her website on a laptop in her shop

Going further

Show me why

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.

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 categoryA release that touches menus, REST API, or the editorA maintenance or security release
Page builders and block pluginsTest firstLow risk
Forms and e-commerceTest firstModerate risk
SEO and cachingTest secondLow risk
Backup and securityTest last, after a backupLow risk

A decision aid, not a rule: the release notes on wordpress.org tell you what actually changed.

Freelancer updating a website on a laptop in the evening

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.

  1. 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.

  2. Stage the update

    On a staging copy, update core first, then plugins, then themes. Test each layer before moving on.

  3. Push to live, then verify

    Check the front page, logging in, and one form or test order. Clear caches and confirm the site loads.

  4. 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

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.

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 typeBackup statusPlugin compatibilityNext action
Security releaseBackup from the last 24 hoursCore plugins not known to conflictUpdate now, then re-check the front end and login
Security releaseNo backup, or older than 24 hoursAnyBack up first, then update the same day
Major releaseRecent backupUnverifiedTest on staging, then push live
Major releaseNo recent backupUnverifiedBack up, stage it, test, then push live
Minor or maintenance releaseRecent backupKnown compatibleUpdate now during a low-traffic window
Any releaseAnyA plugin you cannot afford to loseBack 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.

11 / 11

Frequently asked questions

Frequently asked questions
The Web Insider editorial team
About the author The Web Insider editorial team

Web Insider is a practical magazine for people who build, run or grow a website. Every fact is checked against its official source, and every test shows its proof.

Your feedback

Was this page helpful?

Share

Could this page help someone?

Related reading

Read next

Man checking a charge on his phone next to a laptop
Guides & How-tos

Amazon Digital Charge: What It Is and How to Check It

An Amazon Digital charge is a real Amazon billing label for digital items like Prime Video rentals, Kindle books, Audible, and app purchases. This guide walks you through matching the charge to your account, canceling the right subscription, and escalating if it's truly unauthorized.

·13 min
Marketing team discussing a target audience around a computer
Guides & How-tos

Target Marketing: A Simple Method to Pick Your Audience

Target marketing means choosing one specific group of buyers and tailoring your product, message, and channels to them. Here is a repeatable five-step method, a scoring table you can copy, and a one-page audience brief.

·15 min
Team reviewing website performance charts on a large monitor
Guides & How-tos

Why Do an SEO Audit Before You Fix Your Site?

An SEO audit is a structured diagnostic of your site, technical health, content, backlinks, and now AI-search visibility, that tells you what is broken and what to fix first. Skipping it means paying twice: once for the wrong fix, again for the fix you actually needed.

·19 min
Consultant walking a client through a tracking plan on a laptop
Guides & How-tos

Hiring a GTM Consultant: A Buyer's Guide

A Google Tag Manager consultant builds, audits, and maintains the tags, triggers, and dataLayer that feed GA4 and your ad platforms. This guide covers when the spend is justified, fair US price ranges, and how to screen candidates.

·20 min
Laptop showing a web page built from layered structure, style and script blocks
Guides & How-tos

HTML vs CSS vs JavaScript: What Each One Does

HTML is the structure, CSS is the look, JavaScript is the behavior. This guide gives you one mental model for all three, a single worked example, and a straight answer on what to learn first.

·13 min
Explore the topicData & Analytics

Audience measurement, Google Analytics 4 and Google Tag Manager: set them up, check them and keep your data reliable.

Explore the topicWebsites & Platforms

WordPress, Shopify, PrestaShop and WooCommerce: run, integrate and maintain a site without making it fragile.

Explore the topicGuides & How-Tos

Methods, training and practical benchmarks to scope a web project, test a site and make better decisions.

Explore the topicSecurity & Compliance

Backups, updates, GDPR, cookies and audience measurement: keep a site safe and compliant.