Cloud Transcoding
Convert codecs, stabilize streams, and create multiple output formats.
Quick Navigation
Passthrough vs Transcoding
By default, Meshcast uses passthrough - your stream is forwarded to destinations without re-encoding. This is fast and free, but requires your source to already be compatible with the destination.
Cloud Transcoding re-encodes your stream on our servers. This converts incompatible codecs, stabilizes variable streams, and can output multiple formats. Access requires a paid plan or available trial credits; cloud runtime is billed separately from your subscription.
- No re-encoding
- Lowest latency
- Source must be compatible
- Variable quality passed through
- Full re-encoding
- Converts any codec to H.264
- Fixed resolution and bitrate
- Stabilizes variable sources
Codec Compatibility
RTMP destinations (YouTube, Twitch, Facebook, Kick) only accept H.264 video and AAC audio. Other codecs will fail.
| Video Codec | RTMP Output | Notes |
|---|---|---|
| H.264 | ✓ Supported | Works with passthrough |
| VP8 | ✗ Not supported | Requires transcoding |
| VP9 | ✗ Not supported | Requires transcoding |
| AV1 | ✗ Not supported | Requires transcoding |
| H.265/HEVC | ✗ Not supported | Requires transcoding |
WHIP/WebRTC sources use Opus audio. Meshcast automatically converts Opus to AAC for RTMP/HLS output (registered and paid tiers). No action needed.
When is Transcoding Needed?
You need cloud transcoding if your source has any of these issues:
- Incompatible codec - VP8, VP9, AV1, or HEVC video
- Variable frame rate - Some platforms require constant FPS
- Variable resolution - Resolution changes mid-stream
- Variable bitrate - Some platforms prefer CBR over VBR
- Packet loss - WebRTC sources may have gaps that get passed through
- Multiple outputs - Need different resolutions or bitrates for different destinations
Passthrough works well for:
- RTMP/SRT sources with H.264 and stable settings
- OBS or hardware encoders with constant bitrate
- Sources already configured for your destination's requirements
How to Enable Cloud Transcoding
- Go to Dashboard → Transcode Open Transcode from your Meshcast dashboard and check service availability, access, and the hourly rate.
- Create a transcode session Choose your input source, output quality, and destination settings, then start the session.
- Start your source stream For an encoder, send your stream to the session's Ingest URL. For a browser source, use the supported page URL you configured.
- Check your destinations Verify audio and video at each configured output. Choose Stop Session when finished to end cloud runtime billing or trial-credit use.
Pricing
Paid plans set the maximum number of transcode outputs. Cloud server runtime is billed separately at the hourly rate shown before starting a session:
- Solo Creator ($10/mo) - 2 transcode outputs
- Creator Plus ($25/mo) - 4 transcode outputs
- Studio Pro ($50/mo) - 6 transcode outputs
Accounts with trial credits can try transcoding within their available credit balance and trial limits. Each output can have its own resolution, bitrate, and destination. Check your access, credits, and runtime rate in Cloud Transcoding; see Pricing for plan limits.