ESP Partition Table Inspector
Inspect how an ESP partition table divides device memory. See each region and catch overlaps or out-of-bounds areas before flashing.
A selected file takes precedence over pasted text. Six columns, up to 256,000 characters and 95 entries. Blank offsets use documented alignment.
Documented 32-byte entries only, up to 4 KiB. Optional ESP-IDF partition MD5 is validation data, not a general-purpose hash choice.
Bootloader CSV rows require target-specific offset configuration and are unsupported in this interface. Inspect the generated raw binary table instead. Ordinary CSV rows use blank automatic offsets, not N/A.
Use your board’s actual flash capacity. This checks whether each named region fits in memory; the 4 MiB default is an example, not device detection.
Paste ESP-IDF CSV or choose a raw binary table.
Background worker · local memory only
Waiting for a partition table
| Name | Type | Subtype | Area | Offset | Bytes | Flags |
|---|
WARNINGS
LAYOUT BEFORE FLASH
See every region.
Catch collisions early.
CSV and documented binary.
CSV supports ESP-IDF’s six fields, numeric K/M sizes, blank automatic offsets, current app, data, and partition-table names, plus encrypted or read-only flags. Binary mode accepts the official 32-byte entry structure, end marker, and optional partition-table MD5 record.
Warnings require judgment.
The map and table flag overlaps, the reserved partition-table sector, non-sector-aligned offsets and app sizes, non-64-KiB application offsets, unknown codes, and ranges beyond your selected flash size. They do not prove that a layout matches a particular board or bootloader.
Labels must fit the format and decode as UTF-8. They are inserted as text only. Parsing happens in one cancellable job; edits, Clear, and leaving the page terminate or invalidate it.