PKG-006
Updated:
EPUBCheck PKG-006 is an error message: “Mimetype file entry is missing or is not the first file in the archive.” The mimetype file is missing or is not the first entry of the ZIP archive, so reading apps cannot identify the file as an EPUB from its first bytes.
The official message
Mimetype file entry is missing or is not the first file in the archive.
- 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
Typical causes
- The book folder was compressed with a generic tool that adds files in alphabetical or arbitrary order.
- The mimetype file was deleted while editing the EPUB.
How to fix it
- Make sure a file named mimetype containing exactly application/epub+zip sits at the root of the book.
- Rebuild the archive with the mimetype file first and stored uncompressed, for example from the folder that contains the book:
zip -X0 book.epub mimetypeand thenzip -rX9 book.epub META-INF OEBPS(use your own folder names).
Terms used here
Other PKG messages
PKG-005The mimetype file has an extra field of length …. The use of the extra field feature of the ZIP format is not permitted for the mimetype file.PKG-007The content of the mimetype file must be the string "application/epub+zip"…PKG-004Corrupted EPUB ZIP header.PKG-003Unable to read EPUB file header. This is likely a corrupted EPUB file.PKG-009The file name "…" contains characters that are not allowed in OCF file names: ….PKG-010The file name "…" contains spaces, which may create interoperability issues with older reading systems.
Message text and severity from EPUBCheck 5.4.0 (W3C, BSD-3-Clause). Explanation by EPUBLab.