XPath Online Tester

When to Use It

Whether you're writing a web scraper to extract product price links, debugging element locators in automated test scripts, or just curious about how many specific tags exist in an HTML snippet—XPath lets you locate them with a single line. But did you write the XPath correctly? Expressions are easy to mistype. Our Online XPath Tester allows you to paste an HTML/XML document, write your XPath, and instantly see the match count and highlighted content, saving you the hassle of repeatedly refreshing pages or opening developer tools.

The Concept in a Nutshell

XPath is a path language used to find nodes in an XML document, similar to directory paths in a file system. For example, //div[@class='price'] means "all div elements with a class attribute equal to price". Think of it as giving elements in a document an "address" that you can use to retrieve them directly. Developers frequently use it to extract data from web pages or control automated workflows.

How to Use This Tool

1. Prepare the test document: Open our tool page, and you'll see a large multi-line text box (labeled "XML/HTML Document"). Paste the web page source code or XML snippet you want to test. If you don't have one handy, you can use the sample data button to load default HTML.
2. Write the XPath expression: Enter your selection path in the adjacent input box (labeled "XPath Expression"). For example, //a/@href extracts the addresses of all hyperlinks.
3. Click the "Test" button: The tool will immediately parse the document and execute the expression.
4. View the results: The "Match Results" area below will display the number of matched nodes and list the text or attribute values of each node. If the document has a highlighting feature, matched nodes will also be marked in the document preview.
5. Adjust the expression: If the results aren't what you expected, modify the XPath and click test again until you get the desired data.

Complete Example: Extracting a Product List

Suppose you have a simple product HTML snippet (paste this into the document box):

<div id="products">
  <div class="item">
    <span class="name">Wireless Mouse</span>
    <span class="price">$39.9</span>
  </div>
  <div class="item">
    <span class="name">Mechanical Keyboard</span>
    <span class="price">$129</span>
  </div>
</div>

You want to extract all product names. Enter //span[@class='name']/text() in the XPath box. Click test, and the results area will show "Matched 2 nodes" and list:
1. Wireless Mouse
2. Mechanical Keyboard
If you want to get both the name and price at once, you can use a union selection or return the parent node of the elements, but beginners should stick to simple expressions first.

Let's look at a comparison: If you write //span[@class='price'] (without /text()), the match result will show "2 nodes", but each node is the entire tag like <span class="price">$39.9</span>—because XPath returns nodes by default, not text. If your goal is to get the numbers, remember to add /text() or string().

Typical Use Cases

• Web Scrapers: Extracting product titles and prices from e-commerce pages. Verify your XPath expressions with the tool first to avoid finding out the path is wrong only after running the code.
• Frontend Automated Testing: When writing element locators using Selenium or Playwright, test the XPath on an HTML snippet here first, then copy it into your test script.
• Data Analysts: Occasionally needing to extract data from XML configuration files or RSS feeds. Use XPath for quick filtering; this tool saves you from installing any software.
• API Debugging: Some endpoints return XML data. If you want to extract specific fields, paste it in and test expressions to see the results.

Common Mistakes & Pitfalls

• Forgetting Namespaces: If the document has a default namespace (like SOAP or SVG), //tag often won't match, requiring you to register a namespace prefix first. Our tool currently only supports matching without namespaces or with explicit prefixes. When encountering namespaces, please manually remove them first or use the local-name() function instead.
• Case Sensitivity: XPath is case-sensitive for tag and attribute names. HTML often mixes cases; for example, <Div> and <div> are two different nodes. Pay attention to this when writing expressions.
• Misusing // Causing Performance Issues: Although the tool processes small documents quickly, abusing // in real, large documents will scan all nodes. It's recommended to use specific paths like /html/body/div[1]/ to improve efficiency.
• Extra Spaces in Paths: //div [@class=...] (with a space before the bracket) is a syntax error, and the tool will prompt "Invalid expression". Avoid adding unnecessary spaces when writing expressions.
• Assuming text() Gets All Text: text() only returns direct text child nodes; text inside nested elements won't be automatically merged. To get all text, you can use string() or normalize-space().

Notes & Limitations

• Document Size Limit: For page responsiveness, we limit pasted XML/HTML documents to 500KB. We recommend splitting oversized files into snippets for testing.
• No Support for XSLT and Extension Functions: The tool only implements standard XPath 1.0 (the default implementation in most browsers). Functions for arithmetic, type conversion, and regex in XPath 2.0/3.0 are not supported.
• Namespace Handling: Currently, default namespaces cannot be handled automatically. You need to manually use local-name() in your expression or remove the namespace declaration first.
• Execution Environment: The tool runs in the browser frontend. It does not save your documents or expressions; they will be lost upon refreshing the page. Please save your results promptly.
• Do Not Test Sensitive Data: Although processing is local, be mindful of the network transmission process (HTTPS encrypted). We advise against pasting confidential information like passwords or API keys.

Frequently Asked Questions (FAQ)

1. I pasted HTML, but XPath can't find any nodes
   Check if your HTML is well-formed (e.g., tags are closed, attribute values are in quotes). Malformed HTML can lead to unexpected parsed structures. Try copying the "outerHTML" using your browser's developer tools first.
2. The expression is correct, but it returns an empty list
   Possible reasons: incorrect casing in the path, misspelled attribute values, or you used @class='value' in XPath but the actual attribute value has leading/trailing spaces. You can use //* to see all elements first, then gradually narrow it down.
3. Is the contains() function supported?
   Yes. For example, //div[contains(@class, 'price')] can match div elements where the class attribute contains "price".
4. How do I extract the href and text of a hyperlink?
   Use //a to return all 'a' elements, and the result box will show the node's text (inner text). To get the href attribute, use //a/@href, but note that it returns an attribute node, so the text will be empty. You can write two expressions and test them separately, or use a multi-expression feature (if the tool provides one).
5. Can this tool test XPath effects on real websites?
   It can only test the static document you paste. The tool does not make network requests, so it cannot simulate dynamically loaded content. To test dynamic pages, please use your browser's developer tools.
6. The result box shows something like [object Text], not the text I want
   This is because XPath returned a text node object instead of a string. Add /text() or /string() to the end of your expression to get the string.

Now you can try your own HTML and XPath expressions in the input boxes above.