A batch should save repetitive work without hiding what is about to be downloaded. Flux accepts up to 500 URLs per batch and supports provider-dependent playlist or channel extraction as well as captured page-link collections. A list of ordinary file URLs and a media playlist are related workflows, but they are not interchangeable inputs.
Start with a clear link list
For file batches, review the URLs and remove accidental duplicates or irrelevant navigation links. A web page address is not necessarily a direct file address. Wildcard expansion can help supported file-link workflows, but inspect the expanded results before admitting a large batch to the queue.
Playlists depend on the provider
When the supported provider exposes a collection, metadata extraction can find its entries. Private items, unavailable videos and source access rules still apply. A playlist link does not grant access to every item, and a large collection can require more metadata work than one video. Review output formats and the destination before starting.
Keep the queue usable
- Group related downloads and choose their destination.
- Inspect filenames so outputs are easy to find later.
- Set priorities for items you need first.
- Use a shared bandwidth limit for a large collection.
- Test a few entries before starting hundreds of similar tasks.
Recover individual failures
A failed entry does not always mean the whole batch is invalid. Check whether its source expired, needs authentication or is no longer available. Retry the affected task with the appropriate current source rather than adding the entire collection again. Persistent history lets you distinguish completed entries from pending or failed ones and avoid unnecessary duplicate work.
Sources and release context
This guide describes the Flux 2.6.6 documentation. Check the current release record for package conditions.
