How to Take a Screenshot of a Speed Test on a PC
Taking a screenshot of a speed test on a PC is useful when documenting broadband performance for an ISP, comparing Wi-Fi with wired results, or reporting a connection issue. However, screenshots can be unclear, incomplete, or misleading when the test page has not finished, the wrong window is captured, or private details remain visible. This guide explains how to capture speed test results on Windows and macOS, examines common causes of poor screenshots, shows how to verify the evidence, and suggests practical ways to improve both screenshot quality and the accuracy of download, upload, and latency measurements.
What a Speed Test Screenshot Should Show
A useful screenshot should clearly display the completed download speed, upload speed, and latency or ping result. It should also show enough of the test page to identify that the result came from a speed test rather than a manually typed value. If the test identifies the ISP, server, connection type, or time of testing, those details can provide helpful context.
Before capturing the screen, wait until the test has fully completed and all key measurements are stable. Avoid taking a screenshot while the speedometer is still moving because the displayed values may change or the result may not yet be recorded.
How to Take a Screenshot on Windows
On Windows, open the speed test in a browser and wait for the final result. Press Windows + Shift + S to open the Snipping Tool overlay, then drag around the result area. The image is copied to the clipboard, where it can be pasted into an email or saved from the Snipping Tool. You can also use PrtScn to capture the screen or Windows + PrtScn to save a full-screen image in the Pictures and Screenshots folder.
If only the browser window is needed, select the browser with Alt + PrtScn. This usually creates a cleaner image than capturing the entire desktop.
How to Take a Screenshot on macOS
On a Mac, press Command + Shift + 4 and drag around the completed speed test result. For a full-screen capture, press Command + Shift + 3. To capture a specific window, press Command + Shift + 4, then press the spacebar and select the browser window.
macOS normally saves screenshots to the desktop unless the capture settings have been changed. Open the saved image before sharing it and check that the speed values, labels, and any relevant test details are readable.
Common Reasons a Speed Test Screenshot Is Unclear
The test was captured before completion
A partially completed test may show download results but omit upload speed or latency. This happens when the screenshot is taken as soon as the page opens or while the measurement animation is still running. Confirm that the page shows a final result or a completed status before capturing it.
The wrong window or screen was selected
Multiple monitors, browser windows, and application overlays can cause the capture tool to record the desktop, another tab, or only part of the test. Identify the browser window containing the final result and use a selected-area or window capture instead of relying on a full-screen shortcut.
The browser zoom level is too small
A low zoom level can make numbers and labels difficult to read after the image is uploaded or compressed. Increase the browser zoom to around 100% or higher, keep the complete result visible, and avoid cropping important labels from the image.
The screenshot tool saved the image in the wrong place
Windows and macOS may copy an image to the clipboard, save it automatically, or open a preview depending on the shortcut used. If no file appears, paste the capture into an image editor or document and save it manually as PNG or JPEG.
Private information remains visible
A speed test page may display an IP address, location estimate, account name, or server details. These details may not be needed for a basic report. Crop or obscure sensitive information before sharing the image, while keeping the measured speeds and test context visible.
The screenshot does not reflect the connection being investigated
A result captured over Wi-Fi may not explain a problem that occurs only on a wired connection, or a test from a VPN may measure the VPN route instead of the normal ISP route. Record whether the PC used Wi-Fi or Ethernet and whether a VPN, proxy, or traffic-management application was active.
How to Check Whether the Screenshot Is Reliable
Compare the screenshot with the original browser result and make sure the test has finished. Check that the units are clear, such as Mbps, and that download, upload, and latency values are not cut off. Confirm the testing time and connection method if you are sending the image to an ISP or technical support team.
Run the test two or three times under similar conditions rather than treating one result as conclusive. Large differences between tests may indicate Wi-Fi interference, background traffic, a busy local network, or an unstable connection.
Ways to Improve Speed Test Accuracy Before Capturing
- Use an Ethernet cable when possible to reduce Wi-Fi variation.
- Pause large downloads, cloud backups, streaming, and software updates.
- Close unnecessary browser tabs and applications that use bandwidth.
- Place the PC closer to the Wi-Fi router if a wired test is not available.
- Restart the modem or router only when appropriate, then allow it to reconnect fully.
- Disable a VPN temporarily if the goal is to measure the normal ISP connection.
- Use the same speed test service and a similar server when comparing results.
What to Send With the Screenshot
A screenshot is more useful when accompanied by a short test note. Include the test date and time, whether the PC used Wi-Fi or Ethernet, the router or modem status, and whether other devices were using the connection. If the issue affects only certain services, mention that as well.
For ongoing performance problems, provide several screenshots from different times instead of one isolated result. You can also link to the speed test page used for the measurement, provided the link does not expose private account information.