Writing · Comparison

ESP32 Wi-Fi provisioning for products: SoftAP vs BLE vs SmartConfig vs Improv

For a shipping ESP32 product, pick BLE provisioning if you have a phone app and a chip with Bluetooth LE, and a SoftAP hotspot with a setup page if you do not want to ship an app. Skip SmartConfig for new designs; Espressif itself rates it below both. Improv Wi-Fi is a good fit for maker and installer flows but not for iPhone owners. Below is the comparison table, Espressif's own ratings, the support questions each method creates, and the hotspot flow our e-paper signs ship with.

Published 2026-11-18. Written for hardware founders and product teams choosing how customers will get an ESP32 device onto their network. Ratings quoted are from Espressif’s provisioning scheme comparison; our own flow is described from our firmware source.

Wi-Fi provisioning: Getting a network name and password onto a device that has no keyboard or screen input, then joining that network. It happens once at setup and again whenever the customer changes routers.

The methods side by side

MethodApp needed?Phone leaves its Wi-Fi?Chip needs BLE?Best for
SoftAP + captive web pageNo; any phone browserYes, to the device hotspotNoProducts without an app; installers on site
Unified provisioning over SoftAPYes (Espressif or your own)Yes; on iOS, manually in SettingsNoApp-based products on chips without BLE
Unified provisioning over BLEYesNo, stays on home or office Wi-FiYesApp-based consumer and prosumer products
SmartConfig (ESP-Touch)YesNoNoLegacy designs; not recommended for new ones
Improv Wi-Fi (BLE or serial)Browser or app; BLE in Chrome/Edge, not iOSNoFor BLE, yesMaker, smart-home and installer flows

Espressif’s table rates unified provisioning over BLE and over SoftAP as “Recommended”, SmartConfig as “Medium”, and both BluFi (in maintenance mode) and its own web-page provisioning example as “Not Recommended”. Improv is not in Espressif’s table; its details are from improv-wifi.com.

SoftAP: a hotspot and a setup page

The device starts its own access point, the customer joins it from a phone, and a page served by the device asks for the network and password. With a DNS catch-all, phones’ captive-portal detection usually opens the page by itself.

Where it wins

Where it costs you

BLE: the app talks to the device directly

The customer’s phone app connects to the device over Bluetooth LE and sends credentials, while the phone stays on its own network. Espressif’s unified provisioning provides the protocol and phone libraries, and the same protocol runs over SoftAP, so you can offer both.

SmartConfig: avoid for new products

The phone broadcasts packets that encode the credentials, and the device listens in promiscuous mode to decode them. Nothing has to connect, which is why it looked attractive. Espressif notes that success depends heavily on the environment, and a setup method that fails in some homes and offices is a support cost you pay per unit.

Improv Wi-Fi: open standard, maker-friendly

Improv sends credentials over BLE or serial and then hands the user a URL to finish setup. It is used by ESPHome, WLED, Tasmota and Home Assistant, so smart-home users may already know it. The catch for consumer products is the browser support Improv lists: BLE from a browser needs Chrome or Edge, and neither route works on iOS.

What our e-paper signs ship with, and why

Our ESP32-S3 + Spectra 6 signs use a SoftAP hotspot with a hand-written setup page. The flow, from the firmware:

We chose SoftAP because signs are installed by facilities staff and store teams, not by one consumer with our app already installed. We wrote the page ourselves instead of using the popular WiFiManager library because it rendered saved network names into an unescaped HTML attribute, so a name with an apostrophe broke; the replacement also saves about 60 KB of flash. The page only takes a network name and password, so it does not handle 802.1X enterprise Wi-Fi. That is the usual case for signage, and our Wi-Fi checklist for e-paper signs explains what to ask IT for instead.

Questions to answer before you pick

Provisioning is one of twelve checks in our dev kit to product checklist. For the radio itself, see ESP32-S3 vs ESP32-C6 for e-paper; for certification once the radio is chosen, see FCC certification with an ESP32 module; and for what to ask a partner who will build it, see questions to ask an e-paper hardware partner.

FAQ

What is the best Wi-Fi provisioning method for an ESP32 product?

If you ship a phone app and the chip has Bluetooth LE, BLE provisioning is usually the smoothest, because the phone stays on its own Wi-Fi. If you do not want to ship an app, a SoftAP hotspot with a captive setup page works from any phone browser. Espressif rates both transports of its unified provisioning as recommended, SmartConfig as medium and its web-page example as not recommended.

Is SmartConfig still a good choice?

Not for a new product. Espressif's provisioning comparison rates SmartConfig (ESP-Touch) as medium and says its success depends heavily on the environment, because the device decodes credentials from broadcast packets in promiscuous mode. Use unified provisioning over BLE or SoftAP instead.

Does the ESP32-S3 support BLE provisioning?

Yes, the ESP32-S3 has Bluetooth LE. Budget memory for it: Espressif's comparison puts the BLE stack at about 110 KB of RAM at runtime. Chips without Bluetooth LE, such as the ESP32-S2, can only use SoftAP-based methods.

What is Improv Wi-Fi?

A free, open standard for sending Wi-Fi credentials to a device over Bluetooth LE or serial, with SDKs. ESPHome, WLED, Tasmota and Home Assistant use it. Per its site, the browser route needs Chrome or Edge for BLE and does not work on iOS, so it suits maker and installer setups more than consumer products.

How do our e-paper signs get onto Wi-Fi?

With no saved network, the sign opens an open hotspot named after its MAC address and shows that name on its screen. Joining it brings up a setup page with a scanned network list and a password field; after saving, the sign reboots onto that network and shows a six-digit pairing code and QR code to claim it in the cloud.

Can ESP32 provisioning handle enterprise Wi-Fi (802.1X)?

The ESP32 Wi-Fi stack supports WPA2-Enterprise, but most provisioning flows, ours included, only collect an SSID and a password. For offices, ask IT for a separate pre-shared-key SSID for devices; our Wi-Fi checklist explains why.