tencent cloud

Cloud Streaming Services

Release Notes and Announcements
Announcements
User Guide
Product Introduction
Overview
CSS Products
Concepts
Features
Use Cases
Strengths
Use Limits
Purchase Guide
Billing Overview
Basic Service Fee
Value-Added Service Fee
Prepaid plan
Purchase Process
Changing Billing Modes
Refund Policy
Viewing Bills
Renewal
Processing for Overdue Payments
Billing FAQs
Live Video Broadcasting (LVB)
Overview
Use Cases
Getting Started
SDK Integration
Live Event Broadcasting (LEB)
Overview
LEB Versus LVB
Use Cases
Getting Started
SDK Integration
Live Video Caster
Overview
Application Scenarios
Feature Area Introduction
Managing Live Video Caster
General Cloud Director
Configuring Program Lists and Automated Broadcasting
Console Guide
Console Overview
Overview
Domain Management
Stream Management
Package Management
AI Features
Feature Configuration
Relay
Billing Usage Statistics
Monitoring
Toolkit
OOTB live
CAM-Based Access Control
Feature Guide
Push and Playback
Features
Practices in Typical Scenarios
Cloud Native Recording
Live Streaming Security
Global CSS Service
Callback Notifications
User Guides for Common Third-Party Tools
SDK Guide
0. SDK Integration Guide
1. Stream Push
2. Playback
3. Advanced Features
API Documentation
History
Introduction
API Category
Making API Requests
Live Pad APIs
Live Stream Mix APIs
Time Shifting APIs
Monitoring Data Query APIs
Billing Data Query APIs
Live Transcoding APIs
Delayed Playback Management APIs
Domain Name Management APIs
Watermark Management APIs
Certificate Management APIs
Stream Pulling APIs
Recording Management APIs
Live Callback APIs
Screencapturing and Porn Detection APIs
Authentication Management APIs
Live Stream Management APIs
Data Types
Error Codes
Ops Guide
Video Stuttering
Troubleshooting Push Failure
Troubleshooting Playback Failure
CLS Assists in Live Stream Troubleshooting
Troubleshooting High Latency
Troubleshooting Poor Quality of Pulled Video
Authorizing CSS to Store Screenshots in a COS Bucket
Troubleshooting
Live Stream Mixing Error `InvalidParameter.OtherError`
About Pushing
Generating Push URLs
PC Push
Playing Method
Web Player
Live Streaming Quiz
FAQs
Service Region
Live Streaming Basics
Push and Playback
CSS Billing
Global CSS Service
Live Recording
On-Cloud Stream Mix
Domain Configuration
Related to Live Video Caster
Compatibility with Apple ATS
Difference Between Stream Interruption and Stream Suspension
SLA
CSS Service Level Agreement
CSS Policy
Privacy Policy
Data Processing And Security Agreement
Glossary

RTMPS Push Streaming

PDF
Focus Mode
Font Size
Last updated: 2025-07-10 16:24:37
Tencent Video Cloud continuously improves its streaming media transmission to cater to various requirements. Apart from the common RTMP streaming protocol, it also now supports the RTMPS streaming protocol, which specifically caters to users with encryption needs, particularly those with overseas operations. This article primarily focuses on the implementation of RTMPS streaming.

Comparison of Advantages

Standard RTMP streaming protocol relies entirely on adding relevant parameters to the URL for authentication, with the RTMP server carrying out verification based on these parameters. However, this does not encrypt transmitted audio and video data packets, hence, captured and decoded RTMP packets can be played.
The RTMPS protocol effectively resolves these RTMP security issues. It is the SSL-encrypted version of the RTMP protocol, which enhances the security of data communication, allowing safe stream transmission between the encrypted encoder and CDN.
Comparison chart of various streaming protocols:
Protocol
Protocol Type
Transmission Method
Delay
Protocol Characteristic
Application Scenario
Tencent's Optimization Scheme
RTMPS
Streaming Protocol
TCP

-

Encryption

Encryption scenarios
Supporting multiple domains and certificates
SRT
Streaming Protocol
UDP
500 ms-1s
Low latency, packet loss resistance
OTT, cross-regional transmission
-
WebRTC
Streaming Protocol
RTP
200 ms-1s
Low latency
Audio and video calls
Optimizing instant loading and stuttering in Live Event Broadcasting
QUIC
Streaming Protocol
UDP
-
Packet loss resistance, 0rtt
Browser access
Optimizing the first frame transmission

Notes

The RTMPS streaming protocol, which employs SSL encryption, demands the configuration of a push domain name certificate; at present, the default push domain name 'push.tlivecloud.com' of Cloud Streaming Services has been equipped with a common certificate. For other domain names, you need to Submit a Ticket to provide the domain name and corresponding certificate for configuration.
Note:
If you wish to test the RTMPS streaming, you can connect the default push domain name by Cloud Streaming Services.
If you need to use the RTMPS streaming through your own domain, you need to Submit a Ticket providing the domain name and corresponding certificate.

RTMPS Streaming

1. The generation of live streaming URLs can be carried out in the following two methods:
Assemble independently through splicing rules. For detailed operations, please refer to Splicing Live Streaming URLs.
1.1 Go to Tools > Address Generator in the CSS console, select the URL type as Push Address, and select a domain name as needed. For detailed operations, refer to the Address Generator documentation > Address Generator.

2. Modify the generated RTMP live streaming URL into RTMPS, input it into OBS to start RTMPS streaming. For detailed operations, please refer to Push via OBS.


Live Playback

Operate according to the normal live playback process. For more details, please refer to Live Playback.


Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback