BLACK FRIDAY
Save 59% on PageForge Annual $191/year $485/year
Claim 59% Off →
WP BrowserUpdate icon
Actively maintained Tested with WP 7.1 #4 in browser

WP BrowserUpdate

This plugin notifies website visitors to update their outdated browser in a non-intrusive way.

Active installs1K+1K+ tier
Downloads · 30d480▼ -1.6% vs prev. 30d
Rating4.6/516 reviews
Health score76/100Good
All-time downloads135.9KSince Apr 2013
Support resolved—No recent threads
RequiresWP 6.0PHP 7.4+
Downloads · 7d123▼ -20.6% week over week
Our verdict

Solid choice

WP BrowserUpdate is a solid plugin choice in 2026, with a few things worth checking first. It runs on 1K+ sites, is rated 4.6/5 and was last updated 2 months ago, and scores 76/100 on our health check.

  • Tested with the latest WordPress (7.1)

How does it stack up?

Side-by-side on installs, updates, ratings & support

Daily downloads

102132Jun 30Aug 13Sep 27
Yesterday9
Daily average (1y)20
Peak day515May 4, 2026
Last 12 months7.1K

Download spikes usually follow a new release — each site that auto-updates counts as a download.

Rankings

Where WP BrowserUpdate stands today

WordPress.org search rankings

Live position in the plugin search, top 100
KeywordPositionCompeting pluginsCategory
browser #5 10,000 Best browser plugins →
notice #96 10,000 Best notice plugins →
outdated #7 1,005 Best outdated plugins →
update #34 10,000 Best update plugins →
warning #15 9,239 Best warning plugins →

Version adoption

Share of active sites per release.

  • 6.060.6%
  • 5.110.5%
  • 4.610.1%
  • 4.37.3%
  • Other11.5%

Rating breakdown

★★★★★★★★★★ 4.6 from 16 reviews

  • 5★68.8%
  • 4★25.0%
  • 3★0.00%
  • 2★6.3%
  • 1★0.00%

About WP BrowserUpdate

From the official readme · v6.0.1

Description

Many users still browse with outdated browsers, often unaware of the risks. Upgrading ensures better security and reliability. This plugin displays a subtle notification prompting visitors to update their browser. Activate the plugin, and it works seamlessly.

WP BrowserUpdate is based on the browser-update.org detection logic. The plugin now runs independently from browser-update.org at display time: the visitor-facing notification is served from the plugin’s own bundled runtime files, so sites do not need to load scripts, styles, or default notification links from browser-update.org. browser-update.org remains the credited upstream source for the bundled detection logic, and future runtime refreshes are tracked with source URLs and hashes in the plugin assets.

Visit browserupdate.org for more details about the upstream project.

Want to help translate this plugin? Visit the WordPress Translation Project.

How it works

WP BrowserUpdate bundles browser-update.org detection logic for WordPress. After activation, the plugin loads the local notification runtime from the plugin directory and passes your configured browser-version thresholds to those scripts. The notification is shown only when the bundled detection logic matches a browser to your settings.

The settings page is available under Settings > WP BrowserUpdate. You can define browser versions for every browser key supported by the bundled browser-update.org runtime, choose where the message appears and which element should contain it, enable testing mode, decide whether mobile or unsupported browsers should be notified, customize links, language and message text, and add trusted custom CSS for the notification.

Browser version fields accept major versions such as 115 and positive dotted versions such as 137.0.3912.63. Dotted versions are passed exactly to the bundled runtime instead of being reduced to their major version; exact comparison depends on the bundled browser-update.org logic and the browser key used by that runtime. A value of 0 uses the default bundled outdated-browser detection. Negative whole numbers are passed to the bundled runtime as relative offsets from the current bundled upstream version.

Microsoft Edge and Microsoft Internet Explorer have separate settings now.

This local runtime design avoids frontend blocking of external script URLs on sites with strict Content Security Policies or tracker blocking. WP BrowserUpdate ships only the local runtime and CSP adapter files needed by the plugin.

Important Notice

Breaking Changes in Version 6.0
– Requires WordPress 6.0 or newer.
– Introduces a new structured settings model to support the browser-update.org customization surface used by WP BrowserUpdate.
– Moves the visitor-facing browser-update.org runtime into the plugin package so strict Content Security Policies and tracker blockers no longer need to allow scripts from browser-update.org.
– Existing WP BrowserUpdate settings from version 5.x are migrated automatically.

Breaking Changes in Version 5.0
– Requires PHP 7.4 or newer.
– Ensure your hosting is updated to PHP 7.4 before upgrading to version 5.0 or newer.
– Servers running older PHP versions are no longer supported.
– If your server is running an earlier PHP version, please download version 4.8.1.

Installation

Installing via WordPress Plugin Search (Recommended)

