Better evidence for UI bugs
Demonstrate timing, motion, focus, and state changes that a static screenshot can miss.
Video bug reports
Add a focused video link to a bug report
Show the starting state, exact trigger, and unexpected result without asking a reviewer to watch unrelated setup or download the raw recording.
No account required for the basic flow.
Direct answer
Direct answer
Record one clean reproduction with safe test data, trim the clip to the starting state, action, and visible result, and paste the Save Replay watch link beside environment details, written steps, expected behavior, and actual behavior. The video demonstrates the bug; the text keeps it searchable and reproducible.
The workflow
From source video to useful link
- 1
Prepare a safe test state
Use dummy data, hide notifications, and remove secrets before recording the reproduction.
- 2
Trim to one defect
Keep the initial state, trigger, and result while removing exploration and waiting.
- 3
Write around the link
Add environment, steps, expected and actual behavior, then point to the important moment.
Why it works
Use video for behavior and text for durable context
Motion, timing, focus changes, animation, and transient UI states can be easier to understand in a short recording than in several screenshots. A focused clip lets a developer replay the precise transition without searching through an entire support session.
The recording should support the issue rather than replace it. Keep exact error text, versions, logs, input values, and reproduction steps in writing, and explain beside the link what the reviewer should notice and when it occurs.
Safer, shorter review
Remove unrelated desktop activity and verify the chosen access mode before submitting the report.
Current product details
What to know before you upload
- Accepted sources
- MP4, MOV, M4V, and WebM files that your browser can decode and prepare.
- Free limits
- 10 minutes per clip, 512 MB per prepared upload, and 10 clips per day.
- Account requirement
- No account is needed for the basic upload, trim, share, or watch flow.
- Privacy behavior
- New clips are public by default. Public and unlisted links can be forwarded; private clips require a verified owner.
Limits can vary by plan or deployment. See the current pricing page for the limits shown by this service.
Evidence and next steps
Read the detailed workflow
Use the deeper guides and current primary pages behind this feature. External product conditions can change after review.
Questions for this workflow
Can I add the link to a GitHub issue?
Yes. Paste the watch URL beside written reproduction steps and tell reviewers what to notice at the relevant time.
Should I use unlisted for a private repository?
Unlisted avoids intentional search discovery but remains forwardable. Use password protection if a shared secret is appropriate, and never record repository secrets.
Can video replace logs and error text?
No. Keep machine-readable details in text so they can be searched, copied, compared, and referenced without replaying the video.
What should I remove before upload?
API keys, tokens, customer data, private tabs, notifications, clipboard overlays, unrelated terminal output, and anything outside the defect.
Need product help or more detail about how clips are handled? Visit Support and read the Privacy Policy.
More ways to share
Related Save Replay workflows
Product facts reviewed July 19, 2026. Explore every Save Replay feature and workflow.
Choose the moment you want to share
Preview locally, trim the useful range, and get one link for the prepared clip.
Start with your video