or drag and drop
Free EDI to JSON Converter
Paste or upload an X12 EDI file and get structured JSON you can copy or download. Runs entirely in your browser.
Your data never leaves your browser
Conversion runs 100% client-side. Nothing is sent to our servers.
Upload EDI File
.txt, .edi, .x12 files up to 2MB
OR
Paste EDI Content
Privacy: Parsing and validation run entirely in your browser. Your EDI documents are never sent to our servers.
Need a sample? Try loading an example EDI document from the sample library below to see how the visualizer works.
Or try a sample
X12 to JSON Field Mapping
X12 is positional and JSON is named, so the parser has to decide what each position becomes. The structure it produces mirrors the EDI envelope rather than flattening it, because flattening loses the grouping that tells you which line item an address belongs to.
| X12 structure | Becomes | Notes |
|---|---|---|
| ISA / IEA | Interchange object | Sender and receiver IDs, qualifiers, control number, test or production flag |
| GS / GE | Functional group array | One entry per group, carrying the GS08 version |
| ST / SE | Transaction array | One entry per transaction set, with its type and control number |
| Segment | Object with segment ID | Segment tag preserved so you can map it yourself |
| Element | Positional array entry | Positions are kept as sent, including empty ones, so element numbering still lines up with the spec |
Empty elements are preserved rather than dropped. That looks noisy but it matters: if the converter silently removed empty positions, PO107 would shift into PO106 and every downstream mapping would be wrong by one.
Which Transaction Sets Work?
Any valid X12 document parses, because the converter works from the envelope and segment structure rather than a per-transaction template. That includes the 850 purchase order, 810 invoice, 856 ship notice, 997 acknowledgment, 830 planning schedule, 832 catalog, 940 and 945 warehouse documents, and the rest. Transaction sets with a named reference in the tool get friendlier labels; everything else still converts, just with the raw segment tags.
Going the Other Direction
This tool reads EDI and writes JSON. It does not generate X12 from JSON. Building a valid outbound interchange means constructing the ISA envelope with its fixed-width elements, matching control numbers across ISA and IEA, GS and GE, and ST and SE, and satisfying whatever your trading partner requires on top of the standard. A subtly invalid 850 sent to a large retailer is worse than no file at all, which is why we have not shipped a one-click generator.