FAQEU

EU Radio Equipment Directive FAQ

A practical index of recurring RED questions for connected products, wireless modules, consumer devices, and other equipment that intentionally emits or receives radio waves.

Use it to route the first review: decide whether RED applies, identify the relevant Article 3 duties, confirm cybersecurity and common-charger triggers, and assemble CE and technical-file evidence.

Author
Sorena AI
Published
May 9, 2026
Updated
Jul 25, 2026
FAQ modules
10

Structured answer sets in this page tree.

Primary sources
7

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated Jul 25, 2026
Overview

This FAQ index answers common questions at the point where product, regulatory, engineering, quality, and launch teams need a documented decision. It does not supersede product-specific legal assessment; it helps teams identify which RED rule and evidence file to check first.

Browse sub-FAQs

Choose the question set you need

These focused FAQ modules break this artifact into narrower answer sets so teams can move straight to the right source-backed guidance.

Browse all FAQ items45
Focused FAQ modules
10
Showing 10 of 10
FAQ module

Are radio kits and evaluation boards covered by the RED? | RED FAQ

RED FAQ for radio kits, construction kits, amateur-radio kits, and custom-built professional R&D evaluation boards under Directive 2014/53/EU.

4 items
FAQ module

EU RED Common Charger FAQ: Which devices need USB-C?

FAQ on EU RED common charger scope, 28 December 2024 and 28 April 2026 dates, USB-C, USB Power Delivery, charger unbundling, labels, pictograms, and evidence.

4 items
FAQ module

RED DoC and CE marking file: what to include

FAQ answer for Radio Equipment Directive declarations of conformity, CE marking evidence, technical documentation, notified-body records, and related labels.

4 items
FAQ module

RED importer obligations FAQ | Directive 2014/53/EU

What importers must check before placing radio equipment on the EU market: conformity assessment, spectrum use, technical documentation, EU declaration, CE marking, traceability, instructions, restrictions, storage, corrective action, and authority cooperation.

6 items
FAQ module

RED radio modules FAQ: host product assessment

FAQ on how Directive 2014/53/EU treats RF modules and host products, including module evidence, final-product responsibility, Article 3 assessment, technical documentation, instructions, antennas, software, and DoC records.

5 items
FAQ module

RED SAR and RF Exposure Evidence FAQ

What SAR and RF exposure evidence to keep under the EU Radio Equipment Directive, including Article 3(1)(a), foreseeable use, frequency, power, antenna, and standards evidence.

5 items
FAQ module

RED standards not cited in the OJEU: can you use them?

FAQ answer for Radio Equipment Directive products when a standard is useful but not OJEU-cited, including presumption of conformity, Article 17 route selection, and technical-file evidence.

4 items
FAQ module

When do RED cybersecurity requirements apply to connected radio equipment? | RED FAQ

RED FAQ explaining when Article 3(3)(d), (e), and (f) cybersecurity requirements apply to internet-connected, childcare, toy, wearable, and payment-capable radio equipment.

4 items
FAQ module

Which receivers and transmitters are covered by RED? | Directive 2014/53/EU FAQ

RED scope FAQ for products that intentionally emit or receive radio waves for radio communication or radiodetermination, including receiver-only products, transmitters, accessory-dependent products, and common exclusions.

4 items
FAQ module

Wi-Fi and Bluetooth Products Under the EU RED

FAQ for assessing Wi-Fi, Bluetooth, BLE and other short-range wireless products under the EU Radio Equipment Directive, including Article 3, CE, technical file, cybersecurity and notified-body triggers.

5 items
Question 1

Which RED questions should teams answer first?

Start with the questions that determine whether the product can be placed on the EU market: is it radio equipment, which Article 3 essential requirements apply, whether a delegated Article 3(3) requirement is triggered, whether a common-charger rule applies, and which conformity route supports the CE mark.

