ManYue: Set an image-cache limit and check what it covers

A cache limit is easily mistaken for a cap on the whole app or a quota for downloaded comics. ManYue’s current public release notes mention cache limits; the local settings text further distinguishes image and cover caches from local comics and PDF reading caches. Here you adjust one recoverable setting and check its scope with a small sample, without downloading large quantities or filling the device to test a limit.

Define the object of the limit

Open the data area in Settings and locate Image Cache Limit and its explanation. Record the current value, unit and version. The current implementation accepts an integer in megabytes and describes images and covers as its scope; local comics and PDF reading caches are counted separately. Follow the wording actually visible in the installed version. If the entry is absent, do not guess a value in another storage field. Limit here means the management scope of this setting, not a promise that the entire app remains smaller than the number. Write this rule first: total usage exceeding the image-cache limit alone does not demonstrate failure.

Prepare three distinguishable samples

Prepare a six-page imported image comic, a self-made three-page PDF and a short remote image chapter you are authorized to access. Record source, title, format and whether each can be obtained again. If the third sample is unavailable, perform only the local-scope observations; do not invent a remote result. Keep originals outside the app and ensure adequate free device space. Do not use a sole copy, a temporarily authorized paid-content link or a library with important downloads in progress. These conditions let you distinguish changed sample availability from a setting that failed to save if caches rebuild or the network becomes unavailable.

Change one reasonable value and confirm persistence

Save the original limit, then choose a moderate value suited to free device space and the short samples. Changing five hundred megabytes to three hundred is only an example of how to record a change, not a universal recommendation. Enter an integer with the correct unit as the interface requests, submit it and check for an error. Leave the settings area and return to confirm the new value. If saving fails or the old value remains, record a persistence problem before interpreting cache behaviour. Do not enter zero to guess whether it means disabled or unlimited, or test decimals, negatives and extreme values. Keep the original value available for restoration.

Observe image reading without demanding instant equality

While online, open a few pages of the short remote chapter. Record the number opened, the cache reading and the reading time, then check again after leaving the reader. The figure at the instant you submit a limit is not a long-term result, nor must each page add exactly its original-image size. Covers, reused files and cache-management timing affect observations. If images open and the setting persists, record those limited facts rather than claiming a strict cap has been proved. Evaluating a possible anomaly requires stable readings from the same category and reproducible steps; do not compare a total that includes local comics directly with the image limit.

Check scope with the local comic and PDF

Open the local image comic and PDF separately, locating the first, middle and last pages. After leaving each, record the relevant storage changes. An imported comic continuing to exist is not evidence that the cache limit failed. PDF reading caches are separate and need not be squeezed into the same image-limit figure. This checks setting scope; it does not promise that no other operation can ever affect local files. If opening fails, first check original integrity, the entry’s presence and whether you accidentally selected a remote item with the same name. Do not delete a comic to make the figures resemble your expected limit.

Restrict offline conclusions to retained content

For offline use, first complete the required chapter downloads or local imports through the normal workflow, then check the same entries and pages offline. Browsing a few pages online does not mean an entire chapter was saved as a local comic. Image caches may be managed again and should not be the sole guarantee for a travel library. Record that a particular book and page opened offline, including whether it had been downloaded; do not generalize to everything previously browsed. If remote pages fail offline while the local sample works, distinguish sources and retention methods before blaming a damaged cache setting.

Troubleshoot settings and readings separately

If the figures remain puzzling, separate persistence of the limit from growth in a storage category. First leave and re-enter Settings to confirm the value, wait for accounting to finish, then check for imports, downloads or PDF reading. Preserve Unknown readings instead of replacing them with zero. Repeat the same operation only once on a recoverable sample; do not repeatedly clear data, reinstall or redownload a whole library to amplify the change. A useful report includes the limit unit, category labels, sequence, version and sample format. That is more diagnostic than saying cache exceeded its limit and avoids combining different management scopes.

Restore the original value or explicitly retain the new one

Decide whether to restore the original limit or keep the new one, and record the decision. If restoring, re-enter Settings to confirm the original value was saved. If retaining it, name the next review date rather than calling one short trial a permanently optimal configuration. Leave the app and return, confirming that the local comic and PDF still reach the earlier pages; check the remote sample separately under the original network conditions. The outcome is a clearly scoped setting record: content managed by the image limit, content counted separately and offline results still unverified. It is neither a guarantee of total app size nor a promise that cache clearing never requires reloading.

Related guides and sources

ManYue: Read storage categories before deciding what occupies space; Prepare ManYue for offline reading: check the whole comic before leaving.

Checked on November 7, 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 provides reading and checking methods you can perform; it does not claim step-by-step physical-device or private-server testing. Manual records, external tools and actually visible controls are identified separately, and personal analysis or code observations are not presented as verified automatic capabilities.