How to Report a Gmail Bug

Gmail includes a feedback tool to support bug reporting and new-feature ideas

A screenshot of the steps to send feedback about problems with Gmail so you can get help from the tech support team.

Lifewire

When something goes wrong in Gmail while you believe to be doing everything right, you need to keep the frustration, anger and disappointment to yourself, wall and neighbors. It would be good to share it.

If you share the Gmail bug you've encountered with Google, there's a good chance you will not experience it again — and others won't have to deal with it ever. Letting Google know about a bug in Gmail is not only salutary, however, it is also pretty easy.

Check Gmail's status to ensure that the problem isn't already well-known or widespread.

How to Report a Gmail Bug

To report a bug or to offer feedback:

  1. Click the Settings icon in your Gmail inbox on the web and select Send Feedback.

    Gmail open with the Settings menu callout loaded.
  2. Type your feedback in the box.

  3. To include an optional screenshot, ensure the Include screenshot box is checked. The browser window containing Gmail is automatically captured.

  4. Click the overlay text on the screenshot that says Click to highlight or hide info.

    This step is optional. If you're okay with the Gmail team seeing everything in the screenshot, you are welcome to skip this step and the next.

  5. Use the yellow and black boxes to mark up the screenshot. Use yellow to emphasize problem areas and black to suppress private information you don't want Google's engineers to see. The tools draw rectangles of any size you wish. Click Done when you're finished with the tool.

    Gmail's screenshot-annotation tool.
  6. Verify the text of your feedback and that the thumbnail of your screenshot (if it's included) match your expectations. Click Send.

Best Practices for Reporting a Gmail Bug or Sending Google Feedback

Specific information is always better than generic complaints. Saying that something "doesn't work" is less helpful to an engineer than to say that "button X does not activate when I've selected option Y."

  • Be calm: Bugs happen. Showering the tech-support team with angry comments or demands for speedy intervention will not help get the problem resolved with any additional speed.
  • Be concise: State the problem completely, but don't write a book. Focus on the problem only, and offer only one problem per support ticket or feedback session.
  • List the steps you took to generate the bug: If you can make the problem repeat, list the steps (in order) to make the bug reappear.
  • Share if the bug is repeatable: Was it a one-time glitch, or does it persist even after you've taken the usual troubleshooting steps of rebooting, clearing browser caches, etc.?
  • Provide evidence of the problem: Add screenshots, error-log reports, or file attachments (where possible) that show the problem in its context.
  • Offer relevant context: If you can't get a social-login button to work, for example, it's worth sharing whether you're running any privacy plugins with your browser.