EPUB 3.3 package document
The package document defines the metadata, manifest, spine, and navigation wiring that validators inspect before a reading system can process the book reliably.
EPUB error guide
How OPF_030 unique-identifier errors happen and how EPUB Fixer checks OPF metadata safely.
OPF_030: The unique-identifier was not found.
EPUBCheck rejects the OPF package because the package unique-identifier points to an ID that is not declared in metadata.
Plain English
The OPF says 'this is the book identifier', but the identifier it names does not exist.
The package tag may reference unique-identifier="BookId" while the metadata contains a dc:identifier with a different id, or no id at all.
User checklist
These checks keep the repair decision tied to the EPUB package instead of guessing from a generic error code.
Standards context
The package document defines the metadata, manifest, spine, and navigation wiring that validators inspect before a reading system can process the book reliably.
EPUBCheck evaluates EPUB 2 and EPUB 3 publications against official EPUB specifications and reports structure, package, markup, and reference problems.
Repairability
This is often repairable by aligning the package unique-identifier with an existing dc:identifier, or by adding a deterministic identifier when the metadata is otherwise clear.
The tool should not choose between conflicting ISBN, UUID, or channel identifiers when the intended publishing identifier is unclear.
Before: package unique-identifier="uid" but no dc:identifier id="uid" exists. After: the package and dc:identifier point to the same metadata entry.
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