PageForge 1.3: Verifique todas as corridas antes de escrever, atualize as páginas geradas, SpinTax e lotes reumáveis. Veja o que mudou
WP Super Cache icon
Manutenção ativamente Testado com WP 7.1 #36 most installed plugin #1 in cache

WP Super Cache

Um mecanismo de cache muito rápido para WordPress que produz arquivos HTML estáticos.

Instalações ativas1M+Nível 1M+
Downloads · 30d975.4K▲ +10.5% vs prev. 30d
Classificação4.3/51,346 reviews
Pontuação da saúde93/100Excelente
Downloads de todos os tempos67.5MSince Nov 2007
Suporte resolvido5 / 683% in last 2 months
RequerWP 6.8Php 7.4+
Classificação geral#36of 75,818 plugins
Nosso veredicto

Escolha segura

Yes — WP Super Cache is a safe, well-maintained plugin to use in 2026. It runs on 1M+ sites, is rated 4.3/5 and was last updated 3 weeks ago, and scores 93/100 on our health check.

  • Um dos plugins mais usados na web: 1M+ sites ativos
  • Desenvolvido ativamente — última atualização 3 semanas atrás
  • Testado com as últimas WordPress (7.1)
  • Suporte responsivo — 83% dos tópicos recentes resolvidos

Como ele se acumula?

Lado a lado em instalações, atualizações, avaliações e suporte

Downloads diários

125.1K250.2K375.3KAug 22Oct 5Nov 19
Ontem23,739
Média diária (1y)17,473
Dia de pico500,370Aug 27, 2026
Últimos 12 meses6.4M

Os picos de download geralmente seguem uma nova versão — cada site que atualiza automaticamente é um download.

Rankings

Where WP Super Cache stands today
Popularidade geral #36 of 75,818 WordPress.org plugins Top 0,05%
1M+ instala o nível 25 of 56
Próxima camada: 5m+ instala
Esconderijo #1 of 492 plugins → Caching #2 of 124 plugins → Execução #2 of 1,117 plugins → WP Cache #1 of 12 plugins → WP Super Cache #1 de 8 plugins →

WordPress.org Classificações de pesquisa

Posição ao vivo na pesquisa de plugins, top 100
Palavra chavePosiçãoPlugins concorrentesCategoria
esconderijo #3 10,000 Melhores plugins de cache →
caching #9 7,079 Best caching plugins →
execução #36 10,000 Plugins de melhor desempenho →
WP Cache #3 9,505 Best WP Cache plugins →
WP Super Cache #1 1,268 Best WP Super Cache plugins →

Adoção da versão

Compartilhamento de sites ativos por lançamento.

  • 3.159.9%
  • 3.010.3%
  • 1.77.4%
  • 1.125.2%
  • 2.05.0%
  • Outros12.2%

Divisão de classificação

★★★★★★★★★★ 4.3 from 1,346 reviews

  • 5★73.8%
  • 4★8.0%
  • 3★3.5%
  • 2★1.8%
  • 1★12.9%

About WP Super Cache

From the official readme · v3.1.5

Descrição

This plugin generates static html files from your dynamic WordPress blog. After a html file is generated your webserver will serve that file instead of processing the comparatively heavier and more expensive WordPress PHP scripts.

The static html files will be served to the vast majority of your users:

  • Users who are not logged in.
  • Users who have not left a comment on your blog.
  • Or users who have not viewed a password protected post.

99% of your visitors will be served static html files. One cached file can be served thousands of times. Other visitors will be served custom cached files tailored to their visit. If they are logged in, or have left comments those details will be displayed and cached for them.

