ManYue test comic: verify an import with six numbered pages

A comic with known contents makes an import problem easier to investigate. Create six numbered pages yourself and use them to compare the archive with what ManYue displays. This is a repeatable reference sample, rather than a performance benchmark or proof that every archive variant works.

Create six unmistakable pages

Use a familiar drawing tool to make six equally sized JPEG or PNG images. Give each a large number and a different background. Label page one as the cover, page four as the middle, and page six as the end. A short side around one thousand pixels keeps this exercise modest. Avoid animation and unusually long images in the first sample. Change only one characteristic in later comparisons.

Check the original folder order

Name all six images with equal-width three-digit numbers. Keep the cover within that sequence. Remove preview thumbnails and editable artwork from the folder being packaged. Open each image in order and compare its visible number with its filename; correct filenames cannot compensate for images containing the wrong page. Store your drawing originals elsewhere.

Create a simple archive

Create an ordinary unencrypted ZIP containing the six images. Inspect its directory and avoid nested archives. Record any helper folders added by the archiving tool, and make a cleaner copy if necessary. Keep the original image folder. Naming a ZIP as CBZ identifies it as a comic archive; changing an extension does not repair content or alter the compression method.

Import this sample on its own

Select only this sample through ManYue’s local import flow. Check its name and size before importing. Find the resulting local entry and compare its cover with page one. If the entry does not appear, confirm that your file provider has downloaded the complete archive to the device. A visible cloud filename can still be a placeholder rather than available file data.

Verify the pictures as well as the count

Read the sample in a single-page layout and inspect every visible number. Check that the middle page appears and that nothing unexpected follows the end. Compare unexpected or missing pages with the archive directory and open the relevant original images. Write down the displayed sequence rather than relying solely on a reported page count, whose treatment of covers or non-page files can differ.

Reopen and check offline

Return to the shelf from page four and reopen the comic to inspect resume behaviour. After import finishes, disconnect the network and check the beginning, middle and end. Keep the files and application intact during this test. If resume differs from what you expected, record the layout and last action, then repeat the same sequence once before drawing a conclusion.

Compare the sample with a problem file

Keep a small result note with the device, app version, archive format and six-page result. When a larger book fails, reopen the unchanged reference on the same device. If it works, investigate the larger file’s contents and packaging. If both fail, inspect shared conditions such as available storage and file access. Preserve the original reference and use copies for experiments.

Questions and completion criteria

Does a successful six-page test prove that a huge comic will work? No; scale and image complexity remain separate factors. Do you need real comic artwork? Numbered pages are easier to diagnose and share. Completion means that all six originals appear in order after import and remain available offline. If you seek help, share this self-made sample and the observed failure without including private books or connection credentials.

Related guides and sources

ManYue file formats: choose CBZ, CBR, CB7 or PDF and check page order; Troubleshoot ManYue imports: file access, formats and folder levels.

Checked on October 26, 2026: ManYue public version 2.0.3, requiring iOS / iPadOS 15.0 or later. Based on the official App Store description and Apple public version lookup. This guide describes a checking workflow; controls and permissions depend on the installed version. It does not claim that every step was tested on a physical device.