The canvas defines the space used to arrange sources; scaled output defines the delivered picture size. If only delivery resolution must change, test the output setting before rebuilding the canvas.
Keep layout dimensions separate from delivery dimensions, test small text after scaling, and avoid moving every source for an output-only change.
In this guide
Before you start
- A duplicate profile and a note of the current canvas and output dimensions.
- A scene containing the smallest text and graphics that matter.
Distinguish the layout from the delivered picture
Think of a scene as a composition with a deliberate coordinate system. Its labels, camera and game capture were placed relative to that space. A delivery requirement such as a smaller video file does not necessarily mean those objects need to be rearranged.
OBS separates Base (Canvas) Resolution from Output (Scaled) Resolution in Video settings. The former is the composition space; the latter is the scaled output size. This distinction lets you ask a precise question: must the layout change, or only the dimensions of the delivered image?
Record the geometry before changing it
Write down both dimensions and the aspect ratio. Include any recording-specific rescale option already active, because another scaling stage can make it harder to explain the result. Keep a screenshot or a simple note of source positions if the layout contains carefully aligned borders.
Choose a test scene with text near the minimum readable size, diagonal edges and a camera frame. A large logo alone may look acceptable under many settings while the important interface labels become unreadable. The test needs to include the material that could actually fail.
Test an output-only change first
Preserve the original layout
Use a duplicate profile for the experiment and leave the canvas dimensions unchanged. Note the original output resolution.
Look for: The starting arrangement remains available for a clean comparison.
Change the scaled output
Choose the intended Output (Scaled) Resolution in Video settings while keeping a compatible aspect ratio for this test. Record the representative scene.
Look for: The delivered file changes size without requiring every source to be manually repositioned.
Inspect the saved dimensions and detail
Check the resulting file’s dimensions, then play it at the size viewers will use. Read the smallest label and inspect the camera border.
Look for: You know whether the smaller output meets the delivery need and preserves necessary information.
Rebuild the canvas only when the composition needs it
A portrait layout, a different aspect ratio or a deliberate scene redesign may require a different canvas. Treat that as a layout task: preserve the old collection, change the space, then inspect every source’s position and size. Do not expect a canvas change to compose a new design automatically.
OBS performance guidance also cautions that lowering the canvas complicates source management and requires realignment. If performance is the reason for the change, test a smaller output or lower frame rate first and compare the actual symptom. Avoid using geometry changes as an unexplained universal fix.
Solve the readability failure at the appropriate level
If a smaller output makes essential text too small, enlarge or simplify that element in the layout and repeat the recording. Increasing sharpening cannot restore information that was never large enough to survive the reduction. A dedicated close-up scene may serve a tutorial better than an unreadable full desktop.
Keep a brief settings note stating the canvas, output size and purpose of each profile. After switching profiles, inspect both the composition and the resulting file. The successful endpoint is a deliberate layout delivered at the intended size, with the smallest important information still usable.
Still stuck?
Sources move or no longer fit after a resolution change.
Check whether you changed the canvas rather than only the scaled output, then restore the old geometry or realign the copied layout deliberately.
Sources & references
Based on the linked first-party OBS documentation checked on 4 November 2026. The exercises and acceptance checks are editorial workflows for you to run; no hands-on OBS session or hardware benchmark is claimed.
- OBS — Studio Overview ↗Checked 2026-11-04
- OBS — Encoding Performance Troubleshooting ↗Checked 2026-11-04
Spotted something out of date? Let Alex know.
How we put our guides together ↗