Identify the uploading app and intended collection
Emby documents automatic camera upload for its Android mobile and iOS applications. This is a mobile-to-server transfer feature, not a television player’s ability to browse a phone. Begin with the actual mobile app, its current permissions and the account that should own the connection.
Choose one non-sensitive test photo you created specifically for the check. Keep the phone’s original while assessing the server copy. Do not use a private family collection as the first diagnostic sample or assume that an uploaded image has been backed up independently. A transfer destination and a backup policy are separate decisions.
Set the application and server choices deliberately
Enable camera upload through the mobile app’s settings using its current supported controls. Then inspect the server dashboard’s Devices and Camera Upload settings. Emby’s documentation describes a default internal destination and options for a custom folder and device-specific organization.
If several phones will upload, use clear device names and decide whether their photos should share a folder or occupy separate device subfolders. Keep names meaningful to the people administering the server. A generic Phone label becomes difficult to audit when several devices use the same account or when a phone is replaced.
Check storage and library visibility separately
For a custom upload destination, verify that the server process can write to the selected folder. Emby notes that a custom upload path also needs to be added to the server library if it should appear there. A successful file copy and a visible photo library are therefore separate observations.
After the test photo is uploaded, inspect the actual receiving folder privately. Then check the appropriate library as the intended viewer. If the file exists but the library does not show it, investigate the configured library path and access. Repeatedly uploading the same photo can create confusion without solving a visibility issue.
Allow for the mobile app’s transfer conditions
Emby notes that automatic uploading can depend on conditions such as Wi-Fi, connection speed, battery state and other device-specific factors. Read the current app’s settings and system permissions before concluding that the destination is broken. Keep the phone and server network state in the test notes.
Once the single sample has reached the intended folder and appears for the intended user, decide how to monitor and protect future uploads. Preserve an independent copy of valuable originals according to your own storage plan. The expected result is a known transfer-and-library route, not an assurance that every phone condition or photo collection has been tested.
Questions answered
Does choosing a custom upload folder automatically make it a photo library?
Emby says the custom path also needs to be added to the server library. File transfer and library presentation are separate checks.
Why might an enabled phone not upload immediately?
Automatic transfer can depend on the app’s network, battery and device-specific conditions. Inspect the actual app and system settings for the tested phone.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.