How RedPuller handles bulk downloads
Select public media from a profile page, review the preflight plan, and receive bounded ZIP parts with visible progress.
Quick answer
Choose media from the current profile workspace, review the item and size estimates, then let RedPuller process the selection as sequential ZIP parts with retry and cancellation controls.
Steps
- Open a public profile and select the visible media you want to download.
- Review the preflight item count, ZIP part count, and any unavailable or uncertain sizes.
- Start the queue, monitor each part, and retry or cancel a part when needed.
Limits to keep in mind
- Each part is bounded by item and byte limits; an oversized or unavailable item can become a terminal item instead of completing.
- Sizes can be exact, derived, estimated, or unknown, and the provider response can change while a stream is running.
Common questions
Can I process an entire profile in one action?
RedPuller works from the current profile pages and selected items. Larger selections are split into manageable parts rather than treated as one unbounded request.
Why are ZIP parts used?
Parts keep progress, retries, cancellation, and partial failures visible while respecting the server's item and byte budgets.