Match the report title.
Look for "OPF_019 spine tag was not found" or the closest title above. Keep the original EPUBCheck, KDP, or Kindle Previewer wording if it differs.
EPUB error guide
OPF_019 spine tag was not found
Use this when EPUBCheck reports OPF_019 or says the OPF spine is missing. Check the package reading order before changing nav.xhtml, toc.ncx, or chapter files.
Scan when the message does not name the affected path. The report shows affected paths and repair decisions, not manuscript text.
Fixed-layout, DRM, or source-workflow issue? 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
Use this guide when
Your message matches "OPF_019 spine tag was not found" or one of the report titles above.
Upload if
You have the exported reflowable .epub and need the affected path, file, field, or repair decision before editing.
Handle outside this tool
Use the source tool or publishing workflow for DOCX, PDF, KPF, KCB, fixed-layout, comics, image-first books, DRM, visual design, or KDP listing and approval problems.
Read the scan report
Decide if this report item matches.
Use the report label, affected file, and repair decision together. A matching title alone is not enough if the file path or EPUB structure points to a different problem.
Check the affected file first.
Use the Affected area, Source file, Target file, or Problem type rows before editing OPF, nav, XHTML, CSS, or image paths.
Follow the repair decision.
Repairable means one clear structural change. Needs review or Not supported means use the named file, source project, or platform step.
Keep with your repair note.
Copy these fields from the report instead of rebuilding the fix from memory.
Source file
Target path or field
Original error
Repair decision
Next step
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
Rebuild spine only when nav.xhtml or file order gives one clear reading order.
Do not do this
Do not sort chapter files alphabetically if front matter, appendix, or split chapters make order ambiguous.
Safe repair means restoring a reading order only when the intended sequence is clear from package evidence.
2. Next step
Find whether the reading order can be recovered.
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.
Safe repair
One sequence is clear.
Rebuild the spine only when the package already shows the intended reading order.
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: safe only if navigation order is complete and unambiguous After: add spine itemrefs, 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.
Safe fix
The sequence is already clear.
Add spine itemrefs only when every reading-order file can be confirmed.
Stop
The structure needs author intent.
Do not choose front matter, appendix, or alternate content order automatically.
Start here
Start with the OPF reading order.
The spine tells reading systems which XHTML files are part of the normal book flow. Without it, a book can contain chapters but still fail validation.
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.
Can it be fixed automatically?
It can be repaired when manifest and navigation evidence clearly identify every spine item and 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.
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.
Restore spine only if the order is clear.
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 still show the intended sequence.
Use the nav order only if it covers all reading-order content.
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 EPUB can contain chapter files, but the package does not say which files make up the book's normal reading flow.
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 safe repair needs a clear list of reading-order items. Do not guess chapter order 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.
Can this be fixed safely?
When a missing spine can be repaired safely.
When automatic repair is safe
It can be repaired when manifest and navigation evidence clearly identify every spine item and order.
When you need manual review
It is unsafe when chapter order, front matter, appendix placement, or non-linear content requires author judgment.
Before / after example
Before: content.opf lists chapters but has no spine. After: the spine is restored only when the reading-order sequence is clear.
Ready to retry?
Scan the OPF before rebuilding the spine.
Upload the EPUB that produced OPF_019. The report should show whether there is enough manifest and navigation evidence to rebuild a minimal reading order.
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?
Only when the manifest and navigation files already show one clear sequence. If the reading order is a publishing choice, the report should stop at manual review.
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.
Related EPUB error guides
- OPF_030 unique-identifier was not found
- dcterms:modified missing in EPUB
- More than one title defined in OPF metadata
- OPF_029 manifest media-type mismatch
- PKG_021 corrupted image file encountered
- PKG_022 wrong file extension for image
- OPF_003 or RSC_008 item is not declared in the OPF manifest
- OPF_048 package is missing unique-identifier
- OPF_049 item id was not found in the manifest
- EPUB cover-image property is missing
- PKG_007 mimetype file contents invalid or compressed
- OPF_002 OPF file not found in the EPUB
- RSC_002 container.xml missing in EPUB
- RSC_003 no rootfile tag in container.xml
- PKG_006 mimetype file entry is missing or not first