NodeLoop
Mechanical + electrical check

M.2 Compatibility Checker: Key, Size, Bus and BIOS

Test the card notch, mounting length, socket wiring, and platform support separately. A module can fit perfectly and still use the wrong protocol.

Tool Published Jul 15, 2026 Reviewed against PCI-SIG and SATA-IO references

Four M.2 compatibility layers

1. Keying
Can the card enter the socket?
2. Mounting
Is there a standoff at its length?
3. Interface
Are the required buses routed?
4. Platform
Do firmware and drivers support it?

Reference scenarios

Start from a common installation

Replace every field with the module datasheet and host manual.

Module and host

Use documented interface names, not marketplace labels alone.

Interfaces routed at this socket

Select only buses explicitly listed in the host manual or schematic.

Supported mounting positions

Overall result

Checking...

Keying

--

Mounting

--

Interface

--

Platform

--

Decision checks

Interpretation

What the result can prove

  • Keying: B+M cards can enter B- or M-key storage sockets, but they still need the correct SATA or PCIe wiring.
  • Size: 2280 means 22 mm wide by 80 mm long. WWAN cards commonly use wider 3042 or 3052 formats.
  • Functions: a standard wireless card often splits Wi-Fi onto PCIe and Bluetooth onto USB 2.0.

Remaining uncertainty

What still needs host documentation

  • BIOS/UEFI enumeration and boot support, including storage-mode settings and lane sharing.
  • Vendor allowlists, drivers, antenna connectors, SIM routing, RF certification, cooling, and double-sided-card clearance.
  • Adapters cannot translate SATA to PCIe, CNVio to PCIe, or another protocol unless they contain an active bridge designed for it.

Common combinations at a glance

ModuleTypical keyRequired host wiringCommon trap
NVMe SSDM or B+MPCIeA SATA-only socket can share the same outline.
SATA SSDB+M, B, or MSATAMany M-key sockets are NVMe-only.
Wi-Fi + BluetoothA+E, A, or EOften PCIe x1 + USB 2.0Bluetooth can disappear when USB is not routed.
WWANBModule-specific USB or PCIeSIM, antennas, width, and firmware are host-specific.
CNVio / CNVio2E or A+EExact Intel platform interfaceNeither generation equals standard PCIe/USB.

M.2 compatibility FAQ

Does matching M.2 keying guarantee compatibility?

No. It proves only that the card can enter the socket. Protocol, mounting, power, firmware, and software support remain separate requirements.

Can a SATA M.2 SSD work in an NVMe-only slot?

No. SATA and NVMe over PCIe are different protocols. The host socket must explicitly route SATA for a SATA M.2 drive.

Why does an M.2 Wi-Fi card need both PCIe and USB?

Many cards use PCIe for the Wi-Fi function and USB 2.0 for Bluetooth. The module datasheet defines the exact split.

Does this checker guarantee a module will work?

No. It checks declared compatibility layers. The exact host manual, module datasheet, BIOS/UEFI support, drivers, thermal limits, antennas, and vendor restrictions remain authoritative.

Primary references

Model aligned to the PCI-SIG M.2 specification overview and the SATA-IO M.2 SATA reference. The CNVio warning follows Intel's CNVi compatibility guidance. The full M.2 specification contains optional configurations; the host and module documentation always take precedence.

Related M.2 resources