Upload scan
Use this when container.xml is missing at the root.
The scan can check whether the file is absent, nested inside a parent folder, or present with a bad rootfile path.
EPUB error guide
container.xml missing in EPUB
Why META-INF/container.xml matters, how it points to the OPF package, and when a missing EPUB container file can be rebuilt safely.
1. Example report output
What the container.xml report should show.
The report should prove whether the map is missing and whether there is one clear OPF package file to point to.
Expected file
META-INF/container.xml
Found OPF
OEBPS/content.opf
OPF count
1
Decision
Safe to rebuild only when this is the single valid OPF file.
If the archive contains no OPF file, several OPF files, or an extra parent folder, do not rebuild the container before reviewing the package layout.
2. Next step
Find the package map before rebuilding it.
container.xml is the map to the OPF package. Rebuilding the map is safe only after the OPF target is clear.
Manual check
Use this when the EPUB looks nested.
If META-INF and OEBPS are inside an extra folder, the fix may be repackaging from the correct folder level.
Formatter handoff
Use this when there are multiple package files.
Multiple OPF files can mean old exports, multiple renditions, or a damaged package. The intended package file needs a human decision.
3. Concrete path example
A minimal container.xml repair points to one OPF path.
The target path must match the packaged OPF file exactly.
Missing: META-INF/container.xml Found: OEBPS/content.opf Rebuild: META-INF/container.xml -> OEBPS/content.opf
Do not copy container.xml from another book. The rootfile path has to describe this EPUB package.
Quick decision
Rebuild container.xml only when the OPF target is obvious.
The container file is just a map. If the map is missing but the package has one clear OPF file, it can be rebuilt. If the package has several possible OPF files, the map becomes a publishing decision.
Scan first
You cannot see META-INF/container.xml at the EPUB root.
Scan the archive layout to find whether the container is missing, nested under a parent folder, or present but pointing to the wrong path.
Safe fix
Exactly one valid OPF file exists.
A minimal container.xml can point to that OPF path when the rest of the EPUB structure is intact.
Stop
There are multiple OPF files or no OPF file.
Do not choose a package file automatically. Multiple renditions, old exports, or damage need manual review.
Start here
First confirm whether the EPUB has a real root package map.
A missing container.xml is a packaging problem near the top of the EPUB. Before rebuilding it, make sure the book still has one clear OPF package file for the container to point to.
What it means
Every EPUB needs META-INF/container.xml. It is the small map that tells EPUB readers where to find the OPF package file, such as OEBPS/content.opf or OPS/package.opf.
Can it be fixed automatically?
EPUB Fixer can rebuild a minimal container.xml when there is exactly one clear OPF file in the package and the rest of the EPUB structure is intact.
What to check next
Open the EPUB package and check whether META-INF/container.xml exists at exactly that path.
What not to assume
Automatic repair is unsafe when there are multiple OPF files, multiple renditions, severe ZIP damage, encryption, or no valid package file. It is also unsafe when the folder structure suggests the whole EPUB was nested incorrectly and needs a full repackaging review.
Common situations
Check which container.xml problem you actually have.
A missing container file, a nested container file, and a wrong rootfile path look similar at upload time but need different fixes.
META-INF/container.xml is completely absent.
The archive has no root map, so validators cannot locate the OPF package.
Search for OPF files and rebuild the container only if there is one clear package file.
container.xml is inside an extra parent folder.
The EPUB may contain BookFolder/META-INF/container.xml instead of META-INF/container.xml at the root.
Repackage the EPUB from the contents of the book folder, not from the folder itself.
The container exists but points to a missing OPF.
This is closer to an OPF file not found problem than a missing container problem.
Align the rootfile path only when there is one valid OPF target.
Several OPF files are present.
The file may include multiple renditions, an old package copy, or a damaged export.
Stop for manual review instead of guessing which OPF describes the published book.
The missing container.xml error text
RSC_002: Required META-INF/container.xml resource could not be found.
Where a missing container file shows up
EPUBCheck, Kindle Previewer, or KDP can read the archive but cannot find META-INF/container.xml, so they do not know where the OPF package file is.
What it means
container.xml is often missing because the EPUB was zipped from the wrong level.
Every EPUB needs META-INF/container.xml. It is the small map that tells EPUB readers where to find the OPF package file, such as OEBPS/content.opf or OPS/package.opf.
The file may be missing, placed in the wrong folder, deleted during manual cleanup, or trapped inside an extra parent folder because the EPUB was zipped from the wrong directory level.
Before you edit
Check META-INF/container.xml and the OPF path it should expose.
The safe question is simple: is there exactly one valid package file inside the EPUB, and should it be the rootfile? If not, rebuilding the container could point readers to the wrong book package.
- 1Open the EPUB package and check whether META-INF/container.xml exists at exactly that path.
- 2If container.xml exists, open it and copy the rootfile full-path value.
- 3Check whether that rootfile path points to a real .opf file inside the EPUB.
- 4If container.xml is missing, search the package for .opf files and confirm there is exactly one valid package file.
- 5If the EPUB contains a top-level folder that then contains META-INF and OEBPS, the archive may have been zipped from the parent folder.
- 6Do not rebuild the container automatically when there are multiple OPF files, multiple renditions, encryption, or severe ZIP damage.
Why KDP checks it
Why EPUB readers need META-INF/container.xml.
EPUB ZIP container
The EPUB ZIP wrapper must point readers to the OPF file through META-INF/container.xml and keep packaged resources at the paths the book references.
EPUBCheck
EPUBCheck checks EPUB 2 and EPUB 3 files against the official rules and reports package, markup, link, and file-reference problems.
Can this be fixed safely?
When rebuilding container.xml is safe.
When automatic repair is safe
EPUB Fixer can rebuild a minimal container.xml when there is exactly one clear OPF file in the package and the rest of the EPUB structure is intact.
When you need manual review
Automatic repair is unsafe when there are multiple OPF files, multiple renditions, severe ZIP damage, encryption, or no valid package file. It is also unsafe when the folder structure suggests the whole EPUB was nested incorrectly and needs a full repackaging review.
Before / after example
Before: META-INF/container.xml is absent while OEBPS/content.opf is the only valid package file. After: META-INF/container.xml points to OEBPS/content.opf. Before: both OPS/package.opf and OEBPS/content.opf exist; the tool should stop instead of choosing one.
Ready to retry?
Scan the package before creating a new container.xml.
A scan can distinguish a missing map file from a deeper package problem, such as no OPF file, multiple OPF files, or a book zipped with an extra parent folder.
Upload EPUB to scanFAQ
Questions authors ask about container.xml.
What does container.xml missing in EPUB mean?
It means validators cannot find META-INF/container.xml, the file that points reading systems to the OPF package file inside the EPUB.
Can a missing EPUB container.xml be rebuilt automatically?
Only when the EPUB contains exactly one clear OPF package file. If there are multiple OPF files, missing package files, encryption, or severe ZIP damage, the report should stop for manual review.
Where should container.xml be located?
It should be at META-INF/container.xml inside the EPUB package. If it is inside another nested folder, the EPUB was probably zipped from the wrong directory level.
What should container.xml point to?
It should point to the OPF package file that describes the book, commonly OEBPS/content.opf or OPS/package.opf. The path must match the real file path exactly.
Can I copy container.xml from another EPUB?
Not safely. The file must point to this EPUB's real OPF path. Copying a container file from another book can create a valid-looking package that points to the wrong location.
Does a missing container.xml mean the manuscript content is gone?
Not always. The chapters and images may still be in the archive, but validators cannot find the package map. The next check is whether a single valid OPF file still exists.