Resume from where it stoppedPartial progress and queue state survive an app restart.
Automatic retries with backoffTransient errors are retried; the rest get a one-click retry.
Verified before it landsEach fragment is checked, so a finished file is a complete file.
Windows 10+ / macOS 10.13+·Account sign-in requiredv5.3.0
Downloads · 4 active
+ Add URLsField notes — coastal timelapse
Retry
Design weekly — episode 118
55%
Why a design system — full series
18%
Weekly recap — episode 041
Queued
Interrupt anything, lose nothing
Close the laptop, kill the app, change networks. When Dingdok starts again the queue is intact and every partial file continues from its last verified position.
Read the resume guide →Retries that actually finish the job
Transient failures are retried automatically with a sane delay, and anything that still fails stays in the list with a manual retry button instead of vanishing.
Read the retry guide →Retry policy
How it works
Three steps, once
After that, it runs on its own.
1
Start a batch
Queue one video or a hundred; progress is written as it goes.
2
Interrupt it freely
Sleep the machine, close the app, or drop the network.
3
Pick up where it left off
Reopen Dingdok and the queue continues from the last verified fragment.
Need the detail? The Help Center has a step-by-step guide for each feature. Help Center