RTSPS (RTSP Secure) is RTSP transported over TLS/SSL — the same encryption technology used by HTTPS. It encrypts the video stream between your camera and viewer, preventing interception on untrusted networks. SmartRTSP supports both standard rtsp:// and encrypted rtsps:// URLs.
Standard RTSP was designed for local trusted networks where interception is unlikely. As cameras are increasingly accessed over the internet or shared corporate Wi-Fi, TLS encryption provides the confidentiality guarantee that plain RTSP cannot. RTSPS uses the same RTSP commands and video encoding — only the transport layer is encrypted.
RTSP vs RTSPS
| Property | RTSP | RTSPS |
|---|---|---|
| Encryption | None — plaintext | TLS/SSL |
| URL scheme | rtsp:// | rtsps:// |
| Default port | 554 | 322 (varies — check camera docs) |
| Ideal use case | Local trusted network | Remote / untrusted networks |
| Camera support | Universal standard | Select enterprise/pro models |
| Performance | Standard | Slightly higher CPU (TLS decryption) |
When to Use RTSPS
-
✓
Accessing cameras over public Wi-Fi or the internet without a VPN. On an open or shared network, unencrypted RTSP traffic can be intercepted with basic packet capture tools. RTSPS prevents this.
-
✓
Corporate networks with security policies. Many enterprise networks inspect or block unencrypted traffic. RTSPS passes through TLS-aware firewalls the same way HTTPS does.
-
✓
Cameras with sensitive content — nurseries, private spaces, high-value areas. When the stakes are high, encryption ensures only authorised viewers can decode the stream.
-
✓
When a VPN is not available or practical. RTSPS provides transport-layer security without requiring a separate VPN infrastructure.
When Standard RTSP is Fine
Your home router creates an isolated private network. Traffic between your camera and iPhone on the same LAN never touches the internet. Standard rtsp:// is perfectly secure in this scenario.
If you're already connecting via WireGuard or OpenVPN, your RTSP stream travels inside the encrypted VPN tunnel. Additional TLS via RTSPS is redundant — standard rtsp:// is the right choice here.
RTSPS URL Format
Port 322 is the IANA-assigned port for RTSPS, but many cameras use port 554 for both RTSP and RTSPS, differentiating them only by the URL scheme. Always check your camera's documentation to confirm which port RTSPS uses on your specific model.
Which Cameras Support RTSPS?
RTSPS support is primarily found in enterprise and professional-grade cameras. Most consumer cameras do not implement TLS at the RTSP layer.
- ✓Axis cameras — full RTSPS support across most models; configurable in web UI
- ✓Bosch cameras — full RTSPS support on professional and IP Starlight series
- ✓Hikvision — select enterprise models; check device specs
- ✓Dahua — select professional models; check device specs
- —Reolink — RTSP only; use VPN for secure remote access
- —TP-Link Tapo — RTSP only
- —Eufy — RTSP only (where RTSP is supported)
- —Wyze, Foscam, Amcrest, Annke, Lorex — RTSP only
How to Enable RTSPS in SmartRTSP
SmartRTSP handles TLS negotiation automatically — no extra configuration is required beyond using the correct URL scheme.
-
1
Use
rtsps://instead ofrtsp://in the URL field. Tap + → Manual Entry → enter the URL beginning with rtsps://. -
2
Adjust the port if needed. Check your camera's documentation. Common choices are port 322 or 554 for RTSPS — these vary by manufacturer and model.
-
3
SmartRTSP handles TLS automatically. The app detects the rtsps:// scheme and performs TLS negotiation transparently. No certificates to install manually.
Certificate Handling
IP cameras that support RTSPS typically use self-signed TLS certificates — certificates generated by the camera itself rather than issued by a public Certificate Authority. Standard TLS clients reject self-signed certificates by default, which would prevent connection to most cameras.
SmartRTSP accepts self-signed certificates that are common on IP cameras. This means you can benefit from stream encryption without needing to provision a CA-signed certificate on your camera. The stream content is still encrypted end-to-end — self-signed only means the certificate issuer is unverified, not that encryption is absent.
If your camera's RTSPS certificate is issued by a known CA (common in enterprise deployments), SmartRTSP also validates it correctly. Self-signed acceptance only applies when the camera presents a self-generated certificate.
Frequently Asked Questions
Is RTSPS the same as HTTPS?
Does RTSPS affect video quality?
My camera doesn't support RTSPS — how do I secure my stream?
rtsp:// stream travels over the encrypted VPN tunnel. This is the recommended approach for most consumer cameras that do not support RTSPS.
Is RTSPS needed on a local home network?
rtsp:// is fine.