Do I need a system diagram if it is just OBS on one laptop?

If the show has more than a couple of sources, or more than one person could ever operate it, yes. The single-laptop setups hide a wrong capture-device assignment or an undrawn audio return until they fail live. A one-page diagram is cheap insurance against a black scene at doors.

Should I build a single-PC or dual-PC OBS setup?

Single PC handles most talks and single-operator streams. Move to dual PC when the main machine has no encode headroom, or when heavy scenes compete with encoding for the GPU. The answer depends on your hardware: confirm capacity against the vendor datasheets before committing. Draw the link between the machines either way.

How do I document OBS audio routing?

Put an audio lane beneath the video lane on the same diagram. Show the input devices, any virtual routing (including mix-minus for remote guests), which sources record to which tracks, and what the operator monitors versus what goes to the stream. The return and monitor paths are the ones crews forget.

Can WireFlow diagram an OBS setup when OBS is software?

Yes. The machine running OBS is a device with real capture inputs and network and stream outputs; everything feeding it (cameras, capture cards, NDI feeds, audio interfaces) is ordinary signal flow. Document the physical and network transport in and out of the machine. Treat the software sources as labeled inputs on that box.

What is the difference between an OBS scene collection and a system diagram?

A scene collection lives inside OBS on one machine and configures what that machine shows. A system diagram is the portable, human-readable record of the whole chain: sources, transports, audio routing, and outputs. The scene collection runs the show; the diagram lets anyone rebuild or troubleshoot it.

OBS Studio System Diagram and Setup

By VJ Ries · Published 2026-07-12 · Updated 2026-08-01 · 10 min read

An OBS Studio system diagram maps the full signal chain of an OBS production: every source feeding the software (cameras, USB cameras, NDI and screen captures), how audio is routed, and where the program goes out (stream, local recording and backup). Decide single PC or dual PC first. Then draw each source into the machine by its real transport and label the outputs. The result is a document any operator can run the show from, not a scene collection trapped on one person's laptop.

What is an OBS Studio system diagram?

Before you are staring at a black scene at doors, two questions get answered on paper: what feeds OBS, and where OBS sends it. An OBS Studio system diagram is a signal-flow drawing of an OBS-based production. It shows every source that feeds OBS and how each reaches the machine. How audio is routed. Where the program is sent.

OBS hides its entire signal chain inside one application window.

Which is why these setups fall apart at handoff.

A diagram lifts that chain onto a page the next operator can read: the same AV signal-flow diagram discipline, applied to a half-software system.

What goes into OBS: capture inputs and sources

Start with everything that becomes a source inside OBS, and note how each one reaches the machine:

Cameras through a capture card: an HDMI or SDI camera into an internal (PCIe) or external (USB) capture card, which OBS sees as a video capture device. The camera output format and the card's supported formats have to agree; confirm both against the capture card datasheet.
USB cameras and webcams: enumerated directly as video capture devices. They share USB bus bandwidth with everything else on that controller. Check the hardware; do not assume every port is independent.
NDI and other network sources: cameras, PTZ feeds or a second machine over the LAN. This is a network problem as much as a video one: see NDI network design, and for the cameras, PTZ camera system design.
Screen, window and application captures, and browser sources: pixels rather than a cable. Still a source, and it belongs on the diagram with its own box.
Media and remote guests: local media files, and remote contributors arriving through a call platform or a hardware decoder into a capture input.

On the diagram, each of these is a source box with a labeled transport into the machine: which capture card, which USB controller group, which NIC carries the NDI.

'Camera into OBS' is a wish.

'Camera 1 SDI out to Capture Card A input 2' is a buildable, debuggable fact: the same port-to-port rule any signal-flow drawing needs.

Single PC or dual PC: which layout do you draw?

One machine both captures and encodes, or the work splits across two: that is the first structural decision. It reshapes the whole diagram. Decide before you draw.

Single-PC vs dual-PC OBS layouts
Question	Single PC	Dual PC
Where capture and encode happen	One machine does both	Production PC feeds a second capture and encode PC
Typical fit	Most streams, talks, single-operator shows	Heavy scenes or gameplay, or a main PC with no encode headroom
Main risk to note	Single point of failure for capture, encode, and record	Two machines, two failure points, plus the link between them
What the diagram must show	Every source into one box, all outputs out of it	Feed from PC one to PC two (capture card or NDI), then PC two outputs
Added complexity	Lower	Higher: extra capture card or network path, extra audio routing

In a dual-PC layout, the production machine sends its program to the encoding machine over a dedicated capture card or an NDI path; that machine handles the stream and recording. Draw the hand-off link explicitly. It is the connection most single-diagram setups leave implied and then cannot troubleshoot.

Count the capture inputs before you commit to a layout

Cameras through capture cards: 3
USB cameras: 1
NDI and network sources (PTZ, second machine): 2
Screen and application captures: 2
Hardware capture inputs needed: 3 card + 1 USB = 4
Software-decoded sources: 2 network + 2 screen and application = 4, which take no capture input but draw on CPU, GPU, and NIC headroom instead
Simultaneous encode targets (stream + local record + backup): 3

