Table of contents

Using the command lineUsing the Magento Admin PanelModule output vs full disableDealing with module dependenciesHow to disable modulesBest practicesFAQsHow to get started

Get the industry’s most secure Magento hosting◦ 99.99% uptime
◦ Comprehensive security
◦ 24/7 support

Magento Guide → Extensions → Disable Module

How to disable a Magento module

Need to turn off a Magento module that’s causing trouble or no longer needed? Whether you prefer using the admin panel or command line, Magento gives you multiple ways to disable a module. But there’s one method that fully deactivates the code and one that doesn’t.

Let’s walk through each approach, explain the differences, and show you how to avoid common mistakes when disabling modules in Magento 2.

Host Magento at full throttle.

Get secure, reliable Magento hosting so you can scale faster.

Magento hosting

Disabling a Magento module using the command line

This is the most effective way to disable a Magento 2 module because it prevents the module from loading entirely—code, functionality, and output.

Access your server via SSH. Log into your Magento server and navigate to your Magento 2 root directory:
cd /path/to/magento
Run the disable command. Use the following syntax to disable the module:
bin/magento module:disable VendorName_ModuleName

Replace VendorName_ModuleName with the actual name of the module. You can check enabled modules by running:
bin/magento module:status
Clean the cache. After disabling the module, clean the cache to ensure changes take effect:
bin/magento cache:clean
Run setup:upgrade. Apply the changes to your Magento system:
bin/magento setup:upgrade

If you’re in production mode, you may also want to deploy static content again using:

bin/magento setup:static-content:deploy

Disabling module output using the Magento Admin Panel

This option is available through the backend UI and hides a module’s output from the frontend or admin interface, but it doesn’t stop the module’s backend logic from running.

Log in to the Magento Admin Panel.
Navigate to Stores > Settings > Configuration.
Under Advanced, click “Advanced.”
Scroll through the list of modules.
Find the module and select “Disable” in the dropdown.
Click “Save Config.”

This is useful when you want to hide module features temporarily without affecting backend functionality or risking dependency conflicts. But if you need to completely turn off a module, use the CLI method.

Understand the difference: module output vs full disable

Disabling output via Admin Panel: Prevents the module’s blocks and templates from rendering. The logic, observers, cron jobs, and other background functions still run.
Disabling via command line: Stops the module from loading entirely, preventing both output and logic from being executed.

If you’re trying to improve performance, resolve conflicts, or remove unused functionality, the CLI method is the way to go.

Dealing with module dependencies

Some modules are interdependent. Disabling one can break another, so it’s important to check for relationships before turning anything off.

Check module status: bin/magento module:status
See dependency details: Magento doesn’t have a built-in command for dependency trees, but you can inspect the composer.json file or use third-party tools to analyze dependencies.
Disable in the right order: If Module B depends on Module A, you’ll need to disable Module B first—then Module A. Trying to disable a required module without handling dependencies can result in fatal errors.
Watch for required core modules: Never disable modules like Magento_Store, Magento_Catalog, or Magento_ConfigurableProduct unless you’re absolutely certain it’s safe. Many modules are essential to core functionality.

How to disable modules in Magento Cloud projects

In Adobe Commerce Cloud or similar cloud setups, you can’t run bin/magento module:disable directly in production. Magento Cloud uses Git and a build/deploy process that pulls from configuration files.

Clone your cloud environment locally. Use the Magento Cloud CLI or Git to pull your environment to your local machine.
Disable the module locally. Run the CLI command:
bin/magento module:disable VendorName_ModuleName
Commit changes to app/etc/config.php. Magento stores module states in this file, so Git will track them automatically.
Push to the cloud environment. Deploy your branch to the desired environment and Magento will apply the module disablement during the build process.

Never try to disable a module directly in a live cloud environment; it won’t persist.

Best practices for testing after disabling a module

Even a small change like disabling a single module can cause ripple effects across your site. Test thoroughly to avoid downtime or broken functionality.

Use a staging or development environment. Always test changes in a safe environment before pushing to production.
Check frontend and backend pages. Make sure no layouts, templates, or admin features are broken after the change.
Look at logs. Check var/log/system.log and var/log/exception.log for errors related to missing classes or dependencies.
Run static content deploy. If something looks off visually, try:
bin/magento setup:static-content:deploy
Clear browser and Magento caches. Caching can mask issues, so clear all layers of cache during testing.

Magento module FAQs

To override a module, create your own module and use dependency injection to replace specific classes. You can use the di.xml file to set a preference for a core class, or extend a template or controller in your custom module. Avoid editing core code directly—it will break during updates.

Drush is a command-line tool for Drupal and does not apply to Magento. To disable modules in Magento, use the native CLI:

bin/magento module:disable Vendor_Module

FPC (Full Page Cache) is a cache type, not a module. Disable it using:

bin/magento cache:disable full_page

This prevents Magento from storing and serving cached full-page content, which can be useful during debugging or development.

Next steps for disabling a Magento module

Disabling a Magento module isn’t just a checkbox—it’s an important part of site management and performance tuning. Use the command line for full deactivation and always test before going live.

If you’re unsure which modules are safe to disable, or need help troubleshooting Magento performance, expert guidance can save hours of trial and error.

Ready to upgrade your Magento experience? Professional hosting improves speeds, security, and reliability for a website and a brand that people find engaging and trustworthy.

Liquid Web offers the raw infrastructure power you need with mission-critical features that keep your store running smoothly. Most importantly, our in-house Magento experts are standing by to help with both hosting and Magento application roadblocks.

Click through below to explore all of our Magento hosting options, or chat with an expert right now to get answers and advice.