What it means
The EPUB can contain chapter files, but the package does not say which files make up the book's normal reading flow.
EPUB error guide
OPF_019 spine tag was not found
Use this when EPUBCheck reports OPF_019 or explicitly says the OPF spine tag is missing. Check the package reading order before changing nav.xhtml, toc.ncx, or chapter files.
Scan the EPUB to check file paths and see what can be repaired or needs manual review. Your original EPUB stays unchanged.
No signup before the scan report.Your original file is not overwritten.Repair download only after EPUBCheck passes again.
Need fixed-layout, DRM, or source-file help? Check unsupported or review-first EPUB cases.
Match these report titles
- OPF_019 spine tag was not found
- OPF spine tag missing
- EPUB reading order is missing from content.opf
- Package document has no spine
Start here
Start with the OPF reading order.
In an EPUB package, the spine tells reading systems which XHTML files are part of the normal book flow.
Can it be fixed automatically?
The scan can list manifest XHTML, nav.xhtml or NCX entries, and missing spine evidence, but it does not automatically create a new reading order.
What to check next
Open content.opf and check whether a spine element exists.
What not to assume
It is unsafe when chapter order, front matter, appendix placement, or non-linear content requires author judgment.
1. Example report output
What an OPF_019 report should show.
The report should prove whether the reading order is recoverable or needs source-tool review.
EPUBCheck message
ERROR(OPF-019): OEBPS/content.opf: Spine tag was not found.
Affected file
OEBPS/content.opf.
EPUB Fixer report
Manifest has chapter XHTML files, but the OPF package has no spine element.
Do this next
Use the source project or EPUB editor to rebuild the spine after confirming the complete reading order.
Do not do this
Do not sort chapter files alphabetically if front matter, appendix, or split chapters make order ambiguous.
EPUB Fixer does not synthesize a missing spine. The report provides the files and navigation evidence needed for a manual rebuild.
2. Next step
Collect the evidence needed to rebuild the reading order.
The missing spine is a package problem, but the fix can affect how readers move through the book.
Scan first
List XHTML manifest items.
Check which chapter files are in the OPF manifest and whether nav.xhtml points to them.
Manual rebuild
Confirm the complete sequence.
Rebuild the spine in the source project or EPUB editor only after checking every reading-order item, including front matter and appendices.
Manual review
The order affects meaning.
Return to the source project when chapter order, front matter, or appendix placement is unclear.
3. Concrete path example
A typical missing spine package.
The chapters exist, but content.opf does not define the reading order.
EPUBCheck: ERROR(OPF-019): OEBPS/content.opf: Spine tag was not found. Report: Manifest XHTML files: Text/chapter1.xhtml, Text/chapter2.xhtml spine element: missing Navigation order: chapter1.xhtml -> chapter2.xhtml Fix decision: manual — confirm the complete book order Next: add spine itemrefs in the source project or EPUB editor, then validate again
If nav.xhtml is missing or incomplete too, rebuild the reading order in the source tool.
Quick decision
Do not rebuild the spine from file names alone.
The spine is the book's reading order, so a wrong automatic fix can change the reader experience.
Scan first
Compare manifest, nav, and NCX.
Use the package files to see whether the intended reading order is already visible.
Manual rebuild
Confirm the sequence outside the scanner.
Add spine itemrefs in the source project or EPUB editor only after confirming every reading-order file and its position.
Stop
The structure needs author intent.
Do not choose front matter, appendix, or alternate content order automatically.
Common situations
Common OPF_019 cases.
Most missing spine errors happen after OPF editing or a failed converter export.
A manual OPF edit removed the spine.
The manifest and chapters remain, but the reading order section was deleted.
Use version history or the source project to restore the intended order manually.
A converter produced an incomplete OPF.
The export created files but did not finish the package document.
Re-export if navigation and spine are both missing.
Navigation exists but spine is missing.
nav.xhtml may show part of the intended sequence.
Compare it with all manifest XHTML and source content before rebuilding the spine manually.
Multiple reading orders are plausible.
Appendices, samples, or non-linear content make the order unclear.
Review manually before editing content.opf.
The OPF_019 spine error text
OPF_019: Spine tag was not found in the OPF file.
Where missing spine errors appear
EPUBCheck opens the OPF package document but cannot find a spine element that defines reading order.
What it means
The OPF package has no reading-order list.
The spine can be removed by broken exports, manual OPF edits, aggressive cleanup, or damaged package generation.
Before you edit
Check the manifest and spine together.
A manual rebuild needs the complete intended list and order of reading-order items. Do not rebuild the spine from file names alone.
- 1Open content.opf and check whether a spine element exists.
- 2List all XHTML files in the OPF manifest.
- 3Compare nav.xhtml and toc.ncx entries with the manifest items.
- 4Check whether any content is front matter, back matter, appendix, or non-linear.
- 5Stop if the package does not prove the intended reading order.
Why KDP checks it
Why KDP and EPUBCheck require an OPF spine.
EPUB 3.3 package rules
The OPF file is the EPUB's map: metadata, file list, reading order, and navigation wiring. KDP and EPUBCheck use it to decide whether the book package is coherent.
EPUBCheck
EPUBCheck checks EPUB 2 and EPUB 3 files against the official rules and reports package, markup, link, and file-reference problems.
KDP eBook file formats
KDP supports EPUB files that meet Kindle Publishing Guidelines and recommends checking the file with Kindle Previewer before upload.
Repair example
Why a missing OPF spine requires manual repair.
Before / after example
Before: content.opf lists chapters but has no spine. Next: compare source order, manifest XHTML, nav.xhtml, NCX, front matter, and appendices; rebuild the spine manually and run EPUBCheck again.
Ready to retry?
Scan the OPF before rebuilding the spine.
Upload the EPUB that produced OPF_019. The report should list manifest XHTML files and navigation evidence so an author or EPUB editor can rebuild the intended reading order manually.
Upload EPUB to scanFAQ
Questions authors ask about OPF_019.
What does OPF_019 mean?
It means the OPF package file has no spine element, so reading systems cannot see the normal reading order.
Can EPUB Fixer rebuild a missing spine?
No. The scan can list the manifest XHTML files and available navigation evidence, but an author or EPUB editor must confirm the complete reading order and rebuild the spine manually.
Why can chapters exist if the spine is missing?
The files can be packaged in the EPUB, but readers still need the OPF spine to know which files belong in the main flow.
Should I use file names to rebuild the spine?
Not by themselves. File names can be stale or incomplete, especially around front matter, appendices, and split chapters.