M.2 Form Factor

M.2 · NGFF

How M.2 dimensions, B/M keying, SATA or PCIe, software support and cooling determine whether an SSD fits and works.

Glossary entry on hesela.dev · JSON record

In one minute

M.2 is a family of compact module form factors and connections used for storage and other devices; an M.2 SSD is not necessarily NVMe, and matching its connector does not establish host compatibility.

Start with the layers. SSD describes a storage device, M.2 its module family, PCIe or SATA its connection, and NVMe a host/device interface. The PCI-SIG public summary includes connectorized and soldered-down M.2 variants; this card concentrates on removable storage modules. NVM Express lists multiple physical formats for NVMe, so NVMe does not mean M.2 either. [1] [4]

Read the whole mechanical envelope. A 2280 module is 22 mm wide and 80 mm long; that code alone does not specify component height or whether components occupy both faces. The SNIA presentation documents separate single-sided and double-sided profiles. Check the host's supported length and fixing point as well as clearance above and below the board. [2] [3]

Do not identify the protocol from a notch. B+M keying can permit insertion into either corresponding connector, but only a shared interface makes the device usable. It does not mean the SSD automatically speaks both SATA and PCIe. A host may support one or both interfaces, and the board manual may reserve or share connections with another port. [3]

PCIe is not historically synonymous with NVMe. SNIA's 2014 presentation explicitly distinguishes SATA/AHCI, PCIe/AHCI and PCIe/NVMe configurations. That is evidence of separate interface choices, not a claim about today's market share. Neither a key letter nor the M.2 label identifies a PCIe generation, negotiated lane count or measured transfer rate. [2]

Separate discovery from boot qualification. Intel's Windows boot guide treats firmware support and OS NVMe drivers as different requirements, and confirms bootability by actually starting independently from the SSD. Its 905P support page likewise lists separate boot and secondary-drive setup requirements, including GPT for the documented boot setup. These are scoped platform examples, not a universal OS-version requirement for all M.2 SSDs. [7] [6]

A real host contract is more specific than M.2. Sony's PS5 instructions require a PCIe Gen4x4 NVMe module with M-key, supported length and a cooling assembly within the stated envelope; SATA M.2 is excluded. Sony also warns that an expansion SSD need not deliver the same game performance as internal storage. These are requirements for that console, not requirements imposed on every M.2 host. [5]

Qualify performance and serviceability separately. A compact module may be convenient inside a notebook but is not equivalent to a front-accessible U.2 or EDSFF drive bay. The NVM Express form-factor overview distinguishes these service models. For a concrete installation, retain the host manual, SSD model and firmware, enabled ports, cooling configuration and intended workload as the compatibility record. [4]

Compatibility checks

Use the checklist as a sequence of independent gates. Passing the connector check does not imply that the interface, boot path or thermal checks pass.

M.2 compatibility checks: what each label can and cannot establish

Physical footprint: Relevant evidenceSupported width, length and fixing point; 2280 means 22 x 80 mm. [2] [3]; Not establishedThat the module or heatsink fits vertically.
Connector and interface: Relevant evidenceMatching key plus explicit host and drive interface support. [3]; Not establishedThat B+M means SATA, or that an M-key proves NVMe.
PCIe path: Relevant evidenceHost configuration, allocated lanes and shared-port restrictions. [3]; Not establishedA transfer rate from the M.2 name.
Software and boot: Relevant evidenceFirmware boot support and the required OS driver and installation path. [6]; Not establishedThat detecting a secondary drive qualifies it as a boot drive.
Cooling and service: Relevant evidenceHost clearance, cooling and powered-off installation instructions. [5] [4]; Not establishedHot-swap capability or a universal temperature limit.

M.2 compatibility checks: what each label can and cannot establish
Check	Evidence to obtain	Do not infer
Physical footprint	Supported width, length and fixing point; 2280 means 22 x 80 mm. [2] [3]	That the module or heatsink fits vertically.
Connector and interface	Matching key plus explicit host and drive interface support. [3]	That B+M means SATA, or that an M-key proves NVMe.
PCIe path	Host configuration, allocated lanes and shared-port restrictions. [3]	A transfer rate from the M.2 name.
Software and boot	Firmware boot support and the required OS driver and installation path. [6]	That detecting a secondary drive qualifies it as a boot drive.
Cooling and service	Host clearance, cooling and powered-off installation instructions. [5] [4]	Hot-swap capability or a universal temperature limit.

Strengths

Compact integration: modules attach close to the host board without a conventional drive bay; the form-factor family also accommodates devices other than SSDs. [1]
Several physical sizes: the platform designer can select a module footprint and component-height arrangement appropriate to the enclosure. [2]
Separate choices of package and interface: M.2 provides storage options using SATA or PCIe rather than imposing one performance class. [4]

Limits

A matching notch is not a compatibility certificate. The host must support the device's interface, and shared ports or lanes may impose additional configuration restrictions. [3]
Footprint is not the whole envelope: component sidedness, heatsink clearance and cooling requirements must also fit the host. Sony's console requirements illustrate these separate checks. [5]
Ordinary directly installed M.2 SSD modules are not designed for powered insertion or removal. A carrier or enclosure has its own service contract; do not infer hot-swap support from the module inside it. [4]

Typical fits

Checking an existing host's storage-upgrade compatibility before selecting a module.
Distinguishing a module's physical format from the interface and boot support required by a storage design.

Uncertainty notes

Source-based engineering guidance, not a hardware qualification test or benchmark. No device is certified compatible by this page.
The full PCI-SIG specification was not accessed. The historical SNIA slides establish the cited interface and mechanical distinctions; their forecasts and generation-specific speed examples are not current specifications.
Vendor support pages are used for their stated scope. Kingston's legacy blanket claim that all PCIe M.2 devices use AHCI drivers is not adopted; Sony and Intel examples are not generalized to other platforms.

Sources

01PCI-SIG: PCI Express M.2 Specification Revision 5.1. Public scope summary only; full specification not accessed. · accessed 2026-10-17
02SNIA: All About M.2 SSDs, June 2014 webcast, slides 14-17. Historical interface options, dimensions, sidedness and keys; not current market or performance data. · accessed 2026-10-17
03Kingston: SSD FAQ. Sections on B+M key compatibility, motherboard lane sharing and supported lengths; not the legacy blanket AHCI-driver claim. · accessed 2026-10-17
04NVM Express: NVMe Form Factors, Part III: The Importance of Form. Interfaces, serviceability and form-factor distinctions. · accessed 2026-10-17
05Sony: How to add an M.2 SSD to a PS5 console. Host-specific interface, size, cooling and performance requirements. · accessed 2026-10-17
06Intel: System Requirements for an Optane SSD 905P Series Drive, article 000028298. Product-specific distinction between boot and secondary-drive setup. · accessed 2026-10-17
07Intel: PCIe NVMe Boot Installation Guide, 337143-004US, November 2021, pages 5-6 and 15. Windows/Intel-specific guidance distinguishing firmware, OS drivers and actual boot confirmation. · accessed 2026-10-17