EPUB error guide
How to understand the OPF_049 item id was not found in the manifest error when EPUB spine, guide, navigation, or package references point to a missing manifest id.
Direct answer
Use this summary before the detailed guide. Most KDP, Kindle Previewer, and EPUBCheck messages still need the exact affected path, package field, identifier, or validator message before you edit anything.
The OPF package is pointing to an internal manifest id that does not exist. Unlike a missing file path error, this problem is about the relationship between OPF elements: one part of the package names an item id, but the manifest never defines that item.
EPUB Fixer can repair this when the intended manifest item is clear, such as a spine itemref that points to an old id while the same XHTML file is still declared under a new id. A safe fix updates the reference to the existing manifest id or restores the missing manifest item when the file and media type are unambiguous.
Find the OPF line named by the error, such as a spine itemref, guide reference, fallback, media-overlay, toc value, or another package-level reference.
The tool should not guess the reading order, navigation target, fallback chain, or media overlay target when several manifest items could match. If the missing id affects spine order, fixed-layout pages, multiple renditions, or editorial navigation choices, manual review is required.
OPF_049: Item id was not found in the manifest.
EPUBCheck, Kindle Previewer, or KDP finds an OPF reference that names a manifest id, but the OPF manifest has no item with that id. This can affect spine itemrefs, EPUB 2 NCX wiring, guide references, media overlays, fallbacks, or other package-level links.
Plain English
The OPF package is pointing to an internal manifest id that does not exist. Unlike a missing file path error, this problem is about the relationship between OPF elements: one part of the package names an item id, but the manifest never defines that item.
This often happens after renaming manifest ids, deleting a chapter item, changing nav or NCX entries, merging EPUB files, or editing the OPF by hand. The file may still exist in the ZIP, but the package-level id wiring is broken.
User checklist
Work through the reported path or message, the real EPUB contents, and the safe-repair decision in order. Stop when the next step would require guessing what the author meant.
Validator context
The OPF package file defines the book metadata, file inventory, reading order, 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
EPUB Fixer can repair this when the intended manifest item is clear, such as a spine itemref that points to an old id while the same XHTML file is still declared under a new id. A safe fix updates the reference to the existing manifest id or restores the missing manifest item when the file and media type are unambiguous.
The tool should not guess the reading order, navigation target, fallback chain, or media overlay target when several manifest items could match. If the missing id affects spine order, fixed-layout pages, multiple renditions, or editorial navigation choices, manual review is required.
Before: the spine contains <itemref idref="chapter3"/> but the manifest only has <item id="chap-3" href="chapter3.xhtml" media-type="application/xhtml+xml"/>. After: the spine idref is updated only if chap-3 is the clear intended item. Before: an idref points to a deleted chapter with no matching file; that should stop for manual review.
Next step
The same validator message can come from different files and different causes. Uploading the EPUB lets the report show the affected path or package field and whether the fix is safe to make automatically.
Upload EPUB to scanFAQ
It means an OPF reference names a manifest item id that does not exist. The EPUB package may still contain the file, but the manifest id wiring is inconsistent.
It often comes from spine itemrefs, NCX toc references, fallback chains, guide references, media overlay links, or manual OPF edits where an id was renamed or deleted.
OPF_002 usually means the package file path itself cannot be found. OPF_049 means the OPF package exists, but an internal id reference points to a manifest item that is missing.
Only when there is one clear intended manifest item. If the missing id affects reading order, navigation, fallback behavior, or media overlays, the report should stop for manual review.
Yes. If spine, nav, NCX, or guide references point to ids that do not exist in the manifest, Kindle conversion can fail or produce a book with missing chapters or broken navigation.
