Skip to main content
Configure from Project Settings → Resolution.

​
Resolution modes

​
Default start resolutions

Override per device under Start Resolution Desktops / Tablets / Mobiles.

​
Supported resolutions

​
Viewer-side resolution control

By default viewers can change resolution from the player UI, capped at the Max Stream Quality you set. Disable Show Resolution Settings to lock viewers to your defaults.
Resolution Settings

Resolution Settings

​
Bitrate

How much data the stream uses, in megabits per second. Higher = better quality, more bandwidth required. The encoder adapts within this range based on the viewer’s network. Tighten the range for predictable quality; widen it for the broadest audience.
If your audience is mostly on weak connections, lower Maximum to ~15 Mbps so the encoder doesn’t over-spend bandwidth chasing quality the network can’t deliver.

​
Quality Parameters (QP)

QP controls compression intensity per frame, where lower = better quality, higher bandwidth. The valid range depends on the codec — AV1 supports a wider range than H.264. The encoder picks QP per frame within this range — high motion scenes drift toward Max QP, static scenes drift toward Min QP. For most projects the defaults are correct.
Don’t tune QP unless bitrate alone isn’t getting you the quality you want. Wrong values can produce worse streams than the defaults.
Pick the preset that matches your project, then fine-tune from there. AV1 is the recommended primary codec for every use case. Set a fallback for browsers or UE versions that don’t support AV1.
ArchViz and Digital Twin scenes benefit from VP9 as a fallback because it keeps detail well at constrained bandwidth. For chatbots and games, H.264 is the safer fallback for the broadest device reach.

​
Next

Codec settings

Pick the right codec for your audience.

Performance tuning

Hit your latency, FPS, and bitrate targets.