Open any XML document, RSS feed, or sitemap in your browser and read it as a clean data table. Upload an .xml file to see every record as a row and every tag or attribute as a column — no editor, no namespace wrangling, no install.
Try it free →No signup · No data stored · 100% free
How it works
- 1
Upload your XML file
Drop any .xml file. No account required.
- 2
AI-assisted conversion
Our engine reads your data, detects column types, and picks the best chart for each pattern.
- 3
Visualize your graphs
Interactive charts are ready instantly. Explore trends and share insights.
Everything you need, nothing more
No account needed
Upload instantly, zero signup.
Privacy first
Files are never stored on our servers.
Any device
Works on mobile and desktop.
AI-powered
Smart chart selection from your data.
Common use cases
Inspect SOAP & API responses
Open a SOAP envelope or XML API response and read its nested elements as an indented tree. Find the values buried inside deep tags without scanning one long line.
Read RSS & sitemap files
View an RSS feed or XML sitemap as a structured document to check items, links, and dates. Confirm a feed is well-formed before publishing or submitting it.
Review config & export files
Many systems export XML — settings, reports, data dumps. Preview the structure and attributes to verify a file before importing it or handing it to another tool.
Read an XML file without an editor
XML is written for machines. A single line can carry a whole invoice, and even prettified in an editor it is a wall of angle brackets where the values you want sit four levels down. Most people paste it into a formatter first just to find out what is inside.
This viewer parses the document and lays the records out as a table: one row per repeated element, one column per field. Nothing is installed and no account is created, and it behaves the same on Windows, macOS, Linux, ChromeOS, Android and iOS — a locked-down work laptop reads the file as well as your own machine.
Namespaces and prefixes are stripped for you
Real-world XML rarely arrives clean. A SOAP response wraps its payload in an envelope and tags everything with a prefix; a UBL invoice declares several namespaces before the first useful element appears. Tools that preserve those prefixes hand you column names like <code>soap:Sku</code> or <code>cbc:InvoicedQuantity</code>, and every query you write afterwards has to carry them.
Here the prefixes are removed. A SOAP envelope yields plain Sku and Qty columns; a UBL invoice yields ID and Amount. The documents work exactly as they were sent, with no pre-processing and no namespace map to configure.
Attributes and nesting, handled without preparation
XML stores the same information in two places, and exporters disagree about which to use. One system writes <code><row id="1" qty="5"/></code> with everything in attributes; another writes <code><row><id>1</id><qty>5</qty></row></code> with everything in child elements. Both are read here, and both become ordinary columns.
Nesting is flattened the same way. A record containing <code><user><name>Ada</name></user></code> produces a user.name column beside the rest, so you keep the nested values without simplifying the document first.
The repeating element is located automatically. Whether your records are <item>, <row>, <entry> or something a vendor invented, the parser walks the tree and picks the level that repeats.
When a file will not open
XML is strict, and three problems cause almost every failure.
<strong>An unescaped character.</strong> A bare &, < or > inside text breaks the document. Those must be entity-encoded, which is why an export containing a company name like "Smith & Sons" fails while everything else in the same file is fine.
<strong>More than one root element.</strong> Concatenating two exports into one file produces a document with two top-level elements, which is not valid XML. So does a stray character or blank line before the declaration.
<strong>Mismatched tags.</strong> XML is case-sensitive, so <Item>…</item> is an error rather than a warning.
Your file is parsed and returned as data rather than kept in permanent storage, and your file history stays in your own browser.
Tips & best practices
The viewer parses well-formed XML and lays the records out as a data table: each repeated element becomes a row and each child tag or attribute becomes a column. Namespaces and prefixes are stripped, so a SOAP envelope or a UBL invoice yields plain column names such as Sku and Qty rather than soap:Sku. Nested children are flattened into dotted columns, so <user><name> shows up as user.name without any preparation. A single root element is required; a file with two top-level elements or a stray character before the declaration will fail to parse. If a document won't open, an unclosed tag, a mismatched case in tag names, or an unescaped &, <, or > inside text is the usual cause — those characters must be entity-encoded. Your file is parsed and returned as data rather than kept in permanent storage, and your file history stays in your own browser.
Ready to visualize your data?
Upload your XML file and see your data come alive instantly.
Try it free →Frequently asked questions
Q.What does this site do & how can I convert my XML files to graphs?
This site is a free, instant online tool to view, read, and convert XML (.xml) files into interactive charts. Simply upload your file in the box above, and our system will automatically analyze your data structure, detect column types, and generate chart recommendations which you can customize and export.
Q.What file types are supported?
.xml files are supported.
Q.What chart types can it generate?
Bar, line, area, pie, scatter, and trend charts — chosen automatically based on your data.
Q.Is it free?
100% free. No signup, no credit card, no limits.
Q.Does it handle SOAP responses and namespaces?
Yes. Namespace prefixes are stripped, so a SOAP envelope yields plain column names such as Sku and Qty rather than soap:Sku. No namespace configuration is needed.
Q.Are attributes read, or only child elements?
Both. A record written as <row id="1" qty="5"/> and one written with child elements produce the same columns, so exports from either style work.
Q.Do I need to flatten nested XML first?
No. Nested children become dotted columns automatically, so <user><name> shows up as user.name without any preparation.
Q.Why won't my XML file open?
Usually an unescaped &, < or > inside text, more than one root element, or a mismatched tag. XML is case-sensitive, so <Item> must close with </Item>.
Q.Can it open an RSS feed or a sitemap?
Yes. Both are XML with a repeating element — <item> for RSS, <url> for a sitemap — so each entry becomes a row and each field a column.
Have a different file type?
Each format has its own dedicated tool built for it.