nRF52840 vs ESP32 for Wearables: Power, BLE and SDK

Concept render

Choose the nRF52840 for a BLE-only wearable that syncs through a phone: as of November 2026, Nordic lists 6.40 mA radio transmit at 0 dBm and about 1 to 3 µA idle. Choose an ESP32-S3 when the device must reach Wi-Fi by itself or needs more compute, and plan for 176 mA Bluetooth LE transmit peaks.

Teams building a ring, band, pendant or clip-on recorder often shortlist Nordic's nRF52840 and Espressif's ESP32 family. This guide is for the product or engineering lead who has to commit a wearable to one of them. It compares radios, published currents, firmware stacks and certified modules, then gives a decision table. Every figure comes from a vendor datasheet or a regulator text linked on this page, as of November 2026. We ran no measurements for this article.

nRF52840 vs ESP32: what is the core difference?

The difference is the radio. The nRF52840 is a Bluetooth LE and 802.15.4 chip with no Wi-Fi. The ESP32 family pairs Wi-Fi with Bluetooth. A wearable on an nRF52840 needs a phone, a hub or another radio to reach the internet. A wearable on an ESP32-S3 can upload to your backend directly whenever it sees a known access point.

"ESP32" covers several chips. This page uses the original ESP32 (the classic ESP32) and the newer ESP32-S3. The classic ESP32 adds Classic Bluetooth (BR/EDR). The ESP32-S3 drops it: Espressif's ESP-IDF guide says both of its Bluetooth hosts on ESP32-S3 support LE only (ESP-IDF v6.1 Bluetooth LE overview, as of November 2026).

Sources, as of November 2026: Nordic nRF52840 product page, Nordic nRF52840 Product Brief, ESP32-S3 Series Datasheet v2.2, ESP32 Series Datasheet v5.3, ESP32-S3-WROOM-1 Datasheet v1.8.

How do nRF52 vs ESP32 radio and sleep currents compare?

This is where the two families split for battery products. Read the conditions before you compare: Nordic quotes the nRF52840 at 3 V with the on-chip DC/DC converter. Espressif measures the ESP32-S3 at 3.3 V and 25 °C, with transmit current rated at a 100% duty cycle as a peak. The classic ESP32 radio rows are at 3.3 V and 25 °C with transmitters at a 50% duty cycle.

nRF52840: Nordic Product Brief, specifications table (DC/DC at 3 V). ESP32-S3: Datasheet v2.2, Tables 5-8 and 5-10. ESP32: Datasheet v5.3, Tables 4-2 and 5-4. All as of November 2026.

Radio current

At 0 dBm, the published Bluetooth LE transmit figure is 6.40 mA for the nRF52840 and 176 mA peak for the ESP32-S3, a ratio of about 27. Receive is 6.26 mA against 93 mA. These rows cover the chip only, without your sensors, microphone or regulator.

Sleep floor between radio events

A wearable spends most of its life between radio events. The ESP32-S3 datasheet says wireless connections can remain active in Light-sleep, and that in Deep-sleep only the RTC is powered on, with connection data stored in RTC memory. So a device that keeps a phone connection open sits at Light-sleep or above between events. The datasheet's 240 µA Light-sleep figure is measured with VDD_SPI and Wi-Fi powered down. The nRF52840 lists 0.97 to 3.16 µA in System ON, depending on RAM retention and the RTC, with the radio idle. As a floor between events, that is roughly 75 to 250 times lower. Neither figure is the average current while a link is held: on both chips, each connection event adds radio current on top of the floor, and you need to measure that on your own board. If you add PSRAM to the ESP32-S3, its footnotes add 40 to 200 µA to Light-sleep, depending on the PSRAM type.

What does the current gap mean for a wearable battery?

A short worked example shows the scale. It uses chip rows only, and two numbers are assumptions: the radio duty cycle and the battery capacity. Replace both with your own.

Assumptions (yours to replace):
  radio transmitting 1% of the time, idle the other 99%
  100 mAh cell, all of it usable

nRF52840:  0.01 × 6.40 mA + 0.99 × 0.00316 mA = 0.067 mA
           100 mAh / 0.067 mA = about 1,490 h, or about 62 days

ESP32-S3:  0.01 × 176 mA + 0.99 × 0.240 mA = 2.00 mA
           100 mAh / 2.00 mA = about 50 h, or about 2 days

The chip-level gap is about 30 times in this example. On the ESP32-S3, the idle term (0.24 mA) is already larger than the whole nRF52840 average. The choice matters most for small cells, where a bigger battery is not an option.

Three cautions apply. The two vendors measure under different conditions. A real duty cycle depends on your connection interval, payload and retries. And the rest of the device adds its own current; on a voice wearable the microphone path can dominate. Use the chip rows to rank options, then measure the whole device. Our guide to testing and stating battery life honestly covers the measurement plan.

nRF Connect SDK or ESP-IDF: which firmware stack fits your team?

The SDK decides how your firmware team works every day, so weigh it alongside the currents.

