Products >> Portable WebRTC
Portable WebRTC – Lightweight, Embeddable WebRTC SDK for Real-Time Streaming
Happytime portable rtc is developed based on C language and adopts the core technology stack of WebRTC, including SRTP/SRTCP, DTLS, ICE, STUN and other protocols, ensuring the security and real-time communication. At the same time, the project has undergone a lot of optimization and expansion, making it more compact, portable, and supporting more media transmission and sharing functions.
Support multi browser client access to different streams
Support desktop and application window sharing
Support streaming from camera and audio device
Support RTSP / RTMP / SRT stream to WebRTC stream
Support media proxy on-demand connection
Lightweight WebRTC to browser streaming
Key Features of Portable WebRTC
✅ RTSP/RTMP/SRT to WebRTC: Convert legacy streams to browser-compatible WebRTC
✅ Desktop & Window Sharing: Share screen or specific app windows in real time
✅ Camera & Microphone Streaming: Direct device capture to browser
✅ H.265 &
H.264 Support: Full support for H.265/HEVC, H.264, OPUS, G.711 and data channel.
✅ Media File Streaming: Play MP4, AVI, etc., as live stream
✅ Multi-Browser Access: Viewers on Chrome, Firefox, Edge, Safari
✅ On-Demand Media Proxy: Connect only
when needed, save bandwidth
✅ WHIP Ingest: Push streams to any WHIP-compliant WebRTC server
✅ WHEP Playback: Serve streams to any WHEP-compliant client
✅ Cross-Platform: Runs on Windows, Linux, Android, iOS, Embedded Linux
WHIP & WHEP Support
Happytime Portable RTC supports the WHIP (WebRTC HTTP Ingestion Protocol) and WHEP (WebRTC HTTP Egress Protocol) standards for interoperable, standards-based WebRTC streaming.
WHIP Push (Ingest): Portable RTC can push its media streams (RTSP, RTMP, SRT, camera, desktop, or file sources) to any remote WHIP-compliant WebRTC server using a simple HTTP POST with an SDP offer. This enables standards-based contribution to third-party WebRTC media
servers, SFUs, and cloud live-streaming platforms without proprietary signaling.
WHEP Pull (Egress): Other WHEP-compliant clients (browsers, media players, or other servers) can pull streams from Portable RTC using a standard HTTP POST with an SDP offer to a WHEP endpoint. This allows any WHEP client to consume Portable RTC's WebRTC streams without
needing the Happytime signal server or a custom WebSocket signaling protocol.
Advantages of Portable WebRTC
1.Highly customizable:
Happytime portable rtc allows users to customize and extend according to their own needs. Whether it is adding new media transmission protocols or optimizing existing functions, it can be easily achieved.
2.Strong extensibility:
In addition to supporting the core functions of WebRTC, Happytime portable rtc also provides rich extensibility features, such as desktop sharing, application window sharing, audio and video media file transfer, etc. These features can be selected
and combined according to specific application scenarios to meet the needs of different users.
3.High performance:
Happytime portable rtc focuses on performance optimization in design and implementation, using various technical means to reduce latency, improve transmission efficiency and stability. This makes it excellent in real-time communication scenarios.
4.Security:
Happytime portable rtc uses multiple security mechanisms to protect the security of the communication process, including data encryption, authentication, and access control. These mechanisms can ensure that communication content is not leaked or tampered with,
while preventing unauthorized access and attacks.
Use Cases & Applications
Video Surveillance: View CCTV/IPC cameras directly in browser, no plugin
Remote Education: Teacher shares desktop + camera + media files
Live Streaming: Stream from OBS (RTMP) or IP camera (RTSP) to audience
Telemedicine: Share medical imaging + video call
IoT Devices: Embed WebRTC in edge devices for real-time monitoring
Cloud Contribution: Push streams to third-party WHIP servers for cloud processing or redistribution
Standards-Based Playback: Serve streams to any WHEP client without custom signaling
Why Choose a Portable WebRTC Solution?
Smaller size
Lower latency (optimized transmission stack)
Easier to embed (no complex dependencies)
Support for more input sources (native support for RTSP/RTMP)
Frequently Asked Questions (FAQ)
What is portable WebRTC?
Portable WebRTC refers to a lightweight, easily deployable WebRTC server or SDK that can be embedded in various platforms. Happytime Portable RTC is a C-based solution that converts RTSP, RTMP, SRT, desktop, or camera streams into WebRTC for browser playback.
Can I use this to stream RTSP to WebRTC?
Yes! Our portable WebRTC server supports direct RTSP input and converts it to WebRTC in real time, allowing you to view IP camera feeds directly in any modern browser without plugins.
Is there a WebRTC SDK available?
Yes, Happytime Portable RTC provides a C-based SDK for developers to integrate WebRTC streaming capabilities into their applications or devices. Contact us for documentation and source code licensing.
How many concurrent streams does it support?
The demo version supports up to 4 concurrent streams. The full release version supports up to 100 concurrent streams, ideal for enterprise or surveillance deployments.
Does it work on embedded systems?
Yes, it's designed for portability and runs on embedded Linux, Android, and other resource-constrained environments due to its small footprint and C-language implementation.
What is WHIP and how does Portable RTC support it?
WHIP (WebRTC HTTP Ingestion Protocol) is a standard for publishing WebRTC streams to a server. Portable RTC can act as a WHIP client, pushing its RTSP/RTMP/SRT/camera/desktop streams to any remote WHIP-compliant WebRTC server or cloud platform using a simple HTTP-based SDP exchange.
What is WHEP and how does Portable RTC support it?
WHEP (WebRTC HTTP Egress Protocol) is a standard for consuming WebRTC streams from a server. Portable RTC can act as a WHEP server, allowing any WHEP-compliant client to pull its WebRTC streams over HTTP without requiring the Happytime signal server or custom signaling.
Is the source code available?
Source code is available under commercial license. Contact sales for licensing options and customization support.
Version limitation
Portable RTC demo version supports up to 4 concurrent streams.
Portable RTC release version supports up to 100 concurrent streams.
How to ...
How to deploy signal server?
Troubleshooting WebRTC Connection Failures in LAN?
How to convert RTSP IP camera stream to WebRTC for browser viewing?
How to share desktop screen and application windows to multiple browsers via WebRTC?
How to push streams to a WHIP server?
How to play streams via WHEP?