About

What problem does it solve?

One day a file with an .edi extension arrives in your inbox. You open it and find something like this:

UNB+UNOC:3+8712345678901:14+8798765432109:14+260117:1030+REF00042'
UNH+ME000001+ORDERS:D:96A:UN:EAN008'
BGM+220+PO-2026-0042+9'
NAD+BY+8798765432109::9++MEGA RETAIL AS+Barbaros Bulvari 12+ISTANBUL+34353+TR'

This is a purchase order. Who sent it, who it is for, which products are wanted and when they should be delivered are all in those lines — but none of it is visible in a plain text editor.

Enterprise EDI software reads these files, but the licences are expensive and usually require an installation. For a small supplier, an accountant, or a developer doing their first integration, all of that is out of proportion to simply looking at one file. ediviewer exists to fill exactly that gap: open the file, see what it says.

What can it do?

• Makes files readable. It shows every segment and every data element inside it with a description. It tells you that a NAD+BY line is the buyer's address and that DTM+137 means the document date.
• Lets you edit. Syntax highlighting, line numbers and active line marking, with the ability to edit and save the file.
• Exports to PDF. Turns message types such as ORDERS, INVOIC and DESADV into a readable document — the order as a table, the invoice with its totals.
• Exports to Excel. Converts sales report (SLSRPT) and price catalogue (PRICAT) files into a spreadsheet.
• Converts to JSON and XML. EDI ↔ JSON ↔ XML in every direction, and after each conversion it converts the result back and compares it to the source to prove nothing was lost.
• Speaks seven languages. Turkish, English, German, French, Spanish, Italian and Simplified Chinese.

Where is your data processed?

On your device. All of it. The entire application is JavaScript running in your browser; parsing, PDF generation, Excel export and format conversion never reach a server.

This is not a policy choice but a consequence of the architecture: there is no server that could receive your files. Commercial documents — your prices, your customers, your order volumes — are sensitive, and they should not be uploaded to a website. See the Privacy Policy for details.

There is a practical side benefit: once the page is open, the application keeps working even if your connection drops.

EDI Reference

Alongside the application there is a free reference section that requires no sign-up: the EDI Reference. It covers 48 segments, the structure of common message types, guides explaining the underlying concepts, and practical articles.

It is designed as a dictionary you can reach for at the moment you get stuck. When you select a segment in the detail panel, a direct link to that segment's reference page appears.

Who builds it?

ediviewer is developed by Metin Karaduman. It grew out of a practical need that comes up when working with EDI files: you have a file in hand, you need to see what is in it, and you would rather not install enterprise software to do so.

It was first written as a macOS desktop application, then brought to the web so that anyone could reach it without installing anything. The web version is a faithful counterpart of the desktop one.

Is it free?

Yes. No registration, no subscription, no usage limits. The site shows adverts to cover its running costs. Adverts do not affect how the application works, and every feature remains fully functional even if you decline cookies.

Feedback

If you find a missing segment, a mistranslated description, or a file that does not behave as you expect, I would like to hear about it. Bug reports are especially valuable: if a file of yours does not display correctly, chances are other people's files do not either.

You can write from the contact page.