esp-idf-size
In the field of IoT development, memory constraints are a common challenge, often requiring developers to optimize their application size. Whether it involves ensuring the firmware fits within available flash memory or analyzing impact of code changes on the final binary size, effective firmware size management is essential for resource efficiency. The esp-idf-size tool provides developers with the means to explore statically allocated RAM used by the final binary firmware image generated by ESP-IDF SDK for Espressif devices.
The esp-idf-size tool is included in the ESP-IDF and is installed
automatically. It can be accessed using the idf.py command or the
idf_size.py wrapper. The idf.py command provides access to the most
commonly used esp-idf-size commands and automatically sets some options for
user convenience, while the idf_size.py wrapper allows full access to all
esp-idf-size features. For more information on using esp-idf-size in
ESP-IDF, please refer to
Minimizing Binary Size.
Starting from version 2.0.0, esp-idf-size uses the new generation (NG)
implementation by default, providing improved performance and additional features
compared to the legacy version.
Breaking Changes in v2.0.0:
- The new generation functionality is now the default behavior
- Legacy
--ngflag andESP_IDF_SIZE_NGenvironment variable are no longer needed - Output formats may differ from the legacy version (
jsonvsjson2)
Migration Guide:
- Remove
--ngflags from your commands - the new functionality is now default - Update any imports from
esp_idf_size.ngtoesp_idf_size - Review and update any scripts that parse the output format
For more detailed information about the available features and options, please refer to the documentation available here.
Metadata
Release files for esp-idf-size 2.3.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| esp_idf_size-2.3.2.tar.gz | 64.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| esp_idf_size-2.3.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 135.9 kB
Release files / esp_idf_size-2.3.2.tar.gz
| Download URL | esp_idf_size-2.3.2.tar.gz |
|---|---|
| Size | 64.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d99479bd903f436b3f68b9edd5680108abe8ec85d0f015e657e20f82e48b5a66
|
|
BLAKE2b-256 checksum How to use checksums |
42c1bd96f62b1f0332bcaea6125ee3e56b9f86fd50f3b0e1c44ce37b47090d73
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logRelease files / esp_idf_size-2.3.2-py3-none-any.whl
| Download URL | esp_idf_size-2.3.2-py3-none-any.whl |
|---|---|
| Size | 71.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dd395d7baa2693bc0b6092a50bf4dadf31a0a8a8f0920c6da3dcde6c75b2a9ef
|
|
BLAKE2b-256 checksum How to use checksums |
9e688ea7f4f702c168e7ba238ba9d1fb636fe2b8701a6c1f1408920e030073a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency log