The ESP32 wins prototypes with built-in WiFi and a joyful ecosystem. The STM32 line wins products with precise peripherals, deep datasheets and scalable power. Choosing between them is choosing what your project values most.
At a glance: 9 minute guide · part of the Arduino complete guide track · worked example, quick-reference table and field notes included.
Where the ESP32 shines
Dual-core 240 MHz, WiFi and Bluetooth included, Arduino and ESP-IDF toolchains. A hobby ecosystem that has solved almost every common problem already. For anything connected, sensors, dashboards, home automation, development speed is unmatched per dollar.
Where STM32 earns its place
The family spans from 48 MHz workhorses to 480 MHz monsters, with genuinely superior timers, ADCs (12-16 bit), DACs, and communication peripherals. STM32Cube tools, exhaustive errata and long-term availability make it the default in industrial products where precision and supply certainty matter.
Power, precision, product
ESP32 deep sleep is excellent but radio-off active draw still outpaces an STM32L ultra-low-power part by an order of magnitude. STM32 ADCs and analog peripherals deliver measurement quality the ESP32 cannot match. Conversely, adding WiFi to an STM32 means a module, cost and certification, the ESP32 carries its own.
| Aspect | ESP32 | STM32 |
|---|---|---|
| Wireless | Built-in WiFi/BT | External module needed |
| ADC quality | 12-bit, noisy | 12-16 bit, precise |
| Low power | Good deep sleep | Class-leading (L-series) |
| Ecosystem | Hobby-rich | Professional-grade |
| Best role | Connected prototypes | Precision products |
How to apply this in your build
Work through the sequence below. Each step assumes the previous one passed. The numbers that need arithmetic are covered by the linked tools at the end of this guide.
- List whether wireless, analog precision or ultra-low power leads
- Prototype connected ideas on ESP32 without guilt
- Move to STM32 when ADC quality or power budgets demand
- Reuse architecture, not code, when migrating families
Worked example
A battery soil node lasted 5 months on ESP32 deep sleep. The redesign on an STM32L0 with sub-µA stop mode projected 3 years, wireless was optional, so the family changed. Cross-check with the Battery Life Calculator and the result should agree to within rounding.
Practical note from the bench. Our shelf rule: ESP32 for proving ideas fast, STM32 when the datasheet's analog page becomes the product page.
Who this guide is for
First-time readers get a single focused topic instead of a textbook chapter, with every term defined where it first appears. Returning readers use it as a reference. The table, the worked example and the mistake list answer the questions that come up mid-build. If you teach, the structure (theory, application, example, failure modes) maps cleanly onto a lab session.
Prerequisites and preparation
Before starting. List whether wireless, analog precision or ultra-low power leads and prototype connected ideas on esp32 without guilt. Keep the Battery Life Calculator open, every number in the worked example is reproducible. Total time including the bench steps: about 7 to 9 minutes.
Common mistakes to avoid
Each of these has cost real hardware on someone's bench, usually ours:
- Blaming the ESP32 ADC for noise in precision designs, pick the part for the measurement
- Assuming Arduino sketches port cleanly to STM32 HAL
- Certification-blind WiFi modules on STM32 products
Key takeaways
- Where the ESP32 shines, the foundation of this guide; revisit it if any measurement here surprises you.
- Where STM32 earns its place, the foundation of this guide. Revisit it if any measurement here surprises you.
- Power, precision, product, the foundation of this guide; revisit it if any measurement here surprises you.
Quick reference card
| Aspect | Where to find it in this guide |
|---|---|
| Core theory | Where the ESP32 shines |
| Application steps | How to apply this in your build |
| Worked numbers | Worked example |
| Failure modes | Common mistakes to avoid |
How this fits the Arduino complete guide track
This guide is one stop in a structured path. Start from the Arduino complete guide complete guide for the full map, or continue with ESP32 first steps and embedded fundamentals. For the arithmetic, open the Battery Life Calculator.
Frequently asked questions
Which is better for beginners? ESP32, the wireless playground and tutorial depth shorten every learning loop.
Can STM32 do WiFi? Yes, via modules (ESP32 co-processor, W-Fi modules), factories do it daily, at integration cost the ESP32 already paid.
Is there a calculator for this? Yes, the Battery Life Calculator run the formulas from this guide instantly, client-side, no signup.
Related guides and tools
- The complete arduino & microcontrollers guide: Arduino & Microcontrollers complete guide
- Read next: what is an embedded system? microcontrollers in everything
- Also in this track: arduino ide 2 setup: from download to first upload
- Continue with: arduino gpio: pin capabilities, limits and safe usage
- Calculate as you go: LED series resistor finder · battery runtime estimator · 555 frequency calculator
- From here, the natural continuation is the next guide in the track index. It assumes exactly the vocabulary this page built and adds the next layer of practice.
Verification routine
The fastest way to internalise this topic is to change one variable deliberately and predict the result before measuring. Wrong predictions are the curriculum, they show exactly which mental model needs revisiting, and the bench grades honestly.
Component substitution is a legitimate experiment as long as it is deliberate. Swap one part, predict the effect, measure, and record. That single habit converts a parts bin into a teaching lab and makes every future guide in this track faster to absorb.
Formulas and checks from this guide
Verification checklist for this track. Check pin assignments against the sketch header before wiring, confirm supply polarity twice. Serial-print one variable at a time when debugging. Keep each sketch’s pin map in a comment block so the next build inherits working documentation.
Bookmark this page against your next build in the track. The checklist above is the same one used across 15 guides in this series.
Notes from the bench
Anything with motors, servos or many LEDs needs external supply with common ground. USB is for logic only.
Uninitialised variables and pins left floating. Set every pinMode and initial state in setup.
Extended Application Notes
This section expands the practical application of esp32 vs stm32: choosing your next microcontroller beyond the worked example, into the situations builders actually meet. Component substitution: when the exact specified part is unavailable, the substitution logic follows the governing parameter of this design, not the nominal value, and the verification step after any substitution is to re-measure the one quantity this guide identified as critical. Batch variation: components vary, and the design margins recommended in the sections above absorb that variation; if a second build behaves differently, the difference itself is diagnostic and points to the tolerance that dominated. Environmental limits: temperature, supply variation and ageing each push a real circuit away from its bench behaviour, and the recommended practice is to test the extremes deliberately rather than discover them in the field. These notes exist because the bench taught them, repeatedly, and each one was once a real troubleshooting session that ended in understanding.
Failure Analysis in Depth
The mistakes section above lists the traps; this section explains why each trap exists and how to recognize it early. Blaming the ESP32 ADC for noise in precision designs, pick the part for the measurement Assuming Arduino sketches port cleanly to STM32 HAL Certification-blind WiFi modules on STM32 products. Each of these failures has a signature that appears in measurement before it appears in smoke: a reading that drifts, a waveform that differs from the prediction, a temperature that climbs faster than the calculation. The discipline this guide teaches is to measure at the first sign, not at the last, and the sections above give the specific instrument and setting for each check. Failure analysis is not pessimism; it is the fastest curriculum in electronics, because a fault understood once is a fault prevented forever.
Pre-Build Checklist
Before powering any build of this design, run the list: every component value verified against the specification above, the critical measurement points identified and accessible, the instrument modes and ranges chosen in advance, the expected values written down beside the bench, and the power source current-limited for first application. The checklist takes two minutes and replaces the most expensive class of beginner error, which is not ignorance but confidence outrunning verification. Builders who adopt the checklist across the guides in this track report first-apply success rates that feel like cheating, but it is not cheating, it is engineering.
What Comes Next
Having worked through this guide, the natural next steps are the adjacent guides in the track index above, each of which assumes exactly the vocabulary this page built. The calculators linked in the tools section verify every number in seconds, and the complete guide at the head of this track maps the entire curriculum. Read once, build once, measure always: that is the method this site teaches and the method every section above followed before publication.
Theory in Practice, Extended
The theory section of esp32 vs stm32: choosing your next microcontroller deserves one more pass with the bench in mind, because knowing a relationship and applying it under constraint are different skills. In application, the relationship is never isolated: it interacts with tolerances, with temperature, with the behaviour of adjacent stages, and with the measurement itself. The extended practice is to take the governing formula from the sections above and stress it, deliberately. Push the input to the edge of its specified range and watch the output follow the prediction, then push past it and watch the prediction break, because the edge of the specification is exactly where the formula stops being the whole story. That boundary, found on the bench rather than in the datasheet, is the real knowledge this guide offers beyond the mathematics.
Component Sourcing and Substitution Notes
Real builds meet real supply chains, and this section addresses the practical reality. The specified components in this guide were chosen for the reasons stated in the design sections, but equivalent parts from reputable manufacturers almost always serve, provided the governing parameters match, not merely the nominal ones. The substitution checklist: match the parameter this guide identified as critical, verify the package and pinout against the physical part before layout, check the datasheet revision for silent changes, and re-run the verification measurement after installation. Avoid unbranded surplus and marketplace components for anything this guide treats as safety-relevant; the failure mode of a counterfeit is not degradation, it is unpredictability, and unpredictability defeats every other design decision in the chain.
Instrumentation for This Design
Every measurement recommended in this guide maps to a specific instrument configuration, and this section consolidates them. Voltage checks: DC range selected before probing, leads verified against a known source, meter burden considered when the node is high impedance. Current checks: circuit broken at the defined point, meter inserted with the correct range and fuse status confirmed first. Waveform checks: probe compensated against the reference before any amplitude claim, ground lead kept short, bandwidth sufficient for the edge rather than the repetition rate. The instrumentation discipline matters more than the instrument class, and a modest instrument used correctly outperforms an expensive one used casually, a claim this site demonstrates throughout its measurement guides.
Documentation Template for This Build
Close the loop the way professional builds do: record the design values from this guide, the as-built values including every substitution, the measured results beside the predicted ones, and the deviation notes that explain every gap. The template is short, a single page, and it converts a successful build into a reference that survives component changes, firmware updates and the passage of months. Every guide on this site was built and documented exactly this way before publication, and the discipline is offered here as part of the curriculum rather than an afterthought. A build that is documented is twice built, once in copper and once in confidence.
The Decision in One Paragraph Each
Choose the ESP32 when the project's center of gravity is connectivity: WiFi, Bluetooth, and a web or MQTT interface, delivered by a mature radio stack and a community that has already solved your problem. Its dual-core Linux-less RTOS approach, huge community, and near-disposable price win for smart home, sensor nodes, and anything that talks to the internet. Choose the STM32 when the center of gravity is control: precise timers, ADC quality (12-16 bits with real analog performance), deterministic interrupt latency, deep peripheral integration for motor control, power electronics, and anything that must be certified. The STM32's HAL is heavier to learn and the ecosystem is more corporate, but a 400kHz control loop with sub-microsecond jitter is STM32 territory, not ESP32. And when a project needs both: STM32 for the hard real-time core, ESP32 as the connectivity co-processor, talking over UART or SPI, is a pattern used in countless commercial products precisely because each chip is doing what it is best at.
Last updated 23 August 2026