A free screen recorder Chrome extension that captures the bug and the logs behind it
Updated
Midge is a screen recorder Chrome extension made for bug reports. It records a browser tab, an application window or your whole screen for up to 15 minutes, with optional microphone narration, and it saves the page's console logs and network requests next to the video on one timeline. Midge is free: unlimited recordings, videos up to 15 minutes, and no watermark.
Most screen recorders stop at the video. That works for a product demo, but a developer looking at a bug needs to know what the page was doing while you clicked. Every recording includes console logs, network requests, user actions and device info. The person who opens your link sees the failed request and the error message at the same moment the screen froze.
What you can record
A single tab
Tab recording is the usual choice for web app bugs. It captures only the content of that tab, so your other tabs, bookmarks bar and desktop notifications stay out of the video. Password and card fields on the page are blurred while you record, which keeps them out of the frames even if you click into them.
A window or the whole screen
Some bugs live outside one tab: a file picker, a payment popup that opens its own window, or a desktop app that talks to your web app. For those, pick a window or the entire screen. Two things work differently in this mode:
- Console and network logs come from Chrome tabs. A recording of another app's window has no browser logs to attach.
- Nothing on screen is blurred automatically. Midge shows a short reminder before the recording starts, so you can close your inbox or a password manager first.
Your voice
Turn on the microphone if you want to narrate. A sentence like "I applied the coupon, the total should drop to $42, but it stays at $60" saves the developer from guessing what you expected.
What lands on the timeline
When you stop recording, Midge packages the video with everything it observed on the page:
- Console:
log,info,warn,erroranddebugmessages, uncaught errors and unhandled promise rejections, with stack traces. See console logs. - Network: fetch, XHR and WebSocket traffic with request and response bodies, status codes and timings. Scripts, styles, images and fonts are listed with status, size and timing. See network logs.
- User actions: clicks, page changes and the fact that you typed in a field. The typed text itself is never recorded.
- Device info: browser and version, operating system, window size, language, time zone and the page URL.
Midge keeps a short rolling buffer of logs in memory while you browse, so the timeline can begin before you pressed record. If the error fired and only then you thought "I should record this", the error is still in the report.
A typical bug recording
Say the checkout button on a staging site does nothing. You start a tab recording, add an item to the cart, apply a coupon and click Pay. Nothing happens. You stop the recording and Midge uploads it.
The developer who opens the link watches the 40-second video and, on the same timeline, sees this:
POST /api/cart/checkout 422 184 ms
response: {"error":"coupon_expired","coupon":"FALL25"}
Uncaught TypeError: Cannot read properties of undefined (reading 'total')
at renderSummary (checkout.js:212:31)
The bug is now clear: the API rejects an expired coupon, and the front end crashes on the error response instead of showing a message. Nobody had to ask "which browser?" or "can you open DevTools and try again?".
Free, without a watermark
There is no trial and no watermark burned into your video. Midge is free: unlimited recordings, videos up to 15 minutes, and no watermark. Workspaces, teammates and folders cost nothing either. Paid plans may come later; the current terms are on the pricing page.
Privacy while you record
A bug report often contains the exact data you would rather not share: session cookies, API tokens, a customer's email. Passwords, card numbers, tokens and cookies are redacted in your browser before anything leaves your device. Emails and international phone numbers are half-masked, so [email protected] becomes j***@acme.com. The full rule list is on the redaction page and the security page.
Redaction is rule-based. It removes the patterns it knows, and teams can add their own field and header names, but an unusual secret format can slip through. Review what you captured before you share a recording of anything sensitive.
When a screenshot or a replay fits better
A video is not always the right format. If the problem is a misaligned button or a typo, an annotated screenshot is faster to make and to read. If the bug happened a moment ago and you were not recording, instant replay can save the last 30 to 120 seconds of the page, if you turned it on for that site.
Learn more
If you are new to writing bug reports, start with how to report a bug and our bug report template. If someone sent you a HAR file instead of a recording, you can open it in the free HAR viewer, which runs entirely in your browser.
Frequently asked questions
- Is the Midge screen recorder free?
- Yes. Midge is free: unlimited recordings, videos up to 15 minutes, and no watermark. Teams and folders are free as well.
- Can I record my whole screen instead of one Chrome tab?
- Yes. You can record a single tab, an application window or the entire screen. Console and network logs come from Chrome tabs, and window or full-screen recordings are not blurred automatically, so Midge reminds you to close anything sensitive before you start.
- Does Midge record my voice?
- Only if you turn on the microphone before recording. Narration is optional, but saying what you expected to happen is often the quickest way to explain a bug.
- Who can watch my recording?
- You choose per recording: anyone with the link, members of your workspace, or only you.
- How long can a recording be?
- Each recording can be up to 15 minutes long. Most bug recordings are much shorter, usually under a minute.