The plugin serves cached files in 3 ways (ranked by speed):

  1. Expert. The fastest method is by using Apache mod_rewrite (or whatever similar module your web server supports) to serve “supercached” static html files. This completely bypasses PHP and is extremely quick. If your server is hit by a deluge of traffic it is more likely to cope as the requests are “lighter”. This does require the Apache mod_rewrite module (which is probably installed if you have custom permalinks) and a modification of your .htaccess file which is risky and may take down your site if modified incorrectly.
  2. Simple. Supercached static files can be served by PHP and this is the recommended way of using the plugin. The plugin will serve a “supercached” file if it exists and it’s almost as fast as the mod_rewrite method. It’s easier to configure as the .htaccess file doesn’t need to be changed. You still need a custom permalink. You can keep portions of your page dynamic in this caching mode.
  3. WP-Cache caching. This is mainly used to cache pages for known users, URLs with parameters and feeds. Known users are logged in users, visitors who leave comments or those who should be shown custom per-user data. It’s the most flexible caching method and slightly slower. WP-Cache caching will also cache visits by unknown users if supercaching is disabled. You can have dynamic parts to your page in this mode too. This mode is always enabled but you can disable caching for known users, URLs with parameters, or feeds separately. Set the constant “DISABLE_SUPERCACHE” to 1 in your wp-config.php if you want to only use WP-Cache caching.

If you’re not comfortable with editing PHP files then use simple mode. It’s easy to set up and very fast.

Recommended Settings

  1. Simple caching.
  2. Compress pages.
  3. Don’t cache pages for known users.
  4. Cache rebuild.
  5. CDN support.
  6. Extra homepage checks.

Garbage collection is the act of cleaning up cache files that are out of date and stale. There’s no correct value for the expiry time but a good starting point is 1800 seconds.

Consider deleting the contents of the “Rejected User Agents” text box and allow search engines to cache files for you.

Preload as many posts as you can and enable “Preload Mode”. Garbage collection of old cached files will be disabled. If you don’t care about sidebar widgets updating often set the preload interval to 2880 minutes (2 days) so all your posts aren’t recached very often. When the preload occurs the cache files for the post being refreshed is deleted and then regenerated. Afterwards a garbage collection of all old files is performed to clean out stale cache files.
Even with preload mode enabled cached files will still be deleted when posts are modified or comments made.

Development

  • Active development of this plugin is handled on GitHub.
  • Translation of the plugin into different languages is on the translation page.

Documentação

If you need more information than the following, you can have a look at the wiki or the Developer documentation.

Preloading

You can generate cached files for the posts, categories and tags of your site by preloading. Preloading will visit each page of your site generating a cached page as it goes along, just like any other visitor to the site. Due to the sequential nature of this function, it can take some time to preload a complete site if there are many posts.
To make preloading more effective it can be useful to disable garbage collection so that older cache files are not deleted. This is done by enabling “Preload Mode” in the settings. Be aware however, that pages will go out of date eventually but that updates by submitting comments or editing posts will clear portions of the cache.

Garbage Collection

Your cache directory fills up over time, which takes up space on your server. If space is limited or billed by capacity, or if you worry that the cached pages of your site will go stale then garbage collection has to be done. Garbage collection happens on a regular basis and deletes old files in the cache directory. On the advanced settings page you can specify:
1. Cache timeout. How long cache files are considered fresh for. After this time they are stale and can be deleted.
2. Scheduler. Setup how often garbage collection should be done.
3. Notification emails. You can be informed on garbage collection job progress.
There’s no right or wrong settings for garbage collection. It depends on your own site.
If your site gets regular updates, or comments then set the timeout to 1800 seconds, and set the timer to 600 seconds.
If your site is mostly static you can disable garbage collection by entering 0 as the timeout, or use a really large timeout value.

The cache directory, usually wp-content/cache/ is only for temporary files. Do not ever put important files or symlinks to important files or directories in that directory. They will be deleted if the plugin has write access to them.

CDN

A Content Delivery Network (CDN) is usually a network of computers situated around the world that will serve the content of your website faster by using servers close to you. Static files like images, Javascript and CSS files can be served through these networks to speed up how fast your site loads. You can also create a “poor man’s CDN” by using a sub domain of your domain to serve static files too.

OSSDL CDN off-linker has been integrated into WP Super Cache to provide basic CDN support. It works by rewriting the URLs of files (excluding .php files) in wp-content and wp-includes on your server so they point at a different hostname. Many CDNs support origin pull. This means the CDN will download the file automatically from your server when it’s first requested, and will continue to serve it for a configurable length of time before downloading it again from your server.

