Short answer: A NAND or eMMC part number encodes the maker, product family, capacity and, depending on the maker, width, voltage, generation, temperature grade and package. Three rules prevent most ordering mistakes. First, raw NAND capacity is in bits and eMMC capacity is in bytes: a 2Gb raw NAND holds 256 MB, while an 8 GB eMMC holds 8 GB. Second, the same capacity does not mean the parts are interchangeable; width, voltage, interface version, temperature grade and package must also match. Third, the prefix tells you whether you are looking at a raw die or a managed device, for example Micron MT29F (raw NAND) versus MTFC (eMMC).
Raw NAND vs managed NAND
- Raw NAND is only the memory array. The host controller handles ECC, bad block management and wear leveling. Part numbers usually show the capacity in bits, the data width (x8 or x16), the generation and the voltage. Examples: Micron MT29F, Kioxia TC58.
- Managed NAND (eMMC, UFS) combines NAND and a controller behind a standard interface. Part numbers show the capacity in bytes and the interface family. Examples: Samsung KLM, Kioxia THGBM, Micron MTFC, SanDisk SDIN (iNAND).
If a part number contains a bit capacity and x8 or x16, it is usually raw NAND. If it contains a GB capacity and an eMMC or UFS family code, it is a managed device.
Example: reading a Micron MT29F part number
Micron raw NAND part numbers follow a fixed pattern. Using parts from our catalog:
| Part number | What it tells you |
|---|---|
| MT29F2G08ABAEAWP-E | MT29F = NAND flash; 2G = 2 Gb; 08 = x8; WP = TSOP package; :E = design revision (this one is 34 nm SLC, 3.3 V) |
| MT29F2G08ABAEAWP-IT-E | Same device with -IT = industrial temperature grade |
| MT29F2G08ABAGAWP-IT-G | Same 2 Gb x8 capacity and TSOP package, but a different generation (:G, 25 nm) |
| MT29F2G08ABAGAH4-IT-G | Same as above in a VFBGA package (H4) instead of TSOP |
The letters between the width and the package code describe the cell type, die configuration, voltage, generation and interface. Their exact meaning is defined in Micron's part numbering chart and the datasheet, so use those for anything beyond the fields above. The table also shows why the full code matters: these four parts share "MT29F2G08", but differ in temperature grade, generation or package.
Example: Samsung and Kioxia eMMC
| Part number | What it tells you |
|---|---|
| KLMAG1JETD-B041 | KLM = Samsung eMMC; AG = 16 GB; the following characters identify generation and version; -B041 identifies package and grade |
| KLM8G1GETF-B041 | KLM8G = 8 GB Samsung eMMC |
| THGBMNG5D1LBAIL | THGBM = Kioxia eMMC family (this one is 4 GB in a 153-ball BGA); later characters encode capacity, generation, package and version |
Managed NAND codes change from generation to generation, so do not guess the eMMC version (4.5, 5.0 or 5.1) from the middle of the code. Check the datasheet or the maker's ordering guide. For Samsung capacity codes, see our Samsung eMMC selection guide; for DRAM, see Reading DRAM Part Numbers.
What to read from any NAND or eMMC part number
| Field | Raw NAND | eMMC / UFS | Why it matters |
|---|---|---|---|
| Capacity unit | Bits (2Gb = 256 MB) | Bytes (8 GB) | Converting quantities and capacity correctly |
| Data width | x8 or x16 | Fixed by the interface | Affects the controller connection on raw NAND |
| Voltage | VCC, for example 3.3 V or 1.8 V | VCC and VCCQ, for example 3.3 V and 1.8 V | A mismatch does not work |
| Interface | Asynchronous, ONFI or Toggle | eMMC 4.5 / 5.0 / 5.1; UFS 2.x / 3.x | Performance and host compatibility |
| Temperature grade | Commercial or industrial, usually a suffix | Commercial, industrial or automotive, usually a suffix | Essential for wide-temperature products |
| Package | TSOP, BGA, WSON and others | BGA | Replacements must match the footprint |
Common mistakes
- Mixing up bits and bytes: a 2Gb raw NAND is 256 MB. Ordering it as if it were a 2 GB part is an error of eight times.
- Ignoring the temperature suffix: the same base part often exists in commercial and industrial grades. For wide-temperature products, order the industrial code.
- Assuming the eMMC version: eMMC 5.1 and 4.5 differ in speed, and the host must support the version and bus mode.
- Ignoring the package: the same capacity from another maker can use a different package or ball map. Compare the footprint before switching.
- Ignoring the revision: a change in the last characters can mean a different generation with different behavior. For critical projects, lock one complete code.
Send us your requirements
Send us the part numbers or BOM you need decoded or cross-checked, with the yearly volume. We will confirm what each code means and suggest equivalent options. We reply to routine inquiries within 1 business day. Submit your BOM.