Is my data sent to a server?

No, all processing happens in your browser.

What do the segment codes mean?

The "Description" column translates the purpose of the most common segments into plain language (for example, N1 is "Party name" and PO1 is "Order line item"). For less common segments, you'll need the document's specific implementation guide.

Can I download the table?

Right now the tool only displays the table on screen; if you need the result as JSON to save or process it, use this site's EDI to JSON Converter.

Does it work with large EDI files?

Yes, your browser can process files with several thousand segments without issue; the practical limit depends on your device's available memory.

EDI Viewer

View an EDI/X12 file's contents as a readable table: each row shows the segment, a plain-language description, and its elements, instead of the hard-to-read raw text.

How it works

Paste the EDI/X12 file you want to inspect (or use the built-in example).
The tool detects the file's delimiters and splits every segment into its elements.
Each segment is shown as a table row, with its code, a plain-language description (for the most common segments: ISA, GS, ST, BEG, N1, PO1, etc.), and its elements.
Scan the table to understand the file's contents without manually decoding the raw text.

Use cases

Quickly review what an EDI file contains before processing or forwarding it.
Explain to someone without EDI experience what information a file carries, visually.
Compare two EDI files segment by segment to spot differences.
Visually confirm that an EDI file generated by your system has the expected segments, in the expected order.

Common mistakes

Expecting a description for every possible X12 segment.
The tool includes descriptions for the most common envelope segments and the most frequent document types (purchase orders, invoices, ship notices). Less common or trading-partner-specific segments are still shown, labeled "Document-specific segment."
Confusing the viewer with a validator.
The viewer only shows the content in a readable way; it doesn't check for structural errors. For that, use this site's EDI Validator.
Pasting an EDI file with line breaks inside a single segment and expecting it to be read as several segments.
The tool splits segments using the segment terminator declared in the ISA (usually ~), not line breaks; line breaks are ignored when processing the file.

Frequently asked questions

Alternatives

Specialized EDI editors like EDI Notepad offer deeper inspection with built-in validation. This viewer is useful for a quick, visual review without installing software.

EDI to JSON Converter

Convert an EDI/X12 file into structured JSON (interchange, functional group, and transaction set), right in your browser.

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.

JSON to EDI Converter

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