
Common ports for RTSP MJPEG ONVIF and WebRTC cameras
Ports help locate a camera service, but they do not identify a valid stream by themselves. Vendors can move services, require TLS or use a path that matters as much as the port.
Printer Tools communicates with supported printers and cameras through local protocols. Keep devices private, preserve credentials and use the current compatibility matrix as the authority for model-specific capabilities.
RTSP and RTSPS
RTSP commonly appears on TCP port 554, while secure RTSPS uses vendor-specific ports. Supported Bambu RTSPS cameras use their model-specific local route rather than a generic external-camera guess.
MJPEG and snapshots
MJPEG and JPEG snapshots often use HTTP or HTTPS on ports such as 80, 443 or 8080. The required path can be /stream, /video, a CGI route or something completely different.
ONVIF discovery and media
ONVIF discovery uses WS-Discovery on the local network, while device services and media profiles use HTTP endpoints that advertise their actual URLs. A guessed port cannot replace discovery metadata.
WebRTC negotiation
WebRTC does not reduce to one fixed media port. Signaling, ICE, STUN or TURN and dynamically selected transport all matter. Use the supported printer integration instead of inventing a URL.
Local troubleshooting checklist
- Check vendor documentation.
- Discover services on the trusted LAN.
- Verify scheme, host, port and path.
- Do not expose guessed ports publicly.
Frequently asked questions
Is port 554 always RTSP?
No. It is common, not guaranteed.
Can an ONVIF camera still use RTSP?
Yes. ONVIF can advertise an RTSP media profile.
Which port does WebRTC use?
It depends on signaling and negotiated ICE candidates rather than one universal port.