This is the easiest and quickest way to install the plugin:
1. Log in to your WordPress admin dashboard.
2. Navigate to Plugins > Add New.
3. In the search bar, type WP BrowserUpdate.
4. Locate the correct plugin in the search results.
5. Click Install Now next to WP BrowserUpdate.
6. Once installed, click Activate to enable the plugin.

Manual Installation

If you prefer to install the plugin manually via SFTP, follow these steps:
1. Download the plugin
– Download the latest version from the WordPress Plugin Directory.
2. Extract the plugin files
– Locate the downloaded ZIP file and extract it on your computer.
– You should now have a folder named wp-browser-update.
3. Upload the plugin to your website
– Connect to your website using an FTP client (e. g., FileZilla) or access the File Manager in your hosting control panel.
– Navigate to /wp-content/plugins/ in your WordPress installation directory.
– Upload the extracted wp-browser-update folder.
4. Activate the plugin
– Log in to your WordPress admin dashboard.
– Go to Plugins > Installed Plugins.
– Find WP BrowserUpdate in the list and click Activate.

Installing via the WordPress Admin Panel

If you have already downloaded the ZIP file, you can install it via the WordPress admin panel:
1. Log in to your WordPress admin dashboard.
2. Navigate to Plugins > Add New.
3. Click Upload Plugin at the top of the page.
4. Click Choose File, select wp-browser-update.zip from your computer, and click Install Now.
5. Once the installation is complete, click Activate Plugin to enable it.

Changelog

6.0.1

  • Fixed:
    • Corrects the original plugin source strings to en-US so WordPress.org translations can provide locale-specific variants such as en-GB.

6.0.0

  • Breaking:
    • Requires WordPress 6.0 or newer.
    • Replaces the legacy space-separated settings storage with the structured wp_browserupdate_options option.
    • Migrates existing wp_browserupdate_browsers, wp_browserupdate_js, and wp_browserupdate_css_buorg values automatically.
    • Removes the old normal-render-path conversion of negative browser versions; values are now passed predictably to the bundled runtime.
    • Removes developer callback settings from the admin UI and saved settings model.
  • Added:
    • Adds interface coverage for the browser-update.org customization options used by WP BrowserUpdate: all runtime browser keys, reminderClosed, notify_esr, noclose, no_permanent_hide, container, url, url_permanent_hide, burl, fixed language, and text overrides.
  • Changed:
    • Takes the long-postponed step of making the browser-update.org integration CSP-compatible by shipping the complete runtime with the plugin, so sites on shared hosting or strict Content Security Policies no longer need to allow scripts from browser-update.org.
    • Adds the required browser-update.org runtime/adapter asset files intentionally, with upstream source URLs and hashes documented for attribution and review.
    • Loads bundled browser-update.org runtime files from the plugin directory through the WordPress script queue.
    • Removes browser-update.org runtime requests from the frontend by loading only same-origin plugin assets.
    • Uses WP BrowserUpdate CSP adapter files for the notification and test-mode scripts so the runtime can avoid generated inline styles.
    • Moves the frontend browser-update.org configuration and notification styles to local, enqueueable assets for better compatibility with stricter Content Security Policies.
    • Uses the WordPress HTTP API with a host allowlist for remote browser-version checks.
    • Uses the WordPress Settings API for the admin settings page.
    • Splits admin settings handling into smaller validation, migration and rendering steps.
    • Documents the bundled browser-update.org runtime, local frontend loading, and expected visitor-facing behavior.
    • Passes dotted browser versions such as 137.0.3912.63 to the bundled runtime without reducing them to major versions.
    • Adds separate Microsoft Edge and Microsoft Internet Explorer thresholds.
    • Ships only the loaded runtime/adapter files in the release package; upstream reference copies are documented by URL and hash rather than duplicated in the plugin ZIP.
  • Security:
    • Adds stricter settings validation before saving options.
    • Sanitizes custom CSS before saving and before frontend output.
    • Hardens external admin links with rel="noopener noreferrer".

5.1.1

  • Added:
    • Support for free-text input of browser versions (replaces dropdown selection)
    • Browser version check and caching
    • Cache duration filter: Added a wpbu_browser_version_cache_hours filter to allow developers to adjust the browser version cache duration (default: 6 hours).
  • Changed:
    • Admin settings page follows WordPress admin standards
    • Cleaner field structure: Improved markup and consistency of settings form fields
    • Security: Improved sanitization and nonce handling for all settings fields
    • Performance: Fewer unnecessary remote lookups when opening the admin settings page
  • Fixed:
    • Prevented a frontend “Uncaught Error” caused by invalid/unexpected browser version strings by hardening version parsing and normalization. Thanks to @danyloliptuha for pointing out.

5.0.0

  • Breaking Changes: PHP 7.4 now required.
  • Updated to follow WordPress Coding Standards.
  • Improved security and sanitization.
  • Integrated WordPress Settings API.
  • Added customization filters.
  • Optimized script and style handling.
  • Updated outdated browser versions.

