System file server and local import
Copy a comic from a system file server into ManYue: import one book and check offline reading
Connect to an authorized share in Files, copy one comic to the device, then import it and check pages after disconnection.
On this page
Connect to an authorized share in Files, copy one comic to the device, then import it and check pages after disconnection.
Choose one comic on an existing server
Prepare a file server or NAS you are authorized to use, an iPhone or iPad with ManYue, and one small owned or authorized CBZ on the server. Record server name, shared folder, filename, size and recognizable first and last pages, retaining an independent original. This uses system Files to connect, copy one file and then import it locally. It is not the built-in ManYue SMB library and does not automatically synchronize the folder. Connectivity depends on network, server and current system.
Verify address and account access
Obtain the local network address, share name and your authorized account from the server administrator, and put the device on a network that can reach the server. An administration webpage URL is not necessarily a file-share address; opening the webpage does not prove the account can read the comic share. Do not publish passwords or full private addresses, enable guest sharing merely for practice, or expose file-sharing ports publicly. If you have only a web link or cannot confirm the address, mark it pending and ask the administrator.
Connect in system Files
In Files on iPhone, tap Browse and use the currently visible More action to choose Connect to Server, then enter the administrator-provided address; on iPad use the corresponding sidebar entry. Choose Registered User as authorized, or Guest only if the server really permits it. Apple documents selecting a volume or shared folder after connection; labels vary by OS. If connection fails, record the actual message and check address, network and account before repeatedly deleting app data.
Locate and identify the sample on the share
In the shared location actually shown, navigate to the target folder and verify volume, folder, filename and size. Multiple servers or shares may contain namesakes; compare directory, edition and existing notes. A visible file icon does not mean it has been copied locally. If the share lists but the file cannot be opened, record login success, directory visibility and file-access failure separately, then ask the administrator to check that account’s permission for this file. Do not move, rename or delete the server original to test access.
Copy into a clear on-device location
In Files, use the current system’s Copy and Paste or another operation that explicitly creates a copy, placing the file in an accessible On My iPhone/iPad folder. Start with an empty folder to avoid overwriting a namesake. Moving is not copying and does not preserve the source. Wait for completion, confirm the original remains on the share, and compare the new copy’s name and size. If no local folder is available in the current system or destination, mark copying unperformed and choose another trusted transfer method; do not assume every device has the same directory. Do not assume an iCloud Drive folder remains permanently on the device; if only a cloud location is usable, confirm the file has downloaded and verify offline behavior separately. If a conflict prompt appears, cancel and choose an empty folder rather than replacing existing material. Record the copy time to distinguish a pre-update copy from the server’s later original.
Import the local copy into ManYue
Open the local comic import entry actually visible in ManYue, browse in the system picker to the recorded device location, select the CBZ and wait as prompted. Do not accidentally choose the same-named item on the share and call it the local copy; if the picker path is unclear, verify in Files first. When processing finishes, locate the work on the shelf and compare name and first, middle and last pages against the server sample and recorded visual anchors. A cover, closed picker or completed copy alone does not prove a complete import.
Check reading after disconnecting the share
After copy and import finish, you may disconnect the server from the shared location in Files as Apple describes. If practical temporarily disconnect the network as well, reopen the checked first and last pages in ManYue, then restore the network. Record readability and tested pages; a sample does not prove all pages are complete or that later server changes will reach the copy. If it fails after disconnection, reconnect and check whether the remote namesake was selected, copying finished and the shelf points to the intended work. Do not delete the server original. Mark untested if this cannot be checked.
Keep system connection and app outcomes separate
Keep a redacted record of device and app versions, network, server and share visibility in Files, copy destination, import state and actual pages. A working system connection does not configure ManYue’s built-in SMB; conversely a built-in connection does not prove Files uses the same account and path. Restore network and share state as needed and confirm server original and local copy remain. For ongoing remote library browsing, see the built-in SMB guide and check current entitlement. This one-file copy is neither two-way synchronization nor a whole-library backup.
Related guides and sources
ManYue’s built-in SMB library; Local comic basics.
Checked 20 November 2026: Apple lookup lists ManYue 2.0.6 and iOS / iPadOS 15.0 or later; local import and built-in SMB entitlement are in the App Store. System file-server steps follow Apple’s file-transfer guide. No device, private-server or offline test is claimed.