Recorded steps
The ordered actions leading to the failure.
Featured on the Chrome Web Store (opens in a new tab)
Record the steps behind the bug.
Record a browser bug and inspect the recording, down to the affected elements and interactions. Share the recording with teammates and AI agents to pinpoint what went wrong and get to a fix faster.
Free extension for desktop Chrome. Try it before signing up.
Trusted by 2,000+ professionals weekly, across quality assurance, engineering, and support.
01 / See the whole story
See what happened. And what led to it.
Follow the clicks and page changes that lead to a bug. Give your teammate the sequence to replay, inspect, and understand.
The product, in motion.
Video coming soon
02 / Make the handoff count
From “it broke”to “here’s how.”
Give your teammate a replay of the steps that led to the issue, so they can see what happened and where to start.
Walk through a recordingTry the extension for free. Create a free account to save and share.
Record the lead-up.
Choose Record Steps in the extension, then repeat the issue. Capture the path that gets you there.
Save it. Look it over.
Choose Stop & Save, then open the recording in your workspace. Review the steps before you share.
Send the context.
Share with project members or create a public link. Your teammate can follow the recording and inspect the steps.
You choose who can open the recording.
03 / Inspect the change
Find the moment.Inspect what matters.
Pause the replay. Select the button, field, or message that needs a closer look. Tag the issue and add a note, right where it happened.
Try it below: select the error message to inspect its element.
Renewal quote mismatchon billing.example
billing.example / renewalClick an element to inspect
Team plan
Seat renewal
00:12 / 00:12
The context belongs with the recording.
Review the recording, the affected element, and the browser details captured with it.
Affected button or field
The element involved in the issue.
Page and browser details
The available page, browser, and viewport context.
Notes for your teammate
What you expected, and what happened instead.
Selectors for this example
CSS selector
button[data-testid="assign-selected"]Playwright locator
page.getByTestId('assign-selected')Exported test code is a starting point. An engineer reviews it and adds the setup, test data, and checks your application needs.
04 / Pass the context along
Give your teammate the story behind the issue.
Add the recording link to the issue your team already uses. Your teammate can open it and review what happened.
See sharing and integrations
A clearer starting point
“Here’s what I did before it broke.”
Add the recording to the conversation your team is already having.
Example issueExample using test data
BUG-042 Needs investigation
Assign button disabled after a page change
I selected two tickets, then went to page two. The count still says two, but I can't assign them.
See the browser stepsExplore the example abovePrivate recordings need project access. Public links can be opened by anyone who has them.
Review what you share. Choose who can open it.
Input values are masked by default, but other page content can still appear. Check the recording before sharing it.
Before you record your first bug
Does it record all my browsing?
You start a bug recording when you want to capture a problem. The extension records the browser steps you choose to record.
Can I use it without writing code?
Yes. You can record browser steps without writing code. Your teammate can review the recording and inspect the available technical details.
Do I need an account?
You can try the extension before signing up. Create a free account to save and share recordings through your workspace.
Will it fix the bug or create a finished test?
You still investigate and fix the issue. If you export test code, review it and add the setup, test data, and checks your application needs.
Can it show what happened before I started recording?
No. Start recording before you repeat the steps that lead to the issue.
What does the free plan include?
You can start with short recordings and try sharing an issue with your team. See the current recording length, sharing, and account limits on the pricing page.
Who can open a recording I share?
Private recordings require access to the project. If you make a recording public, anyone with its link can open it. You can make it private again to remove public-link access.
The next bug deserves a clearer story.
Start with the steps.
Record your next browser bug. Give engineering a place to begin.