Skip to content
midgeDocs
Bug reportsHow to report a bug, even if you're not technical
Bug reports

How to report a bug, even if you're not technical

How to report a bug clearly: where to send it, what to include, how to take a screenshot or screen recording, and what to leave out for your privacy.

To report a bug, tell the people who make the app what you were trying to do, the steps you took, what you expected to happen, and what happened instead. Include the page or screen where it happened, your device and browser, and a screenshot or short screen recording. Send it through the app’s help or feedback option, its support email, or, for open source software, its issue tracker.

You do not need to be technical to write a useful report. Developers can fix almost anything they can see happen for themselves, so the most valuable thing you can give them is a clear description of how to make the problem appear. This guide walks through it step by step, including how to take screenshots on Windows and Mac, and what to keep out of your report to protect your privacy.

Step 1: Write down what happened while it’s fresh

Before you do anything else, jot down four things:

  1. What you were trying to do. “I was trying to change my delivery address.”
  2. What you did, step by step. “I opened My account, clicked Addresses, clicked Edit next to my home address, changed the postcode, and clicked Save.”
  3. What you expected. “The new address would be saved.”
  4. What happened instead. “A red message said ‘Something went wrong’ and the old address was still there.”

Use the names you see on the screen, like the button labels, so the developer can follow along. If there was an error message, copy the exact words. “It gave an error” is much harder to act on than the message itself.

If you can, try once more. Did it happen again the same way? Saying “it happens every time” or “it happened once and I couldn’t make it happen again” is very helpful.

Step 2: Take a screenshot or a short recording

A picture shows things you might not think to mention. Here is how to capture one.

On Windows

  • Press Windows logo key + Shift + S to open the Snipping Tool overlay and select the area you want. The image is copied so you can paste it into an email or form.
  • Press Print Screen (PrtSc) to copy an image of your whole screen.
  • To record a video on Windows 11, open the Snipping Tool, select Record, then New, or press Windows logo key + Shift + R. Select the area, click Start, and click Stop when you are done.

On Mac

  • Press Shift-Command-4 and drag to capture part of the screen.
  • Press Shift-Command-4, then the Space bar, then click a window to capture just that window.
  • Press Shift-Command-3 to capture the whole screen.
  • To record, press Shift-Command-5 to open the Screenshot toolbar, choose Record Entire Screen or Record Selected Portion, and click Record. Stop with the Stop button in the menu bar or Command-Control-Esc.

On a phone

Phones have their own screenshot shortcuts, usually a combination of side and volume buttons, and most have a built-in screen recorder in the control or quick settings panel. Check your phone’s help pages if you are unsure.

Keep recordings short: start just before the problem and stop right after. A 30-second video is far easier to watch than a ten-minute one.

Before sending, look at your screenshot. Crop or cover anything private that is not needed: your address, card details, other people’s names, messages, or other open tabs.

Step 3: Note where it happened

Developers often need to know your setup, because many bugs only appear on certain devices or browsers. Write down:

  • The page address (the URL in the browser’s address bar) or the name of the screen in an app.
  • Your device: for example “Windows laptop”, “MacBook”, “iPhone 15”, “Samsung Galaxy tablet”.
  • Your browser and its version, if it was a website. You can usually find the version in the browser’s Help or About menu.
  • The date and time, including your time zone. This lets the team find what happened in their own logs.
  • Your username or account email, so support can look at your account. Never your password.

Step 4: Find the right place to report it

  • In the app or website. Look for Help, Feedback, Report a problem or a chat bubble. These usually go straight to the right team and may attach useful details automatically.
  • Support email or contact form. Often listed at the bottom of the website. Put a short summary in the subject line, such as “Can’t save new delivery address”.
  • Open source projects. Use the project’s issue tracker, often on GitHub. Read the contributing guidelines first and search existing issues; someone may have reported it already, and you can add your details there.
  • At work. Your team may have a form, a chat channel or a tracker like Jira for bugs. Ask where bugs should go if you are not sure.

Step 5: Send it, and keep your private data out

A finished report can be short:

Subject: Can't save a new delivery address ("Something went wrong")

Hi, I was trying to change my delivery address and it won't save.

Steps:
1. Signed in and went to My account > Addresses.
2. Clicked Edit next to "Home".
3. Changed the postcode to 94107 and clicked Save.

Expected: the new address is saved.
What happened: a red message "Something went wrong" appeared and the
old address is still there. Happens every time (tried 3 times).

Where: shop.example.com, Chrome on a Windows laptop,
today around 3:40 pm Pacific time. Account: [email protected]

Screenshot attached.

Things to leave out:

  • Passwords and one-time codes. No real support team needs them.
  • Full card numbers or bank details. If a payment failed, the last four digits are enough.
  • Other people’s personal data visible in screenshots.

If they ask for technical details

Sometimes support will ask for more, such as “console logs” or a “HAR file”. These are recordings of what the browser did behind the scenes, and they help developers see errors you cannot see on the page. They sound intimidating but take a few minutes. Our guides walk you through it:

A HAR file can contain your login session and personal data, so clean it with the HAR sanitizer before sending. It works in your browser and does not upload the file.

What happens next

Most teams reply to confirm they received your report, and may ask a follow-up question. Answer it if you can; one quick reply often makes the difference between a fix and a ticket closed as “can’t reproduce”. Not every bug is fixed right away, because teams fix the most serious problems first, but a clear report makes yours much easier to fix when its turn comes.

An easier way for teams

If you report bugs regularly at work, for example as a tester, a support agent or a product manager, Midge can do most of this for you. It is a free Chrome extension. You record your screen or take a screenshot, write a short title, and share one link. Every recording includes console logs, network requests, user actions and device info. Passwords, card numbers, tokens and cookies are redacted in your browser before anything leaves your device.

Official documentation

The screenshot and recording shortcuts above were checked against these pages on November 10, 2026. Operating system shortcuts and menus can change between versions.

Frequently asked questions

Where should I report a bug in an app or website?

Use the app’s own help or feedback option first, then the support email or contact form. For open source projects, use the project’s issue tracker, usually GitHub Issues, after reading its contributing guidelines.

What should I include when I report a bug?

What you were trying to do, the steps you took, what you expected, what happened instead, the page or screen, your device and browser, and a screenshot or short screen recording.

Do I need technical knowledge to report a bug?

No. Clear steps and a screenshot are the most valuable parts of any bug report. If the team needs technical details such as console logs or a HAR file, they will usually tell you how to get them.

Should I send my password so support can check my account?

No. Legitimate support teams do not need your password. Never include passwords, full card numbers or one-time codes in a bug report or screenshot.