Skip to main content
SwiftSpeedTest
Speed TestQualityStabilityBufferbloatPlan auditCalculatorProvider testsDataSlow InternetGuides
Speed TestQualityStabilityBufferbloatPlan auditCalculatorProvider testsDataSlow InternetGuides

Save, share, and document

Share internet speed test results without hiding the caveats

Run a full browser measurement, open your device share sheet, or download a privacy-safe PNG card or structured JSON record. Every format states what the result proves, what it omits, and when another test is needed.

Native sharingPNG result cardStructured JSONLocal generationEditable-link warning
Privacy default: the PNG and single-result JSON are generated in your browser and omit provider, custom location, and server identifiers. A share link includes only the context you explicitly added and keeps its editable values in the URL fragment, outside the normal HTTP request. Recipients and sharing services can still read the complete link.

Test Your Internet Speed

Measure your connection's download speed, upload speed, and latency

Optional context is saved with recent results and included only if you copy a share link.

Low-data measurement

Active because the browser cannot report connection quality. The time- and byte-bounded run requests at most about 52 MiB of test payload, and usually less. Protocol overhead may add a little more.

Test endpoint

Default Server - Nearest Location

Same-origin hosted endpoint

Endpoint readiness unavailable

Default endpoint is ready.

For the most accurate results, close other apps and devices using your network

Choose the right artifact

Four formats for four different jobs

A convenient image, a reproducible record, and a support history do not carry the same evidence. Pick the smallest artifact that preserves what the recipient actually needs.

Native share sheet

Sends an editable result URL through the browser's share interface. New links encode values in the URL fragment so the normal request to SwiftSpeedTest does not contain them. The complete link can include any provider or custom-location context you chose to add.

Caution: Recipients, browser history, extensions, and sharing services can still read the complete link. The values are not signed or independently verified.

PNG result card

Generates a 1200 by 630 image locally with the core result, loaded response when available, measurement label, and test time.

Caution: Provider, custom location, and server identifiers are deliberately omitted.

Single-result JSON

Preserves the exact metrics, responsiveness diagnostics, transfer confidence, method links, verification state, and limitations.

Caution: It is a transparent browser record, not a cryptographically signed certificate.

History JSON or CSV

Exports repeated local runs for longitudinal analysis, support discussions, or your own spreadsheet workflow.

Caution: Review the full history export before sharing because it can contain context you entered.

Need a repeated record instead of one result? Use the private internet performance history to import, filter, analyze, and export up to 100 local runs.

Better evidence for support

Build a result that someone else can interpret

  1. 1. Control the run

    Use one device, pause avoidable traffic, record Wi-Fi or Ethernet, and keep the endpoint consistent.

  2. 2. Preserve context

    Record the room, device, plan, and test time separately when they matter. The privacy-safe downloads omit custom labels.

  3. 3. Repeat the test

    One result is a snapshot. Collect several comparable runs across relevant times before claiming a persistent shortfall.

  4. 4. Compare carefully

    Use the median of eligible runs and the plan-audit workflow instead of treating a single image as provider proof.

Audit speed against your planCompare two measured runs
Published by Swift Speed Test. See our testing method, sourcing standards, limitations, and corrections policy.

What the downloads deliberately exclude

The PNG and single-result JSON do not contain the provider, custom location, server ID, server label, or server location. This reduces accidental disclosure when a file is attached to a ticket, message, or public post.

What no export can establish

A browser result does not isolate every bottleneck or prove contractual compliance. Device limits, Wi-Fi, competing traffic, routing, endpoint behavior, and the measurement method remain part of the interpretation.

Frequently asked questions

Speed test result sharing questions

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.

Speed benchmarks topic cluster

More speed-test benchmarks and explainers

Continue with the most relevant explainers from this topic.

  • Internet speed test results explainedRead download, upload, ping, and jitter together instead of relying on one big Mbps number.
  • Internet connection diagnostic reportRun a full browser measurement and export a privacy-safe support report with loaded response, confidence signals, next steps, and a controlled retest protocol.
  • Internet quality testRun one test for gaming, HD video-call, 4K-streaming, and large-upload readiness using capacity, loaded latency, jitter, and HTTP probe misses.

© 2026 SwiftSpeedTest. All rights reserved.

Open dataShare resultsWebsite widgetSupport reportProvider testsSpeed historyPlan auditCompare resultsQuality testStability testBufferbloat testGaming testStreaming testWork-from-homeSlow internetWi-Fi vs EthernetGood speed resultsSpeed calculatorHow it worksGuidesRSS feedPrivacyTerms