Match the report title.
Look for "EPUB metadata check" or the closest title above. Keep the original EPUBCheck, KDP, or Kindle Previewer wording if it differs.
EPUB error guide
Use this when content.opf has a metadata or file-list error, including identifiers, modified date, incomplete manifest items, duplicate entries, missing feature properties, or media:duration totals.
You see
Choose this guide when your KDP, Kindle Previewer, or EPUBCheck wording matches "EPUB metadata check" or a close variant.
You get
The report points to the package, OPF, nav, XHTML, resource, anchor, metadata, or ZIP area behind the message.
Do not upload
Use the source tool or publishing workflow for DOCX, PDF, KPF, fixed-layout, DRM, cover design, KDP listing, or review problems.
Scan when the message does not name the affected path. The report shows affected paths and repair decisions, not manuscript text.
Need fixed-layout, DRM, or source-file help? Check unsupported or review-first EPUB cases.
Match these report titles
Use this guide when
Your message matches "EPUB metadata check" 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
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.
A useful report does not stop at the error name. It connects the message to an internal file and a next action.
Look for "EPUB metadata check" or the closest title above. Keep the original EPUBCheck, KDP, or Kindle Previewer wording if it differs.
Use the Affected area, Source file, Target file, or Problem type rows before editing OPF, nav, XHTML, CSS, or image paths.
Repairable means one clear structural change. Needs review or Not supported means use the named file, source project, or platform step.
Copy these fields from the report instead of rebuilding the fix from memory.
1. Example report output
A useful metadata report should name the exact OPF field, not just say metadata is wrong.
OPF file
Usually OEBPS/content.opf or another package document path from container.xml.
Metadata field
unique-identifier, dc:identifier, dcterms:modified, manifest item, or another package field.
Manifest structure
Whether an item is missing id, href, media-type, required feature properties, or appears more than once.
Read-aloud duration
Whether every unique SMIL item has one valid refined duration before the package-level total is calculated.
Validator signal
OPF_030, OPF_048, OPF_049, MED_016, RSC_005 duration, modified date, duplicate manifest item, missing attribute, or media-type message.
Decision
Repair when one required value or link is clear; review manually when several identifiers or source metadata values compete.
The report should tell you which OPF field to inspect before you change title, author, ISBN, or source metadata.
2. Next step
Use the scan report to decide whether an OPF metadata problem is a simple wiring repair or needs the real book metadata.
Identifier
Repair only when one real metadata id is clearly the intended package identifier.
Manifest item
A missing id or media-type, required scripted/svg/mathml/switch property, or proven redundant entry can be repaired only when the existing file provides one exact answer.
Read-aloud duration
Correct the package total only when every unique SMIL manifest item already has exactly one valid refined duration. Missing, duplicate, or malformed per-SMIL values remain manual.
Manual review
Do not choose an identifier just to clear the validator if the real book identity is unclear.
3. Concrete path example
The package unique-identifier must point to a real identifier element.
EPUBCheck: OPF_030: The unique-identifier "bookid" was not found. Report: Package field: unique-identifier="bookid" Metadata ids found: uuid_id, isbn_id Decision: manual review unless one id is clearly the intended book identifier
Do not change visible title or author fields to fix this. The broken link is inside OPF package metadata.
Quick decision
Metadata checks are useful only when they lead to a specific OPF field and a safe next step.
Good fit
A unique-identifier link, modified date, item attribute, required feature property, redundant duplicate, or package duration total can be checked safely when the existing package proves the answer.
Manual fit
The report can name the candidates or missing SMIL duration fields, but a person should supply the real metadata or read-aloud timing.
Not this tool
Title, subtitle, author bio, categories, keywords, pricing, synopsis, and retailer listing metadata belong in the publishing platform or source workflow.
Start here
This is not a metadata editor for polishing title, author, or synopsis. It checks whether content.opf metadata and package fields line up well enough for KDP, Kindle Previewer, and EPUBCheck validation.
EPUB metadata lives in the OPF package document. Validators check whether required fields exist and whether package fields point to real metadata entries.
A checked repair is possible when the existing package proves one exact OPF change, including an identifier link, modified timestamp, item attribute, feature property, redundant duplicate, or package duration total calculated from a complete unique set of valid per-SMIL durations.
Find the OPF file path from the EPUB package or report.
It does not choose competing identifiers, rewrite sales metadata, infer narration timing from audio, invent missing per-SMIL durations, or decide publishing platform listing fields.
Common situations
Start with the OPF field that the validator names.
The package tag names an identifier that does not exist in the metadata block.
Align only when one existing dc:identifier is clearly intended.
The EPUB needs a real language value for the book, not a guessed placeholder.
Add one clear value such as en, en-US, or another real language code when known.
EPUB 3 files can fail when modified metadata is absent, duplicated, or malformed.
Normalize only the package metadata field, then run EPUBCheck again.
The file exists, but content.opf does not give its file-list entry an internal label or confirmed file type.
Add the generated id or detected media type only when the packaged file makes the value unambiguous.
Some entries are byte-for-byte identical; others use different ids or settings and may still be referenced by the book.
Remove only identical copies or a proven unused equivalent entry. Conflicting entries need manual review.
The package read-aloud total can be missing, malformed, or different from the refined durations declared for the SMIL items.
Recalculate only when every real, unique SMIL item has exactly one valid refined duration. Do not infer timing from MP3 files or incomplete metadata.
EPUB metadata checker: OPF metadata, unique-identifier, dcterms:modified, manifest fields, duplicate entries, media:duration, MED_016, and package field errors.
KDP, Kindle Previewer, EPUBCheck, Apple Books, Google Play Books, or another platform reports OPF metadata, identifier, modified date, manifest item, media:duration, duplicate entry, property, or media-type issues.
What it means
EPUB metadata lives in the OPF package document. Validators check whether required fields exist and whether package fields point to real metadata entries.
Common causes include a missing identifier target, draft identifiers, missing or malformed modified metadata, incomplete manifest items, duplicate entries, missing feature properties, wrong media types, stale package fields, or a package duration that does not match complete per-SMIL declarations.
Before you edit
Do not edit visible title or author fields to fix an OPF identifier problem. The validator usually cares about id links, required metadata, and package wiring.
Why KDP checks it
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 checks EPUB 2 and EPUB 3 files against the official rules and reports package, markup, link, and file-reference problems.
KDP supports EPUB files that meet Kindle Publishing Guidelines and recommends checking the file with Kindle Previewer before upload.
Can this be fixed safely?
A checked repair is possible when the existing package proves one exact OPF change, including an identifier link, modified timestamp, item attribute, feature property, redundant duplicate, or package duration total calculated from a complete unique set of valid per-SMIL durations.
It does not choose competing identifiers, rewrite sales metadata, infer narration timing from audio, invent missing per-SMIL durations, or decide publishing platform listing fields.
Before: unique-identifier points to bookid, but no metadata element has id=bookid. After: align it only when one real dc:identifier is clearly intended. Before: several identifiers compete; stop for manual review.
Ready to retry?
Upload the EPUB so the report can inspect content.opf, identifier links, modified metadata, manifest item attributes, duplicate entries, media types, feature properties, media-overlay duration declarations, and package-level wiring.
Upload EPUB to scanFAQ
No. It checks OPF metadata structure and validation blockers. It does not edit sales metadata, categories, keywords, or descriptions.
The OPF package file, often content.opf, contains the metadata block, manifest, spine, and package fields.
Only when one real dc:identifier is clearly the intended package identifier. If several identifiers compete, the report stops for manual review.
Only when the existing item is unique and the packaged file provides one exact id or detected media type. If the file type or intended target is unclear, the report stops for manual review.
Only when the entries are identical, or when one equivalent entry is already used and the others are provably unused. Conflicting duplicate ids, hrefs, properties, or references remain manual.
Only when every real, unique SMIL manifest item already has exactly one valid refined media:duration. The package total can then be calculated from those declarations. Missing, duplicate, or malformed per-SMIL durations need manual review; the tool does not inspect MP3 length to guess timing.
Usually no. OPF validation errors are inside the EPUB package, not the KDP listing form.