Identify the page
Include the full URL and whether it is the English or translated page.
Support and feedback
Contact VF M3U8 Tools
Send feedback about the public M3U8/HLS tool site, page content or responsible-use boundary.
Contact channel
Contact information
Review the contact information and reporting guidance published by this site. Include the page URL and steps when reporting an issue.
Use this page for correction requests, site feedback and operational questions about the M3U8 tool site.
Before sending a report
- Do not include private stream tokens, account-bound URLs, cookies, credentials or paid media links.
- Include the public page URL, browser name, visible error and whether the stream is public or authorized.
- For playback issues, say whether the Checker reports CORS, 403, manifest, segment or encryption signals.
- For content corrections, include the page title and the sentence or section that needs review.
What we can help with
- Broken internal links or missing public pages.
- Incorrect M3U8/HLS explanations.
- Tool page wording that is unclear for site owners.
- Static publishing issues related to public site pages.
What not to send
Do not send credentials, private keys, paid-stream URLs, DRM keys or any URL you are not allowed to test.
Page URLIdentify the page where the issue occursReproductionExplain what happened before and after the actionNo secretsNever send accounts, tokens or DRM keys
Report checklist
Send reproducible details, not sensitive content
Most page reports do not need a private stream URL. Start with the page, environment and symptom.
Describe the environment
Browser, operating system, device type and approximate viewport width.
List the steps
Explain what happened before and after the click. Screenshots can help, but must not expose credentials.
What to report
Types of issues to describe
Pages and links
Blank pages, inactive buttons, broken links, layout shifts or mobile display problems.
Content and translation
Factual errors, unclear terminology, mixed languages or copy that does not match the product.
Product experience
Hard-to-find routes, unclear steps, weak state feedback or difficulty choosing a tool.
Privacy and responsible use
Data handling, authorized use, policy copy or responsibility-boundary questions.
Do not sendAccounts, cookies, private tokens, DRM keys or copyrighted media URLs
Public feedback is not a channel for bypassing access controls.
FAQ
Before you report
Confirm the report boundary and use self-service diagnostics first.
What should I include in a report?
Include the page URL, browser, device width and a short description. Do not include private streams or credentials.
Is this a place to ask for bypass help?
No. The public site is for authorized diagnostics and content feedback.
Where should playback errors go first?
Start with the Browser Stream Test and share the non-private diagnosis category if needed.
Next step
Open the browser stream testUse a self-service route first
Open the relevant tool, guide, problem page, or FAQ before sending a report.