Does the developer need a Pixelmatic account to watch?

No. Published recordings get a public share link. Anyone with the link can open it in their browser. No sign-up, no app, no login required. Just a link.

What if a bug report is sensitive?

Mark the recording private. It stays visible to you alone until you add people, and you choose exactly who. The rest of your team can't see it, and it stays out of their search. If the person who needs it isn't on your team, you can hand them a magic link that opens without an account, and revoke it later. Team-visible is still the default; private is built for the rare moments when something needs to stay that way.

Can I record screen and voice at the same time?

Yes. Pick the screen + camera mode (or screen + audio only). Your microphone captures your commentary while the screen shows the repro. The transcript covers everything you said.

What if I need to record a native app, not a browser?

You can share any window or your entire screen, not just a browser tab. The recorder captures whatever's on screen, native apps included.

Is there a recording time limit?

No. Recording is unlimited on the free tier as long as you're fine with saving locally. Cloud publishing limits depend on your plan, but the recording itself has no length cap.

Can the whole team share a library of past repros?

Yes. On any team plan, every published recording goes into the shared org library. Your team can search across all bug recordings by what was said, which is useful for spotting recurring issues.

Pixelmatic

Start recording, free

Bug reports

Show the bug.
The captions explain it.

Record the repro in your browser, publish it, paste the link into the ticket. The transcript captures what you said while it was happening. Your developer sees it without a Zoom call.

Start your team's 14-day trial Try the recorder, free

Free account. No card. No install.

The problem

Writing a bug report is hard.
Showing one takes fifteen seconds.

Three paragraphs. Still needs a demo call.: You describe the bug in precise detail. You attach a screenshot. The developer still comes back with "can you just show me?" The written format doesn't carry the context.
The bug only reproduces under very specific conditions.: "Click here, then scroll, then open the modal in less than two seconds, then resize." Writing that down accurately is genuinely hard. Showing it takes fifteen seconds.
Sydney reports it. Amsterdam fixes it. Nobody's awake at the same time.: Async bug handoffs collapse when the only artifact is a ticket. The developer needs to watch the repro, not reconstruct it from notes.
The ticket gets reassigned. The context disappears.: The new person picks up a bug with three sentences of notes and has to start from scratch. The original reporter has moved on.

How Pixelmatic helps

The bug report is the recording.

Record where the bug lives: Most bugs are in the browser. The recorder is in the browser. No screen mirroring, no capture software, no extra steps. Reproduce the bug, hit record, show it.
What you said becomes searchable text: Every recording is automatically transcribed, published or not. Walk through the bug out loud ("so here I click this, and you can see the state doesn't update") and that becomes a searchable caption alongside the video.
Paste a link. No account required to watch.: Publish, copy the link, paste it into Linear or Jira or Notion. The developer opens it in their browser. No Pixelmatic account, no login, no "open in app" prompt. Or keep the recording private and share it with only the people you pick. The choice is yours.
Recordings save locally first: The recording saves to your device before anything uploads. You won't lose a repro to a network hiccup or a failed upload. Cloud sync is a separate, retryable step.

Where this pays off

Bugs worth recording.

Reproducing a bug that only shows under specific user flows
Cross-timezone handoffs between QA and engineering
Attaching a repro to a Linear, Jira, or GitHub issue
Escalating a customer-reported bug with visual proof
Tagging a repro with its ticket number or bug category so you can find it months later
Building a library of past bug repros for pattern matching

Frequently asked questions.

Try it on your next ticket.

Free account. No install. The whole thing takes about as long as the repro.

Try the recorder, free Start team trial

Show the bug.The captions explain it.