Is my data sent to a server?

No. All processing happens in your browser via JavaScript. Your EDI file never leaves your device.

Which delimiters does the tool detect?

It automatically detects the three delimiters declared by the ISA segment: the element separator, the sub-element separator, and the segment terminator, by reading the fixed positions of that segment (always 106 characters).

What happens if my file has several ISA...IEA interchanges in a row?

They're all processed: the result is a JSON array, one entry per interchange detected in the file.

Does it work with any EDI transaction type (850, 810, 856, etc.)?

Yes, the tool breaks down the envelope's structure regardless of the transaction type; the transaction set (ST01) is identified in the resulting JSON.

EDI to JSON Converter

Convert an EDI/X12 file into structured JSON directly in your browser. The tool automatically detects the delimiters the file itself declares and groups segments into the real EDI envelope hierarchy: interchange, functional group, and transaction set.

How it works

Paste your EDI/X12 file into the input panel (or use the built-in example).
The tool automatically detects the ISA segment's delimiters (element, sub-element, and segment terminator).
Each segment is broken down into its elements and grouped into the real EDI envelope hierarchy: interchange (ISA/IEA), functional group (GS/GE), and transaction set (ST/SE).
The result is shown as readable JSON, ready to copy or download.
All processing happens in your browser — the file is never uploaded anywhere.

Use cases

Debug an EDI/X12 file received from a trading partner without installing specialized software.
Convert a purchase order (850), invoice (810), or ship notice (856) to JSON to integrate with a modern API.
Quickly review the contents of an EDI file before loading it into an ERP system.
Learn the structure of an X12 file by seeing its real hierarchy in a more readable format.

Common mistakes

Expecting the tool to validate the business rules of a specific document type (850, 810, etc.).
This tool converts the EDI envelope's structure (segments and their hierarchy) to JSON; it doesn't validate rules specific to each transaction, like product codes or a particular trading partner's rules. For that, use this site's EDI Validator, which checks the envelope's syntax.
Pasting a file that doesn't start with an ISA segment.
The EDI/X12 envelope always starts with ISA, which is where the tool detects the delimiters. If the file doesn't start with ISA, it can't be interpreted as a complete EDI interchange.
Getting confused because the file doesn't use the standard delimiters (*, :, ~).
X12 lets every file declare its own delimiters in the ISA segment; the tool detects them automatically by reading the fixed positions of that segment, so it works the same regardless of which characters your file uses.

Frequently asked questions

Alternatives

Desktop tools like EDI Notepad, or code libraries like pyx12 (Python), do similar conversions but require installation. This tool is useful for a one-off conversion straight from the browser, with nothing to install.

JSON to EDI Converter

Convert a JSON list of segments into an EDI/X12 file using the standard delimiters.

X12 Parser

Parse an X12 file and get its full structure as JSON, with automatic delimiter detection.

EDI Validator

Validate an EDI envelope's syntax (ISA/GS/ST and their closings) and catch structural errors instantly.

EDI Viewer

View an EDI/X12 file as a readable table, segment by segment, with a description for each one.