Writing · Question
Do you need CE marking if you use a certified ESP32 module?
Yes. In the EU the finished product carries the CE mark, and its manufacturer signs the declaration of conformity under the Radio Equipment Directive. A module like the ESP32-S3-WROOM-1 with published CE test reports lets your lab reuse much of the radio-spectrum work, but EMC, electrical safety, RF exposure, technical documentation and, since 1 August 2025, the EN 18031 cybersecurity requirements are assessed on your product. The Cyber Resilience Act adds more from 2026 and 2027. The table below shows what the module covers and what stays with you.
Published 2026-11-19. Written for hardware founders and product teams taking an ESP32 device to the European market. We build battery e-paper signs on ESP32-S3 and E Ink Spectra 6. We are not a test lab or a notified body, and this is not legal advice: use it to prepare for the conversation with an accredited lab, and check every point against the current texts.
Why the module’s CE documents don’t cover your product
The Radio Equipment Directive (2014/53/EU) applies to radio equipment placed on the EU market, and the thing you place on the market is your sign, sensor or controller, not the module inside it. Its manufacturer is the one who runs the conformity assessment, keeps the technical file, signs the EU declaration of conformity and puts the CE mark on the product.
That is the main difference from the US. Under FCC rules a modular grant can carry the transmitter approval into a host product, which is why our FCC guide can say “usually no new FCC ID”. There is no equivalent transfer in Europe. What Espressif publishes, on its certificates page, are CE documents and test reports per module. The ESP32-C6-MINI-1 document, for example, lists conformity with EN 300 328, the radio spectrum standard for 2.4 GHz equipment, alongside EMC standards. A lab can lean on those reports for the radio part of your assessment, which is where most of the saving comes from. It still has to look at your product.
CE marking (for radio equipment): The manufacturer’s claim that the finished product meets the essential requirements of the directives that apply to it. For a Wi-Fi or Bluetooth device that is mainly the RED, which covers safety and health, EMC, efficient use of radio spectrum and, for connected devices, cybersecurity.
What the module covers and what you still owe
| Requirement | Module covers it? | What that means |
|---|---|---|
| Radio spectrum, RED Art. 3.2 | Partly covered | Module CE reports (EN 300 328 for 2.4 GHz Wi-Fi and Bluetooth LE on Espressif's documents) can be reused if you keep the antenna, power and firmware settings they were tested with |
| EMC, RED Art. 3.1(b) | Yours | Your whole board: MCU clocks, panel driver, charger, DC-DC converters, any cable that leaves the case |
| Electrical safety, RED Art. 3.1(a) | Yours | Enclosure, battery, charger and power supply; the RED has no lower voltage limit for this, unlike the Low Voltage Directive |
| RF exposure | Yours | Assessed for how your product is used; a wall sign is a different case from a wearable |
| Cybersecurity, RED Art. 3.3(d)(e)(f), EN 18031 | Yours | Applies since 1 August 2025 to internet-connected radio equipment; the module helps, the product is assessed |
| Technical documentation | Yours | Test reports, risk assessment, schematics, firmware version, user instructions, kept for inspection |
| EU declaration of conformity and CE mark | Yours | Signed by the manufacturer of the finished product, naming the product, not the module |
| Cyber Resilience Act | Yours, from 2026/2027 | Reporting obligations from 11 September 2026, main obligations from 11 December 2027 |
Your lab will confirm the exact standards for your product. For a battery Wi-Fi device the list usually covers a radio standard (EN 300 328), the EMC standards for radio equipment, a safety standard for the electronics and an RF exposure assessment. The table shows the shape of the work, not a test plan.
The part most teams miss: RED cybersecurity and EN 18031
Since 1 August 2025, internet-connected radio equipment sold in the EU also has to meet the cybersecurity requirements that a delegated act added to Article 3(3)(d), (e) and (f) of the RED. Those cover protecting the network, protecting personal data and privacy, and protecting against fraud. The harmonised standards are EN 18031-1, -2 and -3. Espressif’s RED DA compliance guide is clear about who owns this: responsibility lies with the manufacturer of the final product, and the end product is evaluated as a whole even when the module is secure.
The same guide notes that the standards’ references were published in the Official Journal on 28 January 2025 with restrictions. One of them matters for almost every connected device: if users can choose not to set a password, following the standard does not give you presumption of conformity. Products that hit a restriction need a notified body.
What Espressif provides, and what it leaves to you
Espressif offers a security guide, firmware with recommended security features enabled, pre-filled documentation templates from the platform side, and a mapping of EN 18031 requirements to chip features. In that mapping, several areas depend on your design rather than the chip: logging, resilience, network monitoring, traffic control and user notification. Those are firmware and product decisions, which is why they cannot be bought with the module.
Questions an EN 18031 assessment will ask about a connected sign
- Setup: how does the device get Wi-Fi credentials, and is that setup channel protected while it is open?
- Passwords and access: are there any default or shared credentials, on the device or in its local web pages?
- Cloud traffic: is every connection encrypted and the server certificate verified, for API calls and for content downloads?
- Secrets: where are the Wi-Fi password and the device token stored, and what does a factory reset erase?
- Updates: how does a security fix reach a device in the field, and how is the firmware checked before it runs?
- Logging and resilience: what does the device record, and what happens when the network or the cloud is unreachable?
- Personal data: does the device or its content touch personal data (names on a door sign, a calendar), which brings in EN 18031-2?
Answer these in the design, not the week before testing. Some of them, such as how a field device gets a security update, are hard to retrofit once the partition table and the case are fixed; our dev-kit-to-product checklist lists the firmware decisions that get locked early.
The Cyber Resilience Act is next
The Cyber Resilience Act (Regulation (EU) 2024/2847) entered into force on 10 December 2024. Per the European Commission, its reporting obligations apply from 11 September 2026 and its main obligations from 11 December 2027. A product you start designing this winter will very likely still be on sale when the main obligations apply, so treat vulnerability handling and a security update path as product requirements now. How the CRA and the RED cybersecurity rules interact for your product category is a question for your lab or counsel; don’t assume one replaces the other.
A CE plan for an ESP32 product, in order
- Pick a module with published CE reports for your exact variant, and download them before you commit; check the Espressif certificates page for the current versions.
- Keep the tested antenna and radio settings: the PCB antenna variant with its keep-out area, or a listed antenna on a connector variant, and no firmware overrides of transmit power or country settings.
- Lay out for EMC: switching regulator and charger away from the antenna, short current loops, and care with any cable that leaves the case.
- Write down your security design against EN 18031-1 (and -2 if the device handles personal data), including setup, credentials, TLS, storage, updates and logging.
- Choose a lab early and ask which standards apply, whether the module's radio reports can be reused, and whether any EN 18031 restriction brings in a notified body.
- Test the product you will ship: final case, final battery, final firmware build, plus a test mode that holds the radio on and one that refreshes the panel in a loop.
- Assemble the technical file, sign the EU declaration of conformity, mark the product and keep the file for inspection.
How this applies to our own signs
Our 7.3-inch sign runs on Good Display’s ESP32E6-E01 board with an ESP32-S3-WROOM-1-N16R8 module. The firmware uses the module’s 2.4 GHz Wi-Fi through the standard Espressif stack and does not override transmit power or country settings. Setup is a temporary hotspot and a local page that takes a network name and password, described in our provisioning comparison. After setup the sign is claimed with a pairing code and gets its own device token, and its API calls to our cloud verify the server certificate against root certificates built into the firmware. Firmware updates today go over USB, not over the air. Those are exactly the points an EN 18031 review asks about, so on a custom build for a customer we go through them with the lab before the first board is ordered rather than claiming the module has settled them.
If you are earlier in the process, the ESP32-S3 vs ESP32-C6 comparison covers module choice, the Spectra 6 development kits guide shows which kits use which modules, and the hardware partner checklist has the certification questions to ask anyone you hire.
FAQ
Do I need CE marking if my product uses a CE-certified ESP32 module?
Yes. Under the Radio Equipment Directive (2014/53/EU), the finished product is the radio equipment placed on the EU market, so its manufacturer runs the conformity assessment, signs the EU declaration of conformity and affixes the CE mark. A module with published CE test reports lets a lab reuse much of the radio work, but it does not transfer a CE mark to your product.
Is there a European equivalent of FCC modular approval?
Not in the same sense. In the US a modular grant can carry the transmitter certification into a host product. In the EU the manufacturer of the end product takes responsibility for the whole device: radio spectrum, EMC, electrical safety, RF exposure and, since 1 August 2025, the cybersecurity requirements of the RED delegated act.
What is EN 18031 and does it apply to an ESP32 product?
EN 18031-1, -2 and -3 are the harmonised standards for the cybersecurity requirements the RED delegated act added: protecting networks, protecting personal data and privacy, and protecting against fraud. An internet-connected ESP32 device is typically in scope of at least EN 18031-1. Espressif's own guide states that responsibility lies with the manufacturer of the final product, not the module.
Can I self-declare against EN 18031?
Often, if you apply the standards fully. But the references were published in the Official Journal with restrictions, and Espressif's guide notes, for example, that a product which lets users choose not to set a password does not get presumption of conformity from the standard. In those cases a notified body gets involved. Ask your lab early which route your product needs.
Does the Cyber Resilience Act change this?
It adds to it. The Cyber Resilience Act (Regulation (EU) 2024/2847) entered into force on 10 December 2024; its reporting obligations apply from 11 September 2026 and its main obligations from 11 December 2027, according to the European Commission. A connected device you design now will be sold under it, so plan vulnerability handling and an update path today.
Do I need a notified body for CE marking a Wi-Fi product?
Not always. If you apply the harmonised standards in full, the manufacturer can usually self-declare. A notified body is needed when you do not apply harmonised standards, apply them only in part, or fall into one of the restrictions on the EN 18031 references. Your test lab can tell you which applies to your design.