Inspect UI nodes without a device session
Need a locator without a live device? Inspect a mobile XML dump and find unique node identities.
Need a locator without a live device? Inspect a mobile XML dump and find unique node identities. Check locally in your browser. No upload. No sign-up required. Jump to: What does it mean?, How to fix it, Break it, Ask your agent.
Example A synthetic Android screen includes a named purchase button and an unlabeled action.
3 UI nodes inspected. 1 actionable node lacks a label.
A dump is a snapshot, not a live accessibility tree. Coordinates are recorded bounds, and generated XPath suggestions must be verified on the device.
The XML dump stays in your browser. It is parsed and searched here; no device or server is contacted.
Nothing is sent to our server. This tool has no server step.
Findings
Check 1 actionable node lacks a label
Inspect accessibility labels on the device. This is a dump heuristic, not a full accessibility audit.
Pass 3 UI nodes read
Attributes and nesting are preserved as evidence. Bounds describe recorded coordinates, not a screenshot.
Evidence
3 nodes. Expand a row to inspect attributes, bounds and its unique XPath.
Index 1 Depth 1 Type android.widget.FrameLayout Text Not set Attributes class android.widget.FrameLayout Bounds [0,0][1080,1920] XPath Not checked Bounds 0 0 1080 1920 Index 2 Depth 2 Type android.widget.Button Text Buy Attributes class android.widget.Button resource-id shop.example:id/buy Text Buy clickable true Bounds [40,200][500,300] XPath //*[@resource-id='shop.example:id/buy'] Bounds 40 200 500 300 Index 3 Depth 2 Type android.widget.Button Text Not set Attributes class android.widget.Button Text Not set clickable true Bounds [40,350][500,450] XPath Not checked Bounds 40 350 500 450
Unique XPath suggestions
Show the unique xpath suggestions
//*[@resource-id='shop.example:id/buy']Take it further
What this result means
Written for the example.
Ask for a review of the findings and a test that verifies the proposed fix. Input values are not included automatically.
A synthetic Android screen includes a named purchase button and an unlabeled action.
A synthetic Android screen includes a named purchase button and an unlabeled action.
Check representative input and one deliberate failure. Confirm the result in the application that consumes it.
Read the findings before changing the input. Break it lets you inspect a failure, and Heal it restores the previous input.
A dump is a snapshot, not a live accessibility tree. Coordinates are recorded bounds, and generated XPath suggestions must be verified on the device.
How it works
Mobile UI Dump Viewer reads ui hierarchy xml locally and presents findings with the evidence behind them. A synthetic Android screen includes a named purchase button and an unlabeled action. The full method, every rule and worked examples are on docs.tamperbox.dev.
Limits and interpretation
A dump is a snapshot, not a live accessibility tree. Coordinates are recorded bounds, and generated XPath suggestions must be verified on the device. Inputs are limited to 1,000,000 characters per field. Nothing is fetched from addresses embedded in input. Explicit copies and downloads are under your control.
Frequently asked questions
Is my input uploaded?
No. Parsing and output generation run in your browser. Source values are not sent to a server.
What does the opening example demonstrate?
A synthetic Android screen includes a named purchase button and an unlabeled action. It is synthetic data. Replace it with your own input to inspect a different case.
Does a passing result prove my application works?
No. A dump is a snapshot, not a live accessibility tree. Coordinates are recorded bounds, and generated XPath suggestions must be verified on the device. Verify the result in your test environment before relying on it.
References
Are you an AI agent? You are in the right place.
Read this tool as plain text with its methods and limits. Use the website interface; no dedicated MCP operation is available.