Clean a stack trace before you ask for help

Stack traces look harmless, but the lines around them often carry request headers, connection strings and the email of the user who hit the bug. Paste the whole thing here; the frames and line numbers stay, the secrets go.

Runs 100% in your browser. Nothing is uploaded.

What usually leaks

Authorization headers logged with the failed request
Database URLs with the password inside
Your home directory name in every file path
Customer emails and IP addresses in the error message

Tips

Keep the file paths and line numbers: they are what the person helping you needs.
If the trace includes a request body, check it for names and addresses, which no pattern can reliably catch. Select them and press Redact selection.

Other presets