---
title: "Reproduce the browser behavior someone else saw | Proofline"
description: "A maintainer can only fix what they can make happen again."
url: https://proofline.sh/learn/replay-browser-bug-report/
---

[Learning center](/learn/)

# Reproduce the browser behavior someone else saw

A maintainer can only fix what they can make happen again. When a report says "it breaks for me", the missing piece is usually one of five things the reporter had and the maintainer does not: the build, the browser, the stored state, the exact input or the timing. This guide shows how to capture each one so the behavior replays on another machine.

Network outages The Proofline team November 22, 2026 7 min read

## The five things a replay needs

Work down the list. Each layer is cheap to record at the moment of the bug and expensive to reconstruct a day later.

| Layer | What differs between two machines | What to record |
| --- | --- | --- |
| Build | The page's HTML, JavaScript bundle and the API version behind it | The page URL, the time in UTC, and any build or request ID the page or its responses expose |
| Browser | Engine, exact version, extensions, device emulation, preferences | `chrome://version`, the OS, and the extensions that were on |
| State | Cookies, local storage, IndexedDB, the service worker, feature flags | A storage snapshot from a test account, the service worker's version and the flags the client evaluated |
| Input | The exact text, file, click target and navigation path | Code points for odd text, the file's size and type, the URL sequence including redirects |
| Timing | Response order, network speed, the clock, how long the tab was open | A trace with timestamps, the throttling used, the reporter's local time and time zone |

A report that pins all five usually replays on the first try. A report that pins only the input ("click Export") leaves the maintainer to guess the other four.

## Choose the format the maintainer can run

The best evidence is something the maintainer executes, not something they watch.

-   **A script** that drives the browser through the failing steps, such as a [Playwright script from codegen](/learn/playwright-codegen-reproduction/) or a [Chrome Recorder flow](/learn/chrome-recorder-user-flow/). It replays exactly and fails the same way.
-   **A trace** of the failing run, which the maintainer opens and steps through with the DOM, network and console at each action. [Send a Playwright trace](/learn/playwright-trace-bug-report/).
-   **Captured state or responses**, such as a [storage snapshot of a signed-in test account](/learn/replay-logged-in-state/) or a [recorded HAR served back to the page](/learn/har-replay-playwright/), when the bug depends on data the maintainer does not have.
-   **A recording to watch**, such as a screen video or a [session replay](/learn/session-replay-vs-trace/), when only the visual sequence matters.

The further down that list, the more the maintainer has to reconstruct by hand.

## Worked example: an export that only fails for one tester

This example is fictional. A QA engineer reports: _Export CSV downloads an empty file. Steps: open Orders, click Export._ The maintainer follows the steps and gets a full file.

The maintainer asks for a trace instead of more steps. The tester runs the steps in a Playwright session with tracing on and sends `trace.zip`. In the trace, the request at the Export click is:

```
GET /api/orders/export?from=2026-11-01&to=2026-10-31&status=open
200  text/csv  0 rows
```

The date range is inverted. The trace's earlier actions show no date picker interaction, so the range came from stored state. The maintainer asks for the page's local storage, and the tester copies it from DevTools' **Application** panel: `orders.filter = {"from":"2026-11-01","to":"2026-10-31"}`, written by an earlier version of the date picker. The maintainer [seeds that value before the page loads](/learn/seed-local-storage-indexeddb/) and the empty export replays on their machine every time.

The report the maintainer would have needed from the start fits in four lines:

```
Build: orders page, 2026-11-21 14:05 UTC, x-request-id 7f3c…
Browser: Chrome 153.0.8010.12, macOS 15.1, no extensions
State: localStorage orders.filter = {"from":"2026-11-01","to":"2026-10-31"}
Input: Orders > Export CSV; request has from > to; response 0 rows
```

## Guides in this collection

Pick the guide for the layer you are missing.

Formats a maintainer can open or run

