Conservative vs Progressive Caching in Joomla
Both modes use Joomla's System Cache setting
Joomla exposes Conservative and Progressive caching under System → Global Configuration → System → Cache Settings. Both can cache eligible component-view output, but they differ most clearly in how Joomla handles modules. They are separate from the System - Page Cache plugin, which caches an entire eligible page by URL.
Conservative caching gives each module control
With Conservative Caching enabled, an individual module can participate when it supports Joomla's caching parameters. In the module's Advanced settings, Use Global allows caching while No caching excludes that module. This makes Conservative mode useful when some modules are safe to reuse but others display frequently changing or request-sensitive output.
Progressive caching treats modules as a set
Current Joomla Programmer Documentation explains that Progressive Caching caches the modules displayed on a page together in the com_modules cache group. Individual modules do not control this progressive module caching in the same way they do under Conservative mode. That makes Progressive mode more aggressive and less selective.
Component-view caching is similar in both modes
For both Conservative and Progressive modes, a component must indicate that its view is cacheable. Joomla then uses its cache system and request parameters to distinguish eligible cached views. Administrators cannot force a component that was not designed for view caching to behave correctly merely by enabling System Cache.
Neither mode caches these pages for logged-in users
Joomla's current Programmer Documentation states that Page Cache, Progressive Caching, and Conservative Caching do not cache for logged-on users. Test cache behavior while logged out; testing only from an authenticated Administrator session can make an enabled cache appear inactive.
Cache lifetimes use different units in different places
Global Configuration Cache Time is expressed in minutes. When a cacheable module exposes its own Cache Time, Joomla documentation notes that the module value is expressed in seconds. Record both values when troubleshooting apparently stale or unexpectedly refreshed module output.
Choose based on control, then test
Conservative caching is the safer starting point when you need module-by-module control. Progressive caching can be appropriate when the site's module output is broadly safe to cache together. Whichever mode you choose, test menus, forms, personalized output, frequently changing modules, and extension workflows as a logged-out visitor before relying on it in production.
Need More Help with Joomla?
Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.
Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.
QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.