How to record a bug reproduction on a shared computer

A bug can be hard to explain in a chat message, especially when it happens only after a particular sequence of clicks. A short recording can show the steps, the unexpected result, and what the person using the computer saw.

On a shared team computer, the recording can also expose names, messages, customer details, or sign-in information. Prepare the desktop first, then use the Screen Recorder to capture only what your teammates need to see.

Record the bug reproduction

Open the Screen Recorder on the shared computer. It works on computers, not phones. Decide whether you need to record a screen, a window, or a browser tab.
Prepare a safe example. Sign in with an approved test account if one is available, and use sample data rather than real customer or employee information. Close unrelated documents, messages, and browser tabs.
Select the area that contains the problem. Choose a single window or tab when the bug is confined to it. Choose a screen only when the reproduction needs to show activity across multiple windows.
Start the recording, then reproduce the bug once at a steady pace. Include the action that triggers it and pause briefly when the unexpected result appears. If narration will help, allow microphone access when your browser asks and explain what you expected to happen.
Stop the recording using the control shown in the recorder. Play it back before sharing. Check that the result is visible, the audio is understandable if you used it, and no private information appears in the clip.

If the browser asks you to confirm which screen, window, or tab to share, check the selection carefully. The selected area is what the recording can show, so do not choose a whole screen just because it is the first option.

Choose what to capture

A browser tab

Use a tab when the issue happens in a website and the other open tabs are not relevant. This keeps the recording focused and makes it less likely that unrelated windows will appear. If the bug involves a link opening another tab or a browser-level prompt, a single-tab recording may miss part of the behavior.

A window

Use a window when the bug occurs in a desktop app or when you need to show more than one page within the same app. Check the edges of the window before recording. A notification or private item visible over the window can still end up in the clip.

The whole screen

Use a screen when the problem depends on switching between apps, moving a file between windows, or using more than one display. This captures the most context, but it can also reveal other open windows and pop-up notifications. Close anything unrelated before you begin.

Sound, microphone, and camera

Include sound if the bug involves an alert, playback, or another audible result. Use the microphone to add a short explanation when it saves your teammate from guessing what you did. A camera is optional, and usually unnecessary for a software bug. The browser will ask for permission when you use the microphone or camera.

Make the clip easy to reproduce

A useful clip shows a small, repeatable sequence rather than a long session. Begin with the page or app in the state needed to start. Move the pointer deliberately, wait for loading to finish, and avoid clicking extra controls while the result appears. If the issue takes several attempts, record one clear example instead of making the clip difficult to follow.

Show the starting point. Include enough of the page or window to identify where the steps begin, without exposing unrelated information.
Show the exact action. Make the relevant click, selection, or key press visible. If timing matters, pause before and after the action.
Show the unexpected result. Leave the error message or changed screen visible for a moment so someone reviewing the clip can read it.
Say what should have happened. If you narrate, state the expected result and what happened instead. Do not read out passwords, access codes, or private records.

When you send the clip, add a short note with the app or page, the steps to reproduce the problem, and whether it happens every time. Mention anything that may affect the result, such as a specific account role or a particular browser. A recording illustrates the issue, but it does not replace those details.

Protect information on a shared computer

Before recording, look for email addresses, chat previews, saved credentials, internal dashboards, and browser autofill suggestions. Use a test account or dummy information when possible. If a real record must be shown, follow your team’s rules for handling it and share the recording only with the people who need it.

Notifications can appear even when you are focused on another app. If your workplace policy allows it, pause them for the recording: on Windows 11, open Settings › System › Notifications; on macOS, open System Settings › Notifications. On a managed computer, ask the administrator before changing settings. You can also close the relevant apps or wait until you can record in a clean test session.

The Screen Recorder runs in your browser, and the recording stays on the device. Store or share the resulting file only through a location approved by your team.