Alternatives

SelectorsHub alternatives

SelectorsHub is the locator tool a lot of testers learned XPath with: inspect an element, get XPath, CSS and Playwright locators, and check your own in an editor that flags mistakes as you type. Teams look past it less because its locators are weak and more because a locator is only one step of the job. Recording, link checks, test data and screenshots each live in another extension, and the advanced features sit in a paid Pro version.

Add FindMyLocator to Chrome See what FindMyLocator does

SelectorsHub limitations taken from its own Chrome Web Store listing and website on 27 October 2026, not from third-party round-ups.

Why testers look for an alternative

Recording is a separate product. SelectorsHub finds and checks locators; recording test steps is TestCase Studio, another extension from the same team, with its own paid Pro version.
The everyday page checks are more installs. Link checks, page load timing, header changes, request building, form filling and screenshots are each a separate extension from the SelectorsHub team: Check My Links, Page Load Timer, Modify Header, Request Maker, Auto Data Filler and Screenshot with URL.
The advanced features are paid. SelectorsHub Pro is a separate, paid extension next to the free SelectorsHub.

What SelectorsHub still does better

If most of your day is writing and debugging XPath and CSS by hand, SelectorsHub is the stronger tool and we will not pretend otherwise. Its editor suggests attributes, text and occurrences as you type and flags a broken XPath or CSS expression before you use it, XPath Healing checks a whole list of XPaths at once, and it handles iframes, shadow DOM and SVG elements. It also publishes Firefox and Edge versions next to Chrome, and has years of tutorials and a very large user base behind it. FindMyLocator tests a locator you paste and tells you whether it finds nothing, one element or several, but it has no editor that suggests as you type, no bulk check, and it runs only in Chrome.

The alternatives, and what each is best at

Listed with the trade-off that comes with each. For some teams the right answer on this page is not us, and it is more useful to say so.

Chrome DevTools

Built into Chrome

Best forA quick one-off locator with nothing to install. Search the Elements panel by CSS selector or XPath, and right-click a node to copy its selector, JS path or XPath.

Trade-offCopied paths follow the page's structure, so they often break when the layout changes, and there are no Playwright locators.

Playwright Pick locator

Open source

Best forPlaywright teams. Pick locator in the Playwright Inspector or the VS Code extension gives you the locator Playwright itself would write, preferring role, text and test id, refined until it finds one element.

Trade-offPlaywright only, and it works in a browser Playwright opens rather than on the tab you already have open.

FindMyLocator

Free Chrome extension

Best forTesters who want locators, recording and the everyday page checks in one free extension. Click an element for Playwright, XPath and CSS locators with a Test button, record a flow as Playwright, Cypress or Selenium code, and build a Page Object.

Trade-offChrome only, no editor that suggests as you type, and Playwright locators by role, label, placeholder or test id only. Its text locators are XPath and CSS, not Playwright's getByText; Playwright's own Pick locator writes those.

Where FindMyLocator fits

Locators, recording and page objects together

Pick an element for Playwright, XPath and CSS locators, with a warning when an id looks generated and may change on the next release. Record a flow and export it as Playwright, Cypress or Selenium code, or collect up to 100 elements into a Page Object class. All free.

The checks you would otherwise install separately

Link checks, page load times, request headers, a request log with Copy as cURL, form filling, test data and annotated screenshots sit on the same extension's Network, Test data and Report tabs, in the toolbar popup or Chrome's side panel.

Test cases from the page you are on

Connect a QAEverest API key and the Test cases tab writes test cases from the page, a user story or your recording, as Gherkin or step by step. It uses QAEverest credits, and nothing is sent until you press Generate.

Questions

Is FindMyLocator really free?

Yes. Install it from the Chrome Web Store. Locators, recording, exports, the Network checks, test data and screenshots need no account. Writing test cases on the Test cases tab, and Check text on the Report tab, use a QAEverest API key and QAEverest credits; where Chrome offers its own proofreader, Check text can use that instead.

Is SelectorsHub still a good choice?

Yes, especially if you write XPath and CSS by hand and want an editor that checks them as you type, or you test in Firefox. FindMyLocator is worth a look when you want recording, page objects and the everyday page checks in the same free extension.

Does FindMyLocator write Playwright locators?

Yes. For the element you pick it shows Playwright's getByRole, getByLabel, getByPlaceholder and getByTestId locators when they find that element alone, in JavaScript or TypeScript, Python, Java or C#, next to XPath and CSS. It does not write getByText locators; its text locators are XPath and CSS.

Does FindMyLocator work in Firefox or Edge?

Not today. It is published on the Chrome Web Store only. SelectorsHub publishes Firefox and Edge versions, so it is the better pick for those browsers.

Try it on the page you are testing

Install FindMyLocator, pick the elements you would use SelectorsHub for, and compare the locators side by side. Keep whichever works better for you.

Add to Chrome, it's free See FindMyLocator

Other alternatives guides

Playwright alternatives Selenium alternatives Cypress alternatives Appium alternatives

Platform comparisons

QAEverest vs Katalon QAEverest vs Functionize QAEverest vs TestMuai QAEverest vs mabl QAEverest vs Testsigma QAEverest vs BrowserStack

Something here out of date about SelectorsHub? Tell us and we will correct it.