When sharing a problem, you may reach automatically for a screenshot. Sometimes that is the best choice; sometimes the exact text is more useful. Think about what the recipient needs to inspect before choosing the format.
Match the format to the question
A screenshot can show where a message appears and how the surrounding interface looks. A text copy makes a long error message easier to search, quote, or compare. For a visual layout issue, text alone may miss the important part; for a long identifier, a tiny image may be hard to read.
You can provide both when each adds something. Include the application or page context and the action that preceded the message. Avoid sending a large, unrelated screen area that makes the relevant detail difficult to locate.
Review what will be exposed
Check for personal information, account details, or unrelated messages before sharing. If you remove information, make sure the recipient can still understand the problem. Do not modify the relevant error wording without explaining the change.
Keep the original available privately if further clarification is needed. A useful support attachment is not merely a record that something happened; it preserves the particular evidence another person needs to reason about it without guessing what was outside the frame.