- How do I share an internet speed test result?
- Run the test, open Results, and choose Share result. On browsers that support the Web Share API, this opens the device share sheet with an editable result URL. New links keep the encoded values in the URL fragment, which is not sent to SwiftSpeedTest in the normal HTTP request. Otherwise, SwiftSpeedTest attempts to copy the link. You can also download a PNG card or single-result JSON file.
- Is a SwiftSpeedTest share link verified?
- No. The URL contains editable result values and is not cryptographically signed or server-attested. When someone opens it, SwiftSpeedTest labels the values as unverified and recommends a new test before using them as evidence.
- What information appears in the downloaded PNG card?
- The card shows download, upload, idle latency, jitter, the worst retained loaded-response value when available, the test time, and a measurement-quality label. It omits the provider, custom location, and test-server identifiers.
- What does the single-result JSON export contain?
- It contains the measured metrics, loaded-response diagnostics when retained, transfer-confidence counts, connection and use-case categories, method links, limitations, and an explicit verification state. Provider, custom location, and server identifiers are excluded.
- Does sharing upload my saved history?
- No. Recent history remains in local browser storage. A share action sends only the chosen link through the browser share sheet, while PNG and JSON files are generated on the device. A full history export happens only when you explicitly request it.
- Can one result prove my ISP is underdelivering?
- No. One browser result is affected by the device, Wi-Fi, background traffic, endpoint conditions, route, and time. For an ISP discussion, collect several controlled wired tests across relevant times and compare the median with the plan and Broadband Consumer Label values.
- Should I send a screenshot or JSON file to ISP support?
- The PNG is convenient for a ticket or message. The JSON preserves more measurement and confidence detail. For a stronger case, keep both, record the device and test conditions separately, and include repeated results rather than relying on one run.