EPUB OCF container
The EPUB container must expose the package document through the expected container structure, including META-INF/container.xml and the packaged resources it points to.
EPUB error guide
Why OPF_002 happens when container.xml points to a missing package file, and how to scan for a safe fix.
OPF_002: The OPF file was not found.
container.xml exists, but the rootfile path points to an OPF file that is not inside the EPUB package.
Plain English
The EPUB has a map to the package file, but the map points to the wrong place.
The OPF may have been moved, renamed, zipped from the wrong folder, or referenced with the wrong case or relative path.
User checklist
These checks keep the repair decision tied to the EPUB package instead of guessing from a generic error code.
Standards context
The EPUB container must expose the package document through the expected container structure, including META-INF/container.xml and the packaged resources it points to.
The package document defines the metadata, manifest, spine, and navigation wiring that validators inspect before a reading system can process the book reliably.
Repairability
The rootfile pointer can be repaired when the correct OPF target is clear and the package has a single safe match.
It is unsafe when multiple OPF files exist, when the OPF is missing, or when multiple renditions require an editorial choice.
Before: container.xml points to OEBPS/content.opf, but the EPUB contains OPS/package.opf. After: the rootfile path is aligned only if that is the single valid package file.
Next step
The same error code can come from different files and different causes. Uploading the EPUB lets the report show the affected path and whether the fix is deterministic.
Upload EPUB to scan