Hide WordPress Paths in Cached and Minified CSS Files with WP Ghost
May 7, 2019
This tutorial has moved to the new WP Ghost Knowledge Base where each feature is presented in detail.
Hide WordPress paths inside cached and minified CSS files using WP Ghost’s (formerly Hide My WP Ghost) Change Paths in Cached Files feature. Caching plugins generate static CSS files that bypass WP Ghost’s real-time path rewriting. Enable one toggle, clear your cache, and WP Ghost rewrites paths in those files in the background with zero speed impact.
Why Cached CSS Files Leak WordPress Paths
WP Ghost changes WordPress paths in real time as pages are generated. But caching plugins like WP Rocket, LiteSpeed Cache, W3 Total Cache, and WP Fastest Cache generate static CSS and JS files in a cache directory. These files are served directly by the server without passing through WordPress, so WP Ghost never gets a chance to rewrite the paths inside them.
The result: your HTML shows custom paths, but the minified CSS files still reference /wp-content/plugins/, /wp-content/themes/, and /wp-content/uploads/ in their @import rules, background-image URLs, and font-face declarations. CMS scanners pick up these inconsistencies.
How to Fix: Enable Change Paths in Cached Files
Go to WP Ghost > Tweaks. Switch on Change Paths in Cached Files. Click Save. Then clear your cache plugin’s cache so it regenerates the static files.
Once the cache is regenerated, WP Ghost processes the new cached files in the background and replaces all WordPress paths with your custom ones. This happens after the cache files are created, not during page loads. Visitors experience the same cached performance as before.
Tested Cache Plugins
WP Ghost has been tested with: Autoptimize, Breeze, Cache Enabler, Comet Cache, Hummingbird, Hyper Cache, LiteSpeed Cache, NitroPack, Power Cache, W3 Total Cache, WP Fastest Cache, WP Rocket, and WP Super Cache. All passed successfully. For the full list and configuration notes, see the Compatibility Plugins List.
Troubleshooting
WordPress paths still appear in CSS files after enabling
The cache was not cleared after enabling the feature. Clear your caching plugin’s cache completely, then let it regenerate. WP Ghost processes the newly generated files. Also clear your browser cache and CDN cache. View a CSS file directly in a private browser to confirm paths are changed.
Cache plugin uses a non-standard directory
WP Ghost auto-detects most cache directories. If your caching plugin stores files in a non-standard location, click Set Custom Cache Directory in WP Ghost > Tweaks and enter the path. This is common with cloud-based optimization services like NitroPack or Rabbit Loader.
CSS files load but the site is slightly slower on first visit
The first uncached page load triggers cache generation and WP Ghost’s background processing. Subsequent visits are served from the processed cache at full speed. This is normal behavior for any cache plugin and not specific to WP Ghost.
Frequently Asked Questions
Does this slow down my website?
No. Path rewriting happens in the background after cache files are generated, not during page loads. Visitors experience the same cached performance. The only difference is the cached files contain custom paths instead of default WordPress paths.
Do I need this if I do not use a caching plugin?
Not for caching purposes, but you may still need it for page builders. Elementor, Divi, WPBakery, and other builders save their own CSS files separately from caching plugins. Enable this feature if any plugin generates static CSS files that contain WordPress paths. See the Page Builder Image Paths tutorial.
Will this work with minified and combined CSS files?
Yes. When caching plugins minify and combine CSS files, the resulting files still contain WordPress paths in url() references. WP Ghost processes these combined files the same way it processes individual CSS files.
Does this also change paths in cached JS files?
Yes. The feature processes all file types in the cache directory: CSS, JS, and HTML. Any cached file containing WordPress paths gets updated.
Does WP Ghost modify WordPress core files?
No. WP Ghost modifies the contents of cached files generated by your caching or builder plugin, not WordPress core files. Original CSS, JS, and PHP files remain untouched. Only static copies in the cache directory are rewritten.
Related Tutorials
Hide Image Paths for Page Builders – the same feature applied to Elementor, Divi, and other builders.
Compatibility Plugins List – all tested cache plugins with configuration notes.
URL Mapping and Text Mapping – rename class names and URLs that remain after path changes.
Customize All WordPress Paths – set up the custom paths that this feature applies to cached files.
Website Security Check – verify your configuration after enabling.