# iCouldPlay folder scans: turn a file source into a browsable library
Language: en
Canonical: [iCouldPlay folder scans: turn a file source into a browsable library]()
中文：[中文 HTML]()
English: [English HTML]()
Published: 2026-10-23T00:00:00+08:00
Modified: 2026-10-23T10:34:08+08:00
Author: Bison
Begin with one clear source folder, choose the scan scope and verify items and categories, then handle missed files, matching names and rescan limits.
English translation of the [Chinese original](), translated on 2026-10-23. The article body uses automated translation; app descriptions, historical reading notes and video subtitles receive separate editorial checks. Original publication dates, attribution, code and version notes are retained.
After connecting a file source, its videos still need media-library records for browsing by cards, titles, and categories. Scanning reads file information and creates records; it does not copy every video to the phone or guarantee a correct poster match for every file. Use a small folder to establish a verifiable scan process before expanding.
## Confirm that you are scanning a file source
This tutorial covers local folders and file sources such as SMB and WebDAV. Emby, Jellyfin, and Plex manage their libraries on the server, so organize them there first and let iCouldPlay read them. Keep the workflows separate. If you do not yet have an accessible file source, first complete [SMB connection]() or [WebDAV connection]().
Prepare a folder with three files: one ordinary short video and two episodes from the same series. Record file count, names, and paths. Initially avoid same-named copies and do not include subtitle or cover-image files in the video count. Confirm all three appear in file browsing and play at least one; scanning cannot repair an unreadable folder.
## Choose a small, explicit scope
In Sources, find the target file source and open folder selection or video scanning. If folder selection appears while adding the source, select the test folder then. If you postponed it, return to the source controls now. Avoid selecting both a parent folder and several already-included children, which makes the actual traversal scope harder to understand.
After selecting, confirm the source name and folder path, then start scanning. A clear initial scope makes results easier to compare. Starting at the entire NAS root may include backups, samples, and historical copies, increasing waiting and duplicate checks. Scan the content you want to browse rather than everything the server exposes.
## Understand quick and full scans
Some interfaces offer quick and full scanning. Quick scanning targets common media directories; full scanning covers a broader area and may take longer. Use the options actually shown in your version. If your folder names do not follow common structures, a quick scan missing them does not prove unsupported video formats. Check an explicit folder selection or broader scan scope first.
Observe progress and result messages, waiting for completion before repeating an operation. Avoid launching repeated scans of one source from multiple entry points simultaneously, which makes it hard to connect results to scope. For large folders, finish evaluating the practice scope first and add folders in batches rather than continually enlarging the task and expecting immediate completion.
## Check results by source and the All category
After scanning, return to the media library, select the target source, and open “All.” Find each of the three samples and compare names, durations, and actual content. Item count need not always equal file count: episodes may be grouped into series, and some files may be unrecognized or deduplicated against existing records. Inspect series or details rather than judging solely by homepage card count.
If Movies is empty but All contains items, classification or matching may be the issue, not a completely failed scan. Personal clips should not be forced into movie metadata. Confirm that the file is in the library and opens before addressing titles and posters. For naming, continue with [Movie matching and release years]() and [Series seasons and episodes]().
## Distinguish missed scans, wrong matches, and playback failures
A missed scan means a file appears in browsing but not in the library. A wrong match means its entry exists but points to another work's information. A playback failure means the entry and metadata may be correct but opening the video fails. These require different checks, not one universal rescan. Record the sample path and behavior before choosing the next step.
For missing items, check whether the scan includes the folder, whether the extension is supported in that workflow, file integrity, and possible merging with an existing same-path record. For wrong matches, check title, year, and series information. For playback failures, open the same file directly in file browsing and compare with a local copy, avoiding confusion between network access and missing library records.
## Rescanning does not automatically reset all metadata
After adding a file, scan through the available entry point and see whether the new item appears. Existing files or metadata may be skipped or retained; do not assume every scan clears and rebuilds everything. Renamed files, moved folders, and changed source addresses require checking old records against new locations, not just reading the completion message.
Do not delete local video entries merely to rematch posters. A deletion confirmation may also remove in-app video files, unlike refreshing metadata. Retain important originals and read the current confirmation carefully before any cleanup. Confirm the relationship between server files, local app copies, and media records for your specific source type before acting.
## Expand in batches to keep the library understandable
Once the three samples pass, add a movie folder or one season. After each batch, check source, approximate counts, and representative entries, recording obvious errors. If a folder mixes finished videos, editing exports, and low-resolution previews, first select a clear scope containing the viewing versions so automatic matching does not combine similar names under one work.
Stable file organization makes later updates easier to track. You do not need to reorganize all storage for the app; choose a suitable library scope first. Confirm that each new scope works before expanding to avoid a large scan whose entry origins are difficult to explain.
## Common questions and completion criteria
**Does scanning download every video to the device?** No. Scanning a network file source mainly creates media-information and path records. Playback may still require the server and network. Offline availability requires an actual local file or a download completed through the current version's available workflow; it cannot be inferred from a successful scan.
**Why does the same file not create a second card?** The workflow may deduplicate by existing paths or records. Repeated scans are not a file-copying method. If two different videos share a name, check actual paths and files before adjusting names rather than repeatedly scanning to create more indistinguishable entries.
At completion, you should be able to reach the correct content for every sample from the media library, identify its source and folder, and explain whether missing items involve scope, classification, matching, or playback. Such a library is ready to expand, rather than merely containing more cards.
## Sources and version
Based on [iCouldPlay official store description]()for public media-management and automatic-matching capabilities, together with the existing folder-selection and scan controls. The public version checked on October 23, 2026 was 1.1.0. Scan scope, deduplication, and options may change by version. Check matches after scanning; a media entry is not proof of an offline file.