What is the difference between / and // in XPath?

A single slash / selects from the immediate children of the context node, so /html/body selects body only if it is a direct child of html. A double slash // is shorthand for the descendant-or-self axis, so //div selects div elements at any depth below the context.

How do XPath predicates work?

A predicate in square brackets filters the node-set at a step. //li[1] selects the first li within each parent (XPath indexes from 1, not 0), //a[@href] selects anchors that have an href attribute, and //p[contains(text(),'hi')] filters by text content.

What is an XPath axis?

An axis defines the direction of navigation from the context node, such as child, parent, ancestor, descendant, following-sibling or attribute. The full syntax is axis::node-test, for example ancestor::div selects all ancestor div elements. The common axes have abbreviations like @ for attribute and // for descendant-or-self.

What changed in XPath 2.0?

XPath 2.0 adds a richer type system aligned with XML Schema, sequences instead of node-sets, the for/if/some/every expressions, many new functions (string, date, regex via matches/replace/tokenize), and the union/intersect/except operators. XPath 1.0 remains common in browsers and tools like Selenium.

Does the browser support XPath?

Yes, browsers expose XPath 1.0 through document.evaluate. Many automation tools (Selenium, Playwright via the xpath= engine) also use XPath 1.0. Full XPath 2.0/3.1 support generally requires a dedicated XSLT/XQuery processor such as Saxon.

XPath Reference — Gera Tools

Email me this result

Get this tool's output sent to your inbox, plus one useful tool a week. No spam, unsubscribe any time.

XPath is the expression language for addressing parts of an XML (or HTML) document. It is the backbone of XSLT, XQuery and most browser/automation element selectors. An XPath is a sequence of steps, each navigating an axis from a context node and optionally filtered by predicates. This reference lists the axes, syntax and the functions you reach for most often.

How it works

A location path is a series of steps separated by /. Each step has the form axis::node-test[predicate]. Starting from a context node, the engine moves along the named axis (e.g. child, descendant, following-sibling), keeps nodes matching the node test (an element name, *, text(), @attr), then filters with any predicates. Steps compose to walk the tree precisely. Abbreviations make common paths short: // is descendant-or-self::, @ is attribute::, . is the context node and .. is the parent.

Worked examples

//div[@class='item']        every div whose class is "item", any depth
//ul/li[1]                  the first li child of each ul
//a[contains(@href,'pdf')]  anchors whose href contains "pdf"
//input[@type='text']/..    the parent of each text input
count(//tr)                 number of table rows

Notes and tips

XPath indexes from 1, not 0 — [1] is the first node. A bare text() returns the text node, while string(.) returns the concatenated string value of an element. Prefer normalize-space() when matching text to ignore surrounding whitespace. XPath 1.0 is what browsers and Selenium use; reach for Saxon when you need 2.0+ features like matches(), tokenize() and sequences.