AV Wiring Diagram Examples (With Annotated Breakdowns)
By WireFlow Team · Published 2026-07-12 · Updated 2026-07-12 · 9 min read
The fastest way to learn AV wiring diagrams is to read good ones. Below are four worked examples, a huddle room, a house-of-worship stream, a corporate ballroom, and a broadcast flypack, each annotated with what the drawing gets right and the mistake it avoids. In every case the same three things separate a real diagram from a picture: connections drawn port-to-port, format converters shown as their own devices, and every cable carrying a signal name. These are teaching examples; to open a full interactive one, explore the sample project.
How to read any AV wiring diagram
Every diagram in this gallery is built the same way, and you read them the same way. Whatever system you are looking at, walk it in this order:
- Find the sources on the left (cameras, laptops, playback, microphones) and the destinations on the right (displays, walls, recorders, streams).
- Locate the device everything organizes around, usually a switcher, matrix, or mixer in the middle.
- Follow one signal at a time from its source to its destination, reading the port it leaves and the port it lands on.
- At every box where the connector or signal type changes, expect a converter or extender. If none is drawn, that is a gap, not a shortcut.
- Read the cable label and signal name on each run. That is how the drawing maps to the physical cable in the case.
Example 1, huddle and conference room
The simplest real system: a presenter's laptop and an all-in-one conferencing bar (camera, microphones, and speaker in one device) feeding a single display, with a small switcher or the display's own inputs handling source selection. Five or six devices, but it still fails the same ways big rigs do when the drawing is sloppy.
What makes this example correct:
- Port-level connections. The laptop HDMI OUT lands on a specific switcher HDMI IN, and the bar connects to the room PC over a specific USB port, not a vague line labeled "connected."
- The USB path is shown. A conferencing bar is a USB device to the computer and an HDMI or analog device to the display. The diagram draws both, so nobody forgets the USB run that actually carries the camera and microphones.
- Signal names on every leg. "Laptop HDMI", "Room Cam USB", and "Program to Display" tell a tech what each cable does without tracing it by hand.
Example 2, house of worship and small stream
Two or three cameras, a production switcher, an audio console feeding a separate stream mix, and an encoder pushing to the platform. This is where a wiring diagram starts earning its keep, because the audio and video paths split and rejoin, and that is exactly where shows break.
What makes this example correct:
- Cameras drawn to specific switcher inputs. Cam 1 SDI to switcher IN 1, Cam 2 to IN 2, so the input count is verified on the page instead of discovered at load-in.
- A converter surfaced for the odd source. The lyrics or graphics laptop outputs HDMI while the switcher takes SDI, so the HDMI-to-SDI converter is its own box on the drawing. That means it lands on the gear list and earns a row in the cable schedule.
- The stream audio path is explicit. A separate stream mix (or mix-minus) feeds the encoder, drawn as its own line from the console to the encoder audio input, not assumed to "come from the switcher."
This is the core streaming pattern, scaled down. For the larger multi-camera version with ISO records and redundancy, read the full multicamera livestream walk-through.
Example 3, corporate ballroom general session
A general session in a hotel ballroom: multiple presenter laptops at the lectern and on stage, a playback machine, a camera or two for image magnification, a large switcher, an LED wall with its processor, confidence monitors, and a record leg. Enough sources that the input map is the whole game.
What makes this example correct:
- Every source to a real input on the switcher. With eight or more sources, the diagram numbers each one so nothing doubles up on an input or quietly goes missing.
- The LED processor is a device, not part of the wall. Program video leaves the switcher, enters the LED processor, and the processor feeds the wall. Drawing the processor as its own box shows where scaling and the data-path limit actually live. The LED wall calculator shows how processor ports cap the panels one processor can drive.
- A dedicated record and confidence path. The record leg and confidence monitors branch from their own switcher outputs, so losing a monitor never threatens the program feed or the recording.
Example 4, simple broadcast flypack
A portable production kit in cases: cameras over SDI, a compact switcher, a multiviewer, intercom, and a record or stream output, all built to strike and travel. A flypack diagram is dense because it is also the re-rig instructions for the next city.
What makes this example correct:
- SDI runs numbered end to end. Every camera and return feed is an SDI cable with an ID, because in a flypack the diagram is what gets the crew re-patched correctly in a venue they have never seen.
- Reference and return feeds shown, not implied. If the switcher and cameras genlock, the reference distribution is drawn; return video to each camera is drawn. A sync or return problem you cannot see on a box-and-line sketch is obvious when those runs are on the page.
- Multiviewer and intercom as their own paths. The multiviewer output to the operator display and the intercom lines are drawn explicitly, so the documented build is the whole kit, not just the program chain.
The four examples at a glance
| System | Key devices | Signal types | Watch out for |
|---|---|---|---|
| Huddle / conference room | Laptop, conferencing bar, display, small switcher | HDMI, USB | Forgetting the bar's USB run to the PC |
| Worship / small stream | Cameras, switcher, audio console, encoder | SDI, HDMI, audio, stream | No dedicated stream mix to the encoder |
| Corporate ballroom | Multi-source switcher, LED processor, LED wall, recorder | SDI, HDMI, LED data | Record leg sharing an output with a monitor |
| Broadcast flypack | Cameras, compact switcher, multiviewer, intercom | SDI, reference/sync, intercom | Skipping intercom, reference, and return feeds |
Notice the pattern across all four: the correct diagram always draws connections at the port, always shows the converter or processor as its own device, and always names the signal on the wire. Learn that and you can read a system you have never seen. To build one yourself from port-aware devices, start a free diagram, or study the interactive sample first.
Frequently asked questions
- Where can I find AV wiring diagram examples I can actually open?
- Static images teach the layout, but an interactive diagram lets you click a device and trace its connections. The WireFlow sample project is a complete conference production you can explore without an account: signal flow, LED wall, rack, and the derived gear list and cable schedule. Use it as the live version of the examples on this page.
- What is the difference between an AV wiring diagram and a one-line diagram?
- A one-line (or single-line) diagram collapses each path to a single line to show the system at a glance, useful for a quick overview or a proposal. A full wiring diagram draws every port-to-port connection and cable ID. The examples here are closer to full wiring diagrams, because that detail is what makes a system buildable and troubleshootable. Many projects keep both.
- Do these examples work as templates for my own show?
- Treat them as patterns, not drop-in templates. Every venue and rig differs, so copy the method (port-level connections, converters surfaced, signals named) rather than the exact device list. To start from a real editable base, create a free diagram and place your own gear from the device library.
- How much detail should an example diagram include?
- Enough that a tech who has never seen the system could build or trace it. That means every connection a human will plug is drawn at the port, every format change has its converter, and every cable has an ID and a signal name. Summarize only what is genuinely atomic; you do not draw the inside of a stagebox. See how to create an AV signal-flow diagram for the full method.
- Which example is closest to a live-stream setup?
- The house-of-worship example is the core streaming pattern: cameras into a switcher, a dedicated audio mix, and an encoder to the platform. For a larger multi-camera version with ISO records and backup paths, read multicamera livestream signal flow.
See a full show documented in WireFlow
A complete conference production, signal flow, LED wall, rack, gear list, and tech pack, open to explore without an account.