# Two WordPress security plugins together: what to turn off

Run two WordPress security plugins without clashes: which jobs overlap, how BetterShield’s Coexistence step splits them, and how to test and undo the choice.

By M Asif Rahman, Nov 13, 2026.

You can run two WordPress security plugins on one site, and with **BetterShield** the sensible way is to give each shared job to one of them. The jobs that overlap most are the sign-in attempt limit, two-factor and a custom sign-in address. When BetterShield finds another active security plugin that shares one of them, **Quick Setup › Coexistence** asks which plugin should do what, and it starts with **Use BetterShield** selected for each row.

Switching over fully is a different decision, and our guide to [switching WordPress security plugins](/blog/switch-wordpress-security-plugins/) covers it. This post is for the middle ground: you want to keep your current plugin for now, or for some jobs, and you want the two not to fight.

## Quick summary

- Two plugins doing the same sign-in job can lock out the people you want in, so give each shared job to one plugin.
- **Quick Setup › Coexistence** appears when an active plugin shares a job BetterShield recognizes, and each row offers **Use BetterShield** or **Keep**.
- If you keep the other plugin’s sign-in limiter, BetterShield’s own limiter stands down. If you keep its two-factor, BetterShield does not set up its own enrollment in the wizard.
- On **BetterShield › Overview**, the **Who does which job** card names the recognized plugin and the jobs it covers.
- BetterShield has no firewall and no malware scanner, so keeping a plugin that has one is a reasonable choice, not a clash.

## Why two plugins can get in each other’s way

Two sign-in limiters count the same failed attempts and can each pause the same person, so a typing slip is punished twice. Two two-factor plugins can each ask for a code, or one can ignore the other’s setup. Two plugins that move the sign-in address can send people to a page that no longer exists.

None of that is a fault in either plugin. It is what happens when two tools both believe a job is theirs. The fix is not a longer list of settings. It is one named owner for each job.

## What actually overlaps

BetterShield recognizes three shared jobs in the Coexistence step, and the Overview can explain a few more.

| Job | What BetterShield does when you keep the other plugin |
|---|---|
| Sign-in attempt limit | BetterShield’s own limiter stands down |
| Two-factor | BetterShield does not set up its own enrollment in the wizard |
| A recognized custom sign-in address | Defaults to BetterShield only when the preview can carry the address over; otherwise the other plugin keeps it |
| HTTPS, vulnerability protection, firewall | Shown as explanations; BetterShield’s optional vulnerability checks report advisories and do not replace another plugin’s blocking features |

The documentation is careful about one point, and so are we: these statements are not proof that every possible overlap was found. Treat the list as a good first pass, then check your own site.

## See who does which job

You do not have to open the wizard to look. When another active security plugin is recognized, **Who does which job** can appear on **BetterShield › Overview**. It names that plugin and the jobs already attributed to it, which helps explain why a BetterShield control may be unnecessary. Read the card as information only. It does not certify the other plugin or prove that every part of a feature is configured correctly, and it is read-only, so opening it changes nothing.

Deactivating the other plugin removes its coverage from the next view of the card. The [Security plugin roles](/docs/security-plugin-roles/) page describes it in full.

## Set it up

1. Update BetterShield and keep a working administrator session open in one browser. You will test in another.
2. Save a [recovery link or recovery codes](/docs/set-up-recovery/) outside the site before you change anything about sign-in.
3. Open Quick Setup and its **Coexistence** step. On a site that is already set up, open **BetterShield › Settings › General** and press **Run Quick Setup again** under **Plugin data & tools**. An overlap card on the Overview can also offer **Migrate**.
4. Review the settings BetterShield can copy from the other plugin. For each shared sign-in job, pick **Use BetterShield** or **Keep**.
5. Read the main button. When every shared job moves to BetterShield it reads **Migrate & Deactivate Plugin**, with a count if there are several plugins. A mixed choice reads **Save & Continue**.
6. Read what each deactivation would stop, including features BetterShield does not replace. Then confirm.

Quick Setup opens with your current choices, so running it again revises only the answers you change. It is not a reset. The [Run Quick Setup again](/docs/rerun-quick-setup/) page lists what it can cover.

## The choices that make sense

Our advice is to let one plugin handle sign-in limiting and one handle two-factor. The pairing matters less than having exactly one owner of each.

| Your situation | A choice that works |
|---|---|
| You like your plugin’s firewall and want to keep it | **Keep** it for that, and choose **Use BetterShield** for sign-in limits and two-factor if you want one place to manage them |
| Your people already use another plugin’s two-factor | **Keep** two-factor there and let BetterShield handle the limiter |
| You are trying BetterShield before you commit | Choose **Keep** on every row, review the Overview, and revisit Coexistence later |
| You are ready to move completely | Follow the [switching guide](/blog/switch-wordpress-security-plugins/) instead |

If you keep another plugin’s two-factor, BetterShield will not enroll people in its own during the wizard. That is the intended result of the choice, not a missing step.

## Two-factor deserves its own care

Two-factor is the job where a wrong move costs people access, so it is worth a closer look. When you hand two-factor to BetterShield and then deactivate the other plugin, supported authenticator apps can keep working. The accounts that cannot move are named in the preview and must set up an app again. Email codes, security keys and unreadable setups do not become BetterShield enrollments.

The full list of what moves, what does not and how to undo the transfer is on [Move existing two-factor accounts](/docs/migrate-two-factor/). Read it before you deactivate anything that holds your administrators’ two-factor setups, and after that, point people to [Two-factor with an app](/docs/two-factor-app/) if they need to enroll again.

## What it can break, and how to undo

Deactivating the other plugin stops every feature it has, including features BetterShield may not replace. Its settings stay saved, so you can reactivate it from the Plugins screen if you need it back. The setup summary also offers **Turn It Back On** for a plugin that setup switched off.

Undoing the settings BetterShield copied is a separate step. Use BetterShield’s recorded changes, which restore the supported settings but do not reactivate a plugin. If an import was only partial, read the receipt before you decide the switch is complete.

Two cautions come from the documentation:

- Where your permissions or a network-wide activation prevent deactivation from the wizard, use the Plugins screen it points to or ask the network administrator.
- Disabling an overlapping control removes protection if the other plugin does not cover the same behavior. If testing shows a gap, turn the original control back on.

WordPress itself explains how to switch a plugin off and on in its guide to [managing plugins](https://wordpress.org/documentation/article/manage-plugins/).

## Check it is working

1. In a separate browser session, sign in with a normal account, using its password and, if it has one, its current authenticator code.
2. Look at **BetterShield › Overview**. **Who does which job** should name the other plugin and the jobs you kept with it.
3. Open the plugin list and confirm which plugins are actually active.
4. Open **Protection › Login & Access** and confirm the attempt limit is on, or that you chose to leave it to the other plugin.
5. Read the overlap warnings on individual hardening fixes as well as in the setup summary.
6. Check proxy handling, meaning how visits reach your site, in the saved setup choices.

Only after the second session works should you close the first one.

## Recommended settings

We recommend one owner for sign-in limits and one for two-factor, a recovery link saved away from the site, and a second browser session for every test. Revisit the choice after a host change, a move to a CDN or a staging-to-live move, since each can change how sign-ins reach the site. If you are unsure, choose **Keep** and look again once you have watched the Overview for a few days.

The [Alongside another security plugin](/docs/alongside-another-security-plugin/) page has the full steps, and our post on [setting up a WordPress security plugin](/blog/wordpress-security-plugin-setup/) covers the rest of the baseline.

## Frequently asked questions

### Can I run BetterShield with a firewall plugin?

Yes. BetterShield has no firewall and no malware scanner, so it can sit beside a plugin that has one. Give sign-in limits and two-factor to one plugin so only one of them acts on each.

### What happens if both plugins limit sign-in attempts?

Both count failures and either can pause a person, so the same mistake is penalized twice. In Coexistence, choose one owner. If you keep the other plugin’s limiter, BetterShield’s own limiter stands down.

### Will Quick Setup turn the other plugin off by itself?

Only when you choose to. When all shared jobs move to BetterShield, the main button reads **Migrate & Deactivate Plugin** and shows what it will stop. A mixed choice reads **Save & Continue** and leaves the other plugin active.

### Does BetterShield find every overlap?

Not necessarily. The documentation says its statements are not proof that every possible overlap was detected, so check the plugins on your own site as well.

### Can I put the other plugin back?

Yes. Its settings stay saved after deactivation, so you can reactivate it from the Plugins screen, and the setup summary offers **Turn It Back On** for a plugin that setup switched off.

## Conclusion

Two security plugins can share a site when each shared job has one owner. Open the Coexistence step, choose **Use BetterShield** or **Keep** for each row, save a recovery link first and test in a second browser session before you finish.

BetterShield is free on [WordPress.org](https://wordpress.org/plugins/bettershield/). The reference page is [Alongside another security plugin](/docs/alongside-another-security-plugin/), and our guide to [choosing a WordPress security plugin](/blog/choose-wordpress-security-plugin/) helps if you are still deciding which pair to run.
