What should I include or hide in an FPL bug-report screenshot?
Keep the problem, round, state and necessary message visible, while removing unrelated private information and account secrets.
FFTQL privacy notice and saved preferencesCheck the whole captured area
Inspect the address, sidebars, notifications and open dialogs as well as the main issue. A screenshot should identify the unexpected behaviour without exposing verification links, credentials or irrelevant personal details. Add written reproduction steps and the occurrence time so the image supports a specific report.
When account state matters, a brief description may be sufficient. Provide only the information needed through the site's normal feedback route and retain the source context for comparison.
Practical checks
- Capture the relevant problem and state.
- Remove unrelated private details and attach reproducible steps.
Context and sources
Public reading and public Draft lookups on FFTQL are available without registration. Browser preferences and optional account records have different storage behaviour. Consult the current privacy notice for account and saved-data details.