Serial continuity and file checks
ManYue archive companion-file audit: distinguish pages, notes and system helpers
Inventory a comic archive and inspect thumbnails, notes and hidden helper directories separately, preserving metadata and originals while testing a minimal derivative.
On this page
An archive can contain page images, notes, thumbnails and system helper folders. These are neither all reading pages nor all disposable. Audit an existing personal archive to identify the item behind unexpected display or organisation. Produce an evidence inventory and minimal derivative rather than another beginner six-page sample or a guarantee that every non-page file is ignored.
Inspect the archive without altering the original
Make a working copy and inspect the full directory with a trusted archive tool, noting pages, subfolders, notes and metadata. Resolve any password or multipart requirement through an established extraction flow first. Preserve the original and use private filename/purpose notes. Do not delete unfamiliar items before inspection: apparently minor files can carry creator or chapter information, and removing them first destroys the comparison baseline.
Classify items by evidence
Classify a page by actual readability and story correspondence, a thumbnail by comparison with its larger counterpart, and notes by reading them. Keep unknowns. Names such as cover, thumb or note are clues, not proof, and extensions do not determine disposability. Distinguish metadata from optional system helpers and author appendices. Verify a few representatives before applying a classification across thousands of images.
Compare displayed pages with archive contents
Inspect beginning, middle, end and unexpected displayed images, mapping each to the source directory. For an absent image check cover treatment, structure and readability before calling it deleted. Archive-entry count is not page count. A current implementation may treat certain hidden helpers specially, but code observation does not replace results for this file or explain every nested structure.
Isolate one confirmed unrelated item
Move one confirmed thumbnail or companion note outside the working archive scope while retaining it. Repackage a labelled comparison with everything else fixed and inspect the result. Do not combine isolation with renaming, chapter merging or metadata removal. If unchanged, reconsider the hypothesis rather than deleting more. A cleaner-looking directory is not itself evidence of a repaired reading result.
Preserve metadata and appendices deliberately
Keep possible title, creator or chapter metadata with an unconfirmed-purpose label. Afterwords, instructions and publication pages can belong to the work even without advancing the plot. If making a body-only derivative, document omissions and retain the complete archive rather than calling it an unchanged original. Do not promise import of every metadata tag or recommend internal database edits to preserve unknown fields.
Avoid confusing hidden helpers with page content
After revealing hidden items, inspect full paths and contents instead of recursively deleting a similarly named directory. Prefer reversible isolation and check whether repackaging tools regenerate helpers. Use supported tool options or document the behaviour; there is no assumed universal cleanup switch. Keep server originals unchanged while auditing your working copy so a stable reference remains available.
Recheck order and documented completeness
Inspect cover, chapter boundaries, middle and end after the derivative works. Compare retained and omitted inventory items rather than celebrating a lower page count. Map any new entry’s position by chapter and scene while keeping old records. State the specific cause and derivative scope. Unchecked files remain unknown; one successful isolation does not justify collection-wide deletion of similarly named folders or all text files.
Acceptance and rollback decisions
Finish with a source item explaining the anomaly, a controlled change, recoverable original/companions and checked content scope. Fewer pages may mean a lost appendix, and a code-level ignore rule does not certify every version/structure. Keep inventory, operation and results, rebuilding evidence for another archive instead of applying a universal deletion list. Reliable organisation requires understanding items, not treating unfamiliar files as useless.
Related guides and sources
Import image folders into ManYue: one book or separate chapters; Troubleshoot ManYue imports: file access, formats and folder levels.
Checked on November 3, 2026: Apple public version information lists ManYue 2.0.4, requiring iOS / iPadOS 15.0 or later. Feature scope follows the official App Store description and the installed version. This article describes actions and content checks you can perform; it does not claim step-by-step physical-device or private-server testing. Manual records, external tools and application controls are identified separately, and code observations or personal inferences are not presented as verified automatic capabilities.