Does my EDI file get uploaded anywhere?

No. The conversion runs entirely in your browser — there is no upload to make. You can disconnect your network and it still works. That matters when the file is a customer's purchase order.

Which EDI standards are supported?

X12 and EDIFACT. The parser detects the standard, delimiters, and segment terminator from the file itself, so you don't have to tell it anything.

Is this the same parser Flowitz uses for paid EDI kits?

Yes — literally the same code. The EDI Studio grounds its documentation on this exact parse, so what you read here is what the kit is written from.

converters · free tool

EDI to XML

Turn an X12 or EDIFACT file into readable XML — in your browser, nothing uploaded.

Runs in your browser — your data never leaves it

Input

Paste, type, or drop a file. Runs as you type.

Output

Output appears here as you type.

Worked example

Input

ST*850*0001~BEG*00*SA*PO123**20260101~N1*BT*NORTHWIND SUPPLY CO.~PO1*1*2*EA*9.99*CP*BP*SKU-1~CTT*1~SE*6*0001~

Output

<Transaction standard="X12" code="850" name="Purchase Order">
  <Header>
    <Number>PO123</Number>
    <Date>20260101</Date>
    <Purpose>00</Purpose>
    <Currency/>
  </Header>
  <Parties>
    <Party code="BT">
      <Role>Bill-to</Role>
      <Name>NORTHWIND SUPPLY CO.</Name>
      <Id/>
      <City/>
      <State/>
    </Party>
  </Parties>
  <LineItems>
    <LineItem line="1">
      <Quantity>2</Quantity>
      <Unit>EA</Unit>
      <Price>9.99</Price>
      <ProductIds>
        <ProductId qualifier="BP">SKU-1</ProductId>
      </ProductIds>
    </LineItem>
  </LineItems>
  <Dates/>
  <References/>
</Transaction>

This example is one of EDI to XML's test cases — if the tool stopped producing this output, the build would fail.

Questions

Does my EDI file get uploaded anywhere?: No. The conversion runs entirely in your browser — there is no upload to make. You can disconnect your network and it still works. That matters when the file is a customer's purchase order.
Which EDI standards are supported?: X12 and EDIFACT. The parser detects the standard, delimiters, and segment terminator from the file itself, so you don't have to tell it anything.
Is this the same parser Flowitz uses for paid EDI kits?: Yes — literally the same code. The EDI Studio grounds its documentation on this exact parse, so what you read here is what the kit is written from.

Related tools

XML Formattertakes xml

Pretty-print and indent XML, however badly it arrived.

XML Validatortakes xml

Check whether XML is well-formed and see exactly where it breaks.

XML to JSONtakes xml

Convert XML into JSON, attributes and text nodes included.

XML Difftakes xml

Compare two XML documents element by element.