If you want a video file to behave predictably in OBS, set the OBS output resolution and frame rate first, then transcode the file to those targets. Do not assume that OBS’s canvas size is the same as the resolution sent to YouTube or used for a recording.
In HandBrake, choose the dimensions and frame-rate behaviour deliberately. A short encode tested in the actual OBS playback, import, or streaming workflow can reveal timing, scaling, or compatibility problems before you process a long file.
Set the OBS output target first
Open OBS and go to Settings > Video. Note these three values:
- Base (Canvas) Resolution
- Output (Scaled) Resolution
- Common FPS Value
The Base (Canvas) Resolution is the space in which OBS arranges sources. It describes the composition canvas: the area where you place a camera, image, browser source, text, or media source.
The Output (Scaled) Resolution is the resolution OBS sends to its output. That output may be a YouTube stream or a recording, depending on how you are using OBS. For this task, it is usually the most relevant resolution target.
Common FPS Value is OBS’s target output frame rate. If it is set to 30, a file intended to match the OBS output should normally be prepared around 30 frames per second. If it is set to 60, a 60-fps output may be appropriate, provided your source and computer can handle it.
Write these settings down before opening HandBrake. For example, you might find:
| OBS setting | Example value | What it tells you |
|---|---|---|
| Base (Canvas) Resolution | 1920×1080 | The composition space |
| Output (Scaled) Resolution | 1280×720 | The output resolution to target |
| Common FPS Value | 30 | The intended output frame rate |
The example does not mean that 720p30 is always the right choice. It shows why you should read the output setting rather than copy the canvas setting automatically. A 1080p canvas can be useful for arranging sources while the final output is 720p.
OBS settings do not rewrite your source videos. They control how OBS composes, scales, encodes, and outputs what is in the scene. If you need the file itself to have particular dimensions or timing, you must transcode it separately.
It is also worth checking the purpose of the file. A video used as a Media Source inside a scene may not need to be transcoded merely because its properties differ from the canvas. OBS can often play and scale it. Transcoding becomes useful when you want a consistent set of files, when an import workflow expects a particular format, or when mismatched timing causes visible problems.
If your wider plan is a recorded playlist, see how to stream a playlist to YouTube Live using OBS in India before converting every file. The playback arrangement can affect what needs to be standardised.
For official explanations of the canvas, output resolution, and frame-rate controls, consult the OBS Studio Overview Guide.
Canvas resolution and output resolution are different
A common mistake is to take the Base (Canvas) Resolution as the file target. That can produce files larger than necessary, or files that are later scaled down by OBS. The better starting point is the Output (Scaled) Resolution, unless your workflow specifically requires the canvas dimensions.
Suppose your canvas is 1920×1080 and your output is 1280×720. A 1920×1080 source placed on the canvas can be scaled to fit the canvas, and OBS can then produce a 1280×720 output. A 1280×720 file may therefore be a sensible match for the output, but it is not automatically a match for every source or scene.
There are three separate questions to answer:
- What dimensions does the source file currently have?
- What dimensions does the OBS scene need for clean composition?
- What dimensions does the final OBS output need?
If the file is a full-screen background with no overlays, matching the output dimensions can reduce an extra scaling step. If the file is a small element placed beside a camera or a logo, matching the full output resolution may serve no purpose. You may prefer to keep that source smaller and let OBS position it.
Aspect ratio matters as much as pixel dimensions. A 16:9 file can fit a 16:9 canvas without cropping, while a portrait or unusually wide file may require letterboxing, cropping, or stretching. HandBrake can change dimensions, but it cannot decide which visual treatment is correct for your scene. Check the preview and the resulting OBS layout.
Do not stretch a 4:3 devotional recording simply to fill a 16:9 output unless that distortion is acceptable. Keeping the original proportions and adding bars may be preferable. Alternatively, crop the sides or top and bottom if the important content allows it. Make that choice before batch conversion, because an automated crop can remove text or faces from every file.
For channels where several files are shown in sequence, consistent dimensions can make transitions easier to inspect. The practical benefit is not that every file becomes identical in every respect, but that OBS has fewer changes to handle as the playlist moves from one item to the next. The guidance in how to keep video quality consistent across a YouTube loop stream is relevant when you are preparing a group rather than a single clip.
Choose the HandBrake dimensions deliberately
Open the source in HandBrake and look at the Dimensions panel. Confirm the source’s width and height before selecting a preset. Then compare those values with the OBS target you wrote down.
If the source already has the target dimensions, avoid changing them unless you need to crop, pad, or correct the aspect ratio. Re-encoding at the same dimensions can still change quality, file size, codec, and timing, so it is not a harmless copy operation.
If the source is larger than the target, downscaling may be sensible. A 1920×1080 source can be converted to 1280×720 when the OBS output is 1280×720 and the file is intended to fill that output. If the source is smaller than the target, enlarging it does not create missing detail. It may be required for a particular workflow, but do not expect the result to look like native high-resolution footage.
Check the following HandBrake options before encoding:
- Resolution limit or preset target: make sure it does not downscale below your intended output.
- Anamorphic and pixel-aspect settings: confirm that the displayed shape remains correct.
- Cropping: use automatic cropping only if the detected crop is appropriate for all important content.
- Width and height: verify the final values shown by HandBrake, not just the source values.
- Preview: inspect a frame containing text, a face, or an edge that would reveal stretching or cropping.
HandBrake’s official presets are designed for broad targets rather than for your particular OBS scene. Some presets resize video or impose a peak frame-rate limit. A preset described for 720p30 can therefore turn a 1080p60 source into a 720p file with a 30-fps peak. That may be exactly what you want, but it is not the same as preserving the source.
Read HandBrake’s official preset documentation and inspect the result shown in the application. Do not treat the preset name as proof that the final file has the dimensions and frame rate you intended.
For a local news loop or shop promotion, you may choose to make every item 1280×720 because that is the output target. For an archive of mixed devotional recordings, retaining higher-resolution originals and preparing a separate output copy may be more useful. Keep the original files until the test has passed and you have confirmed that the converted copies are suitable.
Decide what “same frame rate” means
Frame rate is not only a label such as 25, 30, or 60. A file can have timing that varies during playback even when a media player displays one nominal rate. Modern recordings may use variable frame rate, often abbreviated as VFR, to adapt the spacing between frames.
That distinction matters when you say that a file should have the “same frame rate as OBS”. You might mean one of two things:
- Preserve the source’s timing behaviour while allowing it to remain variable.
- Make every frame follow one constant rate that matches the OBS target.
These are different goals. In HandBrake, Same as Source with VFR preserves variable portions of the source timing. Same as Source with CFR creates a constant-frame-rate output based on the detected source rate. Selecting a specific frame rate conforms the file to the rate you choose.
The suitable choice depends on the destination. If your editing or playback application handles VFR correctly and preserving source timing is important, Same as Source with VFR may be appropriate. If the receiving workflow expects a constant rate, CFR is the more deliberate choice.
A source can show 30 fps in a player while still having variable timing. Inspect the source information in HandBrake and consider the actual workflow rather than relying on a label from a file manager. If the file came from a phone, screen recorder, or conferencing tool, check this point particularly carefully.
Use CFR when the destination needs constant timing
To produce a constant-rate file, choose Constant Framerate, or CFR, in HandBrake and select the intended rate. If OBS is set to 30 fps, a 30-fps CFR output is a straightforward target when the destination requires constant timing. If OBS is set to 60 fps, choose 60 only when the source and the computer can support the extra work and the content benefits from it.
When converting between rates, HandBrake may need to duplicate or omit temporal samples. For example, a source at one rate cannot be changed to another without changing how frames are distributed over time. The file may keep the same overall duration, but motion can look less even if the conversion is not suitable for the material.
This is why the target should come from the actual OBS workflow rather than from a general preference. A devotional still-image video with slow movement may not expose the same problems as a screen recording with a moving cursor or a local news ticker. Watch text edges, scrolling captions, lip movement, and cuts during the test.
CFR is often useful for a non-linear editor or an older application that does not handle VFR reliably. It can also make a mixed collection easier to reason about when every file is expected to follow one timing policy. It is not automatically better for every source. If preserving the source’s natural timing is more important and the destination accepts VFR, Same as Source with VFR may avoid an unnecessary timing conversion.
Frame rate and resolution are separate decisions. A 1280×720 file can be VFR or CFR, and a 1920×1080 file can be VFR or CFR. Choose the dimensions in the Dimensions panel and the timing policy in the Video or frame-rate controls; matching one does not automatically match the other.
Check presets, then test a short encode
Before adding a long file to a conversion queue, create a short test. Select a representative section rather than an easy opening frame. Include a portion with motion, a transition, speech or music if relevant, and any text or ticker that matters in the final stream.
In HandBrake, set the dimensions and frame-rate mode, then encode only that short section. The test is not a benchmark and it does not prove that every source will behave identically. It is a practical check of the particular file, preset, and OBS workflow you are about to use.
Test the result in the same way viewers or your automation will use it:
- Import it into the intended OBS scene or add it as the relevant media source.
- Watch the first minute and a later section rather than only the start.
- Check whether the picture is cropped, stretched, or unexpectedly letterboxed.
- Look for repeated or uneven motion when the source was converted to another rate.
- Listen for audio drift, missing audio, or a change in duration.
- If it is part of a loop, observe the end-to-start transition.
- Confirm the output settings in OBS still match the target used for the encode.
If the file plays correctly in a normal media player but fails in OBS, the issue may be in the source type, scene configuration, or media-source handling rather than in resolution alone. OBS’s troubleshooting guidance discusses Media Source and VLC Source as relevant playback options. Transcoding is not automatically required merely because a file was produced by a different device.
If a preset changed the dimensions or frame-rate ceiling, return to the preset and inspect its options before trying another encode. Do not assume that choosing a higher-quality preset will preserve the source dimensions or timing. Presets package several decisions together, and their target may be designed for a different playback device or resolution.
A higher output frame rate can also require more processing. OBS advises testing whether the system can handle the chosen output, particularly for 60-fps work. Let the test run long enough to expose dropped frames, stutter, or resource pressure in your actual scene. The OBS encoding performance troubleshooting guide is useful when the file itself appears sound but playback or output is struggling.
Once the short file works, apply the same settings to a small batch before converting an entire library. Compare one short, one long, and one visually busy source if the collection is mixed. Keep the originals and name the converted files clearly so that you can identify the dimensions and timing policy later.
Keep transcoding separate from remuxing and streaming
Transcoding decodes and re-encodes the video, which can change quality, file size, codec, dimensions, and frame-rate behaviour. Remuxing changes the container around existing streams without re-encoding the video. These operations solve different problems.
OBS recommends recording to MKV because it is more resilient if a recording stops unexpectedly. If another application needs MP4, OBS provides a built-in remuxing function. That operation is not a way to change a 60-fps file to 30 fps or a 1080p file to 720p; use a transcoder for those changes.
The OBS Standard Recording Output Guide explains the recording and remuxing workflow. If your task is only to make an OBS recording available as MP4, remuxing may be enough. If your task is to match an output resolution and constant frame rate, it is not.
For a 24/7 channel, the test should also include the part of the workflow that runs unattended. A file that looks correct in a five-minute manual check can still reveal a loop, import, or playlist problem later. If you want to remove the need to keep your computer on for a YouTube-only uploaded-video stream, StreamNeo can take an uploaded file and run the channel from the cloud while monitoring and restarting the broadcast if it drops; you still need to verify the file and the YouTube setup yourself.
This is also where operational choices matter. Running OBS locally gives you direct control over scenes and sources, but the computer, power, network, and maintenance remain part of the overnight setup. A cloud-based workflow reduces the need to leave that computer running, while a local OBS workflow may be preferable when you need live scene changes, several input devices, or software that cannot be replaced by an uploaded file.
If a stream stops unexpectedly rather than merely playing a badly timed file, see how to troubleshoot YouTube Live Stream packet loss on an Indian ISP. Network symptoms and media-file symptoms can look similar from the viewer’s side, but they require different checks.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Should I match OBS Base (Canvas) Resolution or Output (Scaled) Resolution?
Usually, start with Output (Scaled) Resolution because that is the resolution OBS sends to its output. Match the canvas instead when your scene or another part of the workflow specifically requires those dimensions. Check both values before converting.
Should I choose Same as Source, VFR or CFR in HandBrake?
Use Same as Source with VFR when preserving variable source timing is suitable for the destination. Choose CFR when the receiving workflow needs constant timing, then select the intended rate and test motion and synchronisation. There is no single choice that is correct for every source.
Does an OBS setting change the original video file?
No. OBS settings control how OBS uses and outputs the source; they do not rewrite the original file. Use HandBrake or another transcoder when the file itself must have different dimensions or frame-rate behaviour.
Can I trust a HandBrake preset to preserve my resolution and frame rate?
No. Presets can resize video and limit the peak frame rate, so inspect the final settings before encoding. Make a short test in the actual OBS workflow, especially before converting a long playlist or a complete channel library.