An “unsupported video format” message in OBS does not identify one universal fault. First check whether it appears when you start a local recording, when OBS starts streaming, or after YouTube receives the live feed.
Each location points to a different fix. A recording error usually concerns OBS’s output format, encoder or audio tracks, while a YouTube warning usually concerns the incoming codec, resolution, frame rate, protocol or HDR settings.
Find where the message appears
Write down the exact wording before changing anything. Also note which button you clicked, which application showed the message and whether a preview appeared in YouTube Live Control Room.
There are three useful routes:
| Where the problem appears | What it usually concerns | First place to check |
|---|---|---|
| OBS when you click Start Recording | Recording container, encoder or audio-track combination | Settings → Output → Recording |
| OBS when you click Start Streaming | Selected service, protocol or local encoder | Settings → Stream and Settings → Output |
| YouTube Live Control Room after OBS connects | Ingest codec, resolution, frame rate, bitrate or protocol | YouTube’s stream status and encoder guidance |
These categories can overlap, but they should not be treated as the same problem. If OBS can record successfully but YouTube rejects the live feed, changing the recording container is unlikely to solve the ingest problem. If OBS cannot create a local file, changing YouTube’s stream key or bitrate is not the first step.
You may also see a separate account or channel issue before format checks begin. If YouTube will not let you create or start a broadcast at all, check why YouTube says live streaming is unavailable before troubleshooting OBS media settings.
Check OBS recording output and audio tracks
If the error appears when you click Start Recording, open Settings → Output → Recording in OBS. Check the recording path, file format, selected video encoder and audio tracks together. The OBS interface includes an error stating: “The output format is either unsupported or does not support more than one audio track. Please check your settings and try again.”
This message is about creating the local recording. It does not mean that YouTube has rejected your live stream.
OBS’s audio and video formats guide describes MKV as compatible with every audio and video encoder supported in OBS Studio. MKV is therefore a useful diagnostic choice when a recording format or multiple audio tracks are involved. It may need remuxing before some editing applications can open it, so compatibility with OBS is not identical to compatibility with every editor.
To test this branch, temporarily simplify the recording settings:
- Choose MKV as the recording format.
- Select one known-working video encoder shown by your OBS installation.
- Reduce the recording to the audio tracks you actually need.
- Start a short local recording and stop it again.
- Confirm that the file opens and contains the expected picture and sound.
Do not change several unrelated settings at once. If the short MKV recording works, restore only the setting you need, such as a particular editor-friendly container or additional audio track, and test again. The setting that brings the error back identifies the local recording conflict.
A recording container is not a live-stream codec. A file can be easy for OBS to write while the corresponding live output still has an encoder or protocol problem. Conversely, a live stream can work while a chosen recording format fails because it cannot carry the selected audio tracks.
If your source file is large or difficult to process, compression can also affect local preparation, but it is not a cure for a live ingest rejection. The HandBrake walkthrough for compressing video without visible quality loss is useful when the problem is the media file itself rather than the connection from OBS to YouTube.
Check live encoder ingestion requirements
If the message appears when you click Start Streaming, or YouTube reports an unsupported format after OBS connects, move to the live-output path. In OBS, check the service selected under Settings → Stream, then check the active encoder under Settings → Output → Streaming.
YouTube recommends RTMPS for live streaming. Use the service and protocol selected for your YouTube workflow rather than assuming that a setting used for another platform will work unchanged. You can compare the protocol, codec and target format against YouTube’s live encoder settings.
Then open YouTube Live Control Room and inspect the status beneath the preview. OBS’s guidance also tells streamers to watch the status reported by YouTube after output begins. This matters because OBS may show that it is sending data while YouTube is still reporting a problem with the incoming stream.
Check these questions in order:
- Is the OBS service set to YouTube rather than a custom service left over from an earlier setup?
- Is the stream key copied into the correct OBS field and associated with the intended broadcast?
- Is the selected protocol RTMPS where that is the intended YouTube workflow?
- Which encoder is active: a hardware encoder or a software encoder?
- Is the output SDR or HDR?
- What resolution and frame rate are OBS actually sending?
Do not prescribe one codec or bitrate before answering those questions. YouTube’s recommended bitrate depends on the ingestion codec, resolution and frame rate. For example, YouTube lists 10 Mbps for H.264 at 1080p and 30 frames per second, and 17 Mbps for H.264 at 1080p and 60 frames per second, as listed on YouTube’s live encoder settings page accessed in October 2026. For AV1 or H.265 at 1080p and 60 frames per second, it lists 12 Mbps on that page.
Those are recommendations for particular combinations, not a universal repair. A bitrate change cannot make an unsupported encoder or protocol acceptable, and a supported codec can still fail if the output dimensions or frame rate do not match the workflow you selected.
Verify codec, resolution, frame rate and protocol
Once you know that the failure is on the live path, compare what OBS is producing with what YouTube documents for the selected workflow. Start with a simple SDR test rather than trying to preserve every advanced setting from the original stream.
In OBS, record the actual output values shown in your Video and Output settings. Pay attention to the canvas resolution, output resolution, common FPS value, encoder name and colour settings. A source may be 4K while OBS is scaling it to 1080p, or the canvas may be one frame rate while the stream output uses another. The value that matters for ingestion is the output being sent to YouTube.
Automatic detection is often the least confusing starting point on YouTube’s side. YouTube states, “By default (recommended), YouTube will automatically detect your resolution and frame rate.” That does not mean every source is accepted without checks. It means you should avoid forcing a manual setting unless you have a reason to do so.
For a first SDR test, use a resolution and frame rate that your current encoder can produce consistently. Keep the protocol at RTMPS where appropriate, use a standard SDR colour workflow and avoid changing the encoder, frame rate, resolution and bitrate simultaneously. Start the stream and watch the Live Control Room status.
If YouTube accepts the test, add complexity one setting at a time. For example, test a higher frame rate first, then a higher resolution, and then any special colour or codec requirement. Stop when the error returns and record the last change.
The table below separates the decisions that are often confused:
| Decision | What it changes | What it does not prove |
|---|---|---|
| Recording container | How OBS writes a local file | That YouTube accepts the live stream |
| Live encoder | How OBS compresses the outgoing video | That the protocol or colour workflow is valid |
| Resolution | The dimensions YouTube receives | That the selected encoder can handle the workload |
| Frame rate | The number of video frames sent each second | That the source is genuinely producing those frames consistently |
| Protocol | How the stream reaches YouTube | That the video codec is supported |
| HDR colour workflow | The colour and bit-depth interpretation | That an SDR stream should use the same settings |
If the active encoder is unavailable, greyed out or fails to initialise, check compatibility and current drivers for the relevant hardware. OBS explains that hardware encoders can reduce CPU work, but that does not mean buying a new graphics card is the general answer to an unsupported-format message. First establish whether the existing encoder is supported and whether OBS can initialise it.
A software encoder may be a useful diagnostic comparison if your computer can run it at the selected output. A hardware encoder may be preferable when CPU load is the limiting factor. Neither choice overrides YouTube’s documented ingest requirements.
Treat HDR as a separate workflow
HDR should not be added as a small colour toggle to an otherwise ordinary SDR setup. If you intend to stream HDR, follow the HDR-specific requirements for the encoder, colour format, transfer characteristics and protocol rather than applying those settings to every channel.
YouTube’s OBS HDR instructions specify a hardware HEVC encoder, the Main 10 profile, P010 colour format, and Rec. 2100 PQ or HLG. They also describe protocol and stream-key conditions for the documented HDR-over-HLS setup. Check the current YouTube HDR streaming instructions before changing the workflow, because HDR requirements are not interchangeable with the ordinary SDR RTMPS path.
The practical test is to decide first whether HDR is genuinely required. A devotional loop, study station or local news graphic may be intended as SDR even if some source footage was recorded in HDR. If the target is SDR, turn off HDR-specific output settings and test a normal SDR stream. Do not choose HEVC Main 10, P010 or Rec. 2100 merely because an error contains the word “format”.
If HDR is required, verify each part as a set:
- The hardware encoder supports the required HEVC profile and bit depth.
- OBS is using the intended hardware encoder rather than silently falling back to another option.
- The colour format is P010.
- The transfer and colour settings match Rec. 2100 PQ or HLG as intended.
- The YouTube protocol and stream key meet the documented HDR workflow.
- Your source, preview and output are not being converted unexpectedly between SDR and HDR.
A device may support ordinary H.264 streaming while lacking the encoder support needed for this HDR workflow. That is a compatibility limit, not necessarily an OBS installation fault. If the HDR encoder is unavailable, test a standard SDR configuration to separate the general streaming path from the HDR-specific limitation.
Retest the action that triggered the error
After making one relevant change, repeat the same action that originally failed. If the problem occurred on Start Recording, make a short recording. If it occurred on Start Streaming, start the output and inspect YouTube Live Control Room. If YouTube flagged the feed after connection, use the same broadcast type and check its status again.
Keep a small note of the test: OBS version, operating system, service, protocol, encoder, resolution, frame rate, SDR or HDR, and the exact message. This prevents a successful recording test from being mistaken for a successful live test.
If the local recording branch is fixed but live output still fails, leave the recording settings alone and continue with the live encoder and YouTube checks. If a simple SDR stream works but HDR fails, keep the successful SDR result as your baseline and investigate only the HDR requirements. If changing the protocol fixes the connection but YouTube reports a codec problem, continue with the encoder and output-format checks rather than repeating the protocol change.
For a channel that must keep running while your computer is off, the operational question is separate from the OBS error. StreamNeo removes the need to leave OBS running locally by taking an uploaded video and running the YouTube broadcast from the cloud, but you still need to provide a compatible file and YouTube stream key and check the channel’s current requirements.
If your aim is a continuous channel rather than a one-off test, the guide to keeping a YouTube live stream running without a PC in India covers that operating decision. It does not replace checking the source file or YouTube’s current ingest rules.
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
Why does YouTube say my OBS stream has an unsupported format?
The message can refer to the live encoder, codec, resolution, frame rate, protocol or HDR workflow. Check the stream status in YouTube Live Control Room and compare the actual OBS output with YouTube’s current encoder guidance. Do not assume that an OBS recording-format setting is responsible unless the error appears during recording.
How do I fix an unsupported format error when recording in OBS?
Open Settings → Output → Recording and check the container, encoder and audio tracks together. MKV is documented by OBS as compatible with every audio and video encoder supported in OBS Studio, although it may need remuxing for some editing applications. Test a short recording before changing live-stream settings.
Should I use H.264, HEVC or AV1 for YouTube?
The suitable choice depends on the YouTube workflow, your resolution and frame rate, and the encoder available on your device. Use YouTube’s current live encoder documentation rather than selecting a codec solely because it appears newer. HDR has separate HEVC, colour-format and protocol requirements.
Does an unsupported format error mean I need a new graphics card?
No. First check whether the current encoder is supported, enabled and initialising correctly, and whether the problem is actually a protocol or output-setting mismatch. New hardware is only a case-specific consideration when the logs and documented requirements show that the existing device cannot provide the required encoder or HDR workflow.