For QA testers
Screen recorder for QA testers
Last updated
Fastest way: record it right here — no install, no signup.
Captures the bug, the developer console, your narration, and turns the whole thing into a transcript + shareable link + ask-the-video chat.
Pick how you want to record
iOS and Android don't allow screen capture in browsers. Use your camera to record.
Click to start recording
Saving your recording…
Uploading video…
Recording saved!
Your link is ready. Free hosting for 30 days.
Email me this link
Free recordings are kept for 30 days. We'll email you a copy and a reminder 3 days before it is deleted.
This link expires in 30 days. Pro adds SOP export, 90-day+ retention, and password protection.
+ Embed in Notion, Slack, or your site
More archive tools
Pullsy also ships free browser-only tools for archiving the rest of your online content.
Two QA workflows.
Recording bug reports is the QA workflow where Pullsy's transcript and ask-the-video chat do the most work.
A repro that takes 45 seconds to trigger and 4 minutes to explain
You found a bug. It takes 45 seconds of clicking through a flow to trigger, and you need to narrate what you are doing, what you expected, and what happened. Pullsy records the browser tab including DevTools (so the console errors are visible), your narration (which becomes the transcript), and the screen state. The developer gets a shareable link. They can watch the 5-minute repro, or read the transcript in 30 seconds, or ask the video 'what does the network panel show at 2:14?' and get a timestamped answer. The Jira ticket that used to be a 200-message Slack thread is now a single link with comments.
A visual regression that needs before/after comparison
You recorded the same flow on the previous build and on the new build. Both Pullsy links are in the bug ticket. The developer opens both, sees the visual difference without re-running the test, and the AI-generated chapter markers on each video jump to the moment the bug appears. Two recordings, one verdict.
Frequently asked
Should I include the developer console in the recording?
Yes, if it is relevant. The console errors at the moment of the bug are usually the most useful artifact for a developer — they tell the dev exactly which line of code threw, what the network response was, and what the JS state was. The Pullsy recorder captures the whole tab, so anything in DevTools is included. For purely visual bugs (a layout glitch, a misaligned button), the console is noise — close it before recording to keep the video clean.
How long should a bug-report recording be?
The best bug reports are 30 seconds to 2 minutes. Long enough to show the reproduction, short enough that the developer watches the whole thing. Pullsy's free tier has no time cap, but a 14-minute rambling recording gets skipped. The right structure: 5 seconds of context, 15–60 seconds of the actual repro, 5 seconds of expected vs actual. Pullsy's auto-chapters will segment the recording for you, so even if you ramble, the developer can skip to the relevant chunk.
Can the developer reply with a video?
Pullsy does not have a video-reply feature, but the developer can: (1) leave a text comment on the share page, with a timestamp attached, so the comment is anchored to a moment in the video; (2) record their own Pullsy video in response and share the link back; (3) react with an emoji on the share page. The ask-the-video chat is the most useful: a developer who cannot reproduce the bug locally can ask the video 'show me what happened at 1:14' and get a clickable timestamp back.
Try the recorder above.
Same flow for visual regression reports, accessibility audits, and product feedback videos.