For each answer, record the product model, radio technology, intended use, EU role, applicable article or delegated act, source link, test or assessment evidence, and release owner. This record can then point to the supporting technical-file evidence.

Does the RED apply to my product?

Usually yes if the product intentionally emits or receives radio waves for radio communication or radiodetermination and is made available on the EU market or put into service in the Union. Check the Directive's exclusions for specified amateur-radio, marine, airborne, State-use, and custom-built professional R&D evaluation equipment before concluding. Then identify the product's radio function, intended use, exact marketed configuration, applicable Article 3 requirements, and evidence file.

What evidence do I need for a RED decision?

Keep the scope memo, Article 3 matrix, standards or technical specifications used, test or assessment evidence, cybersecurity and common-charger evidence where applicable, labels and instructions, and the EU declaration and CE-marking record so the answer can be traced back to the product configuration.

  • Scope: confirm whether the product intentionally emits or receives radio waves for radio communication or radiodetermination.
  • Requirements: map Article 3(1)(a), Article 3(1)(b), Article 3(2), and any applicable Article 3(3) requirement.
  • Cybersecurity: check whether Delegated Regulation (EU) 2022/30 applies from 1 August 2025 to the product category.
  • Common charger: check whether the device category is covered by the USB-C, fast-charging, unbundling, and consumer-information rules.
  • Conformity route: decide whether harmonised standards support internal production control or whether an EU-type examination or full quality-assurance route is needed.
Question 2

When is a product in RED scope?

RED applies to radio equipment made available on the EU market or put into service in the Union, unless an exclusion in the Directive applies. The first FAQ answer should identify the radio function, intended use, accessories or software needed for intended operation, and whether the product is a finished item, module, kit, receiver, transmitter, or connected device.

A useful scope answer avoids labels like wireless device without analysis. It states the radio technology, frequency or spectrum assumptions, intended communication or radiodetermination use, EU economic operator role, and any reason a different EU product regime is also being checked.

  • Keep a scope memo with the product identifier, hardware and firmware version, radio interface, intended EU market, and assumptions.
  • Check whether the product can be operated in at least one Member State without infringing spectrum-use requirements before import or launch.
  • Reopen the scope decision after radio module swaps, antenna changes, firmware changes affecting radio behavior, new markets, or new accessories.
Question 3

Which Article 3 requirements should the FAQ map?

Every RED answer should separate the baseline Article 3 requirements from delegated Article 3(3) requirements. Article 3(1)(a) covers health and safety protections, Article 3(1)(b) covers electromagnetic compatibility, and Article 3(2) covers effective and efficient use of radio spectrum to avoid harmful interference.

Article 3(3) requirements apply only where the relevant category or class has been specified. The FAQ index should therefore point teams to a requirement matrix rather than implying that every Article 3(3) point applies to every radio product.

  • Use a matrix with one row per Article 3 requirement and columns for applicability, standard or technical solution, test evidence, owner, and unresolved assumptions.
  • For harmonised standards, record the exact standard, edition, OJEU citation status, clauses applied, and any limitations or partial application.
  • If a harmonised standard is not applied or is only partly applied, document the alternative technical solution used to meet the essential requirement.
Question 4

When do RED cybersecurity requirements apply?

Delegated Regulation (EU) 2022/30 applies Article 3(3)(d) to internet-connected radio equipment. It applies Article 3(3)(e) to listed categories that can process personal data, traffic data, or location data, including internet-connected radio equipment, childcare radio equipment, toy radio equipment, and wearable radio equipment. It applies Article 3(3)(f) to internet-connected radio equipment that enables transfer of money, monetary value, or virtual currency.

