calibre Edit Book Check Book Errors: How to Fix It

When calibre Edit book Check book reports errors or warnings after you edit an EPUB or AZW3 file, the problem is usually inside the e-book rather than in your calibre library, device connection, Content server, email account, or metadata download settings. Check book examines the package's HTML, CSS, links, resources, manifest, spine, and other structural details that reading devices depend on.

The safest approach is to preserve a working copy, reproduce the result, and fix one class of diagnostic at a time. Start with malformed HTML and missing resources because they can generate secondary messages. Then address broken links, CSS problems, package errors, and genuinely unused files. Re-run Check book after every small group of changes, preview the affected pages, and stop when the remaining warnings are understood and harmless for your book.

1. Confirm the Symptom With a Small Safe Test

Open the affected book in calibre's Edit book window and choose Tools > Check book. Check book displays a list of detected problems. Select an item to read its explanation, or double-click it to open the relevant file and location when calibre can identify one.

Before changing anything, determine whether the message is reproducible:

1. Save any edits that you intend to keep.
2. Create a checkpoint with Edit > Create checkpoint.
3. Run Tools > Check book.
4. Record the number and types of errors and warnings.
5. Close Check book without using a bulk fix.
6. Run it again and confirm that the same messages appear.

If the same list returns, you have a repeatable book-content problem. If the list changes after files are saved, added, renamed, or deleted, save all open files and run the check again. An old results window can refer to a file or line that has already changed.

1.1 Understand Errors Versus Warnings

An error generally indicates invalid markup, a broken reference, malformed package data, or another condition that can prevent part of the book from being processed correctly. Errors deserve priority because they may affect conversion, navigation, styling, images, or compatibility with stricter reading systems.

A warning identifies a condition that may be intentional but deserves review. An unreferenced image is a common example. It might be leftover production material that should be removed, or it might be a resource that was meant to appear in the book but is no longer linked.

Do not judge a diagnostic only by its label. Read its description and inspect the referenced file. A warning about an image needed by a script, special navigation document, or vendor-specific feature may require more investigation. Conversely, an unused duplicate image left behind after replacing a cover can often be removed safely.

1.2 Define What a Successful Fix Looks Like

A successful fix has four signs:

• The targeted diagnostic disappears when Check book is run again.
• No unexpected new errors appear.
• The affected chapter, image, link, or style works in Preview.
• The saved book opens and navigates correctly in at least one separate reading application or device.

Stop changing settings when those conditions are met. A zero-warning result can be desirable, but it is not worth deleting valid content merely to make the list empty. Every remaining warning should instead have an understood explanation.

2. Check the Book Components Directly Related to the Diagnostic

Check book diagnostics are normally controlled by the contents of the open EPUB or AZW3 file. They are not usually fixed by changing device drivers, metadata sources, email delivery accounts, Content server ports, news-download schedules, or send-to-device templates.

Likewise, changing a book's title, author, tags, or cover in the main metadata window will not repair malformed HTML inside a chapter. Metadata becomes relevant only when the message identifies package metadata, a cover declaration, language information, identifiers, or the OPF structure.

2.1 Fix HTML Validation Errors First

EPUB content documents are built from HTML or XHTML. A missing closing tag, incorrectly nested element, malformed attribute, duplicate identifier, or invalid character can cause one mistake to produce several later diagnostics.

Double-click the first HTML error and inspect the indicated line, plus the lines immediately above it. The true cause is often earlier than the reported location. Look for:

• An opening tag without a matching closing tag.
• Elements closed in the wrong order.
• Quotation marks missing around an attribute value.
• A stray less-than sign or ampersand in ordinary text.
• Two elements using the same id value.
• Markup pasted from a web page or word processor with unsupported fragments.

Correct one clear problem, save the file, and run Check book again. If many downstream errors disappear, continue from the new first error rather than working from the old list.

calibre may offer to correct fixable errors automatically. Automatic repair can be useful for extensively malformed markup, but it can also restructure HTML in ways you did not expect. Create or verify a checkpoint first, fix one category at a time, and compare the result before accepting broad changes.

2.2 Resolve CSS Errors and Compatibility Warnings

Check book examines external stylesheets, <style> sections, and inline style attributes. CSS messages can involve malformed declarations, unknown properties, invalid values, missing punctuation, or compatibility concerns.

Double-click the message to open the applicable stylesheet or HTML file. Check the surrounding rule for a missing colon, semicolon, brace, quotation mark, or unit. For example, an error reported against one property may actually be caused by an unclosed declaration directly before it.

Not every unknown CSS property means the book will fail. Some reading systems support newer or vendor-specific properties that a validator may not recognize. Before deleting such a property, determine what it does and whether the book relies on it. If removing the declaration changes the layout or typography, restore the checkpoint and investigate a compatible fallback instead.