-   [Send a Playwright trace when a video cannot answer the question](/learn/playwright-trace-bug-report/)
-   [Record a Chrome user flow a maintainer can replay](/learn/chrome-recorder-user-flow/)
-   [Turn written reproduction steps into a script with codegen](/learn/playwright-codegen-reproduction/)
-   [What a session replay can show and what it cannot reproduce](/learn/session-replay-vs-trace/)
-   [Save console output with the lines a maintainer needs](/learn/console-log-evidence/)
-   [Send the page's DOM, not only a screenshot](/learn/dom-snapshot-evidence/)
-   [Show a memory leak with three heap snapshots](/learn/heap-snapshot-evidence/)

The browser the reporter used

-   [Record the exact browser version when the user-agent string hides it](/learn/exact-browser-version/)
-   [Install the reporter's exact Chrome version](/learn/install-exact-chrome-version/)
-   [The bug does not reproduce in headless Chrome](/learn/headless-browser-different-result/)
-   [When device emulation is enough to reproduce a mobile bug](/learn/emulated-device-vs-real-device/)
-   [Is it a browser bug? Reduce it, then test the other engines](/learn/confirm-browser-bug-other-engines/)
-   [The server sent that browser different code](/learn/user-agent-dependent-response/)

The reporter's settings and surroundings

-   [Replay the reporter's time zone and locale](/learn/replay-timezone-locale/)
-   [Report the viewport and zoom, not the screen resolution](/learn/replay-viewport-zoom/)
-   [Dark mode, reduced motion and forced colors are part of the reproduction](/learn/user-preference-media-features/)
-   [A bug only users in one country see](/learn/geo-dependent-behavior/)

State the reporter had

-   [Replay a signed-in state without sharing a real session](/learn/replay-logged-in-state/)
-   [Capture and seed the local storage or IndexedDB value that changed the behavior](/learn/seed-local-storage-indexeddb/)
-   [Record which service worker controlled the page](/learn/service-worker-controlled-page/)
-   [Record the feature flags the browser evaluated](/learn/feature-flag-evidence/)
-   [Reproduce a bug that needs two tabs](/learn/multi-tab-bug/)

Input the reporter used

-   [Input that fails only for some text: report the code points](/learn/unicode-input-bug/)
-   [Typed text works but pasted text fails: capture the clipboard payload](/learn/pasted-text-bug/)
-   [Enter submits half-typed text: reproduce IME composition](/learn/ime-composition-enter-key/)

Navigation and network

-   [Capture every hop of a redirect chain](/learn/redirect-chain-evidence/)
-   [ERR\_TOO\_MANY\_REDIRECTS: a cookie that never sticks, or two layers that disagree](/learn/too-many-redirects-loop/)
-   [An upload fails with 413: the proxy's limit or the application's](/learn/upload-413-proxy-or-app/)
-   [Freeze the backend's answers with a recorded HAR](/learn/har-replay-playwright/)
-   [Make a race reproduce every time by holding one response](/learn/force-response-order/)
-   ["Only on slow connections": add latency where it changes the outcome](/learn/network-throttling-repro/)
-   [Reproduce a failed third-party script by blocking its URL](/learn/block-request-repro/)
-   [Link the browser evidence to the server's logs](/learn/request-id-server-logs/)
-   [Capture and replay the WebSocket messages behind a realtime bug](/learn/websocket-message-evidence/)
-   [A Content Security Policy blocks it only in production](/learn/csp-violation-evidence/)

Time and speed

-   [A bug at a particular date or time: fake the clock](/learn/fake-clock-repro/)
-   ["Only on slow devices": reproduce with CPU throttling](/learn/cpu-throttling-repro/)
-   [The bug disappears when DevTools is open](/learn/bug-disappears-with-devtools-open/)

The maintainer's side

-   [Cut a reproduction down to one page](/learn/minimal-reproduction/)
-   [Reproduce on the same kind of origin: file://, localhost or a network address](/learn/localhost-file-origin-repro/)
-   [Find the commit that broke the page with git bisect and a browser script](/learn/git-bisect-browser-repro/)
-   [Run the reproduction in a pinned browser container](/learn/pinned-browser-container/)
-   [Test a fix against the reporter's page with DevTools overrides](/learn/local-overrides-test-fix/)

When the question is which cause explains a symptom, rather than how to make it happen again, start from [the browser bug report method](/learn/browser-bug-report-evidence/) and its symptom guides.

## Limits of a replay

A replay proves that the captured conditions produce the behavior. It does not prove they were the only conditions on the reporter's machine, and it cannot replay what was never captured, such as a server that has since been redeployed. Say which layers you pinned and which you assumed. When a replay fails to reproduce, that is evidence too: it tells the maintainer the cause is in a layer you did not capture.

Keep real customer data out of every artifact. A trace, a HAR, a storage snapshot and a heap snapshot can each hold session tokens and personal data. Reproduce with a test account or synthetic records whenever you can, and see [Share a HAR file](/learn/share-har-file/) for what to remove before sending.

## Record the timeline with Session Recorder

[Session Recorder](/session-recorder-chrome-extension/), a free Chrome extension from Proofline, records clicks, console errors, network activity and screenshots on one timeline while you reproduce a failure, then exports a Markdown report. Recording and export need no account. The [setup guide](/help/session-recorder/) covers installation and export. Review the export before you share it, because automatic redaction can miss values.

## Questions

### Which layer should I capture first?

Capture the build and the time first, because they change soonest: a deploy can land within the hour. Then capture state, because the reporter's next action may overwrite it. Browser details and input can usually be collected later.

### The maintainer still cannot reproduce it. What now?

Ask which layer differs. Run the maintainer's attempt and the reporter's attempt side by side and compare the first request or state value that differs. If none differs, the cause is in something neither of you captured, such as an extension, a proxy or a server-side record.

### Is a reproduction rate useful evidence?

Yes. "Fails 6 of 20 runs" tells the maintainer the bug depends on timing or order, and gives them a baseline to show that a fix worked. Run the same script repeatedly and count, rather than estimating.

## One month of free code review.

New organizations get one calendar month of hosted code review for private and public GitHub repositories. No card or cloud connection required. [Eligibility and fair-use terms](/free-code-review/).

[Start free with GitHub](https://proofline.sh/orgs/plan?offer=free_month)

## Related reading

-   ### [Turn a browser symptom into a bug report another engineer can act on](/learn/browser-bug-report-evidence/)
    
    Network outages The Proofline team November 20, 2026 7 min read
    
-   ### [Send a Playwright trace when a video cannot answer the question](/learn/playwright-trace-bug-report/)
    
    Network outages The Proofline team November 22, 2026 4 min read
