Look at the action and destination together
A file in a browser’s Downloads folder and an offline title inside a mobile app may have started from the same media page, but they are different outcomes. Record whether you selected Download or Download to, which client displayed that action, and where you expected the copy to appear. That prevents a browser file from being mistaken for an unfinished app download.
Distinguish the browser action from a queued job
Emby documents the Web app’s ordinary Download as a single-item browser download without conversion, outside Downloads and Sync. Download to instead selects an eligible target associated with the user, including supported authenticated apps or an accessible Folder Sync destination. A queued job can prepare its requested conversion before transfer. If the target app is not running, the job can remain ready for transfer until that app becomes available. Downloads and Sync is an Emby Premiere feature.
Prepare and verify the intended offline copy
For a journey with a tablet, choose that tablet’s eligible app target rather than expecting a file downloaded on a laptop browser to appear there. Start the target app while it can reach the server, inspect the job state and confirm the item appears in the app’s downloads area. Emby’s offline guide lists Android Mobile, iOS and Emby Windows as supported offline-download apps; Web can initiate jobs to those apps. When selecting quality, remember that forcing an original file can leave it incompatible with the destination. Check playback of one completed copy before relying on a larger queue.
Questions, answered
Does Web Download create an offline item in the mobile app?
Its ordinary Download saves through the browser. Use the applicable Download to workflow for a supported target app.