Bug Report

Found something broken? Tell us exactly what happened — the more detail, the faster we can fix it. Reports are triaged daily and shipping fixes is our top priority over new features.

What Makes a Good Report

The exact tool where you saw the bug — pick from the dropdown so we know which codepath.
Reproduction steps — the exact clicks or input that triggered the bug. "Paste X, click Y, see Z" is perfect.
Expected vs actual — what you thought would happen, and what actually happened.
Browser + OS — we auto-detect this, but correct it if you're testing on a different machine.
No sensitive data — don't paste passwords, personal info, or proprietary content in the description. Describe the bug, don't reproduce it with real data.

Not a Bug?

Missing a feature? Use Request a Tool.
General feedback? Use Contact.

Which tool?

What's the bug?

Steps to reproduce Numbered steps work best. Be specific.

What did you expect to happen?

What actually happened?

Browser + OS (auto-detected, editable) Correct if you're testing on a different machine than you're reporting from.

Email (optional) Leave blank for anonymous.

Please don't include passwords, credit cards, personal data, or proprietary content in your report. Describe the bug, don't reproduce it with real data. See our Privacy Policy.