Sharing screenshots safely

A screenshot can help explain what happened. Include the action, visible status, and error message, then crop away anything unrelated.

Before sharing

• Hide passwords, tokens, session cookies, authorization codes, and extension callback URLs.
• Hide private subscription inboxes, device delivery addresses, and personal account details.
• Remove payment details and unrelated browser tabs, bookmarks, or profiles.
• Hide private article titles and newsletter content unless the support process specifically needs them.
• Keep the relevant status, time, and reason code readable.

Use a solid redaction that cannot be removed from the exported image. Reopen the final file and check it before sharing. Never capture a passkey PIN or biometric prompt.

Useful views

For a missing edition, open the reading list’s Run history. For a delivery problem, include the book’s status and the visible error. For an extension problem, include the popup message without its approval URL.

The screenshots in these guides use fictional accounts in a local demo workspace. They show real interface states; email delivery is disabled in that workspace. Your titles, counts, and available actions may differ.

Include the surrounding context from Report a problem so the team can reproduce the issue.