Attach screenshots and files to a ticket
Upload useful evidence and confirm that attachments finish before submitting.
Choose the smallest useful evidence
A screenshot of an error or a short redacted log excerpt is often enough to start. Include context such as the page title, affected control, and visible error code. Avoid uploading an entire mailbox, private repository, database, or customer export for a narrow issue.
Prepare the file
- Remove passwords, keys, session tokens, payment details, and unrelated personal information.
- Use a descriptive filename, such as checkout-error-redacted.png.
- Check the permitted file types and size shown by the upload control.
- Keep the original safely in your own environment if it may be needed later.
Redaction should remove the underlying sensitive data, not simply cover it with an editable shape in a document.
Upload and confirm
Add the file to the request or reply and wait for the upload to complete. If an upload fails, remove the failed item or try a supported file before submitting. Check the completed conversation to confirm that the attachment is present.
If a file cannot be shared safely
Describe what it contains and ask the team to arrange an appropriate transfer method. Do not bypass an upload limit with a publicly accessible link to confidential data. Access to ticket attachments follows ticket permissions; nevertheless, only send information necessary for the support task.
Include this guide and what you tried in your ticket so we can pick up from there.
Contact support