• nRF52840: nRF Connect SDK. Nordic's documentation describes the nRF Connect SDK as its software development kit for nRF52, nRF53, nRF54, nRF70 and nRF91 Series devices, and says it integrates the Zephyr RTOS (nRF Connect SDK introduction, as of November 2026). Zephyr is licensed under Apache 2.0 and supports Arm Cortex-M, Tensilica Xtensa, RISC-V and other architectures (Zephyr introduction, as of November 2026).
• ESP32 family: ESP-IDF. Espressif's framework offers two Bluetooth LE hosts on ESP32-S3, ESP-Bluedroid and ESP-NimBLE, and the current documentation is ESP-IDF v6.1. The same page says ESP32-S3 is certified for Bluetooth LE 5.4. One framework covers Wi-Fi, Bluetooth and the rest of the chip.

Ask which stack your firmware team already ships on, who owns OTA updates and secure boot on it, and how the SDK version will be pinned for the product's life. A stack nobody on the team knows adds schedule risk. For the wider question of whether an MCU is enough at all, see MCU or Linux SoC for an AI wearable.

Which certified modules exist, and what does FCC still require?

For a small batch, a pre-certified module can save you from authorizing a radio design of your own. The two vendors differ here. Espressif sells its own modules and lists their certificates. Nordic's product brief lists chip packages only, and its product page points to third-party modules. Certified modules built on the nRF52840, such as the u-blox NINA-B3 series, come from module makers.

Sources, as of November 2026: Espressif certificates page (Espressif says this page will move to a new documentation site), ESP32-S3-WROOM-1 Datasheet v1.8, u-blox NINA-B3 Data sheet UBX-17052099 R15. The table names one nRF52840 module whose data sheet we read in full.

What a modular grant covers

Under 47 CFR 15.212, a single modular transmitter needs its own RF shielding, buffered modulation and data inputs, its own power supply regulation, a permanently attached or unique antenna coupler, and stand-alone testing. If the module's FCC ID is not visible once installed, the host carries a label such as "Contains FCC ID" followed by the ID. The module must also meet RF exposure requirements in its final configuration (47 CFR 15.212, Cornell LII reproduction, as of November 2026). Compare that text with the eCFR original before you rely on it.

Two points follow. A chip placed directly on your own board has no modular grant behind it, so your product's radio needs its own authorization. And a grant covers stated antennas and conditions: the NINA-B3 data sheet points to a list of approved antennas in the u-blox system integration manual, and says its modules are certified for any radio stack, though only Nordic's S140 SoftDevice is allowed in Bluetooth products. Read those notes for any module you pick. This is an engineering summary and is not legal advice. If you choose an ESP32, ESP32 dev board to custom PCB covers the module or chip-down choice and what else changes on your own board.

Which chip fits which wearable?

Start from what the device must do with no phone in reach. The table gives a first cut. Your own power budget and board measurements settle it.

Also check the lifecycle status of the exact part. The ESP32 datasheet v5.3 marks several classic ESP32 variants as Not Recommended for New Designs, and one as end of life. u-blox lists some NINA-B31 variants as end of life or obsolete in its data sheet. A part that suits a prototype can be wrong for a product you plan to build for years.

What should you ask your hardware team?

• Must the device reach the internet without a phone? If yes, which radio carries that link?
• Which sleep mode holds the phone link between radio events, and what does our own board draw in it?
• Do we need Classic Bluetooth, Thread, Matter, USB or NFC? Which of those does each candidate list?
• How much RAM do our audio buffers, model and BLE stack need, with margin?
• Are we using a certified module or putting the chip on our own board? If a module, which grant, which antennas and which radio stack does its approval cover?
• Which SDK and RTOS does our firmware team already know, and who owns OTA updates on it?

If you are choosing a radio platform for a wearable, tell us about your device. You can also read the platforms we design with.

Sources

All pages accessed November 5, 2026. Re-read them before you rely on any figure.

• Nordic Semiconductor, nRF52840 product page: https://www.nordicsemi.com/Products/nRF52840
• Nordic Semiconductor, nRF52840 Product Brief: https://www.nordicsemi.com/-/media/Software-and-other-downloads/Product-Briefs/nRF52840-SoC-product-brief.pdf
• Nordic Semiconductor, nRF Connect SDK introduction: https://nrfconnectdocs.nordicsemi.com/ncs/latest/nrf/index.html
• Espressif, ESP32-S3 Series Datasheet v2.2: https://documentation.espressif.com/esp32-s3_datasheet_en.pdf
• Espressif, ESP32 Series Datasheet v5.3: https://documentation.espressif.com/esp32_datasheet_en.pdf
• Espressif, ESP32-S3-WROOM-1 and WROOM-1U Datasheet v1.8: https://documentation.espressif.com/esp32-s3-wroom-1_wroom-1u_datasheet_en.pdf
• Espressif, ESP-IDF v6.1 Bluetooth LE overview for ESP32-S3: https://docs.espressif.com/projects/esp-idf/en/stable/esp32s3/api-guides/ble/overview.html
• Espressif, certificates and compliance listing: https://www.espressif.com/en/support/documents/certificates
• Zephyr Project, introduction: https://docs.zephyrproject.org/latest/introduction/index.html
• u-blox, NINA-B3 series data sheet UBX-17052099 R15: https://content.u-blox.com/sites/default/files/NINA-B3_DataSheet_UBX-17052099.pdf
• 47 CFR 15.212, Cornell Legal Information Institute reproduction: https://www.law.cornell.edu/cfr/text/47/15.212