Convert XML records to CSV. Choose the record element, map fields and attributes, review repeated values, and inspect the table before downloading.
将 XML 文件拖到此处,或从设备中选择。
原文件不会被覆盖。
Pick the element that represents one output row, with path, namespace, and sample.
Select element text, attributes, and parent fields; rename and order columns.
Join repeated values, split them into indexed columns, or use a repeated branch as row anchor.
Review the sample table and mapping report, then run the full conversion.
Provide the XML source or start with the example. Review parsing errors before continuing; a file that can be parsed still needs a suitable table mapping.
Select the element that represents one output record. For a catalog that may be a product; for an order export, an order or an individual item. Check the path and sample rather than choosing only by count.
Select element values, attributes, and parent fields needed to preserve relationships. Review column names and namespaces so similarly named fields do not become indistinguishable.
Decide whether repeated values belong in one cell, indexed columns, or separate records. Each choice changes the shape of the output; separate lists are never paired automatically.
Run the full conversion, then review record counts, columns, warnings, and the mapping report. Download the CSV or continue with a compatible table tool only after confirming the result.
Products with attributes and repeated tags
This original example contains two products. The mapping uses one product per row, extracts product and price attributes, and joins tag values with ; .
<catalog xmlns="urn:tinycsv:example">
<product id="0007"><name>Maple & Pine</name><price currency="USD">12.50</price><tags><tag>desk</tag><tag>gift</tag></tags></product>
<product id="0012"><name>River Mug</name><price currency="USD">9.00</price></product>
</catalog>id,name,price,currency,tags
0007,Maple & Pine,12.50,USD,desk; gift
0012,River Mug,9.00,USD,The ID and price text remain text. The XML entity is represented by its decoded character in the CSV, so this is not a byte-for-byte copy. Joining tags also introduces a separator convention: if original tag values contain the separator, another reader needs a documented way to distinguish them. This example does not claim lossless reconstruction.
XML organizes data through elements, attributes, and nested records. A CSV output needs a defined set of rows and columns, so an xml to csv converter must start by choosing what one row represents. Automatic suggestions are a starting point, not proof that the converter has understood your data model.
To convert xml file to csv, choose a file or paste XML, select the records, map the columns, set repeated-value handling, then generate and inspect the result.
The example above uses two products, extracts product and price attributes, and joins tags with a separator. Identifiers keep their leading zeros; decoded entities are text, not a byte-for-byte copy of the source.
When you convert nested xml to csv, an order with several items can become one row with repeated values, several item rows with the order key, or multiple related outputs. These are different mappings, not interchangeable formatting preferences. TinyCSV asks you to review repeated branches rather than silently generating combinations.
Attributes can carry identifiers, units, or other values required by the destination. Namespace prefixes are display choices, not reliable field identities by themselves. Review namespace-aware paths and resolve naming conflicts before creating the output; shorter column names should not merge distinct fields.
A missing element, an empty element, and an explicitly marked null may have different meanings. A plain empty CSV cell may not preserve those distinctions without an agreed convention. Comments, processing instructions, mixed content, and document-level information are not automatically preserved by a flat export; review the mapping report for excluded structures.
A sample helps check the mapping, but it is not the complete result. Full processing must account for records and fields outside the preview. File size alone does not determine the workload: depth, repeated branches, field lengths, selected columns, and output expansion all affect processing. No unlimited-size or instant-conversion promise is made here.
Inspect identifiers, dates, empty values, record counts, and relationships before importing into a spreadsheet. Choose export settings deliberately: encoding, delimiters, quoting, and any formula-safety option should match the destination and remain visible choices rather than silent changes.