| Minimum Software Version | 8.18.10 |
| Solution(s) | Cases International ✓ Cases US ✓ Institutions ⨉ Counsel ✓ |
Explains how files are uploaded, processed, and managed in Opus 2, including upload parameters, OCR options, supported file types, processing statuses, and performance considerations.
Files can be added to an Opus 2 project from either the Documents page or the Files page. The platform supports batch uploads of up to 2 GB, with a maximum number of files per batch dependent on browser capabilities (typically at least 5,000 files). Uploaded files are ingested, processed, scanned for viruses, converted to PDF where supported, and optionally OCR'd.
Opus 2 supports both simple uploads and more structured, service-based workflows where files may be uploaded and reviewed before being published to project users. Depending on project configuration, users may upload documents or transcripts. Processing continues in the background, and document readiness is communicated through system metadata fields.
Uploading files to a project
- Navigate to Documents or Files.
- Click Upload > Upload document or Upload transcript.

- Drag and drop files (or folders) into the upload window, or browse to select them.
- Review and configure upload parameters as required.
- Start the upload.
Files are queued for ingestion and processed automatically.
Upload parameters
The following parameters may be available depending on project configuration.
Batch name Identifier for the upload batch, useful for tracking processing issues.
Publish Determines whether files are immediately published as documents.
- Available only to users with Files page access.
- Otherwise, files are published automatically.
Folder Specifies the destination folder for published documents.
- If no folder is selected, a folder is created under Uploads using the upload date and time.
OCR Choose how Optical Character Recognition (OCR) should be applied during upload:
- None – No OCR processing is performed.
- If required (default) – OCR is applied only when searchable text is not already present in the document. This is the recommended setting in most cases.
- Always – OCR is applied regardless of whether searchable text already exists.
Unpack zip archives Automatically extracts ZIP file contents on upload.
- Password-protected ZIP files generate slipsheets instead.
Extract email attachments When enabled, attachments are automatically extracted from email files (such as .eml and .msg) and uploaded as separate documents alongside the email.
- Leave this selected (recommended) when uploading email files to ensure attachments are available as individual documents.
- Unticking this option uploads email files without extracting their attachments.
Actions (for selected uploads)
- Add tags
- Clear tags
- Remove selected uploads
Further information Free-text notes related to the upload batch.
Duplicate handling Options appear when duplicates are detected:
- Only show duplicates
- Remove duplicates
Uploading without publishing
Files can be kept unpublished for review or validation. Unpublished files are visible only to administrators in the Files area and can be published when ready.
File processing and OCR
OCR adds an invisible text layer to PDFs, enabling text search and annotations. Processing follows a round-robin approach to ensure fair resource allocation across users and uploads. All files are scanned for viruses. If a virus is detected, the file is deleted and the issue is reported.
Supported file types
During ingestion, Opus 2 automatically processes and converts files to PDF where possible to ensure they are accessible within the platform. The conversion covers a broad range of formats; however, there may be isolated cases where a file does not convert as expected. These instances may require support from the Opus 2 team.
| Category | Supported file extensions |
|---|---|
| EML (.eml), Outlook Message (.msg) | |
| Word documents | .doc, .docx, .docm, .dot, .dotx, .dotm, .docb, .wbk |
| PowerPoint presentations | .ppt, .pptx, .pptm, .ppts, .ppa, .ppam, .pps, .ppsx, .ppsm |
| Images | .png, .jpg, .jpeg, .bmp, .gif, .tif, .tiff |
| Text documents | .txt, .rtf |
| OpenDocument formats | .odt, .ods, .odp, .odg |
| Excel | .xlsx, .xls, .xlsm, .xlsb, .xlt, .xltm, .xla, .xlam |
| Web pages | .htm, .html |
| Project files | .mpp |
| OneNote | .one |
| Visio diagrams | .vsd |
| CAD drawings | .dxf |
Note: The following file types may upload as a native slipsheet on ingestion rather than a PDF:,.xlsx,.xls,.xlsm.xlsb,.xlt,.xltm,.xla,.xlam,.odt,.ods,.odp,.odg,.mpp,.ppt,.pptx,.pptm,.ppts,.ppa,.ppam,.pps,.ppsx,.ppsm,.vsdIf you require a searchable version of any of these documents for Search or AI Focused View, you may need to convert the file to a PDF format before ingestion, or contact Opus 2 Platform Support for further guidance.
Transcripts: .txt, .ptf, .pcf, .mdb, .xmef, .lef
.leffiles can automatically link exhibits..mdbsupports synchronised media (.mpg,.mp4preferred).
Media: .mp3, .ogg, .wav, .mp4, .mpg, .mpeg, .webm
Performance considerations
| Feature | Upper limit | Notes |
|---|---|---|
| Documents in workspace | 20,000 | Recommended limit for optimal performance. Load times will begin to increase beyond this number. |
| Pages per document | 15,000 | |
| Documents per folder | 3,000 | |
| Transcripts in workspace | 20,000 | .txt, .rtf, .mdb files for transcripts; .mp3 and .mp4 files for transcript media. |
Processing status and results
File and document processing status is visible via the Status metadata field. Common statuses include:
- Queued – Awaiting the start of processing
- In progress – Processing has started
- Available – Processing completed; document is ready
- Slipsheet – Generated due to an unsupported format or password-protected file
- Processing error – Processing was interrupted
- Virus detected – File has been flagged and deleted
- Unreadable / corrupted – File recognised but unable to be opened
- Not received – File was not located
- Upload error – An error occurred during upload
Detailed processing data is also available on the Files page, including processing status, processing result, processing completion time, and published flag.
| Field | Status | Explanation |
|---|---|---|
| Processing status | Not received | File not located |
| Ready | Processing completed | |
| Queued | Awaiting start of processing | |
| In progress | Processing started | |
| Processing error | Processing was interrupted | |
| Processing result | Available | A PDF was successfully generated from the source file |
| Slipsheet (unsupported format) | Slipsheet generated due to unrecognised file format | |
| Slipsheet (password protected) | Slipsheet generated due to password preventing access to file content | |
| Virus scan failed | Virus scanner failed to run and caused a processing error | |
| Potential virus detected | Virus detection caused a processing error | |
| Unreadable file / corrupted | File recognised but unable to be opened | |
| Processing finished at | Date/time | Process of the file terminated at the indicated date and time |
| Published | True | PDF generated in a documents folder |
| False | File processing complete with PDF output not shown |
Failed files (except those marked Not received) can be reprocessed via Actions → Reprocess files.
Upload history
Previous uploads can be reviewed via Project → Upload history. Filters allow results by batch name, uploader, dates, file counts, errors, and completion status. Selecting a batch displays summary and file-level details.
| Field | Description |
|---|---|
| Name | Batch name specified at time of upload |
| Description | Text inserted into the Further information tab at time of upload |
| Date uploaded | Upload initiation date |
| Uploaded by | User that performed the upload |
| Files | Number of files uploaded in a batch |
| Processed | Number of files processed in a batch |
| Errors | Number of files with errors in a batch |
| Finished | True/False representing completion of the batch upload |
| Time finished | Specific date the batch upload completed |
Plan large uploads carefully by selecting appropriate OCR and publishing options. Use batch names and upload history to track processing, and review status indicators to confirm documents are ready for use.
Related links
Related documentation
Opus 2 has help information accessible within the application; click the question mark and then select Documentation in the upper-right area of the platform. You can also access the documentation at: Opus 2 Support.
How to contact us
To contact us about the documentation, or if you have any other questions or issues about Opus 2 solutions, contact Opus 2 Platform Support by emailing Opus 2 Platform Support.