Success means the CSS error disappears without changing the intended appearance of representative pages. Check ordinary paragraphs, headings, indented text, images, lists, footnotes, and any page that uses the edited class.

2.3 Repair Missing Resources and Broken Links

A missing-resource message means a file refers to something that is not available at the expected internal path. The missing item may be an image, stylesheet, font, chapter, navigation target, or other packaged resource.

Common causes include renaming or deleting a file without updating every reference, importing HTML without its associated assets, typing the wrong relative path, or changing capitalization. Capitalization deserves special attention because a path that appears to work on one system may fail in a case-sensitive environment or on a reading device.

Use this sequence:

1. Open the referring file from the Check book result.
2. Identify the path in href, src, url(), or another reference.
3. Look for the intended target in the editor's File browser.
4. If the target exists under another name, update the reference or carefully rename the file.
5. If the resource is genuinely missing, import a legitimate replacement or remove the reference if the content is no longer needed.
6. Re-run Check book and inspect the affected page.

Do not solve a missing-image error by inserting an unrelated blank image merely to silence the diagnostic. Restore the intended image when available, or remove the image element and revise the surrounding content if the image is not required.

2.4 Review Unlinked or Unreferenced Files

An unreferenced file exists inside the e-book but is not connected to readable content in the expected way. Typical examples include an old cover, a duplicate illustration, an obsolete stylesheet, or a chapter file that is missing from the reading order.

Do not automatically delete every unreferenced file. First ask whether the file should be visible or used:

• If it is an intended chapter, add it to the book's reading order and navigation as appropriate.
• If it is an intended image, restore the reference from the correct HTML file.
• If it is a stylesheet, confirm whether any document should link to it.
• If it is a replaced cover or abandoned production asset, removal may be appropriate.
• If its role is unclear, export a copy before deleting it.

After removing a genuinely unused file, run Check book again. Success means the warning is gone and no new broken references appear. Browse the table of contents and nearby pages to verify that content was not removed accidentally.

2.5 Handle OPF, Manifest, Spine, and Cover Messages Carefully

The package document, often called the OPF, describes the resources in the book and the order in which reading content appears. Diagnostics involving duplicate manifest entries, broken identifiers, missing required sections, invalid spine references, or cover declarations can affect whether a reader can locate and display content.

Prefer calibre's purpose-built tools when one matches the problem. For example, use the editor's cover and table-of-contents tools instead of manually constructing package entries unless you understand EPUB packaging. If a file was imported or deleted through Edit book, save the book and re-run the check before manually editing package data.

For a spine-related warning, confirm that every intended chapter appears in the reading order and that utility files are not displayed as chapters. For a cover-related warning, verify that the intended image and cover page are correctly recognized and that the book does not contain conflicting old cover resources.

3. Check Source File Quality and External Interference

Operating system permissions, USB mode, firewalls, antivirus tools, and network settings are rarely the direct cause of HTML or CSS diagnostics. They become relevant when calibre cannot open, save, replace, or persist the edited book.

3.1 Work on a Local Copy

If the book is stored in a cloud-synchronized folder, network share, removable drive, or device-mounted folder, export a copy to a normal local folder before testing. Cloud software may synchronize a partially saved file, create conflict copies, or replace a newer file with another version.

A connected reader should not be treated as the editing workspace. Copy the book into calibre or save a local test copy, edit it, validate it, and only then transfer the finished file to the device.

On Windows, macOS, and Linux, confirm that your account can write to the destination folder. If saving fails, try a folder inside your normal user documents area. Do not make the entire calibre library globally writable as a first response.

3.2 Consider the Quality of the Original Book

If Check book reports many errors before you make any edits, the source file may already contain malformed markup, conversion leftovers, missing assets, or nonstandard production code. Create a checkpoint immediately and avoid global replacements until you understand the dominant error class.

A practical order for a heavily damaged book is:

1. Fix malformed HTML.
2. Re-run Check book.
3. Fix broken internal links and missing resources.
4. Re-run Check book.
5. Fix package and reading-order problems.
6. Review CSS errors and compatibility warnings.
7. Inspect unreferenced files last.

This order prevents you from deleting a resource that only appears unused because malformed markup stopped calibre from recognizing its reference.

3.3 Account for Reader Limitations

The editor's Preview is useful, but it is not a substitute for testing on the intended reader. A tolerant preview engine may display imperfect markup that a dedicated e-reader rejects. It may also support CSS that a particular device ignores.

After Check book is clear of relevant errors, open the saved file in another reading application or on the target device. Test the table of contents, chapter transitions, internal links, images, font behavior, and several pages that use important styles. Stop editing when the diagnostics are resolved and the real reading result is correct.

