RELY GUIDES
How to write a bug report with a screen recording
Show the steps to reproduce a website bug, explain expected versus actual behavior, and give developers the context they need without sharing sensitive data.
Show the smallest sequence that reproduces the issue
A useful bug recording shows how the problem happens, not just the broken result. Begin one step before the issue appears. If a menu stops responding after a filter changes, show the filter change and then the menu click. Avoid a long tour of unrelated pages.
Try reproducing the issue once before recording. Note whether it happens every time or only sometimes. If you cannot reproduce it again, say so. A single occurrence can still be useful evidence, but it should not be described as a consistent failure.
Explain expected and actual behavior
While recording, say what you are trying to do and what you expect to happen. Then show the actual response. For example: “I choose the monthly plan and click Continue. I expect the payment page, but the button becomes disabled and the page stays here.” Keep the explanation factual; there is no need to guess the underlying technical cause.
Include the page URL, browser, device type, and any relevant error text in the accompanying report. Remove private query parameters, account tokens, and personal details from URLs before sharing them. If the issue depends on a particular account role, describe the role without sending credentials.
Use this report structure
Title: Checkout does not open after selecting the monthly plan. Steps: Open pricing, select monthly, then click Continue. Expected: A checkout page opens. Actual: The button becomes disabled without navigation. Frequency: Three attempts in the same browser. Context: Desktop Chrome; signed-in customer. Evidence: The recording shows the click and the result.
Replace those example details with what you actually observed. Add a timestamp if the relevant moment occurs partway through the recording. For visual problems, explain which element is affected and what makes the result unusable, rather than only saying that it looks wrong.
Record and review with Rely
The person investigating the issue can create a Rely recording request and send you a link with instructions. Open it in desktop Chrome or Edge, choose the screen or window to share, and narrate the reproduction steps if useful. A camera is optional, and guests do not need an account.
Review the take before submitting. Check that the important interaction is visible and that the recording does not contain passwords, payment information, private messages, or unrelated customer data. If it does, record a clean take. Trimming the beginning or end will not remove something visible in the middle.
Keep follow-up attached to the evidence
After submission, the requester can review the video and leave timestamped comments. Use a specific question such as “At 0:18, was the filter already selected before the page loaded?” to resolve missing details. Rely also supports accompanying notes and bug details, so the URL and expected behavior can sit alongside the recording.
Free includes one submitted recording total, up to three minutes. Pro supports additional three-minute recordings within the workspace and request limits. A short, focused reproduction is usually easier to investigate than several unrelated issues in one take.