The same delegated regulation states that it applies from 1 August 2025, as amended by Delegated Regulation (EU) 2023/2444. FAQ answers should identify the specific product category, data or payment function, derogation being considered, and evidence showing how the applicable Article 3(3) point is met. The medical-device derogation covers points (d), (e), and (f); the listed aviation, vehicle, and road-toll derogation covers only points (e) and (f).

  • Record whether the product communicates over the internet directly or through other equipment.
  • For Article 3(3)(e), document whether the product processes personal data, traffic data, or location data and whether it is childcare, toy, wearable, or internet-connected radio equipment.
  • For Article 3(3)(f), document whether the internet-connected radio equipment enables money, monetary value, or virtual-currency transfer.
  • Keep security design evidence, test evidence, threat analysis, residual-risk decisions, and release approvals with the RED technical file.
  • If EN 18031-1, EN 18031-2, or EN 18031-3 is used, record the applicable part and every OJEU notice or restriction rather than claiming unrestricted presumption of conformity.
Question 5

Which products need common-charger FAQ review?

The common-charger review is needed for covered portable radio-equipment categories such as handheld mobile phones, tablets, digital cameras, headphones, headsets, portable speakers, handheld videogame consoles, e-readers, earbuds, keyboards, mice, and portable navigation systems. The Commission page states that these requirements apply to those listed handheld categories since 28 December 2024 and to laptops as of 28 April 2026.

A useful answer does not stop at whether the device has USB-C. It also checks fast-charging interoperability, whether the product is offered with or without a charger, and whether the consumer label, pictogram, and written charging information are ready for the sales channel.

  • Identify whether the exact product category is listed and whether the device is rechargeable by wired charging.
  • Confirm USB-C charging-port implementation and fast-charging communication assumptions where applicable.
  • Maintain label and pictogram artwork, packaging proofs, web-sales copy, instructions, and charger-bundling decisions as evidence.
  • Use the laptop date separately from the handheld-device date; do not collapse both into one deadline.
Question 6

What should the FAQ say about restrictions, labels, and instructions?

If radio equipment is subject to restrictions on putting into service or requirements for authorisation of use in at least one Member State, Article 10(10) information must be presented on packaging and completed in the instructions. Implementing Regulation (EU) 2017/1354 specifies the packaging presentation and instruction content for that information.

The practical answer should name the restricted Member State or geographic area, the type of restriction or authorisation requirement, the packaging mark or wording used, the instruction-language handling, and the owner responsible for keeping the restriction table current.

  • Check spectrum-use restrictions before packaging release, marketplace upload, importer review, and country launch.
  • Keep the restriction table, packaging proof, instruction proof, translation record, and approval date together.
  • Update the record when the product's radio configuration, intended markets, or national restriction information changes.
Question 7

What evidence should teams keep for RED FAQ answers?

The evidence set should let a reviewer trace the answer from product fact pattern to RED requirement to conformity evidence. For manufacturers, RED requires technical documentation and an EU declaration of conformity to be kept for 10 years after the radio equipment has been placed on the market.

The FAQ record should point to the technical file rather than duplicate it. Keep the scope memo, Article 3 matrix, standards list, test reports, cybersecurity assessment, common-charger evidence where applicable, labels and instructions, notified-body certificate where applicable, EU declaration of conformity, and release approval.

  • Use one technical-file index per radio equipment type and version so evidence matches the placed-on-market product.
  • Keep notified-body certificates, annexes, additions, and related technical documentation where Annex III or Annex IV routes are used.
  • Retain supplier declarations and module evidence only when they match the final product configuration and do not replace the manufacturer's own RED conformity decision.
Recommended next step

Review your RED FAQ answers against the technical file

This FAQ index helps align product scope, Article 3 mapping, cybersecurity review, common-charger checks, CE evidence, and supporting source references before release or importer review.

Question 8

Common mistakes in RED FAQ answers

