Concordance DAT ⇄ Opticon OPT ⇄ IPRO LFP ⇄ CSV. Families and field mappings preserved; Bates numbering checked as the file loads. Every byte is parsed on this page.
No file loaded.
Load a file to run the Bates integrity check.
Two families: metadata files carry one row per document; image files carry one row per page. The converter bridges them.
| Format | Shape | Structure | Guide |
|---|---|---|---|
| Concordance DAT | Metadata | Delimited records; ASCII 20 (¶) between fields, þ qualifier, ® for in-value line breaks | DAT format |
| Opticon OPT | Images | Seven comma columns per page; "Y" doc-break flag; page count on the first row | OPT format |
| IPRO LFP | Images | Line-oriented IM records; "D" document flag; @volume;dir;file; token | LFP format |
| CSV | Metadata | RFC 4180; quoted cells carry commas, line breaks, doubled quotes | Overview |
Document families travel with the data: members sharing a BEGATTACH value stay together, so a parent email and its attachments never separate.
Every load is run through the Bates checker: gaps and duplicates in the page sequence, ENDBATES that precedes BEGBATES, a PAGECOUNT that disagrees with the Bates span, pages outside every declared range, and metadata/image document counts that disagree. A dedicated Bates checker page accepts several files at once for cross-file audits.
Encoding is detected the same way: UTF-8 and UTF-16 byte-order marks are honored, strict UTF-8 is verified rather than assumed, and anything else is read as Windows-1252 or GB18030 — whichever decodes your delimiters and custodian names intact.
Upload-based converters hold your load file — and the document index it describes — on their servers. LoadfileKit was built the other way: the conversion engine ships with the page, and your production index stays on your machine. Load the page, disconnect from the internet, and convert offline. There is no account, no API and no server that receives files.
Small jobs are free, and the free tier is the real converter — not a preview that strips your fields.
The full version unlocks on this device for 7 days after viewing a sponsor message — no code, no account.
No. Parsing and serialization run entirely in your browser. There is no endpoint to receive a file — you can load this page, disconnect, and keep working.
Yes. Documents sharing a BEGATTACH value are treated as one family and kept in order; a parent email and its attachments never separate.
Yes. DAT or CSV to OPT or LFP enumerates each document's pages from its BEGBATES–ENDBATES range using the path template above. The reverse collapses each page run back into BEGBATES, ENDBATES, PAGECOUNT and VOLUME.
Documents per file: 25. A typical production volume fits; larger ones need the full version, unlocked by viewing a short sponsor message — it stays unlocked on this device for 7 days.
UTF-8, UTF-16 (with or without byte-order mark), Windows-1252 and GB18030, detected from the bytes themselves — and the output is written back in the same family so a round trip does not corrupt your index.
Gaps, duplicates, backwards sequences, prefix and padding changes, ENDBATES before BEGBATES, PAGECOUNT disagreements, pages outside every declared range, and metadata/image document-count mismatches.