The widget is deliberately invisible until it is needed, so an empty spot where you expect a checkbox is normal. The messages under the button are what distinguish waiting from failing.
Why nothing happens while the page loads
The widget renders explicitly, executes on demand and hides itself when no interaction is required. The page does load the challenge script, but it starts no challenge: a page that looks idle is a page that has not started checking yet.
The states you can actually see, in order
While a challenge runs, a pending message asks you to tick the checkbox if one appears. After about twelve seconds a second line names the likely cause: the challenge host is not reachable. At forty-five seconds the attempt is treated as a failure, and the button can be pressed again.
Rate limiting is not a failed check
Three different refusals exist and they need different responses. Too many requests from your network is a temporary limit that expires on its own. Verification failed means the token was rejected. Bot protection not configured is a server-side state, not something you can fix from the page.
The credential is per page and per tab
A successful check issues a page credential that lasts 30 minutes. It is kept in memory, cleared when the page is hidden or reloaded, and never shared between tabs. Parsing several links in one tab does not ask again until it expires.
Reference
These tables are shared across the site, so a figure you saw on one page is the figure you see here.
| Task | Desktop | Phone | Why |
|---|---|---|---|
| Download a public link | Depends on source/browser | Depends on source/browser | Requires readable media from a provider; the parser does not inherit your platform login. |
| Download a private, paid or DRM-protected video | No | No | The source never hands the media to an anonymous reader, so there is nothing to copy. |
| Save one track | Depends on source/browser | Depends on source/browser | Requires a readable media file and browser saving support; a manifest alone is not a complete file. |
| Merge two tracks into one MP4 | Depends on source/browser | Depends on source/browser | Uses a save picker or temporary browser storage; browser support, quota and memory determine availability. |
| Convert between formats | No | No | No decoding or re-encoding: single files keep their supplied format, while compatible track pairs can be remuxed into MP4. |
| Remove a watermark | No | No | The file is the platform's own copy; nothing is edited or re-encoded on the way through. |
Background and edge cases
Why the check cannot be skipped
The parse endpoint is fail-closed: without a valid token the request is refused. There is no setting that turns the check off, in the page or in the client.
Local testing behaves differently
A real site key is bound to registered hostnames, so on a loopback address the challenge cannot return a token at all. Interface work on a local server needs Cloudflare's always-pass test key, which in turn cannot pass the server check.
