Bug Reports & Download Errors
If a specific video URL is failing, copy the error message shown in the job card and include the URL type (single video, playlist, or bulk) when reporting. Most "sign in to confirm" errors are YouTube bot-detection responses that resolve themselves after a short cooldown.
Security Vulnerability Disclosure
If you have discovered a security vulnerability—including SSRF bypass, path traversal, injection vectors, or rate-limit bypass techniques—please submit a responsible disclosure report. Do not post exploits publicly before contacting us.
Feature Requests
Ideas for new supported formats, improved queue management UI, or additional metadata fields are welcome. Please check the FAQ page first to see if your request has already been addressed.
DMCA & Legal
For copyright takedown requests, counter-notices, or legal correspondence, please review our DMCA Policy page first. Legal notices must be submitted through the formal DMCA process detailed there.
Before reaching out, please check the FAQ page for answers to the most frequent questions about FFmpeg errors, MP3 conversion slowness, supported URLs, file retention, and privacy practices.
Self-Hosted Instance Support
Running your own self-hosted instance? Our Self-Host Guide covers common deployment issues including FFmpeg path configuration, Docker volume mounts, and reverse proxy TLS setup. The yt-dlp Errors & Fixes blog article covers the most common extraction failure modes.
Response Times
We aim to respond to bug reports and security disclosures within 72 hours on business days. Feature requests are reviewed periodically and may be tracked in the project repository. Automated scraping or spam submissions are silently discarded.