“Parse failed” means Dingdok could not read the information it needs from a page. The link itself is usually fine; the failure is about access, page structure, or a protected stream. Work through the checks below in order.
What parsing does
Before downloading, Dingdok opens the page, reads its metadata, and lists available formats. If any of those steps fail, the item is marked Parse failed with a short reason.
Quick checks
- Open the link in a browser. If it does not play there, Dingdok cannot download it either.
- Update Dingdok. Sites change their layout often; a newer build usually carries fixed parsers.
- Remove tracking parameters. Trim the URL back to the canonical video address.
- Check the platform status page. It reports whether a site is currently supported, login-only, or unavailable.
Common causes
- Login required. Some pages need a signed-in session. Dingdok does not bypass logins.
- Protected or DRM stream. Encrypted streams are not supported and never will be.
- Removed or private item. The content no longer exists publicly.
- Changed page structure. A parser update is needed; report it so it is prioritised.
- Geo-restriction. The page returns an error for your region.
Reporting a failure
When you report an issue, include:
- The full link (or the platform and video ID).
- The exact reason text shown in the queue.
- Your Dingdok version from Help → About.
This is enough to reproduce and fix most parser problems quickly.
Workarounds
- Try the mobile variant of the site by editing the URL.
- Use a different but equivalent link (for example, a short link versus a full link).
- For playlists, queue the individual items instead.
What Dingdok will not do
Dingdok does not bypass authentication, paywalls, or DRM, and does not use workarounds that violate a site’s terms. If a link is login-only or protected, treat the failure as expected rather than a bug.