EDI Viewer

Paste or upload a raw X12 or EDIFACT EDI file and explore it as a collapsible tree — nothing leaves your browser.

EDI Source 0 lines
1
Tree View
0 nodes
1
UTF-8 · 0 B
Waiting for input
Related tools EDI to XML EDI to JSON XML Viewer

Why Use Our EDI Viewer?

  • Auto-detects X12 or EDIFACT and its delimiters
  • Instant collapsible tree: envelope → group → transaction → segments
  • Recognises common transaction sets and EDIFACT messages
  • Works completely in your browser
  • No installation or sign-up

Features & Supported Capabilities

  • Auto-detects element, sub-element and segment delimiters
  • Groups segments into interchange / group / transaction / loop
  • Convert the parsed file to XML or JSON in one click
  • Search, expand/collapse, click-to-copy paths
  • Download the tree as text or as an SVG image
  • Handles files up to 10 MB

About this EDI viewer for X12 and EDIFACT

Raw EDI is a dense stream of segments and delimiters that is hard to read. This free online EDI viewer auto-detects whether your data is ANSI X12 or UN/EDIFACT, along with its delimiters, and shows it as an interactive tree of interchanges, segments and elements that you can expand and search.

Parsing happens in your browser and nothing is uploaded, which matters for business documents. You can also convert to structured data with EDI to XML or EDI to JSON, then explore the result in the XML viewer or JSON viewer.

Frequently Asked Questions

Everything you might want to know about the online EDI Viewer.

An EDI viewer takes a raw EDI file — the compact, delimiter-separated text businesses exchange for purchase orders, invoices and shipping notices — and displays it as a readable, collapsible tree instead of one dense line of segments.
Two: ANSI X12 (starts with an ISA segment — the standard used across US supply chain, retail and healthcare EDI) and UN/EDIFACT (starts with a UNA or UNB segment — the international standard, common outside North America). The viewer detects which one you pasted and reads its header to automatically pick up the element, sub-element and segment delimiters, so no manual configuration is needed.
Following each standard's own envelope structure. For X12: Interchange (ISA/IEA) → Functional Group (GS/GE) → Transaction Set (ST/SE) → Segments. For EDIFACT: Interchange (UNB/UNZ) → optional Functional Group (UNG/UNE) → Message (UNH/UNT) → Segments. Common transaction sets and message types — 850 (Purchase Order), ORDERS (Purchase Order), 810/INVOIC (Invoice), 856/DESADV (Ship Notice) and more — are labelled by name.
No. Parsing happens entirely in your browser. EDI files often carry business and trading-partner data, so nothing is ever uploaded, stored, or logged.
Yes. Use the Download XML or Download JSON buttons to export the parsed structure in either format, or use the dedicated EDI to XML and EDI to JSON pages if you'd rather work from a plain converter without the tree view.
Yes, for both formats. It checks that control numbers match up between the header and trailer of each envelope level (ISA/IEA, GS/GE, ST/SE for X12; UNB/UNZ, UNG/UNE, UNH/UNT for EDIFACT), that the declared segment and group counts in the trailer segments match what was actually found, and that common transaction sets and message types include their required beginning segment. Issues are shown as warnings or errors above the tree — this is structural validation, not a full implementation-guide check against every element.
You can paste text or upload a file up to 10 MB.