A screenshot can make a support request much clearer, but it can also expose account access. Before sending one, look for passwords, complete playlist URLs, tokens and unrelated notifications. The goal is to show the failing state, not every private value on the screen.
Keep useful context visible
Show the exact error text, app name or settings labels that explain the problem. For a channel issue, keep the channel name and quality or regional suffix visible. For a device issue, the model and app version are useful. Crop unrelated chats, email addresses and personal notifications.
Treat full URLs carefully
A playlist URL may contain credentials in its path or query string. Cover the full sensitive value rather than only the visible password field. If the URL is essential to private verification, use only the official support channel and share it only when specifically needed. Never post it to a public forum or review.
Check the final image
Open the edited screenshot before sending and confirm the hidden information is no longer readable. Pair it with a short description of the action that produced the error. A screenshot alone may omit timing, device context or whether another channel works.
Your checklist
- Keep error text and relevant labels.
- Hide passwords, tokens and full private playlists.
- Review the final image and add a brief explanation.
What to take away
A safe support image reveals the problem while keeping access private. If credentials were already exposed, ask support about rotating them rather than only deleting the picture.