Problem
Screen-sharing resolution is too low for on-screen text, making a technical demonstration unreadable.
Solution
Root Cause / Diagnostic:
WebRTC screen-capture streams compress high-resolution desktop displays (such as 4K or 1440p) down to low-bitrate video feeds optimized for motion rather than sharpness. Fine code editors, terminal commands, or spreadsheet text become heavily artifacted and unreadable on viewers' mobile screens and standard 1080p players.
Actionable Fix:
1. Lower Source Display Resolution to 1080p: Instruct the demonstrator to change their operating system display resolution to 1920x1080 and set OS UI scaling to 125% or 150% prior to sharing.
2. Maximize Application Font Sizes: Increase font sizes within target applications (e.g., zooming browser text to 150% with Ctrl/Cmd + + and bumping IDE font sizes to 18pt or higher).
3. Force High-Bitrate Detail Mode in Capture Engine: In the capture source or WebRTC settings, set the content hint flag to "detail" (contentHint: "detail") and allocate at least 4500 kbps to the screen-share pipeline to preserve crisp edges.
Pro Tip:
Utilize dynamic digital punch-in zooms (e.g., using OBS Move Transition or zooming screen-share crops) to focus tightly on the active window quadrant being discussed, ensuring mobile viewers can clearly read technical parameters.
WebRTC screen-capture streams compress high-resolution desktop displays (such as 4K or 1440p) down to low-bitrate video feeds optimized for motion rather than sharpness. Fine code editors, terminal commands, or spreadsheet text become heavily artifacted and unreadable on viewers' mobile screens and standard 1080p players.
Actionable Fix:
1. Lower Source Display Resolution to 1080p: Instruct the demonstrator to change their operating system display resolution to 1920x1080 and set OS UI scaling to 125% or 150% prior to sharing.
2. Maximize Application Font Sizes: Increase font sizes within target applications (e.g., zooming browser text to 150% with Ctrl/Cmd + + and bumping IDE font sizes to 18pt or higher).
3. Force High-Bitrate Detail Mode in Capture Engine: In the capture source or WebRTC settings, set the content hint flag to "detail" (contentHint: "detail") and allocate at least 4500 kbps to the screen-share pipeline to preserve crisp edges.
Pro Tip:
Utilize dynamic digital punch-in zooms (e.g., using OBS Move Transition or zooming screen-share crops) to focus tightly on the active window quadrant being discussed, ensuring mobile viewers can clearly read technical parameters.