4. Use Diagnostics Without Chasing Unrelated calibre Problems

Check book already provides the most useful diagnostic information for this symptom: the message category, affected file, location, and explanation. Main-window job details, device-detection logs, server logs, and conversion debug output usually do not explain an HTML error found inside Edit book.

4.1 When Additional Logs Are Useful

Use broader calibre troubleshooting only if the failure extends beyond the book diagnostic. Examples include Edit book crashing, the saved file not changing, a plugin altering files unexpectedly, or the editor failing to open any supported book.

If the problem began after enabling an editor-related plugin, restart calibre with that plugin disabled and repeat the same test on a copy. A plugin is less likely to be responsible when Check book consistently identifies a specific malformed tag or missing image inside one book.

Command-line tools such as calibre-debug can help capture application failures, but they are not a substitute for correcting the file and line identified by Check book. Use command-line diagnosis when the editor itself crashes, hangs, or produces an application-level traceback.

4.2 Compare Against a Checkpoint

Open View > Checkpoints and compare the current book with the checkpoint created before your fixes. Review changes to HTML, CSS, links, and deleted resources. If an automated operation reformatted many files, comparison helps distinguish harmless formatting changes from removed content or altered structure.

If a fix creates worse results, revert to the checkpoint instead of attempting to reverse dozens of changes manually. Then make a smaller correction aimed at the first error class.

5. Run a Clean Temporary Test Before Reinstalling

Reinstalling calibre rarely repairs errors embedded in a particular EPUB or AZW3 file. Before reinstalling, deleting a library, resetting all preferences, or changing many settings, perform a controlled test on a disposable copy.

1. Use Save a copy or export the affected format to a temporary local folder.
2. Keep the original library book unchanged.
3. Open the temporary copy in Edit book.
4. Create a checkpoint.
5. Run Check book and note the first error category.
6. Fix only one or two related items.
7. Run Check book again and preview the affected content.
8. Save, close, reopen, and check the temporary copy once more.

If the fix remains after reopening, the editor is saving correctly and the solution is inside the book. Apply the same carefully verified correction to your working copy or replace it with the repaired test copy after reviewing the differences.

If every unrelated EPUB or AZW3 produces the same application failure, test with nonessential plugins disabled or a temporary clean configuration. A clean profile is appropriate for interface failures, crashes, or settings corruption, but it should not be expected to erase legitimate validation errors in the book.

6. Quick Fix Checklist

• Save current edits and create a checkpoint before any automatic fix.
• Run Tools > Check book twice to confirm a stable result.
• Read the full explanation for the first diagnostic.
• Fix malformed HTML before dealing with secondary warnings.
• Check CSS punctuation and surrounding declarations, not just the highlighted property.
• Match every broken path to the actual filename and capitalization.
• Restore missing resources or remove references only when the content is unnecessary.
• Inspect unreferenced files before deleting them.
• Use calibre's cover and table-of-contents tools for related package problems.
• Fix one class of error at a time and re-run Check book.
• Compare automated changes with the previous checkpoint.
• Preview affected pages and test the saved book outside the editor.
• Stop changing settings once the targeted message is gone and the book works correctly.

7. Frequently Asked Questions

7.1 Do All Check Book Warnings Need to Be Fixed?

No. Every warning should be reviewed, but not every warning requires a change. A warning can describe intentional or specialized content. Keep it only after you understand why it appears and confirm that the book works on the intended reading system.

7.2 Is It Safe to Use Correct All Fixable Errors Automatically?

It can be useful, particularly for malformed HTML, but it may reorganize markup or create an unexpected visual result. Create a checkpoint first, run the operation on a copy when the book is important, and compare the result before saving over your working version.

7.3 Why Does an Error Return After I Fix It?

The same error can return when the wrong occurrence was edited, the file was not saved, another file contains the same defect, or an earlier markup problem causes the parser to report the later location again. Save all files, re-run Check book, and start with the first remaining error.

7.4 Should I Delete Every Unlinked File?

No. Determine whether the file is obsolete or whether its reference was accidentally removed. A forgotten chapter or illustration should be reconnected, while an old duplicate cover or abandoned stylesheet may be safely removed after inspection and backup.

7.5 Can Reinstalling calibre Fix Check Book Errors?

Usually not. Check book errors normally describe the contents of the open e-book. Reinstallation is worth considering only when the editor itself will not launch, repeatedly crashes across multiple known-good books, or shows broader application failures that persist in a clean test.

7.6 When Is the Book Finished?

The book is ready when significant errors are gone, remaining warnings are understood, affected pages display correctly, navigation works, and the saved file passes a fresh check after being closed and reopened. Test it in another reader or on the intended device before distributing or replacing your original copy.