Title: WP CSS Merge
Author: digitalapps
Published: <strong>3 outubro, 2019</strong>
Last modified: 5 setembro, 2026

---

Pesquisar plugins

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

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

# WP CSS Merge

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

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

 * [Detalhes](https://br.wordpress.org/plugins/wp-css-merge/#description)
 * [Avaliações](https://br.wordpress.org/plugins/wp-css-merge/#reviews)
 *  [Instalação](https://br.wordpress.org/plugins/wp-css-merge/#installation)
 * [Desenvolvimento](https://br.wordpress.org/plugins/wp-css-merge/#developers)

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

## Descrição

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.

## Capturas de tela

[⌊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.

[⌊The plugin active on the Plugins screen with its direct Settings action and release
metadata.⌉⌊The plugin active on the Plugins screen with its direct Settings action
and release metadata.⌉[

The plugin active on the Plugins screen with its direct Settings action and release
metadata.

## Instalação

 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.

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.

## Perguntas frequentes

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

## Avaliações

Não há avaliações para este plugin.

## Colaboradores e desenvolvedores

“WP CSS Merge” é um programa de código aberto. As seguintes pessoas contribuíram
para este plugin.

Colaboradores

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

[Traduzir o “WP CSS Merge” para seu idioma.](https://translate.wordpress.org/projects/wp-plugins/wp-css-merge)

### Interessado no desenvolvimento?

[Navegue pelo código](https://plugins.trac.wordpress.org/browser/wp-css-merge/),
consulte o [repositório SVN](https://plugins.svn.wordpress.org/wp-css-merge/) ou
assine o [registro de desenvolvimento](https://plugins.trac.wordpress.org/log/wp-css-merge/)
por [RSS](https://plugins.trac.wordpress.org/log/wp-css-merge/?limit=100&mode=stop_on_copy&format=rss).

## Registro de alterações

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

## Meta

 *  Versão **2.0.2**
 *  Última atualização **3 semanas atrás**
 *  Instalações ativas **Menos de 10**
 *  Versão do WordPress ** 6.0 ou superior **
 *  Testado até **7.1.2**
 *  Versão do PHP ** 7.4 ou superior **
 *  Idioma
 * [English (US)](https://wordpress.org/plugins/wp-css-merge/)
 * Tags
 * [cache](https://br.wordpress.org/plugins/tags/cache/)[css](https://br.wordpress.org/plugins/tags/css/)
   [optimization](https://br.wordpress.org/plugins/tags/optimization/)[performance](https://br.wordpress.org/plugins/tags/performance/)
 *  [Visualização avançada](https://br.wordpress.org/plugins/wp-css-merge/advanced/)

## Classificações

Ainda não foi enviada nenhuma avaliação.

[Sua avaliação](https://wordpress.org/support/plugin/wp-css-merge/reviews/#new-post)

[Ver todas avaliações](https://wordpress.org/support/plugin/wp-css-merge/reviews/)

## Colaboradores

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

## Suporte

Tem algo a dizer? Precisa de ajuda?

 [Ver fórum de suporte](https://wordpress.org/support/plugin/wp-css-merge/)