EPUB Error: Invalid OPF Package Structure

RSC-005: Error while parsing file content.opf — element "spine" not allowed here. Or: OPF-001: Package document is not valid

What causes this error?

The OPF package document (content.opf) is the central index of your EPUB — it declares the book's metadata, lists every resource in the manifest, and defines the reading order in the spine. The EPUB specification requires these child elements to appear in strict order inside the <package> root: <metadata> first, then <manifest>, then <spine>. Placing them out of order causes a fatal XML parse error. Other common structural problems include manifest items missing required attributes (id, href, or media-type), an incorrect or missing namespace declaration on the <package> element, a missing or wrong version attribute, and deprecated EPUB 2 elements like <guide> used in a file declared as EPUB 3. These errors most often appear after manual editing of the OPF file or when a conversion tool generates non-standard output.

How to fix it

  1. Open content.opf in a text editor and confirm the root <package> element has the correct attributes: version="3.0" (or "2.0"), xmlns="http://www.idpf.org/2007/opf", and a unique-identifier pointing to a <dc:identifier> in the metadata block.
  2. Check that the three required child elements appear in order: <metadata>, then <manifest>, then <spine>. If they are out of order, rearrange them to match this sequence.
  3. Verify every item in the <manifest> has all three required attributes: id (unique within the manifest), href (path to the file), and media-type (the MIME type of the file). A manifest item missing any of these will fail validation.
  4. Confirm <metadata> declares the Dublin Core namespace: xmlns:dc="http://purl.org/dc/elements/1.1/". Without this, EPUBCheck cannot parse the dc:title, dc:creator, and dc:language elements.
  5. Re-validate with EPUBCheck after each fix — OPF structural errors are often chained, and resolving the first one may reveal others further down the file.

Common questions

Why does element order matter in an OPF file?

The OPF schema defines a strict content model — the EPUB specification requires metadata before manifest before spine because each section references the previous one. A spine item references a manifest id; a manifest item references a file; metadata describes the package. Processing them out of order breaks the reference chain, so EPUBCheck rejects any OPF where these sections appear in the wrong sequence.

My OPF file looks correct in a text editor but EPUBCheck still reports a parse error. What else could be wrong?

Common non-obvious causes: an encoding issue where the file is saved as UTF-16 instead of UTF-8, a byte-order mark (BOM) at the start of the file that breaks XML parsing, invisible whitespace or control characters copied from a source document, or an XML declaration that incorrectly specifies the encoding. Open the file in a hex editor or use a strict XML validator to catch issues that appear invisible in a plain text editor.

Check your EPUB before uploading

The free EPUB Validator catches structure, metadata, and navigation errors — no signup, no Java, runs in the browser.

Validate Your EPUB Free →

Building your EPUB correctly from the start prevents most of these errors before they happen. See the EPUB formatting guide for the full workflow: manuscript cleanup, TOC, front matter, EPUB 3.0 generation, and validation.

Common EPUB errors: Missing or invalid container.xml, Missing manifest resource, Missing dc:identifier (unique identifier)

Platform rejection guides: Why Amazon KDP rejects ebooks