WP CSS Merge
WP CSS Merge reduces compatible frontend stylesheet requests by combining local CSS files into cached bundles.
Use with caution
WP CSS Merge works, but test it on a staging site before relying on it in 2026. Was last updated 1 month ago, and scores 60/100 on our health check.
- Tested with the latest WordPress (7.1)
- Small user base (<10 active installs)
- Very few reviews so far
How does it stack up?
Side-by-side on installs, updates, ratings & support
Daily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where WP CSS Merge stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| cache | >100 |
| css | >100 |
| optimization | >100 |
| performance | >100 |
About WP CSS Merge
From the official readme · v2.0.2Description
WP CSS Merge reduces compatible frontend stylesheet requests by combining local CSS files into cached bundles.
Version 2 uses a safety-first bundle engine:
- Uses WordPress’s resolved print order, including late dependency changes and already printed styles.
- Creates different bundles for different style sets instead of sharing one global file.
- Keeps external, inline, conditional, RTL, unsupported, and excluded styles unchanged. Bypasses bundling when other plugins filter stylesheet tags or URLs, preserving integrity hashes, CDN rewrites, and per-file attributes.
- Rebases relative image and font URLs to their original public locations.
- Writes cache files atomically in the current site’s uploads directory.
- Automatically serves the original stylesheets whenever bundling is unavailable or unsuccessful.
- Fingerprints the actual source contents, versions, settings, locale, URLs, and printed style combinations. Source changes are detected even when timestamps and file sizes are unchanged.
- Retains published bundles for cached pages across setting changes, updates, theme switches, and deactivation.
- Supports multisite with a separate cache location for each site.
The plugin never downloads remote CSS, contacts external services, or sends telemetry.
Because HTTP/2 and HTTP/3 reduce the cost of multiple requests, combining every stylesheet is not always faster. WP CSS Merge therefore combines only contiguous compatible styles. Source contents are read on each uncached PHP page request to verify freshness; existing bundles avoid repeated CSS transformation and writes.
Installation
- Install and activate WP CSS Merge.
- Go to Settings > WP CSS Merge.
- Enable CSS bundling and save the settings.
- Visit the frontend to allow bundles to be generated for the style combinations in use.
New source contents and style combinations automatically select new bundle URLs. Published files are retained because page and CDN caches may still reference them. Purge those caches before using Clear generated CSS or uninstalling the plugin. Deactivation preserves generated files for existing cached pages.
Frequently asked questions
What happens on the first request?
The plugin builds a bundle when its first stylesheet link is being printed. If generation fails, the original stylesheets load unchanged.
Why are some stylesheets not combined?
External stylesheets and styles with inline, conditional, RTL, unsupported at-rule, or different media behavior remain separate to protect rendering and cascade order. Handles listed in the exclusion setting also remain separate. If another plugin filters stylesheet links or URLs, bundling is bypassed for that request so every original filter and attribute is preserved.
Can the cache grow indefinitely?
New bundle writes have a default 100 MB storage budget per site. At the budget, uncached style combinations fall back to original files while existing bundles remain usable. Concurrent writes may briefly exceed the budget. The wp_css_merge_max_cache_size filter can change the budget in bytes. Purge page and CDN caches before manually clearing generated CSS to reclaim storage.
Where are bundles stored?
Bundles are stored in a wp-css-merge directory inside the current site’s WordPress uploads directory. Multisite installations receive separate site-specific directories through the normal uploads API.
Does the plugin collect or transmit data?
No. WP CSS Merge performs local filesystem and stylesheet processing only. It does not use external services, telemetry, or tracking.
How do I find a stylesheet handle to exclude?
Stylesheet handles are the first argument passed to wp_enqueue_style(). A theme or plugin developer can provide the relevant handle when troubleshooting compatibility.
Changelog
Fixes filtered styles, late print order, cache retention, and same-timestamp CSS updates.
2.0.2
- Built bundles from WordPress’s actual print list only when their first link is emitted.
- Preserved third-party stylesheet filters, integrity hashes, CDN rewrites, and custom attributes.
- Fingerprinted the exact CSS source bytes to detect changes with unchanged timestamps and sizes.
- Retained published bundle URLs across automatic changes and deactivation, with a storage budget and explicit clearing.
- Added real WordPress loader and filesystem regressions and made HTTP tests preserve site options.
- Updated development dependencies and clarified cache management and compatibility.
2.0.1
- Kept styles with WordPress inline-path metadata outside generated bundles.
- Added a WordPress 7 wp-env regression test for inline-style boundaries and automatic fallback.
2.0.0
- Replaced the single global CSS file with context-specific, fingerprinted bundles.
- Added automatic fallback to original WordPress styles on every generation or validation failure.
- Preserved dependency order, media grouping, and unsupported style behavior.
- Added safe same-site path resolution and relative asset URL rebasing.
- Added atomic cache writes, stale cache cleanup, per-site multisite storage, and cache controls.
- Replaced the AJAX toggle and unrelated promotion with accessible native WordPress settings.
- Added exclusions, conservative minification, lifecycle cleanup, and current compatibility metadata.
1.0.5
- Improved path compatibility across operating systems.
1.0.0
- Initial release.
Screenshots
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.
Best WP CSS Merge alternatives
All cache plugins →
FAQ
WP CSS Merge: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Oct 10, 2026
Is WP CSS Merge free?
Yes. WP CSS Merge is free to download and use from the official WordPress.org plugin directory.
Is WP CSS Merge safe to use in 2026?
WP CSS Merge works, but test it on a staging site before relying on it in 2026. Was last updated 1 month ago, and scores 60/100 on our health check.
How many websites use WP CSS Merge?
WP CSS Merge is active on <10 WordPress websites and has been downloaded 1,741 times since it launched in October 2019. It was downloaded 95 times in the last 30 days.
Does WP CSS Merge work with WordPress 7.1?
Yes. The developer has tested WP CSS Merge up to WordPress 7.1.3, the latest release. It requires WordPress 6.0 or newer.
What PHP version does WP CSS Merge need?
WP CSS Merge requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was WP CSS Merge last updated?
The latest version, 2.0.2, was released on September 5, 2026 (1 month ago).
Who makes WP CSS Merge?
WP CSS Merge is developed and maintained by digitalapps.
What are the best alternatives to WP CSS Merge?
The most popular alternatives to WP CSS Merge are WP Super Cache (1M+ installs), WP Fastest Cache (1M+ installs) and WP-Optimize (1M+ 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
