What is SDI? It is a family of digital video interfaces that moves video, and sometimes embedded audio, between compatible production equipment. For live streaming, SDI usually connects a camera or switcher to an encoder; the encoder then creates the network stream sent to YouTube or another destination.
That distinction matters. An SDI cable does not deliver a broadcast over the internet, and an SDI port on one device does not guarantee that every signal from another device will work with it. You need to match the link standard, video format, frame rate and the role of each piece of equipment.
What SDI means in a live production
SDI stands for Serial Digital Interface. It carries digital video as a serial signal from one compatible device to another. In production settings, that often means a camera connected to a switcher, monitor, recorder or encoder. Coaxial cable with BNC connectors is common, though the exact connection and supported signal depend on the equipment.
The key idea is that SDI belongs to the production side of a stream. It moves a video signal around your studio, venue or control room. The encoder takes that signal, compresses it into a suitable format and sends it over a network using a protocol the destination supports. If you are learning how the broader setup fits together, this guide to producing a 24/7 YouTube live stream covers the other decisions around a continuous broadcast.
SDI is used in professional video workflows partly because it provides a direct, low-latency connection between equipment. That is a general characteristic of the interface, not a promise that every complete production path has a particular end-to-end delay. Cameras, converters, processing, switching and encoding all affect the finished output.
You may encounter names such as HD-SDI, 3G-SDI, 6G-SDI and 12G-SDI. These indicate different link generations and rates, but the label is only a starting point for a compatibility check. It does not tell you by itself which resolutions, frame rates, signal mappings or ancillary features a particular device supports.
What SDI can carry
At a basic level, SDI carries digital video. Depending on the standard and the implementation at each end, the signal can also carry embedded audio and ancillary data. Ancillary data refers to information carried alongside the picture, such as timing or production-related information. Do not assume every camera, converter or encoder handles all of these in the same way.
Embedded audio can simplify a production chain. If a camera or switcher embeds audio in its SDI output, a compatible downstream device may receive picture and sound over the same connection. But if sound is on a separate output, or a device does not pass embedded audio through, you may need a separate audio connection or a deliberate embedding step. Check whether the audio is present and correctly routed rather than inferring it from the presence of an SDI cable.
Resolution and frame rate matter as much as the connector. A device may accept one set of formats over SDI but not another, or it may support a format only on a particular input or output. Colour space, bit depth, HDR handling and signal mapping can matter too. A monitor that displays a signal is not necessarily proof that an encoder can ingest it, or that the encoder can deliver the intended stream settings.
SDI is commonly associated with 75-ohm coaxial cable and BNC connectors. Cable choice, signal rate, cable condition, connectors, patch panels and the installation affect how far a reliable signal can travel. There is no single distance that applies to all SDI installations. Follow the cable maker’s attenuation guidance and the equipment specifications, especially when a run passes through several connections or needs to work unattended.
For a permanent venue setup, test the actual cable route with the intended format, not just a short spare lead on a workbench. If the signal becomes unreliable, the solution may involve a different cable, a shorter path, a suitable equaliser or retimer, or a different transport such as fibre. Those options add equipment and setup decisions, so choose them against the real route and signal requirements rather than treating them as universal accessories.
SDI standards and link generations
SDI is a family of standards, not one universal port-and-signal definition. Common generation names include HD-SDI, 3G-SDI, 6G-SDI and 12G-SDI. SMPTE’s standards ecosystem includes specifications such as 292M, 424M, 2081 and 2082, which relate to different link generations. SMPTE’s overview of 12G-SDI mapping illustrates why the generation name alone is not a complete description of how image formats are carried.
A higher-rate label does not mean that any device with a lower-rate label will automatically accept the signal. Some devices support multiple rates; others do not. Support can also depend on a specific input, firmware or chosen format. A connector that looks physically identical may carry a signal the other device cannot decode. Treat the label as one item in the specification, not as a guarantee of interchangeability.
Make a compatibility note for each device in the chain: the SDI standard or rate supported, any relevant level or mapping, the resolution and frame rate, and whether embedded audio and required colour or HDR details are supported. The precise terminology varies by product, so use the manufacturer’s manual or specification page. A camera’s output menu, switcher input list and encoder documentation should agree on a usable combination.
Some equipment can adapt between formats or link arrangements, but conversion is not magic. A converter may change a signal into a format the next device accepts, while also introducing constraints on resolution, frame rate, audio or colour. Check what is converted and what passes through unchanged. In particular, verify that a converter is not merely changing a connector while leaving an incompatible signal intact.
Camera, switcher and encoder: the signal path
A straightforward live path looks like this:
Camera → SDI cable → switcher or encoder → network connection → YouTube
If there is a switcher, the camera feeds it over SDI. The switcher selects or combines sources and sends its programme output onward, often over another SDI connection. The encoder receives a supported video format, compresses it and sends the resulting network stream. Some devices combine switching and encoding; others do only one job. Read the role of the device as carefully as its connector list.
For example, a small event might use an SDI camera at the back of a room, a switcher near the operator and an encoder beside the network connection. The camera-to-switcher link is an SDI production connection. The encoder-to-YouTube leg is a network stream. If the picture is visible on a monitor but the stream is not reaching YouTube, the fault may be in the encoder settings, network path or destination configuration rather than the SDI link.
An encoder is not just a plug adapter. It must accept the incoming signal and produce a stream using a protocol and encoding the destination can receive. As a model-specific example, Blackmagic Design’s Streaming Encoder 4K specifications list SDI input support and network streaming capabilities. That page describes that product, not every SDI encoder; confirm the exact format and protocol for the model you intend to use.
Keep the signal path simple while commissioning. Connect the source directly to the intended input where practical, confirm a stable picture, then add the switcher, converter or longer cable one piece at a time. This makes it easier to isolate whether a failure comes from an output format, a cable route, an intermediate device or the encoder’s input configuration.
Check device and signal compatibility
Before buying or installing equipment, compare the specifications for both ends of every SDI link. The following checklist keeps the conversation focused on a signal that can actually pass through the chain.
| Check | What to confirm | Why it matters |
|---|---|---|
| Link generation or rate | Supported SDI standard and any level or mapping details | Similar-looking ports may not accept the same signal |
| Video format | Resolution and frame rate on the source and receiving input | The receiver must support the output the source is set to send |
| Colour and HDR | Colour space, bit depth and HDR support where relevant | Picture may be altered or rejected if the formats do not match |
| Audio | Embedded audio support, channel handling and routing | Video can arrive without the expected sound |
| Connector and cable | Connector type, cable specification and route | The physical link must suit the signal and installation |
| Device role | Monitor, switcher, converter, recorder or encoder | A device may pass or display video without creating a network stream |
| Network output | Supported stream protocol and encoding | The encoder’s output must suit the destination and workflow |
Use the table as a planning aid, then consult the actual manuals. Product summaries may use broad terms such as “4K” without showing every supported frame-rate combination. Find the detailed input and output format lists, and check whether a format is supported on the port you plan to use. If the manufacturer does not make a point clear, ask for confirmation before relying on it for a live event.
Cabling needs the same care. Match the cable to the signal rate and installation, and account for connectors, patch panels and any active equipment between source and receiver. A cable run that works in a temporary test may not behave the same after it is routed through a venue. For a permanent installation, test the complete route at the format you plan to stream and keep a known-good spare where a failure would interrupt the programme.
If the stream drops overnight, the production connection is only one possible cause. The network leg, encoder state and destination settings need their own checks. A methodical status log can help you separate a source or SDI issue from a network interruption; see how to measure YouTube live stream performance for useful monitoring context. Do not change several parts of a stable chain at once, since that makes the next fault harder to trace.
SDI versus network streaming protocols
SDI and a streaming protocol solve different problems. SDI carries a production signal between compatible local equipment. RTMP and SRT are examples of protocols an encoder may use to send a compressed stream over a network. The word “stream” can describe either stage in casual conversation, but the connection, signal format and troubleshooting steps are different.
| Part of the workflow | Typical connection or format | Purpose |
|---|---|---|
| Camera to switcher | SDI | Move video, and supported embedded audio, through production equipment |
| Switcher to encoder | SDI or another supported video connection | Deliver the programme output for encoding |
| Encoder to destination | Network protocol such as RTMP or SRT | Send the encoded stream to the platform |
The table describes a common arrangement, not a mandatory design. A camera may connect directly to an encoder, or a computer may perform switching and encoding. The important point is to identify where the video becomes a compressed network stream. A device with an Ethernet socket may use it for control, file transfer or streaming; check the specification to know which.
In larger facilities, managed IP media is a separate architectural choice. SMPTE describes ST 2110 as a suite for professional media over managed IP networks, with distinct synchronized flows for video, audio and ancillary data. It changes how media is routed and timed across the facility. It is not simply another SDI cable format, and it brings network design and compatible equipment requirements of its own.
For a small channel or a one-room production, SDI may be a straightforward way to link a camera and switcher if the devices already support matching formats. A managed-IP approach can offer different routing flexibility in a facility designed for it, but that does not make it a default upgrade for every stream. Compare the equipment you own, the number and location of sources, the network skills available and the consequences of a fault before selecting an architecture.
Plan an SDI workflow for a reliable stream
Start with the programme you need to produce, not with a shopping list of cables. Write down the camera or playback source, where the operator will switch or monitor, where encoding happens, and how the network reaches YouTube. Mark each link as SDI, another production connection or network transport. That simple diagram prevents the common mistake of assuming that one interface carries the picture all the way to the audience.
Next, decide which device is responsible for encoding. If a hardware encoder receives the switched output, verify that it supports the source format and the protocol required by your YouTube workflow. If a computer encodes, check how video reaches it and whether the capture device supports the same signal. Make the encoding and platform settings a separate part of the plan; an SDI-compatible camera does not settle those choices.
Then choose a format supported throughout the path. It is usually easier to begin with a shared format listed by the camera, switcher and encoder than to configure each device independently and hope they negotiate. Confirm frame rate as well as resolution, and check audio routing before the stream is live. Record the working settings so a substitute operator can restore them after a restart or equipment change.
Test in stages. Confirm the camera output and the first receiving device. Add the rest of the SDI chain and check picture and audio. Finally, test the encoder’s network output and the destination. For a 24/7 channel, leave the full arrangement running long enough to expose practical issues such as a loose connector, a device that changes state after a power cycle, or a network interruption. Note what each device reports rather than relying only on whether a preview looks normal.
A continuously running stream does not always require a camera or physical production chain. If your channel is built from a prepared video file rather than a live camera feed, SDI may not be needed at all; this article on replaying the same video file all day helps distinguish that workflow from a camera-based setup. Where the actual problem is keeping a prepared file broadcast while your own computer is off, StreamNeo removes that specific burden by running the uploaded file as a 24/7 YouTube stream; it does not replace SDI equipment in a camera production chain.
Finally, decide what you will do when the stream is interrupted. Keep the format and cabling notes near the equipment, identify which status lights or software indicators show a source fault versus an encoder or network fault, and make a restart procedure that an operator can follow. For an unattended channel, test the procedure before relying on it. A sound signal path and a recovery plan are separate requirements: the first reduces avoidable faults, while the second helps you respond when one still occurs.
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
Is SDI the same as HDMI?
No. They are different digital video interfaces, with different connector conventions and equipment ecosystems. Some products convert between them, but a conversion device must support the formats and audio handling you need; a connector adapter alone may not do the job.
Can I stream directly from an SDI camera to YouTube?
Usually, the camera’s SDI output needs an encoder between it and YouTube. The encoder accepts a supported video format, compresses it and sends a network stream using a compatible protocol. Some cameras or combined production devices may have network streaming features, so check the exact model rather than assuming the SDI output itself reaches the platform.
Will any 3G-SDI device work with another 3G-SDI device?
Not necessarily. The generation label is a useful clue, but you also need to match supported signal mapping, resolution, frame rate and relevant colour or audio features. Check both manufacturers’ specifications for the specific ports you plan to connect.
How far can an SDI cable run?
There is no universal distance because signal rate, cable characteristics, connectors and installation conditions affect the usable run. Follow the exact cable and equipment guidance, and test the complete route at your intended format. For a longer or more demanding installation, assess appropriate active equipment or another transport with a qualified installer.