The common mistake is answering a RED question with a broad compliance statement that cannot be traced to a product, article, standard, test, or market. A strong answer is narrow enough to be checked during design review, importer diligence, marketplace onboarding, or an authority request.

  • Do not treat Wi-Fi, Bluetooth, cellular, GNSS, RFID, or another radio technology as automatically low-risk; map the actual Article 3 requirements and standards.
  • Do not cite cybersecurity requirements without identifying the exact Article 3(3)(d), (e), or (f) trigger.
  • Do not use common-charger dates without separating listed handheld categories from laptops.
  • Do not rely on old test reports after antenna, enclosure, radio module, firmware, charging, accessory, supplier, or market changes.
  • Do not publish supporting source references with private file locations, internal research labels, or unsupported URLs.
Primary sources

References and citations

eur-lex.europa.eu
Referenced sections
  • Primary source for RED conformity duties and formal non-compliance issues such as missing or incorrect EU declarations, CE marking, technical documentation, or Article 10 information.
"formal non-compliance"
single-market-economy.ec.europa.eu
Referenced sections
  • Commission overview for the role of harmonised standards and presumption of conformity under EU product rules.
"Harmonised standards are European standards"
single-market-economy.ec.europa.eu
Referenced sections
  • Commission source for the listed device categories, USB-C common port, fast charging, charger unbundling, consumer information, and 28 December 2024 and 28 April 2026 application dates.
"These requirements will also apply to laptops as of 28 April 2026"
Related guides

Explore more topics

