How to Report a Gmail Bug

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

It can be frustrating when something goes wrong in Gmail and you're not at fault. Fortunately, Google allows you to report Gmail bugs so you, and others, won't have to deal with them again. Here's how it works.

Before you report a Gmail bug, check Gmail's status to make sure the problem isn't a known issue that Google is already addressing.

How to Report a Gmail Bug

To report a bug or to offer feedback:

  1. From your Gmail inbox screen, select the Support icon (question mark).

    Gmail inbox screen with the Support icon (question mark) highlighted
  2. Select Send Feedback to Google.

    Gmail inbox screen with "Send Feedback to Google" highlighted
  3. Type your feedback into the box.

    Gmail feedback box with instructions highlighted
  4. To include an optional screenshot, check the Include screenshot box. The browser window containing Gmail is automatically captured.

    Google feedback window in Gmail with Include Screenshot highlighted
  5. Optionally, select the overlay text on the screenshot that says Click to highlight or hide info.

    Gmail feedback screen with "Click to hide or highlight info" highlighted

    If you're OK with the Gmail team seeing everything in the screenshot, skip this step and the next.

  6. 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 feedback's "hide sensitive info" tool highlighted
  7. Verify the text of your feedback and that the thumbnail of your screenshot (if it's included) match your expectations. Press Send.

    Gmail feedback window with Send highlighted

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.
Was this page helpful?