
An OBS capture device can stop displaying a picture when a selected custom resolution or frame rate is unsupported. Compare the device's negotiated input mode with its documented capabilities before changing recording bitrate or the output canvas. Capture negotiation happens upstream of the final encode.
Key Takeaways
- Capture-device input mode and OBS output resolution are different settings.
- A working detected mode is a useful diagnostic comparison.
- Match the actual incoming signal and supported device format.
Locate the stage that went black
Determine whether the device is absent from the source list, appears but produces no picture, or displays correctly while only the recording fails.
If the source goes black immediately after a custom-mode change, record exactly what changed. Do not simultaneously alter several encoder and color settings; that obscures the relationship to the input mode.
Keep a note of the previously working device selection and settings so the test can be reversed.
Check supported input combinations
The OBS Video Capture Sources guide documents the device resolution/FPS controls and notes that unsupported selections can produce no display. Driver-specific controls and available modes depend on the device and operating system.
Compare the selected combination with the capture device's and camera's actual specifications. A camera outputting one mode does not establish that every capture-device input format can accept it.
Use detected or previously working settings as a control where appropriate. Change one supported setting at a time rather than assuming the largest value in a list is the correct signal.
Keep input negotiation separate from delivery settings
Check the source picture before configuring its placement in the scene. An output canvas cannot create input frames that the device failed to supply.
Likewise, a codec selected for recording does not define the camera's incoming signal. The device-specific video compatibility check illustrates the broader need to verify the exact receiving device, though a capture input has its own documented requirements.
If the picture remains absent with a known-supported mode, investigate connection, source selection, device access and driver behavior rather than treating every black frame as an unsupported resolution.
Record a sustained test
Once the source displays, record a representative interval and open the saved file independently. Check continuity, actual dimensions and sound.
Use the film-file inspection checklist to distinguish the preview's appearance from the delivered properties. Confirm the intended input remains stable after the scene switches required by the event.
Accept the setup only when the capture mode is supported and the recorded result is valid. A single visible preview frame does not establish sustained capture or synchronization.
Related tasks
- An MP4 plays on a laptop but not a hotel television: check the model requirements
- I requested 10 seconds in 16:9. How do I check the actual AI video file?
Sources and scope
- OBS video capture sources: video capture unsupported resolution fps custom mode
Based on the relevant official OBS Project documentation, retrieved October 23, 2026. Procedures are documentation-based and platform-dependent; no OBS configuration or recording test was performed.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Pignatta / Pixabay, Pixabay Content License. This is an illustrative source photograph, not an application screenshot or a generated test result.