A USB detection message does not prove that a playback app can read the videos. Check the documented drive format, folder path and app access separately, then investigate video encoding once the file is accessible.
When a display detects a USB drive but the video area stays black, check whether the playback app can read the drive before changing the video. USB detection, readable storage, a correct folder path and supported video encoding are separate checks. A successful preview on a computer does not establish that the display can access the same files. Start with one backed-up drive and one short video, then change only one thing at a time.
Match the symptom to the access layer
A black rectangle alone does not identify the fault. Record what you can actually open or play:
- A USB insertion message appears, but no files are visible: the display detects the device, but file-system support, mounting and app access remain unconfirmed.
- The system file browser opens the drive, but the playback app lists nothing: check the app's storage permissions, media-loading rules and configured folder.
- Some folders work and others do not: compare folder names, nesting and the path assigned to each playback area.
- Images load from the same location, but videos do not: a completely unreadable drive is less likely. Check video filtering, individual files and encoding next.
- The video appears in the playlist but stays black when started: file discovery has progressed further, but decoding and playback configuration still need checking.
- The video works in a computer preview only: that confirms playback in the preview environment, not access through the display's USB storage path.
Do not use an insertion prompt as the final storage check. The useful question is whether the playback app can read the intended file through its normal loading workflow.
Check the drive before changing folders
First identify the file systems supported by the display and its playback application. Use the manufacturer's documentation for the actual configuration. Do not assume that a format supported by your computer is supported by the display.
FAT32 is a compatibility option on many devices, but it is not a universal requirement. Support for FAT32, exFAT or other formats depends on the device and software. The supplied specifications for our displays do not establish a required USB file system, so a particular format should not be presented as an IMD Signage requirement.
Use this sequence:
- Back up everything you need from the USB drive.
- Check its current file system on a computer and compare it with the documented supported formats.
- If the format is unsupported, prepare a spare drive using a supported format. Formatting erases the selected volume, so confirm the target carefully.
- Copy one short, supported video to the location required by the playback app.
- Eject the drive through the computer's normal removal process.
- Connect it to the display and follow the documented media-loading procedure.
Do not reorganize every folder and re-encode every video during this check. If the same file and folder arrangement work after changing only the drive format, that is useful evidence of a storage compatibility problem.
If an identically prepared spare drive works while the original does not, investigate the original drive rather than repeatedly editing the playlist.
Separate folder paths from file names
A setting that asks for a folder usually needs the directory containing the video, not the video's name. A setting that asks for a media file needs the file itself. Those are different targets.
For example, consider this arrangement:
Training/
introduction.mp4
Cleaning/
daily-cleaning.mp4
For an application that selects a directory for each playback area, the first area would reference Training and the second would reference Cleaning, using the path syntax that application documents. Neither folder field would contain introduction.mp4.
For an application that selects individual media files, you would instead choose the relevant file inside its folder. Do not transfer the directory-setting approach to an application that expects a file selection or an import operation.
Check these details against the actual USB contents:
- The configured folder exists on the drive being used.
- There is no extra parent folder introduced during copying.
- The file is inside the selected folder, not beside it at the drive root.
- Spelling and letter case match exactly.
- The file has its intended extension, rather than a hidden extra extension.
- The path uses the form required by the app, including whether it expects a relative path or a storage selection.
A folder named video is not a general USB requirement. Use that name only when the application's instructions or configuration call for it. Likewise, do not assume that several playback areas need separate folders unless the application works that way.
Check app access and media-loading rules
Being able to browse a USB drive in one application does not prove another application has access to it. On Android, access can depend on the app's permissions and the location selected through the system interface.
Check for a storage-access prompt, a required folder selection or an import action. Use the documented controls. Do not try to solve a permissions problem by weakening device security or changing unrelated system settings.
For our offline signage player, follow its documented media-loading workflow rather than assuming it uses a folder field from another application. Our player is designed to keep an internal copy of the show so playback can continue after the removable media is taken out. Existing content on screen therefore does not prove that a newly connected USB drive has been loaded.
Also separate loading from startup. If the files work when selected manually but the intended show does not appear after startup, follow the checks for offline playlist autostart. Reformatting a readable drive is not the first response to a startup-selection problem.
Check the video after file access works
Once the playback app can find the correct file, move on to the file itself. An .mp4 extension identifies a container; it does not establish which video codec is inside it.
For our player, H.264 MP4 is the recommended starting point. A file that plays on a computer can still use encoding that the target playback environment does not support. Keep the original and make a separate compatibility copy rather than overwriting the only source.
Use the image and video preparation guide for the basic export workflow. For this diagnosis, use one short clip with visible motion near the start, so an opening black frame is not mistaken for failed playback.
Compare that clip with the troublesome file using the same drive, folder and playback settings. If the comparison clip plays, return to the troublesome file's encoding or integrity. If neither file can even be listed, return to storage access and path selection before changing export settings again.
Apply the smallest fix and verify it
Keep the final correction tied to the evidence:
- Unsupported file system: use a documented supported format after preserving the drive's contents.
- Incorrect directory: correct the configured path or move the file to the required location.
- Missing app access: grant access through the documented storage-selection or permission process.
- Unsupported encoding: export a supported copy and retain the source.
- Media not loaded: complete the application's normal import or reload procedure.
After the single-file check succeeds, restore the intended folder arrangement and add the remaining videos. Open each playback area and confirm that it shows the intended clip, not merely any clip from the drive.
Finally, repeat the normal loading and startup sequence. Record the working file system, folder arrangement and loading steps. That gives you a repeatable preparation method without treating one successful USB insertion message as proof that every layer works.
Questions
Does a USB detection message mean the videos are readable?
It confirms that the display detected a USB device, not that the playback app can read its files. File-system support, mounting, app permissions and folder selection still need checking. Confirm access through the playback app's documented loading workflow.
Should I format the USB drive as FAT32?
Only if FAT32 is a supported format for the display and playback app. Check the manufacturer's documentation before changing formats, and back up the drive first. FAT32 is a common compatibility option, but it is not a universal requirement for signage playback.
Must USB videos be placed in a folder named video?
There is no general requirement to use a folder named video. The correct name and location depend on the playback app. If a setting selects a folder, it must identify the directory containing the files, not an individual video's name.
Why does a video play in preview but stay black on the display?
A computer preview uses that computer's storage access and decoding capabilities. It does not confirm the display's USB file-system support, app permissions, folder path or codec support. Establish file access on the display first, then compare the video with a supported sample.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.