Configure this on the “CDN” tab of the plugin settings page. This is an advanced technique and requires a basic understanding of how your webserver or CDNs work. Please be sure to clear the file cache after you configure the CDN.

Descanse API

There are now REST API endpoints for accessing the settings of this plugin. You’ll need to be authenticated as an admin user with permission to view the settings page to use it. This has not been documented yet but you can find all the code that deals with this in the “rest” directory.

Custom Caching

It is now possible to hook into the caching process using the add_cacheaction() function.

Three hooks are available:

  1. ‘wp_cache_get_cookies_values’ – modify the key used by WP Cache.
  2. ‘add_cacheaction’ – runs in phase2. Allows a plugin to add WordPress hooks.
  3. ‘cache_admin_page’ – runs in the admin page. Use it to modify that page, perhaps by adding new configuration options.

There is one regular WordPress filter too. Use the “do_createsupercache” filter
to customize the checks made before caching. The filter accepts one parameter.
The output of WP-Cache’s wp_cache_get_cookies_values() function.

WP Super Cache has its own plugin system, loaded before most of WordPress. Add your own plugin either by putting it in the wp-content/plugins/wp-super-cache-plugins directory, or by calling wpsc_add_plugin( $name ) with the full path to the plugin.

The cookies used to identify “known users” can be modified with wpsc_add_cookie( $name ) and wpsc_delete_cookie( $name ). See plugins/searchengine.php as an example.

Solução de problemas

