Elgato 4K S and 4K X Capture Card Workflow for Cloud OBS

Why capture cards still matter

Modern HDMI capture cards are still useful for streamer production because many sources do not send a clean network stream by themselves. Consoles, cameras, phones, tablets, secondary PCs, switchers, and some action cameras may be easier to capture over HDMI, add to local OBS, and then send into StreamableRun as a controlled source.

Elgato's current 4K S support page lists USB 3.0 Type-C, HDMI 2.0 input and output, 4K60 passthrough, 4K60 capture, HDR passthrough, HDR capture up to 1080p60 on Windows, and OBS Studio support. The 4K X support page lists USB 3.2 Gen2, HDMI 2.1 input and output, passthrough up to 4K144, capture up to 4K144, and OBS Studio 27.2.4 or later on Windows and macOS.

The practical question is not which box has the highest number. It is how to turn an HDMI source into a stable live source without making the local computer responsible for the whole show. StreamableRun lets the capture machine become an ingest source while Cloud Hosted OBS handles scenes, fallback, destinations, and producer handoff.

Pick the card by source, not bragging rights

A capture card should match the source and the production target. If your console or camera is only feeding a 1080p or 4K60 show, a lower-bandwidth card may be enough. If you need high-refresh passthrough for gaming while capturing, HDMI 2.1 and USB 10 Gbps may matter. If the captured source becomes a 1080p60 live output in Cloud OBS, do not overbuild the chain just because the card can see more.

Elgato 4K S is a sensible class of device for many creator setups because it supports common sources, OBS Studio, and 4K60 capture or passthrough within its documented limits. 4K X is for setups that need HDMI 2.1, higher frame rate passthrough, higher capture ceilings, or more demanding console and PC paths. Both still need a stable local machine, correct USB path, audio plan, and tested OBS source settings.

For StreamableRun, the capture card is only the input. The finished show can still be managed in the cloud. That is useful when a streamer wants a console, camera, or iPad source inside a larger IRL or remote production without exposing destination keys on the capture computer.

• Choose 4K S-style capture when 4K60 or 1080p production is enough and USB 3.0 fits the machine.
• Choose 4K X-style capture when HDMI 2.1, 4K144-class paths, high-refresh passthrough, or 10 Gbps USB matter.
• Use the source's actual output format, not the maximum number printed on a product page.
• Use Cloud OBS for the public scene stack instead of forcing the capture laptop to run the entire broadcast.
• Test the same source, cable, USB port, resolution, frame rate, and audio path before the show.

Add the card to OBS correctly

OBS's Video Capture Sources guide says the Video Capture Device source can add webcams and capture cards, and notes that resolution and frame rate settings must match what the device supports or the source may show nothing. That is the core capture-card troubleshooting rule: make the source, card, cable, and OBS properties agree.

Do not leave everything on automatic for an important stream. In local OBS, add the capture card as a Video Capture Device, set the expected resolution and FPS, confirm the video format, check color range, and decide whether buffering helps or hurts. If the card has a separate audio input or the HDMI carries audio, decide how it enters the mix.

Once local OBS has a stable source, send local OBS to StreamableRun as an ingest. That could be RTMP or another supported workflow depending on your setup. Then Cloud Hosted OBS can combine the capture-card source with overlays, fallback, alerts, remote producer controls, and destination outputs.

• Set the capture source to a known resolution and FPS instead of guessing.
• Match the source output, card capability, OBS canvas, and StreamableRun output plan.
• Check whether audio comes over HDMI, analog line-in, a microphone, or a separate mixer.
• Disable or tune buffering only after checking delay and stutter in rehearsal.
• Create a fallback scene in Cloud OBS before making the capture-card source public.

HDMI and HDCP realities

Elgato's support pages describe unencrypted HDMI sources. That wording matters. Capture cards generally cannot capture protected video in a way that bypasses HDCP or platform restrictions. If the source is a console game, camera, production switcher, or phone output that permits capture, you can test it. If the source is protected media, streaming services, movies, or restricted app output, do not build a show around capturing it.

