Convert an IPRO LFP to an Opticon OPT
When images arrive from an IPRO shop as an LFP but your review platform (Concordance, Relativity, plenty of others) wants an Opticon OPT, you need to flip the format without touching the images themselves. The LFP is line-oriented: each IM record carries the page key, a "D" flag on the first page of a document, a box number, the @volume;directory;filename location token, a byte offset and a page count. The OPT wants seven flat comma-separated columns instead.
The converter reads each IM record, unpacks the @-token back into a volume and a full path, and uses the D flags to rebuild document boundaries. It then emits Opticon rows: key, volume, path, a "Y" on each document's first page, empty folder/box-break columns, and the page count on that first row. Non-image records in the LFP (such as OF native-file references) are ignored so a mixed file still imports its image base cleanly.
Everything happens in the browser. The LFP describes where your produced images live; that map never gets uploaded.
Open the converter — free, no upload
How to convert LFP to OPT
- Drop the .lfp file into the converter.
- Choose Opticon OPT as the target format.
- Convert. The .opt downloads with doc-break flags and page counts rebuilt from the LFP's D flags.
- Import the OPT into Concordance, Relativity or your image-management tool.
Questions
Does it handle LFP files that also contain native (OF) records?
Yes. Only IM image records are converted into OPT rows; OF and other record types are skipped, so a combined imagebase/nativebase LFP still produces a valid OPT for the images.
Where does the OPT volume label come from?
From the volume segment of each IM record's @-token (@VOL001;… → VOL001). It's written into the OPT's second column for every page.
What about the byte offset in multi-page images?
The OPT format doesn't carry a byte offset; it references one image file per row. The converter maps each LFP image record to its OPT row using the path, which is what Opticon needs.