EPUBCheck
EPUBCheck evaluates EPUB 2 and EPUB 3 publications against official EPUB specifications and reports structure, package, markup, and reference problems.
EPUB error guide
How to understand and scan RSC_007 EPUB errors caused by broken internal references.
RSC_007: Referenced resource could not be found in the EPUB.
EPUBCheck reports RSC_007 during validation, often after an export, rename, or manual edit inside the EPUB package.
Plain English
RSC_007 means the EPUB contains an internal pointer to something that cannot be resolved.
The broken pointer can live in XHTML href or src attributes, CSS url() values, OPF manifest references, nav links, or NCX content sources.
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
Safe repairs include fixing obvious path case differences, URL encoding mismatches, relative path mistakes, or missing manifest declarations.
The repair is not deterministic when several files could match, or when the referenced resource is absent from the EPUB.
Before: a nav entry points to text/chapter-03.xhtml, but the package contains Text/chapter-03.xhtml. After: the nav link uses the packaged path.
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
RSC_007 means an internal EPUB reference points to a file that EPUBCheck cannot resolve. It often appears in links, image sources, CSS URLs, OPF manifest items, nav files, or NCX entries.
Use the path in the EPUBCheck or KDP message as the starting point, then inspect the packaged EPUB files for the closest real match. Case changes, folder moves, and URL encoding differences are common causes.
Sometimes. If the EPUB package already contains the intended file, a targeted path or manifest correction may be enough. If the file is missing, re-exporting or restoring the source file is usually required.
Kindle Previewer can report the same underlying broken reference, but the wording may differ from EPUBCheck. The important detail is the affected path and whether the referenced file exists in the EPUB.