Frequently Asked
Questions
Before you can submit and manage a domain name in the console, it must be registered (with the relevant government authority). The domain name has a character limit of 29 and uppercase letters are not currently supported. Please enter a lowercase domain name address that does not exceed 29 characters. For details, please refer to Domain Names Management .
The playback domain name and push domain name must be two different domain names. However, you can use subdomains to differentiate them.
Example: Use 123.abc.comfor pushing streams and 456.abc.comfor playback.
Although RTMP is not particularly dominant in the entire live streaming landscape, it is the leading protocol for pushing streams from the "streamer" to the "server". Currently, most video cloud services in China primarily use RTMP as the main push protocol (since the first functional module of a live streaming SDK is for stream pushing, it is often called an RTMP SDK).
Common live streaming protocols currently include RTMP, FLV, HLS, and WebRTC.
- RTMP: A versatile protocol suitable for both pushing and streaming. It works by splitting large video and audio frames into smaller packets for internet transmission and supports encryption, offering good privacy. However, the packet splitting/assembling process is complex, which can lead to stability issues under high concurrency.
- FLV: Promoted by Adobe, this protocol has a simple format, adding only header markers to large video/audio frames. This makes it mature for low latency and high concurrency. Its main drawback is limited support in mobile browsers, but it is very suitable for mobile apps.
- HLS: An Apple solution that segments video into 5-10 second chunks managed by an m3u8 index file. As clients download complete chunks, playback is smooth, but this introduces significant delay (typically 10-30 seconds). Compared to FLV, HLS has excellent support in iPhone and most Android mobile browsers, making it common for link sharing (e.g., in QQ/WeChat).
- WebRTC: Stands for Web Real-Time Communication. It's an API supporting real-time audio/video communication within web browsers. It was open-sourced in 2011 and is a W3C standard. "Fast Live Streaming" uses WebRTC, offering an ultra-low latency experience (millisecond level) compared to traditional protocols, ideal for scenarios like online education, sports streaming, and live quizzes.
New users activating the live streaming service receive a free 20GB traffic package for standard live streaming within China, valid for one year. The default billing method is pay-as-you-go (daily settlement). Traffic used for testing standard live streaming playback will be deducted from this package; usage beyond the package is billed daily. Value-added features (e.g., watermarking, transcoding, recording, screenshot, content moderation) are disabled by default, can be activated as needed, and billed separately. For detailed billing items, see Standard Live Streaming Billing .
Frequently Asked
Questions
Before you can submit and manage a domain name in the console, it must be registered (with the relevant government authority). The domain name has a character limit of 29 and uppercase letters are not currently supported. Please enter a lowercase domain name address that does not exceed 29 characters. For details, please refer to Domain Names Management .
The playback domain name and push domain name must be two different domain names. However, you can use subdomains to differentiate them.
Example: Use 123.abc.comfor pushing streams and 456.abc.comfor playback.
Although RTMP is not particularly dominant in the entire live streaming landscape, it is the leading protocol for pushing streams from the "streamer" to the "server". Currently, most video cloud services in China primarily use RTMP as the main push protocol (since the first functional module of a live streaming SDK is for stream pushing, it is often called an RTMP SDK).
Common live streaming protocols currently include RTMP, FLV, HLS, and WebRTC.
- RTMP: A versatile protocol suitable for both pushing and streaming. It works by splitting large video and audio frames into smaller packets for internet transmission and supports encryption, offering good privacy. However, the packet splitting/assembling process is complex, which can lead to stability issues under high concurrency.
- FLV: Promoted by Adobe, this protocol has a simple format, adding only header markers to large video/audio frames. This makes it mature for low latency and high concurrency. Its main drawback is limited support in mobile browsers, but it is very suitable for mobile apps.
- HLS: An Apple solution that segments video into 5-10 second chunks managed by an m3u8 index file. As clients download complete chunks, playback is smooth, but this introduces significant delay (typically 10-30 seconds). Compared to FLV, HLS has excellent support in iPhone and most Android mobile browsers, making it common for link sharing (e.g., in QQ/WeChat).
- WebRTC: Stands for Web Real-Time Communication. It's an API supporting real-time audio/video communication within web browsers. It was open-sourced in 2011 and is a W3C standard. "Fast Live Streaming" uses WebRTC, offering an ultra-low latency experience (millisecond level) compared to traditional protocols, ideal for scenarios like online education, sports streaming, and live quizzes.
New users activating the live streaming service receive a free 20GB traffic package for standard live streaming within China, valid for one year. The default billing method is pay-as-you-go (daily settlement). Traffic used for testing standard live streaming playback will be deducted from this package; usage beyond the package is billed daily. Value-added features (e.g., watermarking, transcoding, recording, screenshot, content moderation) are disabled by default, can be activated as needed, and billed separately. For detailed billing items, see Standard Live Streaming Billing .