A chat bubble pops up in the corner of your site. Or the contact page has a form you need to change, or a banner about cookies says something you never wrote. You open the Plugins screen to fix it and find thirty names, half of which mean nothing to you. The person who installed them has moved on.
You can find which plugin does what without a developer, using the dashboard, your browser and, at the end, a careful test. Work through the steps below in order, because the early ones answer most cases in a few minutes and the later ones are for the stubborn leftovers.
Start on the Plugins screen
The plugin list tells you more than it seems to. Each row has a short description written by the developer, and many rows carry a Settings link that jumps straight to that plugin’s options. For anything unclear, click View details (shown for plugins from the WordPress.org directory) to read the full description in a pop-up window.
Also look at the left-hand admin menu. Many plugins add their own menu item, either at the top level or tucked under Settings or Tools. If a menu item’s name matches the thing you saw on the site, such as “Cookie Banner” or “Live Chat”, you are probably done. Open it and check that the settings match what visitors see.
Above the list, check for Must-Use and Drop-ins links. They only appear when such files exist. Must-use plugins run on every page and cannot be switched off from the dashboard; hosts often place their own tools there. Drop-ins are special files, usually added by caching plugins. Both can explain behaviour that no ordinary plugin accounts for.
Read the page’s code, no coding needed
When the menu does not give it away, the page itself usually does. Plugins load their styles and scripts from their own folder, and that folder name is right there in the page code.
- Open the page where the mystery feature appears.
- Right-click an empty area and choose View Page Source (Ctrl+U in most browsers on Windows).
- Press Ctrl+F (Cmd+F on a Mac) and search for wp-content/plugins/.
- Note the word that comes after it in each result. That is the plugin’s folder name, for example wp-content/plugins/contact-form-7/.
- Match the folder names against your Plugins list. They are usually close to the plugin’s name.
To narrow it to one element, right-click the feature itself, such as the form or the chat bubble, and choose Inspect. The browser highlights its code. Look at the class names. Plugins tend to prefix their classes with a short version of their name: Contact Form 7 uses wpcf7, WPForms uses wpforms, Elementor uses elementor, and Gravity Forms uses gform. You do not need to understand the code around it; you are only reading labels.
Some plugins also leave an HTML comment naming themselves near the top of the source. SEO plugins often do this, which is a quick way to tell whether Yoast SEO, Rank Math or something else is writing your page titles.
A shortcut for the visible plugins
Our free WordPress theme and plugin detector reads a page’s public code and lists your theme and every plugin it can see loading files there. It cannot see plugins that work only in the dashboard or the background, and some security plugins hide folder names, so treat its list as a starting point rather than the full story.
Look inside the editor
If the feature sits inside a page’s content, open that page in the editor.
- Shortcodes. Text in square brackets, such as [wpforms id=”12″], names its plugin more often than not. Search the plugin list for the first word.
- Blocks. Select the block and open the settings sidebar. The block’s name and a short description appear at the top, and the name of a plugin block often hints at where it came from. In the block inserter, many plugins group their blocks under their own heading, which is a second clue. List View (the icon of stacked lines in the top toolbar) shows every block on the page by name.
- Page builders. If the page opens in Elementor or another builder, the feature may be a widget from an add-on pack rather than the builder itself. Hover over the widget in the builder’s panel; add-on widgets often carry a small badge or the add-on’s name.
If the thing you want to change is in the header or footer and not in the page at all, it may come from the theme rather than a plugin. In a block theme, open Appearance → Editor and look at the header and footer template parts. In a classic theme, check Appearance → Customize and Appearance → Widgets.
When the feature is not on any page
Some plugins never show themselves to visitors. They send emails, run backups, resize images or tidy the database on a timer. To trace these:
- Emails. Open one of the automated emails and read the footer and the sender address. Form, backup and shop plugins often name themselves there.
- Scheduled tasks. The free WP Crontrol plugin adds a screen under Tools that lists every scheduled task with its hook name. Hook names usually start with the plugin’s prefix.
- Admin notices. A message at the top of the dashboard often names the plugin in its first words, or has a link to that plugin’s settings.
- Site Health. Tools → Site Health → Info lists active plugins with their authors and versions in one place, which is easier to read than the Plugins screen when you are comparing names.
Confirm it before you change anything
Reading the code tells you which plugin is most likely responsible. A test makes sure. The safe way is to switch the plugin off somewhere visitors cannot see the result.
The first option is a copy of the site. If your host provides one, a staging site lets you deactivate plugins one at a time and watch what disappears, with no risk to the live site.
The second option is the Health Check & Troubleshooting plugin from the WordPress.org directory. Its troubleshooting mode disables plugins for your logged-in session only, so visitors keep seeing the normal site while you switch plugins back on one by one. When the feature reappears, the last plugin you enabled is the one.
Avoid deactivating plugins on the live site to see what breaks. A form, shop or login feature can stop working for real visitors while you test, and some plugins lose settings or interrupt scheduled work when switched off.
Things that look like plugins but are not
- Theme features. Many themes include sliders, top bars, contact details and social icons. Some ship a companion plugin with a name close to the theme’s, which blurs the line further.
- Hosting tools. Hosts often add caching, security or staging features as must-use plugins or as settings in their own control panel.
- Code snippets. A small change might come from code added to the theme or to a snippets plugin. If you have a snippets plugin, look through its list; the snippet titles often describe what each does.
- Outside services. Chat widgets, booking tools and review boxes may be pasted-in code from a service such as a booking platform, added through a header-and-footer plugin or the theme’s settings.
Once you find which plugin does what, write it down
Once you know, record it so nobody has to do this again. A simple sheet with three columns is enough: plugin name, what it does on this site, and where you see it. Add who installed it and whether it is a paid plugin if you know. This list becomes the base of a regular WordPress plugin audit, and it is the first thing a new developer will ask for.
Knowing your plugins is one of the habits described in our WordPress owner’s guide, and the guide to plugins for business owners explains how plugins fit together across a site’s life.
Frequently asked questions
The folder name in the page source does not match any plugin in my list. Why?
Folder names are set by the developer and sometimes differ from the plugin’s display name, especially for older or renamed plugins. Search the folder name on the WordPress.org plugin directory, or open your hosting file manager and look inside wp-content/plugins for that folder; its main file lists the real plugin name at the top.
Can one feature come from two plugins working together?
Yes. A form may be built by one plugin, protected from spam by a second and sent by an email plugin. A page builder widget may come from an add-on that depends on the builder. When you find one plugin, check whether it needs or extends another before you remove anything.
Is it safe to use the troubleshooting mode on a live shop?
The Health Check troubleshooting mode affects only your own logged-in session, so customers keep seeing the normal site. Even so, avoid placing test orders or changing settings while it is on, and switch it off when you finish. If the shop is busy, a staging copy remains the calmer choice.
How do I find out who installed a plugin?
WordPress does not record who installed a plugin. If an activity log plugin was running at the time, it may show the user and date. Without one, the best sources are people: the previous developer, agency or staff member may remember, and old invoices or licence emails often show who bought a paid plugin.
Some features hide well, especially on sites that have passed through several developers. When the trail goes cold, or you have found the plugin but are wary of touching it, tracing it is a normal request for our WordPress support team.
Next in this series: How to Roll Back a WordPress Plugin to an Older Version
