EPUBCheck
EPUBCheck evaluates EPUB 2 and EPUB 3 publications against official EPUB specifications and reports structure, package, markup, and reference problems.
EPUB error guide
Plain-English guide to the RSC_007 missing resource error in EPUBCheck and KDP uploads.
RSC_007: Referenced resource could not be found in the EPUB.
The EPUB opens in a reader, but KDP or EPUBCheck rejects it because one internal file points to another file that is not present at that path.
Plain English
A chapter, stylesheet, nav file, NCX file, OPF file, or image reference is looking for a file name that the EPUB package cannot actually find.
The target may be missing, declared with different letter case, URL-encoded differently, moved to another folder, or omitted from the OPF manifest.
User checklist
These checks keep the repair decision tied to the EPUB package instead of guessing from a generic error code.
Standards context
EPUBCheck evaluates EPUB 2 and EPUB 3 publications against official EPUB specifications and reports structure, package, markup, and reference problems.
The package document defines the metadata, manifest, spine, and navigation wiring that validators inspect before a reading system can process the book reliably.
Repairability
EPUB Fixer can repair this only when the missing target has one clear match in the package, such as a case mismatch or a manifest item that exists but is not declared.
If the image, CSS, or XHTML file is truly missing, the tool should not invent replacement content or guess which file the author meant.
Before: OEBPS/chapter1.xhtml links to images/Cover.jpg but the package contains images/cover.jpg. After: the reference is aligned with the real packaged 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 scanFAQ
Start by locating the exact file path in the validator message, then compare it with the real files inside the EPUB package. The fix is usually safe only when there is one clear path, case, or manifest mismatch.
Many reading apps tolerate broken internal references. KDP and EPUBCheck are stricter because missing images, stylesheets, nav files, or XHTML targets can break the published Kindle file.
No. RSC_007 can come from images, CSS files, chapter XHTML files, OPF manifest entries, nav links, or NCX references. The missing target depends on which internal pointer fails.
It can classify the issue as repairable when the EPUB contains one obvious matching file or manifest entry. If the resource is truly absent, the report stops at diagnosis instead of inventing replacement content.