A useful support screenshot shows the error, app version or affected screen while keeping passwords, playlist links, device keys and personal account information private. Crop or cover sensitive areas before posting publicly. Send account-specific information only through the established private support channel when it is actually needed. Choose evidence that identifies the failed stage, such as installation, source loading or playback. More visible account information rarely improves a public bug report, and it can expose reusable credentials embedded in apparently ordinary URLs.
Capture the relevant evidence
An error message or empty screen is more useful than a photo of the player logo. Include enough surrounding interface to identify the action that failed without exposing the full account page. Capture the exact message and enough of the interface to identify the app, but avoid opening an account panel merely to add context. If the fault is intermittent, write down the action immediately before it occurred. State whether the device remained responsive and whether the problem affects one item or all items, since those facts can narrow the investigation without additional private images.
Inspect every corner
QR codes, MAC-style identifiers, expiry panels and URL parameters can appear away from the obvious password field. Review the image at full size before sharing it. Check the full-resolution original before sharing, including QR codes and reflected or background information in a photograph. Use an opaque redaction that removes the underlying text, then export and inspect the shareable result. A translucent mark or an editable overlay can leave information recoverable. Keep the unredacted original private if it is needed for an authorised support exchange.
Add a short written description
State the device model, app version, action and exact error. This often reduces the need to share additional screenshots and makes the report useful even if small text is difficult to read. Include the exact device and player versions, the expected result and what happened instead. For an installation error, include the package source without publishing account-bearing query parameters. For playback, describe the source type and symptom without posting a private stream link. A concise reproducible sequence is more useful than several near-identical account screenshots with no explanation of the failed action.
A practical sequence
0 of 3 steps completed on this page.
An example to work through
A cropped image of an installation error plus the TV model can be more useful than an uncropped account screen full of private identifiers. Add whether installation failed before launch or the player failed later. Redact any source link and account identifier, then inspect the exported image itself before sharing it with the written fault description.
Questions about this topic
Can a playlist URL be sensitive even without a password label?
Yes. Its query parameters or path may contain account credentials.
Does covering only the password field protect a QR code?
No. Review and remove any QR code or key that can expose access details.
