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
| Method | App needed? | Phone leaves its Wi-Fi? | Chip needs BLE? | Best for |
|---|---|---|---|---|
| SoftAP + captive web page | No; any phone browser | Yes, to the device hotspot | No | Products without an app; installers on site |
| Unified provisioning over SoftAP | Yes (Espressif or your own) | Yes; on iOS, manually in Settings | No | App-based products on chips without BLE |
| Unified provisioning over BLE | Yes | No, stays on home or office Wi-Fi | Yes | App-based consumer and prosumer products |
| SmartConfig (ESP-Touch) | Yes | No | No | Legacy designs; not recommended for new ones |
| Improv Wi-Fi (BLE or serial) | Browser or app; BLE in Chrome/Edge, not iOS | No | For BLE, yes | Maker, 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
- No app to build, publish and maintain on two app stores.
- Works on any phone or laptop with a browser, and on chips without Bluetooth LE.
- Easy for installers: the same steps on every unit, no account needed on the installer's phone.
Where it costs you
- The phone leaves its own Wi-Fi during setup, and some phones jump back to mobile data or the home network because the hotspot has no internet.
- You own the setup page: escaping, languages and layout are yours to get right. Espressif rates its own web-page example "Not Recommended", citing flash space and the age of the example.
- Unless you add one, there is no secure channel to the device; an open hotspot means anyone nearby during setup can join it.
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.
- Best experience when you already ship an app: no network switching, and the app can show progress and errors.
- Needs Bluetooth LE on the chip and memory for the stack; Espressif puts it at about 110 KB of RAM at runtime.
- You maintain phone apps and Bluetooth permission prompts on both platforms.
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:
- No saved network: the sign opens a hotspot named 8frames-setup- plus the last four hex digits of its MAC, and draws that name on the e-paper screen so the installer knows which one to join.
- A DNS catch-all redirects captive-portal checks to the setup page, which lists scanned networks and asks for a password. It is available in English and Korean.
- The portal times out after five minutes and the sign restarts.
- After saving, the sign reboots onto the network, registers, and draws a six-digit pairing code and a QR code on screen to claim it in the cloud.
- To change networks later: on our 13.3-inch board, a long press clears only the Wi-Fi details and keeps the cloud pairing, schedule and cached images; on the 7.3-inch board a long press is a full factory reset.
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
- Who sets the device up: a consumer, an installer, or your own team at the factory?
- Will you ship a phone app anyway? If yes, BLE is close to free.
- Does your chip have Bluetooth LE, and can you spare the RAM?
- What share of your customers use iPhones? That rules Improv over BLE in or out.
- How does a customer change routers without a support call, and without opening the enclosure?
- What does the device show while it waits? A screen, an LED or nothing changes how much you need to explain.
- Does setup also claim the device to an account, or is that a second step?
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.