Skip to content

A screenshot Chrome extension that keeps the logs attached

Updated

Midge is a screenshot Chrome extension for bug reports. You capture the visible part of a tab or a selected region, mark it up with arrows, boxes, a pen, text and blur, and share it with one link. Unlike a plain screenshot tool, Midge attaches the page's recent console logs, network requests, user actions and device info, so the image comes with the evidence a developer needs.

Midge is free: unlimited recordings, videos up to 15 minutes, and no watermark. Screenshots count as recordings, so you can take and share as many as you need.

Two ways to capture

Visible area

One click captures what you see in the tab, without the browser toolbar, bookmarks bar or other windows. Use it when the whole layout matters: a page that renders with the wrong theme, a broken grid, an empty state that shows up when it should not.

Selected region

Drag a rectangle around the part that is wrong. A tight crop of a misaligned button or a truncated label is easier to read than a full page where the reader has to hunt for the problem. You can still add context in the description, such as which page you were on and what you clicked.

Annotations that make the problem obvious

After capture, Midge opens a simple editor:

  • Arrow: point at the exact element. "This one, not the one next to it."
  • Box: frame an area, for example two prices that should match.
  • Pen: circle or underline something freehand.
  • Text: add a short label right on the image, like "should say 3 items".
  • Blur: hide a customer name, an email address or an account number before you share.

Keep annotations few and specific. One arrow and a three-word label usually beat five overlapping boxes.

The logs come with the screenshot

This is the part a regular screenshot tool cannot do. Midge listens to the page's console and network activity in the background and keeps the last few minutes in memory. When you take a screenshot, that context is attached. Every recording includes console logs, network requests, user actions and device info. A screenshot report carries the same data.

Here is why that matters. Imagine a dashboard card that shows "NaN%" instead of a conversion rate. The screenshot shows the symptom. The attached network log shows the cause:

GET /api/metrics/conversion  200
{"visits": 0, "orders": 0, "rate": null}

The developer can see that the API returned null for a day with zero visits and the front end divided by zero. That is a five-minute fix instead of a day of back and forth. For details, see network logs and console logs.

The background capture stays on your device. It lives in memory, is cleared when you close the tab and only leaves your computer when you create a report. You can also list sites where Midge should never run, such as your bank.

Privacy in screenshots

There are two layers to think about.

The image. What you see on screen ends up in the screenshot. Use the blur tool on personal data before sharing. Automatic blurring of password and card fields applies to tab recordings, not to screenshots, so the blur tool is your job here.

The logs. Passwords, card numbers, tokens and cookies are redacted in your browser before anything leaves your device. Emails are half-masked, so the developer can still tell which test account hit the bug. The full list of rules is on the redaction page.

Screenshot or video?

Use a screenshot when the bug is visible in one frame: wrong text, broken layout, a wrong number, a missing icon. Use a screen recording when the bug depends on a sequence of steps, timing or animation, such as a menu that closes before you can click it or a form that submits twice. If something odd just happened and you were not ready, instant replay can save the last few dozen seconds, if you enabled it for that site.

Sharing

Each screenshot gets a link. You decide who can open it: anyone with the link, your workspace members, or only you. File it in a folder, such as one per release or per sprint, so your team can find it later. Teams and folders are free.

A good screenshot bug report

A screenshot answers "what is wrong". The description should answer "what did you expect" and "how do I get there". A short example:

Title: Order count shows 0 on the Orders tab after filtering by "Last 7 days"
Steps: Orders, set filter to Last 7 days, wait for the list to load
Expected: count matches the 12 rows in the list
Actual: count shows 0 (arrow in screenshot)

Our bug report template and bug report examples have more patterns like this. And if a teammate sent you a token from a request and you want to see what is inside it, the free JWT decoder reads it in your browser without sending it anywhere.

Frequently asked questions

Can I capture only part of the page?
Yes. You can capture the visible area of the tab or drag to select a region. Selecting just the broken component keeps the screenshot easy to read.
Which annotation tools are included?
Arrows, boxes, a freehand pen, text labels and a blur tool. Blur is the one to use for names, emails or anything else you do not want in the image.
Does a screenshot include console and network logs?
Yes. Midge keeps recent console and network activity in memory while you browse, so a screenshot taken after an error still carries the logs from before it.
Are password fields hidden in screenshots automatically?
Automatic blurring of password and card fields applies to tab recordings. In a screenshot, use the blur tool on anything sensitive before you share it. Secrets in the logs, such as tokens and cookies, are redacted either way.