CodesBeautify

Random XML Generator

Build a well formed XML document full of believable sample records, with your own element names.

Sample XML5 <item> records
<?xml version="1.0" encoding="UTF-8"?>
<catalog>
  <item>
    <sku>KIT-2536</sku>
    <product_name>Marble Rolling Pin</product_name>
    <category>Garden</category>
    <price>114.93</price>
    <currency>EUR</currency>
    <in_stock>true</in_stock>
    <rating>4.5</rating>
  </item>
  <item>
    <sku>KIT-5347</sku>
    <product_name>Rope Doormat</product_name>
    <category>Outdoor</category>
    <price>15.39</price>
    <currency>SEK</currency>
    <in_stock>true</in_stock>
    <rating>1.8</rating>
  </item>
  <item>
    <sku>KIT-4918</sku>
    <product_name>Copper Watering Can</product_name>
    <category>Travel</category>
    <price>239.54</price>
    <currency>CHF</currency>
    <in_stock>false</in_stock>
    <rating>1.2</rating>
  </item>
  <item>
    <sku>LIG-8480</sku>
    <product_name>Rope Doormat</product_name>
    <category>Travel</category>
    <price>108.03</price>
    <currency>GBP</currency>
    <in_stock>false</in_stock>
    <rating>4.6</rating>
  </item>
  <item>
    <sku>GAR-4132</sku>
    <product_name>Cedar Bookend</product_name>
    <category>Garden</category>
    <price>139.27</price>
    <currency>CHF</currency>
    <in_stock>false</in_stock>
    <rating>2.2</rating>
  </item>
</catalog>
Runs locally in your browser

About the Random XML Generator

Parsers, XSLT sheets and SOAP style endpoints are easier to test against a document that has the shape of the real thing. Set a root element such as catalog, a repeating record element such as item, and choose how many records to emit. Each record is filled from the selected shape, so a Products document carries SKUs, categories and prices while a Log events document carries timestamps, levels and client addresses.

The Values as option decides the document style. Child elements produce the familiar nested form, Attributes squeeze every value onto the record tag for compact feeds, and the mixed setting keeps only the first field as an attribute, which is the usual way an identifier is written. Element names you type are sanitised to valid XML names: spaces and other illegal characters become hyphens and a leading digit is dropped, so the result always parses. Text values are escaped for the five predefined entities, so an ampersand in a company name arrives as &amp;.

Indentation is two spaces, four spaces or a tab, and the XML declaration can be switched off when the fragment will be embedded in a larger document. Check the result in the XML validator, reshape it with the XML to JSON converter, or generate the same records as a spreadsheet file with the random CSV generator.

How to use

  1. Choose the number of Records and the shape of the data.
  2. Type the Root element and Record element names you need.
  3. Decide whether values become child elements or attributes, and set the indent.
  4. Copy the document or download it as an .xml file.

Common questions

Is the output well formed?
Yes. Element names are sanitised, values are entity escaped and every record tag is closed, so the document parses in any XML reader.
Can I control the field names?
Yes. List them in Custom fields, for example sku, product, price, and use heading:type when the tag name should differ from the field type.
Does it produce an XSD or a DTD?
No. It emits instance documents only. Point your schema tool at the generated file if you need a schema inferred from it.
Why do numbers arrive as text?
XML has no native types without a schema, so prices and quantities are written as plain character data, which is what parsers expect.