use-cases
Batch download social media videos
How to decide when a batch download belongs in an extension, Pro queue, API, or MCP workflow instead of a public web form.
Batch downloads need queue limits, source records, retries, and usage boundaries. Use the web tool only for proving that a single link works; move batch work to extension, Pro, API, or MCP paths that can record status and refuse unsupported links.
Direct answer
Batch downloads need queue limits, source records, retries, and usage boundaries. Use the web tool only for proving that a single link works; move batch work to extension, Pro, API, or MCP paths that can record status and refuse unsupported links.
Recommended workflow
Extension or Pro queue first; API/MCP for developer automation and audit logs.
Steps
- Test one representative link in the web tool before creating a queue.
- Separate links by platform, source type, and permission status.
- Set rate limits, retry limits, and failure reason logging.
- Export a record of successful, skipped, and refused links.
Good-fit cases
- Owned video backups
- Permission-based campaign archives
- Rate-limited research collections
Do not use this workflow for
- Mass scraping
- Private account downloads
- Ignoring platform or creator restrictions