NoSuchElementException in Selenium

The Error

org.openqa.selenium.NoSuchElementException:
  no such element: Unable to locate element:
  {"method":"css selector","selector":"#submit-btn"}

You can see the element. DevTools finds it. Selenium can't. Here's why.

What It Means

Selenium searched the current DOM context and found nothing matching your locator.

Two words matter there:

Advertisement
  • Current — at that exact millisecond. The element may appear 200ms later.
  • Context — inside the active frame/window only. Selenium can't see into an iframe you haven't switched to.

That's the whole exception. Every cause below is a variation of one of those two.

The Most Common Causes

Timing — the element isn't there yet ⭐

Roughly 70% of cases. Your script is faster than the page.

driver.get("https://app.com/dashboard");
driver.findElement(By.id("welcome")).click();   // 💥 page still loading

It's inside an iframe ⭐

Selenium cannot see elements inside an iframe until you switch to it. The element is right there in DevTools — but in a different document.

driver.switchTo().frame("payment-frame");
driver.findElement(By.id("card-number")).sendKeys("4111...");
driver.switchTo().defaultContent();   // ⚠️ always switch back

Tell-tale sign: it works in DevTools, fails in Selenium, and the element sits under an <iframe> tag.

The locator is wrong or brittle

  • Dynamic ID: id="user_8f3a91" changes every load
  • Typo / wrong case
  • The locator matches a different element with the same class

It's in a different window/tab

Selenium stays on the original window until you switch.

for (String h : driver.getWindowHandles()) driver.switchTo().window(h);

It's not rendered yet (SPA)

React/Angular render on demand. The element genuinely doesn't exist in the DOM until state changes.

Viewport / headless ⭐

The element exists but is off-screen in headless's default 800×600 — see test passes locally, fails in Jenkins.

The 60-Second Diagnosis

Run this in DevTools console (F12):

// Does it exist at all?
document.querySelectorAll("#submit-btn").length
Result Meaning Fix
0 Not in the DOM Wrong locator, or not rendered yet → causes 3, 5
1 It exists — Selenium is early or in the wrong context Timing or iframe → causes 1, 2
2+ Multiple matches — Selenium takes the first Make the locator specific → cause 3

Then check for an iframe:

document.querySelectorAll("iframe").length   // > 0? Suspect cause 2.

This 10-second check saves an hour. Most people skip it and start adding sleeps.

The Fixes

Use an explicit wait ⭐

The fix for most cases. Not a sleep — a condition.

WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(10));
wait.until(ExpectedConditions.visibilityOfElementLocated(By.id("welcome"))).click();

Pick the right condition — this matters:

Condition Waits for
presenceOfElementLocated In the DOM (may be invisible)
visibilityOfElementLocated In the DOM and visible ⭐ usually what you want
elementToBeClickable Visible and enabled — before clicking

⚠️ presenceOfElementLocated is the classic mistake — it passes while the element is still hidden, so your click() then fails with a different error.

Switch to the iframe

driver.switchTo().frame(0);                        // by index
driver.switchTo().frame("frame-name");             // by name/id
driver.switchTo().frame(driver.findElement(By.css("iframe.payment")));  // by element

// ... interact ...

driver.switchTo().defaultContent();

Write a resilient locator

// ❌ Dynamic ID — breaks every load
By.id("user_8f3a91")

// ✅ Anchor to something stable
By.cssSelector("input[name='username']")
By.xpath("//label[text()='Username']/following-sibling::input")

Don't paper over it with Thread.sleep()

It "works" locally then fails in CI, because you tuned it to your machine's speed. Use conditions.

Diagnosis by Symptom

Symptom Cause Fix
Fails right after get() / navigation Timing Explicit wait
Works in DevTools, fails in Selenium iframe switchTo().frame()
Fails after clicking something SPA re-render Wait for the new element
Fails intermittently Timing / race Explicit wait
Fails only in CI Viewport (headless 800×600) --window-size=1920,1080
Locator has random characters Dynamic ID Stable locator
Fails after opening a popup Wrong window switchTo().window()

The Interview Answer

"NoSuchElementException means Selenium searched the current DOM context and found nothing matching the locator. Most often it's timing — the script runs faster than the page — so I use an explicit wait with visibilityOfElementLocated rather than a sleep. The other common cause is an iframe: Selenium can't see inside one until you switchTo() it, which is why the element shows in DevTools but not to Selenium. I diagnose it by running document.querySelectorAll(locator).length in the console — that instantly tells me whether it's a locator problem or a timing/context problem."

FAQs

What causes NoSuchElementException?

Selenium found nothing matching your locator in the current DOM context — usually timing (element not loaded yet), an iframe you haven't switched to, or a wrong/dynamic locator.

My element is right there in DevTools. Why can't Selenium find it?

Almost always an iframe. Selenium can't see inside one until you switchTo().frame(). Check for <iframe> tags around the element.

What's the difference from ElementNotInteractableException?

NoSuchElement = Selenium can't find it.

NotInteractable = it found it, but it's hidden/disabled/zero-size.

Should I use implicit or explicit waits?

Explicit — it waits for a specific condition on a specific element. Don't mix the two; it causes unpredictable timeouts.

Why does it only fail in Jenkins?

Headless defaults to 800×600, so the element is outside the viewport. Set --window-size=1920,1080.