EU Radio Equipment Directive Timeline: RED, Cyber and USB-C Dates
Understand which RED dates changed market-access rules, including 2016 application, the 2017 transition cutoff, common-charger dates, and cybersecurity requirements from 1 August 2025.
EU RED Applicability Test for Radio Equipment
Decide whether Directive 2014/53/EU applies to a connected product, which RED requirements are triggered, and what evidence belongs in the technical file.
EU RED Common Charger Obligations: USB-C scope, dates, labels
Check RED common-charger device categories, application dates, USB-C and USB Power Delivery specifications, charger unbundling, consumer pictograms, labels, and release evidence.
EU RED compliance evidence guide
Build a Radio Equipment Directive compliance file with Article 3 requirement mapping, harmonised-standard checks, conformity assessment evidence, EU declarations, CE marking, and RED source links.
EU RED Cybersecurity Product Categories: 2022/30 scope
Classify products under RED Delegated Regulation (EU) 2022/30, including exclusions, EN 18031 evidence, and the 1 August 2025 to 10 December 2027 transition.
EU RED Radio Equipment Scope: products and exclusions
Decide whether a product is radio equipment under Directive 2014/53/EU, with RED scope tests, exclusions, examples, and evidence records.
EU RED Requirements Map: CE and Article 3
Map Radio Equipment Directive requirements for radio products: Article 3 safety, EMC, spectrum, selected Article 3(3) duties, common charger rules, conformity assessment, CE marking, EU declaration, and technical documentation.
EU RED Scope and Classification
Classify products under the EU Radio Equipment Directive with cited tests for radio equipment scope, exclusions, Article 3 requirement buckets, cybersecurity, common charging, and evidence records.
EU RED Scope Classification Workflow
Classify products under the EU Radio Equipment Directive with a cited workflow for RED scope, exclusions, Article 3 requirements, standards, CE evidence, cybersecurity, and common-charger triggers.
RED Article 10 labelling, instructions, and restrictions
Apply RED Article 10 to product identifiers, manufacturer contacts, instructions, declaration statements, radio-frequency information, charging labels, and use restrictions.
RED Article 3 requirement selection workflow
Select the right RED Article 3 branches for radio equipment: safety, EMC, spectrum, delegated Article 3(3) duties, cybersecurity, common charging, evidence, and conformity assessment.
RED Article 3 Requirements: Safety, EMC, Spectrum and Cyber
Map Radio Equipment Directive Article 3(1), 3(2), and 3(3) requirements to safety, EMC, spectrum, interoperability, emergency, software, and cyber evidence.
RED Compliance Checklist for Radio Equipment
Use this RED release checklist for product scope, Article 3 requirements, technical documentation, EU declarations, CE marking, cybersecurity, common charging, and notified-body decisions.
RED compliance deadlines calendar: 2016, 2024, 2025 and 2026 dates
Calendar the EU Radio Equipment Directive deadlines that affect launches: RED applicability, transition end, common charger dates, cybersecurity requirements, OJEU standards, CE marking, declarations and technical files.
RED conformity assessment and CE marking
EU Radio Equipment Directive guide to Article 17 conformity modules, notified-body triggers, technical documentation, EU declarations, and CE marking.
RED Conformity Assessment Template
Template fields for documenting RED Article 3 requirements, Article 17 route selection, harmonised standards, notified-body evidence, technical documentation, EU declaration, CE marking, cybersecurity, and common-charger checks.
RED Cyber Compliance Workflow for Article 3(3)(d/e/f)
A cited RED cybersecurity workflow for internet-connected radio equipment, privacy and data safeguards, payment-fraud features, evidence packs, and CE release gates.
RED Cybersecurity Delegated Act Guide | Article 3(3)(d/e/f)
Guide to RED Article 3(3)(d), (e), and (f) scope, EN 18031 evidence, the 1 August 2025 application date, and repeal of Delegated Regulation (EU) 2022/30 from 11 December 2027.
RED Cybersecurity Requirements for Radio Equipment
EU RED cybersecurity requirements under Article 3(3)(d), (e), and (f): scope, affected radio equipment, application date, standards, notified bodies, and evidence.
RED EMC and LVD Safety Interplay for Radio Equipment
Explain how EU RED Article 3 applies LVD safety objectives and EMC requirements to radio equipment, with evidence, test-plan, and technical-file guidance.
RED Harmonised Standards and Test Plans: OJEU evidence guide
Build a Radio Equipment Directive standards matrix and test plan around OJEU-cited harmonised standards, Article 3 requirements, Article 17 route triggers, and Annex V technical-file evidence.
RED notified body route selection under Article 17
Decide when RED radio equipment can use internal production control and when Article 17 requires Annex III EU-type examination or Annex IV full quality assurance.
RED Notified Body Trigger Workflow: Article 17 evidence guide
Decide when the EU Radio Equipment Directive needs a notified body by mapping Article 3 requirements, OJEU-cited harmonised standards, Annex III EU-type examination, and Annex IV full quality assurance evidence.
RED penalties, fines, and enforcement actions
EU Radio Equipment Directive penalties guide covering Article 46, Member State penalty rules, recalls, withdrawals, formal non-compliance, and enforcement evidence.
RED software update impact for radio equipment
Assess when firmware, app, and software updates can affect EU Radio Equipment Directive conformity, technical documentation, DoC, standards, and notified-body evidence.
RED vs Cyber Resilience Act for radio equipment
Compare EU RED cybersecurity and Cyber Resilience Act duties for connected radio equipment, including scope, dates, evidence, reporting, and conformity routes.
RED vs EMC Directive: which law applies to radio equipment?
Decide when EU radio equipment uses RED instead of the EMC Directive and how to place EMC tests, declarations, fixed installations, and technical evidence.
RED vs ETSI EN 303 645: what the IoT standard proves
Compare binding EU RED cybersecurity duties with ETSI EN 303 645 consumer IoT guidance, current editions, EN 18031, evidence reuse, and CE conformity.
RED vs LVD: electrical safety for radio equipment
Decide when EU radio equipment uses RED safety requirements instead of the Low Voltage Directive, including voltage limits, chargers, evidence, and declarations.
RED vs Market Surveillance Regulation for radio equipment
Compare RED product-conformity duties with Regulation (EU) 2019/1020 for responsible operators, online offers, customs controls, authority requests, and corrective action.
RED vs UK PSTI for connected radio products
Compare EU RED with the UK PSTI consumer connectable product regime, including scope, exclusions, passwords, updates, vulnerability reporting, evidence, and dates.