On This Page
On This Page
Remove Version From Scripts
Overview
On the front end, strips ver= from script/style URLs only when the value equals the WordPress core version. Theme and plugin versions remain so updates still bust caches. Conflicts with Remove Query Strings. An optional filter can strip all local ver= for logged-out users.

- Sites that want less core-version fingerprinting in public HTML
- Teams that still need theme/plugin cache busting via
ver= - Security-minded setups reducing obvious WP version leakage in asset URLs
Features
Core version only
Keeps theme/plugin versions
Developer filter
Use Cases
- Core version fingerprint reductionHide the WordPress core version from public asset URLs during a light hardening pass—without claiming full version hiding elsewhere.
- Keep theme and plugin cache bustingTeams that update CSS/JS often can remove only the core ver= and still rely on theme/plugin version strings after releases.
- Preferable to full query-string strippingChoose this when Remove Query Strings is too aggressive and you need local theme/plugin ver= to keep working.
Frequently Asked Questions
What does the Remove Version from Scripts module do in WP PowerSuite?
It removes ver= from public script and style URLs only when that value matches the WordPress core version. Theme and plugin version parameters stay for cache busting.
How do I enable Remove Version from Scripts in WP PowerSuite?
Enable it in the Modules hub, keep Remove Query Strings off, then verify public page source.
Who should use Remove Version from Scripts?
Sites that want less core-version fingerprinting in HTML while still busting caches after theme and plugin updates.
Is this the same as Remove Query Strings?
No. This only removes the core WordPress version. Remove Query Strings strips all local ver= markers. Do not enable both.
Is Remove Version from Scripts a free or Pro module in WP PowerSuite?
It is included (free) with WP PowerSuite.