Streamer operators should also check the legal and platform side, not only the signal. A capture card can carry a console or phone image, but that does not mean the content is cleared for public streaming. Sponsored events, music, sports, paid media, and private app screens need their own permission checks.

For StreamableRun, keep the privacy scene close. If a captured phone or console suddenly shows an account page, code, DM, payment screen, or private menu, the producer should switch away immediately. The capture card is a powerful source, and powerful sources need a fast hide button.

• Use unencrypted HDMI sources only.
• Do not attempt to capture protected streaming-service playback.
• Check console, camera, phone, or app permissions before a public stream.
• Use a privacy-safe scene for menu navigation, account screens, and source resets.
• Have the producer watch the capture source before it goes to the public scene.

Audio and delay checklist

Capture-card audio is where otherwise clean setups become annoying. HDMI audio, analog line-in, party chat adapters, monitor speakers, desktop audio, and microphones can create duplicates or delay. The viewer hears the mistake before they care about 4K.

Build the audio plan before the source goes live. Is the capture card carrying game audio only? Is voice coming from a headset, a mixer, a USB microphone, or the card's analog input? Does local OBS send a mixed feed to StreamableRun, or does Cloud OBS combine sources? If two places monitor the same audio, echo is likely.

In StreamableRun Cloud OBS, label the capture-card source and audio path clearly. Pin the important meters. Test a loud game moment, quiet speech, scene switch, mute, and fallback. If the capture-card source is a backup or secondary angle, decide whether its audio should be active at all.

• Check for duplicate game audio from HDMI and desktop audio.
• Check party chat or voice chat rules before the stream.
• Run a clap or sharp sound test to check delay between camera and audio.
• Record a private test and listen back before going public.
• Create a producer action for mute, lower, or switch away from the source.

Local OBS as an ingest, not the final show

The best StreamableRun capture-card workflow often uses local OBS as an input stage. Local OBS sees the HDMI source, handles card-specific settings, and sends a clean program or source feed to StreamableRun. Cloud Hosted OBS then handles the public production.

This split helps because capture-card troubleshooting is local and physical. The operator near the machine can reseat HDMI, change USB ports, restart the source, or adjust card settings. The remote producer can keep the public stream alive, switch scenes, and manage destinations without remote-desktop lag or stream-key exposure.

Do not put platform destinations inside the capture-card OBS profile unless there is a specific reason. If local OBS owns Twitch, Kick, YouTube, and custom RTMP directly, then every local machine failure becomes a destination failure. StreamableRun keeps those outputs centralized.

• Local OBS job: capture HDMI, set resolution/FPS, mix local source audio if needed, send ingest.
• StreamableRun job: receive source, run Cloud OBS scenes, protect drops, and output destinations.
• Producer job: monitor preview, switch fallback, manage overlays, and return to main when stable.
• Field operator job: manage cables, source device, capture software, and local machine health.
• Backup job: provide a second source or fallback scene if the capture path disappears.

Test scenes for capture-card sources

A capture-card source needs more than a picture test. Create a test scene collection in Cloud OBS with main capture, capture plus overlays, capture muted, fallback, privacy, and technical slate scenes. Then rehearse the likely failures.

Unplug HDMI, unplug USB, change source resolution, wake a console, open a menu, trigger a loud audio moment, switch to fallback while the source is active, and return after the source recovers. The producer should see what each failure looks like before viewers do.

If the source is for a paid event or sponsor segment, test the exact sponsor graphics and platform preview. Tiny text may look fine in OBS and unreadable after compression. A 4K source does not help if the public output is 1080p and the graphic safe area is wrong.

• HDMI unplug: Cloud OBS should switch to fallback, not stay on a black mystery source.
• Resolution change: local OBS should recover or the operator should know the reset steps.
• Audio spike: producer should mute or lower the source quickly.
• Private screen: producer should switch to privacy scene immediately.
• Source return: producer should confirm preview before switching back publicly.

Other resources

Use these resources to verify capture-card capabilities, OBS source behavior, platform output settings, and StreamableRun production features.