EPUBCheck RSC-001: listed file not found
Updated:
EPUBCheck RSC-001 is an error message: “File "…" could not be found.” EPUBCheck looked for a file that the EPUB says exists and did not find it in the archive. The file is usually one the package document or the container lists, so reading apps will fail to load it too.
The official message
File "%1$s" could not be found.
- Default severity
- Error. The EPUB breaks a rule of the specification and is invalid. Stores and Send to Kindle may reject it, and EPUBCheck exits with status 1.
- EPUBCheck version
- 5.4.0
%1$s, %2$s… are filled in with the file, value or element EPUBCheck found.
Typical causes
- A wrong path or a wrong upper/lower case in the name: paths inside an EPUB are case-sensitive.
- A file that was deleted or renamed after it was referenced.
- A file left out when the archive was built, for example by a zip command that skipped a folder.
How to fix it
- Check the path EPUBCheck reports against the files really in the archive, including case.
- Restore the file or correct the reference.
- Rebuild the archive and validate again.
When it's not this
If a link or image reference in the content points to a missing file, EPUBCheck reports RSC-007.
Terms used here
Other RSC messages
RSC-002Required META-INF/container.xml resource could not be found.RSC-003No rootfile tag with media type "application/oebps-package+xml" was found in the container.RSC-004File "…" is encrypted, its content will not be checked.RSC-005Error while parsing file: …RSC-006Remote resource reference is not allowed in this context; resource "…" must be located in the EPUB container.RSC-006bResource "…" is located outside the EPUB Container; please check the resource is retrieved in scripted content.
Sources
Message text and severity from EPUBCheck 5.4.0 (W3C, BSD-3-Clause). Explanation by EpubCC.