If things don’t work when you installed the plugin here are a few things to check:

  1. Is wp-content writable by the web server?
  2. Is there a wp-content/wp-cache-config.php ? If not, copy the file wp-super-cache/wp-cache-config-sample.php to wp-content/wp-cache-config.php and make sure WPCACHEHOME points at the right place.
  3. Is there a wp-content/advanced-cache.php ? If not, then you must copy wp-super-cache/advanced-cache.php into wp-content/. You must edit the file and change the path so it points at the wp-super-cache folder.
  4. If pages are not cached at all, remove wp-content/advanced-cache.php and recreate it, following the advice above.
  5. Make sure the following line is in wp-config.php and it is ABOVE the “require_once(ABSPATH.’wp-settings.php’);” line:

    define( 'WP_CACHE', true );
    
  6. Try the Settings->WP Super Cache page again and enable cache.
  7. Look in wp-content/cache/supercache/. Are there directories and files there?
  8. Anything in your php error_log?
  9. If your browser keeps asking you to save the file after the super cache is installed you must disable Super Cache compression. Go to the Settings->WP Super Cache page and disable it there.
  10. File locking errors such as “failed to acquire key 0x152b: Permission denied in…” or “Page not cached by WP Super Cache. Could not get mutex lock.” are a sign that you may have to use file locking. Edit wp-content/wp-cache-config.php and uncomment “$use_flock = true” or set $sem_id to a different value. You can also disable file locking from the Admin screen as a last resort.
  11. Make sure cache/wp_cache_mutex.lock is writable by the web server if using coarse file locking.
  12. The cache folder cannot be put on an NFS or Samba or NAS share. It has to be on a local disk. File locking and deleting expired files will not work properly unless the cache folder is on the local machine.
  13. Garbage collection of old cache files won’t work if WordPress can’t find wp-cron.php. Check your access_logs for wp-cron.php entries and that your hostname resolves to the external IP address other servers on the network/Internet use.
  14. If old pages are being served to your visitors via the supercache, you may be missing Apache modules (or their equivalents if you don’t use Apache). 3 modules are required: mod_mime, mod_headers and mod_expires. The last two are especially important for making sure browsers load new versions of existing pages on your site.
  15. The error message, “WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed!” appears at the end of every page. Open the file wp-content/advanced-cache.php in your favourite editor. Is the path to wp-cache-phase1.php correct? This file will normally be in wp-content/plugins/wp-super-cache/. If it is not correct the caching engine will not load.
  16. Caching doesn’t work. The timestamp on my blog keeps changing when I reload. Check that the path in your .htaccess rules matches where the supercache directory is. You may have to hardcode it. Try disabling supercache mode.
  17. If supercache cache files are generated but not served, check the permissions on all your wp-content/cache/supercache folders (and each of wp-content cache and supercache folders) and wp-content/cache/.htaccess. If your PHP runs as a different user to Apache and permissions are strict Apache may not be able to read the PHP generated cache files. To fix you must add the following line to your wp-config.php (Add it above the WP_CACHE define.) Then clear your cache.

    umask( 0022 );
    
  18. If you see garbage in your browser after enabling compression in the plugin, compression may already be enabled in your web server. In Apache you must disable mod_deflate, or in PHP zlib compression may be enabled. You can disable that in three ways. If you have root access, edit your php.ini and find the zlib.output_compression setting and make sure it’s “Off” or add this line to your .htaccess:

    php_flag zlib.output_compression off
    

    If that doesn’t work, add this line to your wp-config.php:

    ini_set('zlib.output_compression', 0);
    
  19. After uninstalling, your permalinks may break if you remove the WordPress mod_rewrite rules too. Regenerate those rules by visiting the Settings->Permalink page and saving that form again.
  20. If your blog refuses to load make sure your wp-config.php is correct. Are you missing an opening or closing PHP tag?
  21. Your front page is ok but posts and pages give a 404? Go to Settings->permalinks and click “Save” once you’ve selected a custom permalink structure. You may need to manually update your .htaccess file.
  22. If certain characters do not appear correctly on your website your server may not be configured correctly. You need to tell visitors what character set is used. Go to Settings->Reading and copy the ‘Encoding for pages and feeds’ value. Edit the .htaccess file with all your Supercache and WordPress rewrite rules and add this at the top, replacing CHARSET with the copied value. (for example, ‘UTF-8’)

    AddDefaultCharset CHARSET
    
  23. The error message, “WP Super Cache is installed but broken. The constant WPCACHEHOME must be set in the file wp-config.php and point at the WP Super Cache plugin directory.” appears at the end of every page. You can delete wp-content/advanced-cache.php and reload the plugin settings page or edit wp-config.php and look for WPCACHEHOME and make sure it points at the wp-super-cache folder. This will normally be wp-content/plugins/wp-super-cache/ but you’ll likely need the full path to that file (so it’s easier to let the settings page fix it). If it is not correct the caching engine will not load.
  24. If your server is running into trouble because of the number of semaphores used by the plugin it’s because your users are using file locking which is not recommended (but is needed by a small number of users). You can globally disable file locking by defining the constant WPSC_DISABLE_LOCKING, or defining the constant WPSC_REMOVE_SEMAPHORE so that sem_remove() is called after every page is cached but that seems to cause problems for other processes requesting the same semaphore. Best to disable it.
  25. Set the variable $htaccess_path in wp-config.php or wp-cache-config.php to the path of your global .htaccess if the plugin is looking for that file in the wrong directory. This might happen if you have WordPress installed in an unusual way.

Instalação

Install like any other plugin, directly from your plugins page but make sure you have custom permalinks enabled. Go to the plugin settings page at Settings->WP Super Cache and enable caching.

How to uninstall WP Super Cache

Almost all you have to do is deactivate the plugin on the plugins page. The plugin should clean up most of the files it created and modified, but it doesn’t as yet remove the mod_rewrite rules from the .htaccess file. Look for the section in that file marked by SuperCache BEGIN and END tags. The plugin doesn’t remove those because some people add the WordPress rules in that block too.

To manually uninstall:

  1. Turn off caching on the plugin settings page and clear the cache.
  2. Deactivate the plugin on the plugins page.
  3. Remove the WP_CACHE define from wp-config.php. It looks like define( 'WP_CACHE', true );
  4. Remove the Super Cache mod_rewrite rules from your .htaccess file.
  5. Remove the files wp-content/advanced-cache.php and wp-content/wp-cache-config.php
  6. Remove the directory wp-content/cache/
  7. Remove the directory wp-super-cache from your plugins directory.

If all else fails and your site is broken

  1. Remove the WP_CACHE define from wp-config.php. It looks like define( 'WP_CACHE', true );
  2. Remove the rules (see above) that the plugin wrote to the .htaccess file in your root directory.
  3. Delete the wp-super-cache folder in the plugins folder.
  4. Optionally delete advanced-cache.php, wp-cache-config.php and the cache folder in wp-content/.