4.8.1

  • Optimized code.
  • Fixed bug.
  • Updated outdated browser versions.

4.6.1

  • Removed redundant colons.
  • Updated outdated browser versions.

Full changelog on WordPress.org →

For developers

Is this your plugin? Show off the numbers.

Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.

Active installs badge Rating badge Health score badge

Best WP BrowserUpdate alternatives

All browser plugins →
Alternatives
Rank Plugin Active installs Rating Updated Health
1 WP Console – WordPress PHP Console powered by PsySH WP Console – WordPress PHP Console powered by PsySH An in-browser PHP console for WordPress powered by PsySH by Edi Amin 20K+ ★★★★★★★★★★ 5 (21) 1 month ago 86
2 Browser Screenshots Browser Screenshots Automate the process of taking website screenshots. by Kevin Leary 3K+ ★★★★★★★★★★ 4.8 (19) 3 years ago 39
3 Browser Theme Color Browser Theme Color Add the 'theme-color' meta tag to your website for a seamless user experience on Android &… by Marco Milesi 2K+ ★★★★★★★★★★ 5 (1) 1 year ago 44
5 Polylang – Country Detection Polylang – Country Detection This plugin detects the preferred language according on the country. by Markus Wiesenhofer 1K+ ★★★★★★★★★★ 5 (2) 4 years ago 34
6 PHP Browser Detection PHP Browser Detection PHP Browser Detection is a WordPress plugin used to detect a user's browser. Please report… by Mindshare Labs, Inc. 500+ ★★★★★★★★★★ 4.1 (16) 11 years ago 35
7 Friendly User Agent for WooCommerce Friendly User Agent for WooCommerce Displays the user agent (device/platform, browser and browser version) that was used by a… by Blaze Concepts 400+ ★★★★★★★★★★ 5 (10) 4 years ago 39
8 Developer Tools Blocker Developer Tools Blocker This plugin blocks non-admin users from using inspect element, while still allowing access… by SwiftNinjaPro 400+ ★★★★★★★★★★ 4.2 (15) 4 years ago 36
9 QR Scanner Redirect QR Scanner Redirect This WordPress plugin contains a web Qr scanner with a redirect function. It is also… by aigenseer 200+ ★★★★★★★★★★ 5 (4) 5 years ago 33
10 Open Search Document Open Search Document Lets browsers search your site straight from the address bar. by Matthias Pfefferle 200+ ★★★★★★★★★★ 5 (4) 1 week ago 76
11 WP-UserAgent WP-UserAgent WP-UserAgent is a simple plugin that allows you to display details about a computer's… by kyleabaker 200+ ★★★★★★★★★★ 5 (5) 6 years ago 38

FAQ

WP BrowserUpdate: quick answers

Straight answers, pulled from live WordPress.org data.

Live data from WordPress.org · checked Sep 28, 2026

Is WP BrowserUpdate free?

Yes. WP BrowserUpdate is free to download and use from the official WordPress.org plugin directory.

Is WP BrowserUpdate safe to use in 2026?

WP BrowserUpdate is a solid plugin choice in 2026, with a few things worth checking first. It runs on 1K+ sites, is rated 4.6/5 and was last updated 2 months ago, and scores 76/100 on our health check.

How many websites use WP BrowserUpdate?

WP BrowserUpdate is active on 1K+ WordPress websites and has been downloaded 135,900 times since it launched in April 2013. It was downloaded 480 times in the last 30 days.

Does WP BrowserUpdate work with WordPress 7.1?

Yes. The developer has tested WP BrowserUpdate up to WordPress 7.1.2, the latest release. It requires WordPress 6.0 or newer.

What PHP version does WP BrowserUpdate need?

WP BrowserUpdate requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.

When was WP BrowserUpdate last updated?

The latest version, 6.0.1, was released on August 13, 2026 (2 months ago).

Who makes WP BrowserUpdate?

WP BrowserUpdate is developed and maintained by MacSteini.

What are the best alternatives to WP BrowserUpdate?

The most popular alternatives to WP BrowserUpdate are WP Console (20K+ installs), Browser Screenshots (3K+ installs) and Browser Theme Color (2K+ installs).

Powered by PageForge

Want thousands of pages that rank like these? Build them in an afternoon.

This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.

  • CSV, Google Sheets & API data sources
  • AI content, schema & internal links per page
  • Works with Elementor, Gutenberg, Yoast & Rank Math
  • Free on WordPress.org — no credit card
Sarah is here to help!
Hi there! 👋 Need help finding what you're looking for?
Sarah
Sarah
Online & Ready to Help
Hi there! 👋 Need help finding what you're looking for?

We'll use this to continue our conversation

Just now ✓ Verified

Join 500+ SEO Pros Scaling Their Strategy

Get exclusive programmatic SEO tactics, AI content workflows, and the latest PageForge updates delivered straight to your inbox. Stay ahead of the algorithm.

We care about your data in our privacy policy.