Cloud Transcoding: Reshape Your Stream Before Anyone Sees It

A full live encoder in the cloud, sitting between your incoming stream and your outputs. Change resolution, bitrate, FPS, keyframe interval, and audio, or force portrait, landscape, or square orientation, and the transcoded result is what reaches social platforms, HLS links, and your web player.

Any Orientation Full Encoding Control Live Source Preview Zero Local CPU

Free plan available. Transcoding on hosting plans, see pricing.

Live transcoder Enabled
Start transcoder
Orientation Choose whether output should keep original shape or force a layout
Keep original
Landscape
Portrait
Square
Resolution Select output resolution or define a custom width and height
HD 1280×720
Incoming profile
Resolution 1920×1080
Bitrate 6,000 kbps
FPS 30
Output profile
Resolution 1280×720
Bitrate 3,500 kbps
FPS 30

Send one source, deliver the right shape everywhere

Broadcasters have trusted Livepush transcoding to fit one production feed to every platform's requirements without a second encoder.

1 to 16
Mbps output bitrate range
24 to 60
FPS output frame rates
4
Orientations: original, landscape, portrait, square
300K+
Live events delivered

How cloud transcoding works

By default, Livepush relays your stream untouched. But sources rarely match every destination: your switcher outputs 1920×1020, a partner needs 720p, TikTok wants portrait, and your web player audience is fine either way. The live transcoder solves this in the cloud, between ingest and distribution.

While your stream is live, Livepush reads the incoming source profile and shows it next to your configured output, so you always know what will change before pressing Start Transcoder. Once running, everything downstream (social outputs, HLS delivery, web player) receives the transcoded version.

Transcoder
Social outputs HLS delivery Web player
Between ingest and output
The transcoder modifies the stream after it arrives and before it is distributed, so one source serves every requirement.
Preview before you commit
Incoming profile and expected output sit side by side in the dashboard, read live from your running stream.
Your encoder never knows
All processing runs on Livepush servers. Your machine keeps sending the same stream with zero added load.

Force landscape, portrait, or square, with smart scaling

Keep the original shape or force a layout. For each orientation you choose how the source fits: keep the full framing with padding, center-crop so the frame fills edge to edge, or rotate a landscape source to use the full portrait canvas.

  • Keep Original, Landscape, Portrait, or Square output orientation
  • Scaling types: Original/Default (padded), Cropped (edge to edge), or Rotated
  • Turn a 16:9 production feed into clean 1080×1920 portrait for vertical platforms
Orientation KEEP ORIGINAL
Keep Original
Portrait
Landscape
Square
IN · 1920×1080
OUT · 1920×1080

Every encoding dial, from resolution to audio bitrate

Pick a resolution preset like HD 1280×720 or define a custom width and height, slide video bitrate anywhere from 1 to 16 Mbps, set 24, 25, 30, 50, or 60 FPS, tune the keyframe interval from 1 to 4 seconds, and control audio sample rate and bitrate up to 320 kbps.

  • Resolution presets or fully custom width × height
  • Video 1 to 16 Mbps · FPS 24 to 60 · keyframe 1 to 4s (GOP = FPS × interval)
  • Audio sample rate selection and 64 to 320 kbps audio bitrate
Output Settings CUSTOM
Bitrate3.5 Mbps
FPS30
Key Frame Interval2s · GOP 60
Audio Bitrate160 kbps · 44100 Hz

See incoming vs. output before you press start

The dashboard reads your live source profile in real time and places it beside the expected transcoder output. You verify the change (say, 1920×1020 at 1055 kbps in, 1280×720 at 3.5M out) while the stream runs, then start the transcoder when it looks right.

  • Incoming profile read live: resolution, bitrate, FPS, audio
  • Transcoder Output Preview computed from your current settings
  • Start and stop the transcoder from the same panel, mid-session
Profile Comparison LIVE READ
Incoming 1920×1020 · 1055 kbps · 30 FPS source
Output 1280×720 · 3.5M · 30 FPS preview
Audio out 44100 Hz · 160k preview

One transcode, applied to every output

The transcoder modifies the stream before distribution, so the corrected version flows to everything at once: your social media destinations, your direct HLS delivery links, and the embedded web player. No per-output configuration, no drift between surfaces.

  • Social outputs: YouTube, Facebook, and all multistream destinations
  • Direct HLS links and the embedded web player receive the same output
  • Passthrough remains the default when the transcoder is off, with zero quality loss
Downstream Outputs SYNCED
Social YouTube Facebook Twitch Kick · 40+ 720p
HLS direct .m3u8 delivery 720p
Player embedded web player 720p

Simple, transparent pricing.

Trusted by broadcasters, media teams, and enterprises

Free 20 hrs per month, included

No credit card. No time limit.

Start free

What our customers say

Reviewed on Trustpilot and Capterra by streamers, broadcasters, and teams worldwide.

Go live today. No setup required.

Join thousands of streamers, broadcasters, and communities already on Livepush.

Cloud Transcoding:
Common Questions

Orientation, encoding controls, GOP, and where the transcoded stream goes.

What is cloud transcoding?
Cloud transcoding re-encodes your live stream on Livepush servers before it is distributed. The transcoder sits between your incoming stream and your outputs, so the modified version is what reaches social media destinations, direct HLS links, and your web player, while your encoder keeps sending the same source.
What settings can the live transcoder change?
Resolution (presets like HD 1280×720 or a custom width and height), video bitrate from 1 to 16 Mbps, frame rate at 24, 25, 30, 50, or 60 FPS, keyframe interval from 1 to 4 seconds, audio sample rate (such as 44100 Hz), audio bitrate from 64 to 320 kbps, and output orientation: keep original, landscape, portrait, or square.
How does landscape to portrait conversion work?
Choose the portrait orientation, then pick a scaling type. Original/Default keeps the full source framing inside the portrait canvas with padding where needed, Cropped center-crops the wider input so the portrait frame is filled edge to edge, and Rotated turns landscape or square sources to use the full portrait frame. A 1920×1020 source becomes a clean 1080×1920 output for vertical-first platforms.
When should I use the transcoder instead of passthrough?
Passthrough (the default) relays your stream untouched and is right when your source already fits every destination. Reach for the transcoder when something needs to change: a platform wants portrait video, a partner feed needs a capped resolution or bitrate, your source frame rate does not match a platform requirement, or you want to send a high-quality source and deliver a lighter output.
Can I see what the transcoder will output before starting it?
Yes. While your stream is live, Livepush reads the incoming source profile (resolution, bitrate, FPS, audio) and shows a Transcoder Output Preview next to it, so you can compare the incoming profile against the expected output, for example 1920×1020 at 1055 kbps in, 1280×720 at 3.5M out, before you press Start Transcoder.
Does cloud transcoding load my computer?
No. The entire re-encode runs on Livepush servers. Your encoder keeps pushing the same single stream it always has; resolution scaling, frame rate conversion, and orientation changes all cost your machine nothing.
What is the keyframe interval and why does it matter?
The keyframe interval controls how often a full video frame is encoded, stored internally as GOP = FPS × keyframe interval. Most platforms recommend 2 seconds: shorter intervals help viewers join and seek faster, longer ones squeeze slightly more quality from the same bitrate. Livepush lets you set 1 to 4 seconds and handles the GOP math.
Which outputs receive the transcoded stream?
The transcoder modifies the stream before distribution, so everything downstream gets the transcoded version: social media outputs like YouTube and Facebook, direct HLS delivery links, and the embedded web player.