Short answer: NOR flash is built for fast random reads and code execution: you can read any byte directly and often run code in place (XIP). NAND flash is built for density and low cost per bit: it reads and writes in pages, erases in large blocks, and needs ECC and bad-block management. Use NOR for boot code, firmware and small read-mostly data, typically up to 256–512Mb. Use NAND, raw or SPI, for data storage, file systems and anything from about 1Gb upward.
NOR vs NAND comparison table
| NOR flash | NAND flash (SLC) | |
|---|---|---|
| Read access | random, byte-addressable | page-based (for example 2,048 + 64 spare bytes on a 1Gb SLC part), page loaded into a buffer first |
| Random read latency | low | higher: page read time in the tens of microseconds (W25N01GV: up to 25 µs with ECC off, 60 µs with ECC on) |
| Execute in place (XIP) | yes | no; code must be copied to RAM |
| Program / erase unit | program by page (often 256 bytes), erase by 4 KB sector or 32/64 KB block on SPI NOR | program by page, erase by block (often 128 KB = 64 pages) |
| Write and erase speed | slow | much faster per byte |
| Bad blocks | none at shipment | allowed at shipment (W25N01GV: up to 20 of 1,024 blocks) and can grow over life |
| ECC | not required | required (many SPI NAND parts include on-die ECC) |
| Typical endurance | minimum 100,000 cycles per sector, over 20-year retention (W25Q128JV) | about 100,000 cycles with the required ECC (W25N01GV: over 100,000, 10-year retention) |
| Typical density | 16Mb – 1Gb (up to 2Gb) | 512Mb – 16Gb (SLC); far more in managed NAND |
| Cost per bit | higher | lower, especially above 1Gb |
| Typical use | boot code, firmware, FPGA configuration, fonts and small assets | data logging, Linux file systems, images, audio, large firmware |
Values are typical; check the datasheet of the exact part. Rated endurance is similar for NOR and SLC NAND; the practical difference is that NAND needs ECC and bad-block handling to reach it.
When to use NOR flash
- Boot and firmware storage. Most MCUs and many SoCs boot directly from SPI NOR. XIP lets an MCU execute code without copying it into RAM.
- Reliability without host overhead. NOR has no bad blocks and does not need ECC, which keeps the software simple.
- Small, frequently read data. Configuration, calibration tables, bitmap fonts and icons, where random access speed matters.
- Densities up to about 256–512Mb, where NOR is still cost-effective.
When to use NAND flash
- Data storage and file systems. Logging, user data and Linux root file systems on raw or SPI NAND, typically with UBI/UBIFS or a flash translation layer.
- Large assets. Graphics, animations and audio for HMIs. A single 800 × 480 RGB565 full-screen image is 750 KB uncompressed, so a full UI library quickly reaches hundreds of megabytes.
- Densities of 1Gb and above, where cost per bit favors NAND.
- Write-heavy workloads, because NAND programs and erases much faster.
Many products combine both: a small SPI NOR for boot code and fonts, plus SPI NAND for images and data. When you need gigabytes, managed NAND (eMMC or UFS) takes over ECC and wear leveling; see eMMC vs UFS.
SPI vs parallel interfaces
- SPI NOR (single, dual, quad and octal modes) is the default for MCUs: few pins and enough bandwidth for XIP in quad or octal mode.
- Parallel NOR suits legacy and some high-reliability designs that need very fast random access on a parallel bus.
- SPI NAND gives NAND density on the same few pins as SPI NOR, and many parts include on-die ECC and bad-block mapping helpers.
- Parallel (ONFI-style) NAND offers higher throughput for processors with a NAND controller.
Representative parts
| Type | Part number | Brand | Density / note |
|---|---|---|---|
| SPI NOR | W25Q16JVSSIQ | Winbond | 16Mb, 3 V |
| SPI NOR | W25Q128JVSIQ | Winbond | 128Mb, 3 V |
| SPI NOR | W25Q64JWSSIQ | Winbond | 64Mb, 1.8 V |
| SPI NOR | MX25L12835FM2I-10G | Macronix | 128Mb, 3 V |
| SPI NOR | MX25R6435FM2IL0 | Macronix | 64Mb, 1.65–3.6 V low power |
| SPI NOR | MT25QL128ABA1ESE-0SIT | Micron | 128Mb, 3 V |
| SPI NOR | W25Q01JVZEIQ | Winbond | 1Gb |
| Parallel NOR | MT28EW128ABA1LJS-0SIT | Micron | 128Mb, 2.7–3.6 V, TSOP-56 |
| SPI NAND | W25N01GVZEIG | Winbond | 1Gb SLC |
| SPI NAND | W25N02KVZEIR | Winbond | 2Gb SLC |
| SPI NAND | MT29F2G01ABAGDWB-IT-G | Micron | 2Gb SLC, industrial |
| SPI NAND | TC58CVG1S3HRAIJ | Kioxia | 2Gb SLC, 3.3 V, WSON8 |
| Parallel NAND | TC58NVG0S3HBAI4 | Kioxia | 1Gb SLC, –40 to +85 °C |
More parts: Winbond, Macronix, Micron, Kioxia.
Selection checklist
- Size the content: code, fonts, images and data, plus 20–30% headroom for updates.
- Check the boot path: which flash types and interfaces the MCU or SoC boot ROM supports.
- Match the supply voltage: 3 V and 1.8 V versions of the same density are different part numbers.
- Plan software for NAND: ECC, bad-block management and wear leveling, or a file system that provides them.
- Consider temperature and data retention for long-life and high-temperature products.
- Pick a validated second source. Serial NOR from different makers is often footprint-compatible, but command sets, status registers and protection bits differ. Test before switching.
Need NOR or NAND flash for your design?
SUNTEC supplies serial and parallel NOR and NAND from Winbond, Macronix, Micron and Kioxia. Send the density, voltage, package and quantity; we reply within 1 business day and can suggest footprint-compatible alternatives. Submit your BOM.
References
- Winbond, W25Q128JV serial NOR flash data sheet (Rev. F: endurance, retention, page and erase sizes)
- Winbond, W25N01GV serial SLC NAND data sheet, Rev. G (page and block structure, read time, bad blocks, on-die ECC)
- Kioxia, serial interface NAND news release (2019)
- Kioxia, serial NAND product brief