Example counts, not a spec. The single-PC or dual-PC call hangs on that second group as much as the first, since decoded sources can exhaust a machine that still has capture inputs to spare. Whether one machine handles all of this or you split across two PCs depends on the specific GPU, CPU, and capture hardware. Confirm against the vendor datasheets before you promise it.

How does the audio route through OBS?

Audio is where OBS documentation is thinnest and where live shows actually break. Routing between your interfaces and your applications and OBS: invisible unless you draw it.

Device vs application audio: microphone and line inputs from an interface, versus audio captured from specific applications. They behave differently in the mixer. Note which is which.
Virtual audio routing: virtual devices that send, split or recombine audio between a DAW, a call app and OBS. This is where a guest's audio reaches the stream without feeding back into their ears: the classic mix-minus.
Multi-track recording: microphone, guests and program audio on separate tracks so post can remix. Mark which sources land on which tracks.
Monitoring: what the operator hears is not necessarily what goes to the stream. Draw the monitor path separately from the program path.

Put the audio lane directly beneath the video lane on the same diagram, not a separate file.

The cross-links between them (an embedder here, a virtual cable there) are exactly where shows break.

If any audio rides a network, for example a Dante interface into the machine, see Dante network requirements.

Where does OBS send the program: stream and record?

The output side is short but unforgiving: a stream target, a local recording, a backup any documented show needs.

Stream: the platform's ingest, over whatever protocol it accepts. Bitrate and encoder settings vary by platform and upload path. Check the platform's recommended settings rather than copying a number from another show.
Local recording: written to disk, separate from the stream, so a network hiccup costs viewers but not the archive. Note the destination drive: running out of disk space quietly ends recordings early.
Backup recording: a second record path, a second machine or an isolated recorder, so one crash does not lose the show.
Multiple destinations: when the program goes to more than one platform, note whether a restream service or separate outputs handle it, and draw each target.

Draw each output as its own destination box with its encoder (hardware or software) and target labeled, like the destinations in a multi-camera livestream signal flow; every physical run in and out also becomes a row in the cable schedule, so the drawing feeds the paperwork instead of duplicating it.

How to draw the OBS system diagram step by step

The method is the same one that works for any AV system, adapted to a machine that is half the wiring:

List every source and its transport before drawing a box: cameras and capture cards, USB cameras, NDI and network feeds, screen and application captures, media, and remote guests.
Place sources on the left, the OBS machine (or production PC then encode PC) in the middle, and outputs on the right, so signal reads left to right.
Draw each source into the machine port to port: which camera output, which capture card input, which USB group, which network path. Not box to box.
Add the audio lane beneath the video lane: input devices, virtual routing, record tracks, and what the operator monitors.
Draw the outputs: stream target, local recording, and backup, each with its encoder and destination.
Label every physical run with a cable ID and every feed with a signal name, then walk each path from source to destination and confirm every hop is real.

Keep it usable: the diagram plus the scene collection

The scene collection is the machine's copy of the setup; the diagram is the human copy. Ship both. The diagram lets a second operator understand the show. Or rebuild it on new hardware. Or trace a dead source without calling whoever built it.

Version it like any show document. The layout you plan from is the proposed diagram; the one you update after load-in (the house feed came in on SDI, the second camera moved to NDI) is the as-built. Hand over the as-built. Give your crew the plain-language version with signal flow for crews, and if starting from nothing, build your first diagram walks the mechanics.

Frequently asked questions

Do I need a system diagram if it is just OBS on one laptop?: If the show has more than a couple of sources, or more than one person could ever operate it, yes. The single-laptop setups hide a wrong capture-device assignment or an undrawn audio return until they fail live. A one-page diagram is cheap insurance against a black scene at doors.
Should I build a single-PC or dual-PC OBS setup?: Single PC handles most talks and single-operator streams. Move to dual PC when the main machine has no encode headroom, or when heavy scenes compete with encoding for the GPU. The answer depends on your hardware: confirm capacity against the vendor datasheets before committing. Draw the link between the machines either way.
How do I document OBS audio routing?: Put an audio lane beneath the video lane on the same diagram. Show the input devices, any virtual routing (including mix-minus for remote guests), which sources record to which tracks, and what the operator monitors versus what goes to the stream. The return and monitor paths are the ones crews forget.
Can WireFlow diagram an OBS setup when OBS is software?: Yes. The machine running OBS is a device with real capture inputs and network and stream outputs; everything feeding it (cameras, capture cards, NDI feeds, audio interfaces) is ordinary signal flow. Document the physical and network transport in and out of the machine. Treat the software sources as labeled inputs on that box.
What is the difference between an OBS scene collection and a system diagram?: A scene collection lives inside OBS on one machine and configures what that machine shows. A system diagram is the portable, human-readable record of the whole chain: sources, transports, audio routing, and outputs. The scene collection runs the show; the diagram lets anyone rebuild or troubleshoot it.

Build this diagram in WireFlow

Port-aware devices, validated connections, and exports your crew can read on site. Free plan includes three editable diagrams, no credit card.

Start a free diagram · Explore the sample show first