Skip to content
Add to Chrome (opens in a new tab)
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.

Add to ChromeExplore a bug example

Free extension for desktop Chrome. Try it before signing up.

The Samelogic extension logo sits on a red hub connecting an isometric browser window to app tiles.A browser recording connects to app tiles through a red hub bearing the Samelogic extension logo.

For the people reporting, investigating, and fixing browser bugs.

Follow the steps

Trusted by 2,000+ professionals weekly, across quality assurance, engineering, and support.

AbbottAccentureBoschMicrosoftShopifyCisco
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.

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 recording

Try the extension for free. Create a free account to save and share.

  1. Record the lead-up.

    Choose Record Steps in the extension, then repeat the issue. Capture the path that gets you there.

  2. Save it. Look it over.

    Choose Stop & Save, then open the recording in your workspace. Review the steps before you share.

  3. 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
Interactive demo · sample data
billing.example / renewalClick an element to inspect
Team plan

Seat renewal

00:12 / 00:12
Reproduction steps4 steps · 00:12
SetupStarted on billing.exampleChrome · Desktop · Sample recording
  4. Show Details
    Selector
    #calculate
    Element
    Calculate renewal (button)
    Exact URL
    https://billing.example/renewal
The second click is the missing context.

Go to 00:08 to see the extra seat. Select any element to see its details and leave a note.

The context behind the bug

One recording.More to go on.

The replay shows what happened. The affected element, browser details, and your notes give your teammate a place to begin.

See how sharing works
Inside the recording

Renewal quote mismatch

Sample

The steps that led here

  1. 00:04Add seat
  2. 00:08Add seat again
  3. 00:12Calculate renewal

The affected element

div#result
Quote doesn’t match the seat count

3 seats shown · quote uses 2 seats ($47/year)

The browser context

billing.example/renewalChrome · Desktop

Your note on the issue

00:12
“I added a third seat, but the quote still uses two. I expected the renewal to include all three.”

Illustrated from the demo above. Browser details vary by recording.

04 / Pass the context along

Send the recording.Skip the retelling.

Add the recording to the issue or conversation your team already uses. Your teammate can replay the steps, inspect the element, and read your notes.

See sharing and integrations

Private recordings require project access. Anyone with a public link can open it.

05 / Capture with care

Your recording. Your call.

Start when you’re ready. Review what’s captured. Decide who can open it.

  1. Record on purpose.

    Start before you repeat the issue. Stop when you’ve captured the steps.

  2. Review what’s captured.

    Input values are masked by default. Other page content can still appear.

  3. Choose who can open it.

    Keep it private to your project, or make it public for anyone with the link.

Explore privacy and access controls
06 / Good to know

Before your first recording.

The essentials on getting started, recording, and sharing.

Can I try it before signing up?

Yes. Install the extension and try a recording in desktop Chrome. You’ll need an account to save recordings to a workspace and share them.

Do I need to write any code?

No. Start recording, repeat the issue, then stop. Your teammate can replay the steps and inspect the affected elements in the recording.

Does it record all my browsing?

No. You choose when to start and stop a recording. Start before you repeat the issue; actions from before recording began aren’t included.

Who can open a recording I share?

Private recordings are available to your project members. Make a recording public and anyone with the link can open it. You can make it private again to turn off public-link access.

Does it fix bugs or create finished tests?

Samelogic gives your teammate or AI agent the recording and context to investigate. Fixes still need verification. If you export test code, review it and add the setup, test data, and checks your application needs.

What does the free plan include?

Start with short recordings and a workspace to review them. See the current recording length, storage, and sharing limits on the pricing page.

  1. Record
  2. Inspect
  3. Share

Record the steps.Share the story.

Give your teammate the steps, the affected elements, and your notes in one recording.

Add to ChromeSee plans and limits

Free extension for desktop Chrome. Try it before signing up.