Convert e‑discovery load files — without uploading your production
Move a production between Concordance DAT, Opticon OPT, IPRO LFP and CSV. Document families and field mappings are preserved, and every byte is parsed in your browser — which matters when the data is privileged.
- Files never leave your device
- No signup, no account
- Works offline once loaded
Drop a load file here, or click to choose
.dat · .csv · .opt · .lfp — format is detected automatically
No file is ever uploaded — conversion happens on this page.
From one vendor's load file to another's, in three steps
No desktop suite to license, no account to create. The converter is the page you're on.
Drop the load file
A Concordance .dat, a CSV metadata export, an Opticon .opt or an IPRO .lfp. The format is detected from the extension and the delimiter bytes, and the document and page counts are read back to you immediately.
Pick the target
Same-shape conversions (DAT↔CSV, OPT↔LFP) copy fields and pages verbatim. Crossing shapes enumerates pages from each document's Bates range, or collapses a page run back into BEGBATES/ENDBATES with a page count.
Download the result
The output is written with the correct delimiters and encoding — Windows-1252 with the Concordance control characters for DAT, RFC 4180 for CSV — and downloaded straight from the page.
What each load file actually is
Two families collapse into one model: metadata files carry one row per document, image files carry one row per page. The converter bridges them.
Concordance DAT
Delimited metadata, one record per line. Fields are wrapped in the text qualifier (þ) and separated by the field delimiter (¶); in-value line breaks are stored as ® so a record never spans physical lines.
CSV
RFC 4180 metadata. The first row names the columns; quoted cells carry commas, line breaks and doubled quotes. The plain-text cousin of a DAT, and the easiest to open in Excel.
Opticon OPT
Page-level image cross-reference. Seven comma-separated columns per page; a "Y" doc-break flag on the first page is the only thing grouping pages into documents, and the page count rides on that first row.
IPRO LFP
Line-oriented image load. Each IM record bundles the key, a "D" document flag, box and offset, and an @-token packing the volume, directory and filename with semicolons.
Document families travel with the data: members sharing a BEGATTACH value are kept together so a parent email and its attachments never separate during conversion.
Built for productions that can't take a detour
Upload-based converters hold your load file — and the document index it describes — on their servers. LoadFile Converter was built the opposite way: the conversion engine ships to your browser, and your production index stays on your machine. Load the page, disconnect from the internet, and convert offline.
Zero upload, by architecture
There is no server that receives files. Parsing and serialization are client-side code that runs on the page.
Families preserved
Parent/child relationships keyed on BEGATTACH are grouped and kept intact, so attachments stay with their parent document.
Delimiters handled correctly
The Concordance ¶/þ/® control characters and RFC 4180 quoting are read and written exactly, so round-trips don't corrupt your index.
Encoding aware
UTF-8 and UTF-16 byte-order marks are detected; ANSI DAT files fall back to Windows-1252 so the delimiter bytes survive a round trip.
Free for small jobs. $49 once for unlimited.
No subscription. Credits never expire. Trivial against any litigation budget — the desktop alternatives run $1,000+.
Free
$0
- Up to 25 documents per file
- Every format and conversion direction
- 100% local — no upload, no signup
Full version
$49 once · 1,000 conversions
- Unlimited documents per load file
- All four formats, every direction
- Document families kept intact
- Custom path templates and field mappings
- Nothing ever uploaded
Answers before you convert
Does my load file get uploaded?
No. Parsing and serialization run entirely in your browser. You can load this page, disconnect from the internet, and convert offline. There is no server that ever sees your production index — by design, because the document index of a privileged production shouldn't sit in a stranger's cloud.
Are document families preserved?
Yes. Documents that share a BEGATTACH value are grouped into a family, with the parent identified by its BEGBATES. Conversions keep family members together and in order, so a parent email and its attachments never separate.
Can it convert metadata to an image load file and back?
Yes. Converting a DAT or CSV to an OPT or LFP enumerates each document's pages from its BEGBATES–ENDBATES Bates range using a path template you control. Converting the other way collapses each page run back into BEGBATES, ENDBATES, PAGECOUNT and VOLUME.
What does "1,000 conversions" mean?
Each document in a load file counts as one credit. A typical production runs well under 1,000 documents, and the credits never expire. The free tier converts up to 25 documents per file so you can verify the output before buying.