How to import photos and videos to multiple phones with Swarmbot
Select target phones in the Swarmbot device wall, open Media Import from the dock, and send the same photos and videos to every device or assign different media by device. Recent Tasks tracks progress and failures per device.
Use Swarmbot’s Media Import when you need photos or videos to appear in the gallery on one or many phones. It is useful for content publishing, display devices, test-data preparation and routine maintenance of work phones. Select the target devices in the wall, open Media Import from the dock, choose images or videos on your computer, and start the task.
This is different from a generic file upload. Media Import places files in the public image or video location and asks the phone to refresh its media library. After the task completes, use Quick Open → Gallery in Swarmbot to check the result.
The common workflow: send the same media to every phone
The default mode imports every selected image and video to every selected device:
- Filter the device wall by search, group or connection type.
- Select the target phones and open Media Import in the dock.
- Choose one or more images and videos.
- Leave Assign media by device turned off.
- Choose a reasonable device concurrency and start.
- Follow per-device results in Recent Tasks.
If you choose four images and six devices, the task contains 24 device-file items. A progress value of 100% means all items have been processed; always read the success and failure counts as well.
Swarmbot first prepares the local files in its library, then distributes them to devices. On Android, images go to Pictures and videos to Movies, followed by a media-library refresh request. Android’s documentation explains that the system adds images in Pictures and videos in Movies to the corresponding media collections, which allows gallery apps to discover them. Read Android’s shared-media guide
Different phones need different media
Turn on Assign media by device when every phone should not receive the same set. Swarmbot assigns the selected files according to the current device order. You can choose how many devices receive each media item and whether the assignment cycles when there are more devices than files.
Typical setups include:
- One phone per image: each file goes to the next device.
- A group per image: the same file goes to several consecutive devices before moving to the next file.
- Cycle: after the last file, assignment starts again from the first one.
Before starting, verify the selected count and the order shown in the wall. This matters after filtering, because an incorrect selection can distribute the right media to the wrong phones. See the Swarmbot device-wall selection guide for filters, box selection and current-result selection.
Higher concurrency is not always faster
The dock currently allows 1 to 12 devices to be processed concurrently. File transfers consume much more network bandwidth, memory and storage I/O than simple control actions, so choose concurrency according to file size and connection quality.
A practical approach is to:
- start with a few devices when using new media;
- lower concurrency for large videos or many wireless devices;
- increase it gradually for small images on a stable LAN;
- avoid resubmitting the entire batch because a few devices failed.
Recent Tasks shows each device as waiting, importing, successful or failed. When only part of a job fails, identify the failed device-file items and resend only those. This avoids unnecessary traffic and duplicate work on devices that already completed.
Why a successful task may not appear in Gallery immediately
A successful import means that transfer and the gallery-refresh request completed. It does not mean the gallery UI has already rendered every item. If there is a short delay, use Quick Open → Gallery to reopen the gallery or allow Android time to finish indexing.
A file extension accepted by Swarmbot also does not guarantee that every phone can decode the content. Android’s official format table lists version conditions for formats such as JPEG, PNG, WebP, HEIF and several video codecs. See Android’s supported media formats If one format fails only on certain models, convert images to JPEG or PNG, or videos to a common MP4/H.264 profile, then retry only those devices.
Two more details matter:
- A same-named file in the target directory can be overwritten, so rename files when versions must coexist.
- Swarmbot removes the temporary library files created for this quick-import task after distribution instead of leaving task copies behind.
Media Import vs File Upload, File Download and App Install
These tools solve different jobs:
- Media Import: puts images and videos into the phone’s gallery workflow.
- File Upload: sends documents, archives or other files to a chosen directory; it does not mean Gallery has indexed them.
- File Download: browses storage on the current device and downloads selected files to the computer.
- Install App: handles APK or APKS packages and should not be replaced with Media Import. For multiple devices, see the Swarmbot batch app-install guide.
Media Import, File Upload and File Download are also available from the stream window’s right-side tools. When synchronized control or multiple targets are active, confirm the displayed target count before sending files.
A quick way to verify the result
You do not need to find the gallery icon manually on every home screen. Use Quick Open to launch Gallery or the file manager on selected devices.
A useful verification order is:
- Check success, failure and completed-device counts in Recent Tasks.
- Open Gallery and sample an image and a video.
- For assigned media, sample the first device, each group boundary and the last device.
- Retry only explicit failures.
- Use Launch App afterward if the next step is opening a content app.
The important difference is that Swarmbot manages the target set, distribution rule, progress and failures as one task. With multiple phones, that is easier to verify than opening a file manager and dragging files to every device separately.
The same workflow is available to Swarmbot AI and Local API
When the media already exists in the Swarmbot library, AI, scripts or an external system can call the same media-import capability. It runs asynchronously: creation returns a task identifier, and status is queried until the task reaches a terminal state.
When asking AI to do this, specify the target devices, library files and whether every device should receive every file. Ask for final success and failure results instead of saying only “send these pictures.” External systems can download the version-matched development documentation from the client; the developer page explains Swarmbot’s Local API and scripting options.
For most users, the best start is a small import from the dock. Once file formats, target selection and gallery visibility are correct, expand the same workflow to a larger group or an automated process.