Web developer tools that bring DevTools context into every bug report

DevTools assumes the person with the bug is the person who knows how to open DevTools. In practice, the bug is found by a designer on a tablet breakpoint, a PM clicking through staging, or a support agent following a customer's description. By the time a developer opens the Network panel, the failing request is long gone and the console is clean.

Bugmark is a set of front-end developer tools packaged for the person reporting the problem. It records the same signals you would look at yourself and freezes them into a report, so you start from evidence rather than a reproduction attempt.

Consider a common case: a designer reports that a price label is truncated on the product page. In DevTools terms you want the element's computed width and font, the viewport, and whether the price came back from the API longer than expected. Normally that means three follow-up questions. With a Bugmark capture it means opening one report.

• Network log with bodies — the last 150 requests (fetch, XHR and resources) with method, URL, status and timing. For the 60 most recent fetch/XHR calls you also get query params, request headers, the request payload (JSON, form data, FormData fields, up to 16 KB), response headers and the response body (up to 32 KB).
• Copy as cURL — replay any captured request from your terminal against a local or staging API.
• Download HAR — export the log and open it in Chrome DevTools → Network for the tooling you already know.
• Console with uncaught errors — the last 150 messages, including JavaScript errors and unhandled promise rejections that never reach a visible UI.
• Element inspector — click an element to attach its CSS selector, size and computed font, color, background, padding, margin, border, border-radius and display.
• Environment — browser, OS, viewport, device pixel ratio and scroll position, which settles most “works on my machine” debates.

Bugmark doesn't replace DevTools; it hands you a snapshot that you then open in DevTools or your terminal. Here is how the two divide the work:

If you just need a HAR from a teammate without installing anything, our guide on how to capture a HAR file in Chrome walks through the manual route.

The Mobile · tablet · desktop capture mode uses Chrome device emulation to render the current page at 390×844, 768×1024 and 1440×900, then combines the three into one side-by-side image. It is a quick way to document a breakpoint regression, or to show that a fix holds at every width before closing an issue. For layout fixes, the before/after mode recaptures the page at the same scroll position so the diff is obvious at a glance.

1. Share the install page with the people who test your site; setup takes about a minute.
2. When they hit a bug, they press ⌥⇧S, mark it up and save. The logs are already attached.
3. They create a GitHub issue from the capture, or send you the self-contained HTML report.
4. Open the failing request, copy it as cURL or download the HAR, and reproduce against your local API.
5. After the fix, add an “after” screenshot to the same report to confirm the change.

Developers also use Bugmark solo: when you notice three problems during a feature walkthrough, capturing each with its logs is faster than writing notes and trying to reproduce later. For a deeper look at tracking down a specific failure, see the debugging tool page, and for the request-level details the network request logger page.

Asking non-developers to hand over network logs raises fair questions. Bugmark masks passwords, tokens, API keys, session IDs, card numbers and Authorization/Cookie headers with [redacted] in JSON keys, form fields and URL params before anything is saved. Reports stay in the browser's IndexedDB and are not uploaded to Bugmark servers. Optional anonymous usage stats only count feature use and can be turned off in settings. Typed text is never stored in the recorded steps, only which field was used, so a tester filling in a signup form doesn't leak their input into a ticket.

Bugmark is free, with no account and every feature unlocked. It runs in Chrome, Edge, Brave and Arc. Add Bugmark to Chrome — free.