Log de Changes

3.1.5 – 2026-11-02

  • Fix: requests with a malformed Host header are no longer cached or served from the cache, so they can no longer overwrite another page’s cached copy.

3.1.4 – 2026-09-30

  • Fix: the settings page no longer scrolls sideways in right-to-left languages.
  • Update the tested-up-to version to WordPress 7.1.

3.1.3 – 2026-08-26

  • Fix: a direct page path ending in a backslash no longer breaks the cache config file.
  • Fix: sanitise the CDN URL and CNAME settings so a value containing a quote or an angle bracket can no longer break the asset URLs they are substituted into.
  • Fix: escape string settings written to the cache config file, so a value containing a quote or a backslash no longer corrupts it.
  • Fix: a cookie named “0” could make a logged-in visitor look anonymous to the cache, so their page was served to everyone.

3.1.2 – 2026-08-19

  • Fix: stop the error log filling with path length warnings when a request URL is too long to build a cache directory from.
  • Fix: clear the cache for category, tag and archive pages whose slug contains non-ASCII characters. The delete cache button could not clear those pages either, and now can.
  • Fix: clear the cache correctly when saving a post whose slug contains non-ASCII characters.
  • Removed the Bad Behavior plugin integration. The upstream plugin is no longer maintained and a long-standing inverted guard meant the integration never actually ran.
  • Fix: ignore a post ID of 0 when clearing the cache after a post edit, which could delete the front page cache unexpectedly.
  • Split wp-cache.php into per-responsibility inc/ files (#1061) (#1065)
  • Fix: cache modern security headers, including Permissions-Policy, the Cross-Origin-Opener/Embedder/Resource-Policy family and the remaining CORS headers, so they are sent on cached responses.
  • Fix: honour quality values in the Accept header, so monitoring tools and browsers that list JSON below HTML are served the cached page instead of rebuilding it on every request.
  • Fix: hide debug HTML comments in REST and Ajax responses (#1021)

3.1.1 – 2026-05-27

  • Security: harden supercache filename generation so request-derived data cannot escape the cache directory.
  • Fix: avoid a fatal error on PHP 8+ when closing an unopened file handle in supercache-only mode.
  • Fix: cast the blog ID in wp_cache_clear_cache() so non-integer callers no longer trigger a multisite-only function on single-site installs.
  • Fix: no longer append HTML debug comments to REST API, Ajax, JSON, WooCommerce API, and XML-RPC responses.
  • Fix: avoid a PHP warning when a comment has already been deleted before the cache-clear routine runs.

Registro de change completo em WordPress.org →

Para desenvolvedores

Este é o seu plugin? Mostre os números.

Adicione um crachá ao vivo ao seu site, Documentos ou Readme do GitHub. Ele é atualizado por conta própria - nenhuma conta necessária.

Selo de Instalações Ativas Selo de classificação Distintivo de pontuação de saúde

Best WP Super Cache alternatives

Todos os plugins de cache →
Alternativas
Classificação Plugin Instalações ativas Classificação Atualizada Saúde
2 Cache mais rápido do WP – Plugin de cache WordPress Cache mais rápido do WP – Plugin de cache WordPress O sistema de cache WP mais simples e rápido Por Emre Vona 1M+ ★★★★★★★★★★ 4.9 (4.2K) 2 semanas atrás 89
3 WP-Optimize – Cache, compacte imagens, Minify & Clean Database para aumentar a velocidade e o desempenho da página Wp-otimizar Obtenha cache e muito mais com este poderoso plugin de cache. Cache, otimize imagens, limpe seu… Por David Anderson / Team Updraft 1M+ ★★★★★★★★★★ 4.8 (2.6K) 2 dias atrás 95
4 SpeedyCache – cache, otimização, desempenho SpeedyCache – cache, otimização, desempenho SpeedyCache é um plug-in de cache WordPress que ajuda você a melhorar o desempenho do seu… por sofáculo 500K+ ★★★★★★★★★★ 4.4 (30) 1 mês atrás 86
5 Cache Breeze Cache Breeze O Breeze é um plugin de cache desenvolvido pela Cloudways. A Breeze usa sistemas avançados de cache para… por Cloudways 300K+ ★★★★★★★★★★ 3.6 (134) 3 dias atrás 84
6 OMGF | Compatível com GDPR/DSGVO, mais rápido Google Fontes. Fácil. OMGF | Compatível com GDPR/DSGVO, mais rápido Google Fontes. Fácil. O plugin original de hospedagem de fontes Google original. Cache automaticamente suas fontes localmente - não… Por Daan van den Bergh 300K+ ★★★★★★★★★★ 4.7 (213) 3 semanas atrás 96
7 Jetpack Boost – Velocidade do site, desempenho e CSS críticos Jetpack Boost – Velocidade do site, desempenho e CSS críticos Acelere seu site WordPress com otimizações de um clique, como cache de página, CSS crítico… por Automattic 200K+ ★★★★★★★★★★ 4.7 (613) 1 dia atrás 90
8 Aruba Hispeed Cache Aruba Hispeed Cache Aruba Hispeed Cache Interfaces diretamente com o Hispeed Cache de uma plataforma de hospedagem Aruba… por aruba.it dev 100K+ ★★★★★★★★★★ 3 (10) 4 semanas atrás 83
9 Ativador de cache Ativador de cache Um plugin leve de cache para WordPress que torna seu site mais rápido, gerando… por keycdn 100K+ ★★★★★★★★★★ 4.3 (139) 2 meses atrás 74
10 Nitropack – Plugin de desempenho, velocidade de página e cache para os principais pontos da web, CDN e otimização de imagem Nitropack Aumente a velocidade e o desempenho do site com um plugin completo de cache e otimização de velocidade… Por Nitropack 80K+ ★★★★★★★★★★ 4.3 (311) 2 semanas atrás 78
11 Super Page Cache – Cloudflare Cache, Page Speed & Core Web Vitals Super Page Cache Boost PageSpeed, SEO, and Core Web Vitals with full page caching, JS/CSS optimization… by Optimole 70K+ ★★★★★★★★★★ 4.8 (519) 2 dias atrás 93

FAQ

WP Super Cache: quick answers

Respostas diretas, extraídas de dados ao vivo WordPress.org.

Fonte: WordPress.org

Is WP Super Cache free?

Yes. WP Super Cache is free to download and use from the official WordPress.org plugin directory.

Is WP Super Cache safe to use in 2026?

Yes — WP Super Cache is a safe, well-maintained plugin to use in 2026. It runs on 1M+ sites, is rated 4.3/5 and was last updated 3 weeks ago, and scores 93/100 on our health check.

How many websites use WP Super Cache?

WP Super Cache is active on 1M+ WordPress websites and has been downloaded 67,517,956 times since it launched in November 2007. It was downloaded 975,364 times in the last 30 days.

Does WP Super Cache work with WordPress 7.1?

Yes. The developer has tested WP Super Cache up to WordPress 7.1.5, the latest release. It requires WordPress 6.8 or newer.

What PHP version does WP Super Cache need?

WP Super Cache requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.

When was WP Super Cache last updated?

The latest version, 3.1.5, was released on November 2, 2026 (3 weeks ago).

Who makes WP Super Cache?

WP Super Cache is developed and maintained by Automattic.

What are the best alternatives to WP Super Cache?

The most popular alternatives to WP Super Cache are WP Fastest Cache (1M+ installs), WP-Optimize (1M+ installs) and SpeedyCache (500K+ installs).

Alimentado por PageForge

Um modelo e uma planilha. Uma página real para cada pesquisa.

PageForge Transforma cada linha de um CSV em uma página WordPress com seu próprio título, URL, SEO campos e esquema, construído no layout que você já desenhou. Gratuito em WordPress.org.

  • CSV e XLSX, mais Google Sheets em Profissional e Empresarial
  • Seu próprio título, URL, SEO campos e esquema para cada página
  • Funciona com o editor de blocos, Elementor, Divi e Avada
  • Gratuito em WordPress.org, sem cartão de crédito

↑↓ mover↵ abrir