支持与 FAQ / Support & FAQ

On the NFM home screen, add a connection, choose SMB or WebDAV, and enter the NAS address, share or directory path, username, and password. SMB accepts forms such as //server/share and smb://server/share; WebDAV uses the URL supplied by the NAS. Local SMB discovery can help fill an address.

If a session has expired, NFM attempts to reconnect when you refresh the folder or repeat the operation. For authentication failures, check the username, password, and NAS permissions.

If you choose to remember it, a local copy of the password is protected by iOS Keychain or Android Keystore rather than ordinary connection data. Editing a connection does not reveal the password in plain text. NFM has no account system and does not send NAS credentials to the publisher.

Yes. HTTP WebDAV can be used on a trusted local network, but it does not encrypt file contents or credentials, and NFM will show a security warning. Prefer HTTPS when the NAS supports it. For access over the public internet, use HTTPS, a VPN, or another trusted encrypted connection. When using a self-signed certificate, verify that the server and certificate are trustworthy.

Where supported, SMB and WebDAV downloads resume from the amount already downloaded. NFM retries brief interruptions automatically; if recovery fails, retry the task from the Transfers page. Whether an upload or copy can resume depends on the NAS, protocol, and stage at which it stopped.

Transfers do not overwrite same-named files by default and use an incremented name. NFM is not a backup service; keep independent backups and verify important files after completion.

Open the global Transfers view to see stages, progress, failure details, and retry counts. Supported tasks can be paused, resumed, canceled, or retried. SMB server-side copies may have indeterminate progress; when the server cannot perform the copy, NFM can fall back to a pausable local streamed copy.

Cache may contain files opened with another app, downloads, thumbnails, previews, video-compression outputs, and system-sharing staging files. In Settings, you can review usage, set a limit, and clear individual categories or all cache. When the automatic limit is reached, NFM removes older cached files first.

Diagnostic data stays on the device and is not uploaded automatically. A recipient receives the file only after you export it and send it through the system share sheet. The export removes NAS addresses, usernames, full paths, file names, credentials, and authentication details; check the file before sending it.

When sharing files into NFM, choose the destination NAS and folder in NFM before adding the files to the upload queue. When sharing out from NFM, files are downloaded to local staging controlled by the cache limit and then handed to the system share sheet. Staging is removed when the task is accepted, canceled, or cleared. After another app receives a file, that app’s privacy policy governs its handling.

When you choose Compress & Upload, the video is compressed locally to H.264 MP4 and then uploaded to the selected NAS folder. The original video is not uploaded as part of that compression task. Temporary files are removed when the task completes, is canceled, or is cleared.

Within the App, you can remove saved connections, favorites, cache, diagnostic records, and transfer records. You can also uninstall the App and clear all local data through the operating system. To delete a file on the NAS, use NFM or the NAS administration interface, and keep an independent backup before irreversible actions.

The publisher does not operate NFM accounts or user file servers, so there is generally no user file or account data to delete remotely. Removing a local record does not delete the original NAS file, and deleting a NAS file does not automatically clear local cache.