Product guide

SRT Probe

Test SRT connectivity and network quality in sender or receiver workflows.

Updated 2026-07-23 UTC

Overview

Use SRT Probe before deployment or while troubleshooting an SRT path. It can act as a sender or receiver and test Caller, Listener, or Rendezvous connections without handling video or audio.

Key features

Measure RTT, throughput, and packet loss in real time.
Set a target throughput for sender tests and view performance charts.
Configure SRT passphrase encryption and AES key length.
Run connection diagnostics for settings, network information, process status, and Windows Firewall.
Review, copy, save, and automatically record statistics and regular logs.
Save and reuse presets, restore the window state, and optionally start a test automatically.

Installation

Install SRT Probe from the Microsoft Store or the official GitHub release.
Prepare an SRT-compatible peer and confirm the UDP path before starting a test.

Basic configuration

Choose a sender or receiver test mode and match the connection mode at the other endpoint.
Enter the destination or listen port and configure the target throughput for sender tests.
Apply matching passphrase and AES key length settings when encryption is enabled.
Start the test and compare RTT, throughput, and packet loss while the connection is active.
Stop the test and review the summary in the regular log.

Connection modes

Caller connects to the peer address and port.
Listener waits for a caller on the selected port.
Rendezvous requires both endpoints to use matching rendezvous settings.

Main operations

Run one test at a time while comparing the live statistics and the peer's connection state.

System requirements

Windows 10 or Windows 11 on an x64 PC
Network access between the test endpoints
An SRT-compatible peer such as FFmpeg or another SRT application

Checks before use

Match the mode, address, port, and encryption settings at both endpoints.
Allow the selected UDP port through the applicable firewall.
Treat packet loss and throughput results as measurements of the tested path and settings.
Do not include passphrases or private addresses in support requests.

Troubleshooting

Run diagnostics first, then compare the mode, port, firewall state, and encryption settings one at a time. See the common FAQ.