This plugin hasn’t been tested with the latest 3 major releases of WordPress. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.

Module Control for Jetpack


Jetpack adds powerful features… but sometimes we don’t want them all. This plugin brings additional control over Jetpack modules.


  1. Blacklist / remove individual Jetpack modules.
  2. Prevent module auto-activation on connection or after an upgrade.
  3. Allow activation of Jetpack modules without a connection.
  4. Single site and Multisite compatible.


In most use cases, a carefully considered combination of Jetpack modules can be a really good thing. But not always is much consideration being done beforehand. Or site admins just don’t know all the implications…

  • Maybe your Nginx web server uses FastCGI caching, making it incompatible with the Mobile Theme module? Blacklist that module to prevent any admin from activating it.
  • Do you already a light box provided by your theme or another plugin? Then blacklist the Carousel module to prevent accidental activation.
  • Or you’re running a Multisite and do not want any admins monitoring uptime with the Monitor module just to call you every time their site is briefly inaccessible?
  • Or you offer your own backup service and do not care much for VaultPress competition?
  • You’re running a school network and (some) sites are managed by minors who are not allowed to sign up for an account at Then use the Jetpack Development Mode option to allow usage of modules that do not require a connection.

Any one of Jetpack’s modules can bring overlapping or even conflicting functionality. In such cases, being able to prevent (accidental) activation is a good thing.

Single site and Multisite

Although the original idea arose on a multisite installation, Jetpack Module Control is developed for both single and multisite installations.

On multisite, it can only be network activated and allows global rules for Jetpack on all sites. At this point it also allows per-site changes by Super Admin only. Jetpack itself can, but does not need to be, network activated.

For single site installations, plugin settings can be locked down by adding define('JETPACK_MC_LOCKDOWN', true) to wp-config.php for complete security. This can be useful to prevent other admins being able to reactivate blacklisted modules.


The project can be forked and or contributed to on Github.

All contributions — be it in the form of feature requests, bug reports, translations or code — are welcome!


  • Options section with Blacklist.


  1. Install Jetpack Module Control either via the plugin directory, or by uploading the files to your server.
  2. After activating the plugin, go to either Settings > General (on single site) or Network Admin > Settings (on multisite) you can find the new Jetpack Module Control section.
  3. Select any module you wish to remove and save settings.
  4. If you are on a single site installation and you wish to prevent other admins from reactivating any blacklisted modules, add define('JETPACK_MC_LOCKDOWN', true); to your wp-config.php to lock down settings.
  5. That’s it.


25 Noyabr 2021
The latest version (1.6) requires JetPack >= 8.8.0 for using JetPack without a connected account. I think it would have been (and still could be) better if you test the JetPack version and use the jetpack_development_mode or jetpack_offline_mode filter as appropriate (though I don’t see why Automattic decided to rename it). If already using a plugin such as Unplug JetPack, ‘Use Jetpack modules without a connection’ is checked but greyed out. However, the setting from the other plugin is overwritten by your filter which actually sets it to false (unless it has been previously saved as checked whilst not greyed out). You need to respect the previously set value passed to your Jetpack_Module_Control::development_mode() filter instead of using false as the default (and pass that value to get_option('jetpack_mc_development_mode') as the default). It would also be nice if that setting was initialized on the basis of other installed plugins that affect it, so after deactiviting other plugins it retained its value. I think you’d actually need to invoke the jetpack_offline_mode (or jetpack_development_mode) filter (or perhaps use the Automattic\Jetpack\Status::is_offline_mode()/is_development_mode() method) to find out what other plugins are actually setting. Otherwise looks very good and slimline (just one PHP file with fewer than 1,000 lines).
31 Oktyabr 2019
like the fact that you can ban(blacklist) features in jetpack! Very good considering that jetpacks tends to do what it wants on your website.
13 Avqust 2018 1 reply
Tames the beast known as Jetpack. Jetpack just seems to be getting worse all the time… This plugin works pretty good at getting some control back over it. Thanks, Ravan
Read all 11 reviews

Contributors & Developers

“Module Control for Jetpack” is open source software. The following people have contributed to this plugin.


“Module Control for Jetpack” has been translated into 5 locales. Thank you to the translators for their contributions.

Translate “Module Control for Jetpack” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.



Date: 2020/08/19

  • Replace jetpack_development_mode with jetpack_offline_mode filter
  • New module icons
  • Shorter list when Offline Mode is activated


Date: 2016/12/07

  • NEW: option to allow site admins override contributed by @harshit_ps


Date: 2016/04/14

  • Text domain name change to correspond with plugin slug


Date: 2016/04/01

  • Added FR/NL translation files


Date: 2016/03/29

  • Allow per site settings by Super Admin
  • Added Sitemaps to known modules


Date: 2015/09/02

  • Module names now translated using
  • BUGFIX options not saving deactivation
  • BUGFIX translation files not found


Date: 2015/08/01

  • Fix “Missing argument 1 for Jetpack_Module_Control::add_settings_section()”


Date: 2015/05/11

  • Detect the Unplug Jetpack plugin


Date: 2015/05/05

  • Jetpack Debug Mode to allow modules without connection
  • Show which modules require a connection


Date: 2015/05/01

  • Settings action link on Network plugins page


Date: 2015/04/27

  • Added dashicons


Date: 2015/04/26

  • Added network options


Date: 2015/04/25

  • Initial release