Title: WP CSS Merge
Author: digitalapps
Published: <strong>Mukulukusa bitungotungo 3, 2019</strong>
Last modified: Kasambula 27, 2026

---

Search plugins

![](https://ps.w.org/wp-css-merge/assets/banner-772x250.png?rev=2167386)

![](https://ps.w.org/wp-css-merge/assets/icon-256x256.png?rev=2167263)

# WP CSS Merge

 By [digitalapps](https://profiles.wordpress.org/digitalapps/)

[Download](https://downloads.wordpress.org/plugin/wp-css-merge.2.0.1.zip)

 * [Details](https://lug.wordpress.org/plugins/wp-css-merge/#description)
 * [Reviews](https://lug.wordpress.org/plugins/wp-css-merge/#reviews)
 *  [Installation](https://lug.wordpress.org/plugins/wp-css-merge/#installation)
 * [Development](https://lug.wordpress.org/plugins/wp-css-merge/#developers)

 [Support](https://wordpress.org/support/plugin/wp-css-merge/)

## Description

WP CSS Merge reduces compatible frontend stylesheet requests by combining local 
CSS files into cached bundles.

Version 2 uses a safety-first bundle engine:

 * Preserves the dependency and cascade order managed by WordPress.
 * Creates different bundles for different style sets instead of sharing one global
   file.
 * Keeps external, inline, conditional, RTL, unsupported, and excluded styles unchanged.
 * 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.
 * Invalidates bundles when source files, versions, settings, locale, or queued 
   style combinations change.
 * 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
styles that can be moved safely without changing their behavior.

## Screenshots

[⌊Configure safe CSS bundling, conservative minification, handle exclusions, and
generated cache controls.⌉⌊Configure safe CSS bundling, conservative minification,
handle exclusions, and generated cache controls.⌉[

Configure safe CSS bundling, conservative minification, handle exclusions, and generated
cache controls.

[⌊WP CSS Merge active on the Plugins screen with its direct Settings action and 
release metadata.⌉⌊WP CSS Merge active on the Plugins screen with its direct Settings
action and release metadata.⌉[

WP CSS Merge active on the Plugins screen with its direct Settings action and release
metadata.

## Installation

 1. Install and activate WP CSS Merge.
 2. Go to Settings > WP CSS Merge.
 3. Enable CSS bundling and save the settings.
 4. Visit the frontend to allow bundles to be generated for the style combinations 
    in use.

Use the cache status panel to clear generated files after troubleshooting. Cache
clearing is normally automatic when settings, themes, plugins, or source styles 
change.

## FAQ

### What happens on the first request?

The plugin attempts to build the required bundle before styles are printed. If the
file cannot be created and verified, 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.

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

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“WP CSS Merge” is open source software. The following people have contributed to
this plugin.

Contributors

 *   [ digitalapps ](https://profiles.wordpress.org/digitalapps/)

[Translate “WP CSS Merge” into your language.](https://translate.wordpress.org/projects/wp-plugins/wp-css-merge)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/wp-css-merge/), check
out the [SVN repository](https://plugins.svn.wordpress.org/wp-css-merge/), or subscribe
to the [development log](https://plugins.trac.wordpress.org/log/wp-css-merge/) by
[RSS](https://plugins.trac.wordpress.org/log/wp-css-merge/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

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

## Meta

 *  Version **2.0.1**
 *  Last updated **1 omwezi ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 6.0 or higher **
 *  Tested up to **7.0.4**
 *  PHP version ** 7.4 or higher **
 *  Language
 * [English (US)](https://wordpress.org/plugins/wp-css-merge/)
 * Tags
 * [cache](https://lug.wordpress.org/plugins/tags/cache/)[css](https://lug.wordpress.org/plugins/tags/css/)
   [optimization](https://lug.wordpress.org/plugins/tags/optimization/)[performance](https://lug.wordpress.org/plugins/tags/performance/)
 *  [Advanced View](https://lug.wordpress.org/plugins/wp-css-merge/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/wp-css-merge/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/wp-css-merge/reviews/)

## Contributors

 *   [ digitalapps ](https://profiles.wordpress.org/digitalapps/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/wp-css-merge/)