Route the query, do not clone the page
Common connector searches
These mappings add the vocabulary people actually type to local search and point each phrase at one durable reference route. They intentionally avoid generating one nearly-identical page for every keyword variation.
M12 connector codes explained
A-, B-, D-, X-, L-, S-, T-, K-, M- and Y-coded M12 forms, kept separate from exact network, power and device behavior.
Open the canonical reference →NEMA plug and receptacle types
Resolve common NEMA numbers and plug/receptacle suffixes to the represented connector records without treating shape as wiring or installation approval.
Open the canonical reference →What does a USB-C port support?
Separate the USB-C connector from USB generations, USB4, Thunderbolt, video and charging capabilities.
Open the canonical reference →RJ45 vs 8P8C vs Ethernet and PoE
Separate the familiar modular connector shape from Ethernet service, link rate, pin assignment and PoE behavior.
Open the canonical reference →PC power connector types
Browse ATX, CPU, GPU and modern auxiliary PC-power connector forms without inferring interchangeability from contact count.
Open the canonical reference →Mini-SAS, SlimSAS, OCuLink and MCIO names
Resolve common server and storage interconnect names and SFF identifiers before checking lane count or protocol implementation.
Open the canonical reference →CompactFlash, CFast, XQD and CFexpress types
Distinguish removable-media families and physical forms before checking a camera or reader.
Open the canonical reference →Fiber connector types
Browse represented optical connector forms while keeping fiber type, polish, transceiver and link-budget questions separate.
Open the canonical reference →Coax connector types
Browse BNC, TNC, SMA, N-type and other coaxial forms by shell and coupling without inferring frequency or impedance.
Open the canonical reference →Audio connector types
Browse analog and professional-audio connector forms while keeping contact count, channel role and signal assignment separate.
Open the canonical reference →HDMI, DisplayPort, DVI and VGA connector types
Browse physical display connector forms without treating connector shape as a version or mode guarantee.
Open the canonical reference →IEC appliance connector names
Resolve cloverleaf, figure-8 and common computer-power names to IEC coupler records before checking equipment requirements.
Open the canonical reference →USB internal header types
Distinguish the USB 19-position front-panel header from Key-A internal USB-C header terminology.
Open the canonical reference →EDSFF 1C vs 2C vs 4C vs 4C+
Identify the represented SFF-TA-1002 physical variation while keeping implementation-specific logical assignment and device support separate.
Open the canonical reference →PCIe x1 vs x4 vs x8 vs x16 slot size
Separate PCIe mechanical slot/card-edge form from active lanes, generation, bifurcation and exact platform support.
Open the canonical reference →Mini PCIe vs mSATA vs M.2
Keep the shared Mini PCIe/mSATA socket family distinct from M.2 and from device-specific electrical implementation.
Open the canonical reference →Mini-XLR pin numbers and wiring
Use Mini-XLR contact numbering for orientation without treating pin numbers as universal microphone, headset or device wiring.
Open the canonical reference →LEMO 3T vs 4A vs 00 triax connectors
Separate represented triax series and impedance context without inferring universal camera, CCU or instrumentation wiring.
Open the canonical reference →Does USB-C mean USB 3, USB4 or Thunderbolt?
Separate USB-C connector form from data generation, USB4, Thunderbolt, video and charging capability.
Open the canonical reference →USB-C charges but no display
Explain why charging and display transport remain separate port/cable capability questions.
Open the canonical reference →Why USB-C cables have different speeds
Route USB-C speed confusion into exact cable capability, marking, host and device evidence.
Open the canonical reference →Are all USB-C cables the same for charging?
Keep USB-C endpoints separate from cable-specific charging/current evidence and the complete power path.
Open the canonical reference →Does HDMI shape tell the HDMI version?
Separate HDMI connector form from specification version and exact cable/device capability.
Open the canonical reference →Why is a DisplayPort/HDMI adapter directional?
Keep source/sink direction and active/passive conversion separate from physical connector fit.
Open the canonical reference →Is RJ45 the connector or Ethernet?
Separate the familiar modular physical form from Ethernet service, link rate and PoE.
Open the canonical reference →Can I tell Cat5e, Cat6 or Cat6A from the plug?
Use jacket and exact product evidence for cable category instead of inferring it from a familiar modular plug.
Open the canonical reference →Are all BNC cables 75 ohms?
Keep BNC connector appearance separate from cable impedance, construction and system performance.
Open the canonical reference →Can LC and SC fiber connect just because an adapter fits?
Separate physical LC/SC mating from fiber type, polish, wavelength, transceiver and optical-budget requirements.
Open the canonical reference →Does an XLR cable work with every microphone setup?
Keep 3-pin XLR cable form separate from equipment wiring, phantom power and exact signal role.
Open the canonical reference →Why can a connector fit but still not work?
Treat physical fit as only one layer among direction, protocol, conversion, cable capability, power, performance and exact-device evidence.
Open the canonical reference →How many contacts do SD and microSD cards have?
Identify the conventional first row without assuming every SD generation has the same contact count.
Open the canonical reference →SDHC, SDXC, UHS-I, U3 and V30: which label answers which question?
Separate card shape, capacity family, bus interface and recording class instead of comparing unlike labels.
Open the canonical reference →Do microSD Express and microSD UHS-II use the same extra contacts?
Two cards can share the microSD outline without sharing their second-row geometry or host interface.
Open the canonical reference →Why do VGA pinout tables disagree?
Compare named device manuals instead of combining their assignments into a universal HD15 wiring map.
Open the canonical reference →Does VGA carry audio?
Keep the conventional VGA video path separate from the audio path and any combined cable assembly.
Open the canonical reference →What do RCA colors mean: audio, composite or component?
Read labels and signal roles before choosing a connection by color.
Open the canonical reference →Will a VGA-to-RCA cable convert my video signal?
Separate a documented multi-mode port and breakout cable from actual signal conversion.
Open the canonical reference →HDMI to RCA or RCA to HDMI: which direction does the converter support?
Compare two named powered converters by input, output, separate audio and power—not by the connector pair alone.
Open the canonical reference →Why can three RCA plugs mean component video or composite plus audio?
Keep three-channel video separate from one video signal plus two audio channels, using named cable-series and converter evidence.
Open the canonical reference →Does TOSLINK have an electrical pinout?
Separate the optical cable interface from the electronics in a transmitter, receiver or combination socket.
Open the canonical reference →Is Mini-TOSLINK the same as a 3.5 mm headphone plug?
Similar size is not a signal specification; check the exact socket’s documented role.
Open the canonical reference →Why can a TOSLINK cable fit an ADAT port but not produce sound?
Connector fit does not select the receiver’s digital mode or supply a missing audio decoder.
Open the canonical reference →Does a Mini-TOSLINK adapter convert analog audio?
Distinguish optical form adaptation from signal conversion and device capability.
Open the canonical reference →How should I count DVI contacts: grid, blade or analog group?
Read DVI-D and DVI-I single-/dual-link counts without mixing a visible contact pattern with a numbered assignment table.
Open the canonical reference →Does a full DVI contact grid prove dual-link support?
Use a documented monitor and dock example to distinguish a connector’s physical positions from implemented digital links.
Open the canonical reference →DVI to VGA: when is a passive adapter not enough?
Separate access to a documented analog signal from conversion of a digital-only signal.
Open the canonical reference →Which DVI pinout view am I looking at?
Keep receptacle-front orientation, digital-only and integrated assignments, and device-specific labels separate.
Open the canonical reference →Can I reverse a DVI-to-VGA converter?
Start with the documented source and display, then distinguish passive analog adaptation, active conversion and a bidirectional digital cable.
Open the canonical reference →Why does a DVI adapter have a USB lead?
A USB connection can have a different documented job on different adapters. Separate optional power from audio insertion.
Open the canonical reference →HDMI/DVI cable or USB-audio adapter: what changes?
Do not promote bidirectionality, a full DVI grid or a published timing into unsupported audio and performance guarantees.
Open the canonical reference →FC vs ST: what should I check before connecting them?
Separate connector coupling, ferrule construction and hybrid adapters from polish and optical-path requirements.
Open the canonical reference →Can I connect UPC and APC fiber connectors together?
Do not confuse a hybrid patch cord or a non-contact test port with direct mating of unlike polished endfaces.
Open the canonical reference →BNC, Mini-BNC and HD-BNC: are they the same connector?
A panel-density illustration is not a mating-interface drawing, and similar names do not identify the same counterpart.
Open the canonical reference →Does an HD-BNC connector guarantee 75 ohms or 12G-SDI?
Separate physical form, impedance, the named 12G subset and a complete path’s operating requirements.
Open the canonical reference →Does an M.2 key tell me SATA, PCIe or NVMe support?
Keep the module format, key, wired interface, storage protocol and exact host requirements separate.
Open the canonical reference →Does M.2 2242 or 2280 tell me whether a drive will fit?
Decode nominal module sizes without turning a format code into a mating drawing or clearance guarantee.
Open the canonical reference →Are Mini PCIe, mSATA and M.2 the same connector?
Distinguish a shared socket outline from its electrical role, then separate both from M.2.
Open the canonical reference →Why can installing M.2 disable SATA ports or change PCIe lanes?
Use one exact motherboard manual to separate connector shape from CPU wiring and shared resources.
Open the canonical reference →Will an M.2 adapter or USB enclosure work with my SSD?
Read the drive-facing and host-facing requirements separately, with two named products rather than a universal adapter rule.
Open the canonical reference →How do I read a fiber patch-cable label?
Separate connector ends, each end’s polish, fiber category, fiber count and path mapping before checking the equipment.
Open the canonical reference →Does a reversible LC uniboot prove the polarity of my link?
Keep a named cable’s factory mapping, its change mechanism and the actual end-to-end duplex path separate.
Open the canonical reference →What does A–B mean on a one-fiber simplex cable listing?
Do not turn generic marketing wording into a documented two-fiber mapping.
Open the canonical reference →Is a hybrid fiber adapter the same as a hybrid patch cord?
Separate a documented mechanical coupler from an assembled fiber cable and from an optical compatibility result.
Open the canonical reference →Is CFexpress Type A or B the same as its generation?
Separate the physical type, specification generation, protocol and exact equipment support.
Open the canonical reference →Does an XQD slot automatically support CFexpress Type B?
Use an exact firmware example without extending it to every camera or reader.
Open the canonical reference →What do UDMA, UHS and USB mean on a multi-card reader?
Keep each card slot’s interface separate from the computer connection.
Open the canonical reference →Do two supported card families mean two usable slots?
Distinguish alternative cards, physical slots, insertion and simultaneous access.
Open the canonical reference →Is VPG the same as a card’s read speed or USB speed?
Check sustained-write profile requirements separately from offload claims.
Open the canonical reference →How do USB-C cable power and data markings differ?
Read watts and data rates independently; a power-only USB 2 marking is not a no-data verdict.
Open the canonical reference →Does a USB logo prove an exact cable is certified?
Separate program rules, public listing scope and an authentic exact-product match.
Open the canonical reference →Is an e-marked USB-C cable necessarily active?
An electronic marker and signal-conditioning electronics answer different questions.
Open the canonical reference →Does a 120 Gbps Thunderbolt 5 cable mean 120 Gbps both ways?
Keep balanced links, display-driven bandwidth boost and application throughput separate.
Open the canonical reference →What should I check on a long active USB-C cable?
Keep exact length, retimer construction, USB modes, display conditions and power separate.
Open the canonical reference →Which Nikon Z 8 USB-C socket is for data, and which is for power?
The two USB-C sockets have different documented jobs; computer detection and camera power are not interchangeable.
Open the canonical reference →Which CalDigit TS4 USB-C ports are for data, power or a display?
Keep the ordinary USB-C data group separate from the host and downstream Thunderbolt connections.
Open the canonical reference →How do Elgato 4K X input, passthrough and USB capture differ?
An image on the connected display does not prove that the same signal can be captured in the requested format.
Open the canonical reference →How many HDMI outputs does ATEM Mini Pro ISO have, and what is USB-C for?
One HDMI program output is not the same as the specification’s total-output count or the USB interface’s list of uses.
Open the canonical reference →A search phrase is routing metadata, not a new hardware fact. Keeping one canonical destination reduces duplicated copy, stale claims and competing near-duplicate pages.
These discovery surfaces route and reorganize facts already represented in the atlas. They do not add electrical ratings, universal pinouts, measured tolerances, exact-device support, wiring approval or an end-to-end compatibility result.