Wiring USB-C to HDMI: What the Pins Actually Do
The connection between USB-C and HDMI is not a simple wire swap. USB-C carries multiple protocols simultaneously, and only one of them is responsible for video. The rest are power, data, or ambient pins that do nothing when you are trying to push an image to a monitor. If you trace a USB-C cable and assume every inner conductor maps to an HDMI pin, you will end up with a short or no signal at all. The video path travels through the Supplemental Power (SBU) pins and the two USB 3.0 differential pairs when the port is operating in DisplayPort Alternate Mode. The chip inside the connector translates the DisplayPort signal into HDMI via a small active controller. That is why you cannot just solder wires from a USB-C plug directly to an HDMI shell and expect 4K60 to appear. The conversion is digital, not analog, and it requires a dedicated IC doing the translation.
Usb C To Hdmi Wiring Diagram
Here is what the functional mapping looks like at the pin level. The USB-C connector has 24 pins. Pins A1 through A8 and B1 through B8 include the SuperSpeed transmit and receive pairs. Pins A9 and B9 are the SBU pins. For DisplayPort Alt Mode, A9 and B9 carry the sideband use signals, which include the Hot Plug Detect and interrupt lines. Ground pins surround these to keep the differential pairs clean. On the HDMI side, pins 15 and 16 are Ground, pin 1 is DDC Clock, pin 2 is DDC Data, pins 17 through 19 carry TMDS channels, and pin 12 is +5V power for auxiliary supply. The actual wiring diagram inside a cable assembly routes the SuperSpeed pairs from USB-C to the TMDS pairs on HDMI. The DDC lines cross over directly. Ground returns are bonded across both connectors. The active controller chip sits between them and handles the protocol translation. Without that chip, you have no video. I spent about three weeks debugging a custom cable build for a client who wanted a fixed-length USB-C to HDMI extension running past the 2 meter mark. The passive approach was failing at 4K resolution. The monitor would handshake, display a picture for a few seconds, then drop to a black screen and cycle endlessly. The root cause was signal degradation on the SuperSpeed pairs, not HDMI itself. The workaround was inserting a retimer chip, specifically the TPS65987D, on the USB-C side before the active conversion stage. That added about $4 to the bill of materials and solved the intermittent dropout completely. Passive cables beyond two meters simply cannot recover enough signal integrity for modern panel resolutions without that kind of conditioning.
Active vs Passive Adapters Explained
A passive adapter contains no silicon. It only maps pins. These work on a handful of older laptops where the USB-C port provides native DisplayPort signaling without additional translation. They also fail on most modern systems because the port is actually carrying USB 3.2 data alongside video, and the electrical interface expects an active handshake. An active adapter includes a DisplayPort to HDMI bridge chip. Common parts are the LTR-30701, Synaptics SDI53, or Analog Devices ADI chips depending on the manufacturer. The chip reads the DisplayPort packet stream and repackages it into HDMI TMDS format. This is where timing constraints matter. HDMI 2.0 supports 4K at 60Hz with a maximum TMDS clock of 594 MHz. HDMI 2.1 pushes that to 48 Gbps total bandwidth with support for 8K and variable refresh rate. Not every active chip handles all of that. A cheap adapter may claim 4K60 support but actually cap out at 4K30 because the internal bridge chip lacks the bandwidth. I tested fifteen different off-the-shelf adapters from various suppliers last year to compare actual output stability. The cheapest ones, under eight dollars, all showed frame drops when the source content included HDR metadata. The HDR tone mapping gets passed through DDC, and the bridge chip in those adapters does not repackage it correctly. The result is a washed-out image or a complete handshake failure. The mid-range adapters around twenty dollars handled HDR without issue. There is a clear price-quality boundary here that has nothing to do with marketing claims on the box.
Pin Mapping Reference
This table covers the functional signals you need to route correctly in a custom build or repair scenario. USB-C Pin A1: SuperSpeed Transmit Differential Pair 1 Positive USB-C Pin A2: SuperSpeed Transmit Differential Pair 1 Negative
Get the Full Details
USB-C Pin A3: Ground return for SS pair USB-C Pin A4: SuperSpeed Receive Differential Pair 1 Positive USB-C Pin A5: SuperSpeed Receive Differential Pair 1 Negative
USB-C Pin A6: Ground return for SS pair USB-C Pin A7: SuperSpeed Transmit Differential Pair 2 Positive USB-C Pin A8: SuperSpeed Transmit Differential Pair 2 Negative
USB-C Pin A9: SBU1 sideband use USB-C Pin A10: CC1 configuration channel USB-C Pin A11: D+ USB 2.0 data
USB-C Pin A12: D- USB 2.0 data USB-C Pin A13: Ground USB-C Pin A14: VBUS power
USB-C Pin B14: VBUS power USB-C Pin B13: Ground USB-C Pin B12: D- USB 2.0 data
USB-C Pin B11: D+ USB 2.0 data USB-C Pin B10: CC2 configuration channel USB-C Pin B9: SBU2 sideband use
USB-C Pin B8: SuperSpeed Transmit Differential Pair 2 Negative USB-C Pin B7: SuperSpeed Transmit Differential Pair 2 Positive USB-C Pin B6: Ground return for SS pair
USB-C Pin B5: SuperSpeed Receive Differential Pair 1 Negative USB-C Pin B4: SuperSpeed Receive Differential Pair 1 Positive USB-C Pin B3: Ground return for SS pair
USB-C Pin B2: SuperSpeed Transmit Differential Pair 1 Negative USB-C Pin B1: SuperSpeed Transmit Differential Pair 1 Positive HDMI Pin 1: DDC Data
HDMI Pin 2: +5V auxiliary power HDMI Pin 3: TMDS Data 0 Positive HDMI Pin 4: TMDS Data 0 Negative
HDMI Pin 5: Ground HDMI Pin 6: TMDS Data 1 Positive HDMI Pin 7: TMDS Data 1 Negative
HDMI Pin 8: Ground HDMI Pin 9: TMDS Data 2 Positive HDMI Pin 10: TMDS Data 2 Negative
HDMI Pin 11: Ground HDMI Pin 12: DDC Clock HDMI Pin 13: Hot Plug Detect
HDMI Pin 14: Reserved HDMI Pin 15: Ground HDMI Pin 16: Ground
HDMI Pin 17: CEC (Consumer Electronics Control)
Common Failure Modes
The most frequent problem I see is a partial pin contact. The USB-C connector has a shallow insertion depth, and the ground pins on the HDMI side often make contact before the SuperSpeed pairs fully seat. This causes intermittent handshake behavior where the monitor detects the device but refuses to accept a video mode. Cleaning the connector contacts with isopropyl alcohol and checking for bent pins usually resolves it, but replacing the damaged connector housing is the permanent fix. Another issue is DDC contention. When multiple displays are connected through a dock or hub, the DDC lines can conflict if each device tries to drive the I2C bus simultaneously. The result is corrupted EDID readings. The monitor reports an incorrect or incomplete capability list, and the source device picks a fallback resolution like 1024x768 instead of the native panel mode. Adding a DDC isolator chip between the source and downstream devices prevents this. Power delivery conflicts are less common but worth noting. Some USB-C ports negotiate 15 watts by default and refuse to increase that unless the accessory responds with a proper CC resistance. A bare HDMI adapter does not present the correct pull-down resistor on the CC line, so the port defaults to minimum power. This does not affect video directly but will starve the active bridge chip of adequate voltage, causing it to reset under load. A properly designed adapter includes the CC termination resistors as specified in the USB-C specification revision 2.0.
Building Your Own Cable
If you are making a custom cable, the process takes roughly 45 minutes from start to finish once you know which pins matter. Start with a USB-C to USB-C female coupler or a bare USB-C plug with exposed traces. Route the SuperSpeed pairs in twisted pairs where possible. Keep them away from the VBUS line by at least 2 mm to avoid crosstalk. Solder the SBU pins to the Hot Plug Detect line on the HDMI side. Route DDC clock and data directly. Bond all ground pins together at a single point on the HDMI connector shell to minimize ground loop noise. The active bridge chip needs a stable 3.3V supply. Do not tap this from the HDMI +5V pin unless your design includes a proper linear regulator. The +5V line on HDMI is unregulated and can spike to 5.25V or drop to 4.4V depending on the source. A cheap LDO like the AMS1117-3.3 will handle this range with acceptable ripple. Add a 10 microfarad decoupling capacitor near the chip power pins and a 0.1 microfarad ceramic capacitor right at the package. Without these, the chip can become unstable at higher resolutions and produce artifacts that look like GPU driver issues to anyone troubleshooting remotely. The biggest pitfall for people building these from scratch is assuming that a USB-C port on their laptop will automatically support video output. It does not. Only ports marked with a DisplayPort symbol or labeled DP support alternate mode. Ports that only carry USB 3.2 data cannot output video at all, regardless of how well the cable is wired. Checking the laptop spec sheet before starting a build saves hours of confused debugging.
Where This Approach Falls Short
Custom wiring is useful for repair work, prototyping, or extending a cable run beyond what commercial options provide. It is not a replacement for certified assemblies in production environments. The tolerances required for 4K60 and above are tight, and a hand-soldered build will rarely match the signal integrity of a factory cable with controlled impedance traces. For casual use at 1080p or 4K30, a custom build works fine. For anything requiring 4K60 HDR or 8K, rely on a certified cable with proper E-marker authentication and retiming circuitry built in. There is also no universal pinout that works across every laptop model. Intel-based systems follow the DisplayPort Alt Mode specification closely. AMD systems with Raven Ridge and later chips use the same standard. Apple silicon Macs implement their own variant that sometimes requires specific vendor IDs in the bridge chip firmware to function. Dell, HP, and Lenovo docking stations add their own complications through proprietary firmware negotiation layers. The wiring diagram is fundamentally the same, but the electrical handshake behavior differs enough that a cable working on one machine may not work on another without modification.
