M.2, NVMe, SATA, and PCIe SSDs Explained: Form Factors, Interfaces, Keying, Lanes, and Compatibility

M.2 is a small card and connector form factor used for several device classes, including SSDs. SATA-IO’s M.2 material explicitly defines an internal M.2 connector capable of carrying SATA as well as PCI Express signaling. That is why “M.2” by itself does not tell you whether an SSD communicates through SATA or PCIe, and it is not a synonym for NVMe.

NVM Express defines how host software communicates with non-volatile memory and maintains separate transport specifications, including NVMe over PCIe. NVMe is therefore a storage protocol/interface family rather than a physical connector. In a typical client PC, an “M.2 NVMe SSD” means an M.2 storage module using NVMe over PCIe, but the M.2 shape alone does not establish that protocol or interface.

A conventional 2.5-inch SATA SSD is a drive-shaped device connected through SATA data and power connections. An M.2 SATA SSD packages solid-state storage on an M.2 module but still uses the SATA host interface. Moving the same interface into an M.2 module changes the mechanical packaging and cabling, not the fact that the storage link is SATA.

An M.2 PCIe SSD instead uses PCI Express connectivity. Modern client PCIe SSDs commonly use the NVMe protocol, but PCIe and NVMe remain different layers: PCIe supplies the transport link while NVMe defines the storage communication model. A motherboard socket must therefore support the drive’s actual interface and protocol; two drives can both be M.2 modules while requiring different electrical support from the host.

M.2 modules and sockets use keyed notches to prevent some physically incompatible combinations. Kingston’s technical M.2 guidance identifies B-key, M-key, and B+M-key as the common storage-key arrangements. A B-key storage connection can support SATA and/or PCIe depending on the implementation and is associated with up to two PCIe lanes; an M-key storage connection can support SATA and/or PCIe and can expose up to four PCIe lanes. A B+M-key module can physically fit more socket arrangements, but that does not make the device protocol-agnostic.

The host and SSD still need a shared interface after the key physically fits. The module length also has to fit the board. Common SSD sizes such as 2230, 2242, 2260, 2280, and 22110 encode a 22 mm module width followed by the approximate length in millimetres. The motherboard or system must provide the required socket space and mounting point for the exact module size.

PCI Express uses point-to-point links built from one or more lanes. An M.2 storage slot described as PCIe x4 can expose four lanes, while another implementation can provide fewer lanes. The PCIe generation and the negotiated lane width together determine the theoretical link capacity available between the SSD and its host connection.

Those link labels are not application-performance guarantees. A PCIe 4.0 x4 slot does not prove that every installed SSD will saturate that link, and an older-generation connection does not translate into one universal real-world slowdown. SSD controller design, NAND behavior, queue depth, workload, firmware, caching, and thermals all affect measured performance. Treat generation and lane width as interface constraints first; use representative testing only when making performance conclusions.

Motherboards can mix CPU-connected and chipset-connected M.2 sockets, and individual slots on the same board can expose different protocols. ASUS’s ProArt Z690-CREATOR WIFI is a concrete example: its M.2_1 slot is listed under the processor and uses PCIe connectivity, while chipset-connected M.2_2 and M.2_3 are PCIe-only and M.2_4 supports both PCIe 4.0 x4 and SATA modes. All four are M.2 storage sockets, but they are not wired identically.

The same board also demonstrates why lane-sharing notes matter. ASUS states that M.2_4 shares resources with SATA6G_5 through SATA6G_8 and suspends those SATA ports when a SATA or NVMe device is detected in that M.2 slot. That is an exact-board rule, not a universal property of M.2, NVMe, SATA, or the Z690 chipset. Compatibility therefore has to be checked against the specific motherboard slot and its sharing notes rather than inferred from the connector shape.

An SSD can satisfy the mechanical and electrical requirements of a slot while boot support remains a separate firmware question. The NVM Express Boot specification exists specifically to define consistent interaction between pre-OS environments such as BIOS or UEFI and operating systems when booting from NVMe interfaces. That is different from merely proving that the device can be connected to PCIe.

For a boot drive, check that the motherboard or system firmware supports booting from the intended storage interface and that the target operating system provides the required storage support. Legacy systems can have different firmware and driver limitations even when an adapter or slot can electrically expose the device. Use the exact motherboard/system and operating-system documentation rather than assuming that “the BIOS sees the drive” or “the slot is M.2” automatically proves bootability.

M.2 NVMe SSD controllers can reduce performance when thermal limits are reached. That protective thermal throttling behavior means sustained transfer performance can change as the drive heats up, but the relevant temperature limits and cooling requirements are properties of the exact SSD and system rather than universal values for every NVMe drive.

Whether an SSD needs a motherboard heatsink, an integrated heatsink, or only normal case airflow depends on the drive, workload, slot position, nearby components, and enclosure airflow. Check the SSD manufacturer’s cooling requirements and the motherboard’s physical clearance before stacking an aftermarket heatsink under a GPU or motherboard cover. Thermal behavior affects sustained operation; it should not be confused with SATA-versus-PCIe protocol compatibility.

Start with the exact motherboard or system manual and identify the specific M.2 socket you intend to use. Confirm the supported module lengths, keying, SATA and/or PCIe mode, PCIe generation and lane width, and whether the slot is processor- or chipset-connected. Then match those facts against the SSD’s form factor, key, interface, protocol, and physical size. Read every lane-sharing or disabled-port note for that exact slot.

If the SSD will be a boot drive, verify firmware and operating-system boot support as a separate gate. Then check heatsink requirements and physical clearance. Only after those compatibility checks are complete should performance, endurance, capacity, warranty, and price influence a buying decision. Core Tech Tips does not turn an M.2 label, an NVMe logo, or a PCIe x4 specification into an automatic compatibility or performance score.