Choose an EDIFACT file
Open a local .edi, .edifact or .txt file up to 2 MB.
Inspect UN/EDIFACT interchanges privately.
EDIFACT to JSON
Export the complete bounded UN/EDIFACT hierarchy, separators and ordered source values as JSON.
JSON preserves parsed structural values and raw segment text, with no business interpretation.
EDI File ViewerYOUR WORKSPACE
Your task
Download JSON
Choose a file, then use Download JSON to save the result.
Also with this file: View EDIFACT file · Download CSV · Download Excel
Processed privately in your browserNo uploadNo signup
A simple workflow
Three steps. One less thing to do.
Review structure
Inspect interchanges, messages, segments and ordered components with control counts checked.
Export for review
Download component CSV, four-sheet Excel or full structural JSON.
Made for the everyday
A useful part of your workflow.
Envelope checks
Find an incorrect UNH/UNT or UNB/UNZ reference or count.
Segment inspection
Read unknown business segments without discarding their values.
Structural handoff
Export the full hierarchy for a separate, domain-specific workflow.
Good to know
A few useful answers.
The details that matter before you use EDI File Viewer.
Which EDI syntax works?
ASCII UNOA and UNOB syntax level 3, with default or valid UNA delimiters. UNOC, X12, functional groups and repetition syntax are withheld.
Does this interpret an invoice or order?
No. Message type and structural values are shown, but no business fields are inferred.
Are control totals checked?
Yes. UNT segment count and reference, and UNZ message count and reference, must match before results appear.
How are release escapes handled?
Escaped separators and terminators remain values; raw segment text is also retained in JSON.
Does my file leave this browser?
No. Parsing and exports run locally; EDI values and partner references are excluded from analytics.
What are the limits?
Files up to 2 MB, 20 interchanges, 1,000 messages, 30,000 segments and 150,000 components are accepted. Larger files are refused.