Skip to content

Wi-Fi Alliance: interoperability + Wi-Fi brand

Guide · Wi-Fi Alliance certification

Wi-Fi Alliance certification occupies, in the product certification landscape, a position analogous to that of the Bluetooth SIG. It is not a regulatory framework imposed by a public authority, but a contractual obligation set by a private industry consortium, the Wi-Fi Alliance, on any manufacturer wishing to use the Wi-Fi brand or its logos (Wi-Fi 6, Wi-Fi 6E, Wi-Fi 7, Wi-Fi CERTIFIED Passpoint, EasyConnect, EasyMesh, Miracast, Wi-Fi Aware). It coexists with, and never replaces, national radio certification: RED article 3.2 in the European Union, FCC Part 15.247 and 15.407 in the United States. This page sets out the role of the Wi-Fi Alliance, its membership tiers, the role of Authorized Test Labs, the list of certification programmes, the Wi-Fi Alliance Test Specifications, the access rules for the 6 GHz band and the pitfalls associated with incomplete commercialisation.

The Wi-Fi Alliance, founded in 1999, owns the Wi-Fi trademarks and licenses their use to its members. The word, the logos and the derived brand family (Wi-Fi 6, Wi-Fi 6E, Wi-Fi 7, Wi-Fi CERTIFIED Passpoint, Wi-Fi CERTIFIED Vantage, Wi-Fi Direct, and others) are protected through international trademark filings. Any commercial mention of Wi-Fi on a product, its packaging, its documentation or its website requires an active licence, and the Alliance conditions that licence on two formal acts: joining the programme, and certifying the product through an Authorized Test Lab.

Two objectives coexist within the programme:

  • Trademark protection. Ensuring that any product displaying the logo respects the Wi-Fi Alliance Test Specifications and does not degrade the reputation of the ecosystem.
  • Interoperability assurance. Verifying that an access point, a station or a connected device actually communicates with other certified equipment, regardless of manufacturer or chipset.

The Wi-Fi Alliance is neither a state authority nor a Notified Body in the European sense. Its decisions have contractual, not regulatory, force. But in practice, without certification, a product can neither call itself Wi-Fi, nor use the official logos, nor be referenced by most large distributors or telecom operators, whose purchasing specifications require a valid certificate. The commercial stake is therefore major, even though the legal stake is private in nature.

Radio regulation versus consortium certification

Section titled “Radio regulation versus consortium certification”

A common confusion equates Wi-Fi Alliance certification with radio certification. The two regimes have distinct foundations and effects.

AspectWi-Fi Alliance certificationRadio certification (RED / FCC)
NaturePrivate programme of a consortiumPublic regulatory framework
IssuerWi-Fi Alliance (Austin, TX, USA)European Commission (RED), FCC (USA)
ScopeBrand, interoperability, featuresSpectrum, power, harmonics, safety
SanctionLicence withdrawal, infringement actionMarket access ban, fines
CoverageAny product using the Wi-Fi brandAny radio transmitter placed on the market
ReferenceIEEE 802.11 + Wi-Fi Alliance Test SpecificationsEN 300 328, EN 301 893, EN 303 687, FCC Part 15.247, FCC Part 15.407
DocumentsWi-Fi Alliance certificate, certification IDRED DoC, FCC ID, test reports

A Wi-Fi product must obtain both, without exception: the Wi-Fi Alliance certification for brand usage and access to ecosystems, the radio certification for placement on the market. Both dossiers are built in parallel but never substitute for one another. See RED pillar and RED standards for the applicable radio regimes, and FCC pillar for the US framework.

IEEE 802.11 is the standards working group that develops the technical specification of Wi-Fi (PHY and MAC layers). The Wi-Fi Alliance does not develop the standard: it turns a relevant subset into a certification programme, adding interoperability rules and implementation requirements. Schematically, the IEEE writes, the Alliance certifies. An 802.11 amendment (for example 802.11be for Wi-Fi 7) always precedes, sometimes by several years, the release of the corresponding certification programme.

Access to the programme requires membership. The Wi-Fi Alliance offers several levels, structured by engagement and annual subscription. The exact fees evolve and are published by the Alliance; the grid below describes the rights associated with each tier.

The highest level outside governance, with a substantial annual subscription. The Contributor participates in the development of the Wi-Fi Alliance Test Specifications, has voting rights on technical committees, accesses drafts ahead of publication and benefits from preferential certification fees. Adopted by chipset vendors, major network equipment manufacturers and telecom operators.

Intermediate level with access to some working groups, without voting rights equivalent to a Contributor. The Sponsor can influence the roadmap to a lesser extent and obtain reduced certification rates. Adopted by OEM consumer product manufacturers and Wi-Fi stack vendors.

Level oriented to product certification, with limited access to standardisation work. The Implementer can certify products, obtain Wi-Fi licence numbers, access the member portal, but does not participate in technical committees. This is the tier adopted by most connected-device manufacturers and consumer product makers using off-the-shelf Wi-Fi chipsets.

Entry-level tiers. Affiliate is intended for organisations without direct commercial activity on Wi-Fi products (universities, laboratories, partner standardisation bodies). Adopter allows a manufacturer to certify a limited number of products or to operate under a simplified framework, generally with a reduced subscription and a narrower functional scope.

TierAnnual subscriptionVoting on committeesProduct certificationDraft access
ContributorHighYes, drafts and voteYes, reduced ratesYes, early drafts
SponsorIntermediateOn some committeesYes, reduced ratesPartial
ImplementerStandardNoYesNo
AffiliateAcademic or partnerNoNon-commercialPer agreement
AdopterEntryNoLimited scopeNo

For a manufacturer of a finished product integrating an already certified Wi-Fi module, the Implementer tier is generally sufficient. Moving to Sponsor or Contributor is justified for stack designers, chipset vendors or companies wishing to influence the evolution of the specifications.

The Wi-Fi Alliance programme imposes per-device certification, executed in an Authorized Test Lab and published in the member portal.

An ATL is an independent laboratory recognised by the Wi-Fi Alliance, after audit, to execute the Wi-Fi Alliance Test Specifications. ATLs are distributed worldwide (North America, Europe, Asia), with differentiated accreditations per programme. The same laboratory may be an ATL for Wi-Fi 6 and not for Wi-Fi 7 if the corresponding audit has not been completed.

Unlike some consortium programmes such as Bluetooth SIG where self-test remains possible on certain features, the Wi-Fi Alliance does not accept self-testing for certification. Execution of tests by an ATL is mandatory for every submission.

The test reference is structured around two main document categories.

  • Certification Test Specifications (CTS). Specify the functional interoperability test cases per programme (Wi-Fi 6, WPA3, Passpoint, and others). They define the scenarios between a Device Under Test and reference stations, and the pass criteria.
  • Conformance Measurement Methodology (CMM). Describes the measurement methods and applicable metrology: test environment configurations, attenuations, spectral masks, channel adjustments.

In addition come programme-specific test plans (for example Test Plan for WPA3, Test Plan for Passpoint, Test Plan for EasyConnect), each tied to a given version and published on the member portal.

The sequence of a Wi-Fi Alliance certification, from programme selection to publication.

  1. Joining the Wi-Fi Alliance. If the company is not already a member, create an account on the portal and join at the appropriate tier (Implementer in most cases). Allow time for the application to be processed.
  2. Selecting the certification programmes. Identify the brands to be obtained: Wi-Fi 6 or Wi-Fi 7 (PHY), WPA3 (security), Passpoint, EasyConnect, EasyMesh, Wi-Fi Direct, Miracast, Wi-Fi Aware, TimeSync, depending on the product features. Each brand corresponds to a separate programme.
  3. Selecting the route. Decide whether the product is certified as an independent design or as a derivative product based on an already certified Wi-Fi module (derivative product shortcut).
  4. Preparing the Device Under Test. Prepare a stable firmware and hardware version dedicated to the tests. Any post-certification change outside the re-test scope will require a new submission.
  5. Selecting an ATL. Choose an Authorized Test Lab accredited for the target programmes. Define the scope, the options to be tested, the expected duration, the quotation.
  6. Test execution. The ATL executes the applicable CTS and CMM, documents deviations, negotiates firmware corrections where possible.
  7. Submission to the member portal. Upload the ATL reports, pay the certification fees, declare the features and brands targeted.
  8. Wi-Fi Alliance review. The Alliance examines the dossier, may request additional information, then issues a certification number.
  9. Publication and brand usage rights. The product appears in the public Wi-Fi CERTIFIED database. The manufacturer can then use the Wi-Fi word and the logos corresponding to the validated brands (Wi-Fi 6E, Wi-Fi 7, WPA3, and others), under the terms of the Wi-Fi Alliance Brand Style Guide.
  10. Listing maintenance. Keep the declaration up to date in case of hardware or firmware changes affecting Wi-Fi. An undocumented modification can invalidate the certificate.

This sequence runs in parallel with radio certification (RED, FCC). See FCC scope for coordination with the FCC ID.

The Wi-Fi Alliance maintains a portfolio of programmes, each corresponding to a distinct Wi-Fi CERTIFIED brand. A single product can combine several programmes.

CategoryProgrammeScope
PHYWi-Fi CERTIFIED 6IEEE 802.11ax, 2.4 and 5 GHz
PHYWi-Fi CERTIFIED 6E802.11ax extended to the 6 GHz band
PHYWi-Fi CERTIFIED 7802.11be, Multi-Link, 4K-QAM, 320 MHz channels
SecurityWPA3SAE authentication, Protected Management Frames
SecurityEnhanced OpenOWE for opportunistic encrypted open networks
RoamingWi-Fi CERTIFIED PasspointHotspot 2.0, EAP-based onboarding
OnboardingWi-Fi CERTIFIED EasyConnectDPP, password-less onboarding
MeshWi-Fi CERTIFIED EasyMeshStandardised multi-AP mesh
P2PWi-Fi DirectP2P connection, foundation of Wi-Fi Aware
P2PWi-Fi AwareNAN, proximity discovery
StreamingMiracastScreen mirroring over Wi-Fi Direct
VantageWi-Fi CERTIFIED VantageEnterprise and operator performance profile
TimeWi-Fi CERTIFIED TimeSync802.11mc time synchronisation
LocationWi-Fi CERTIFIED LocationFTM, station-to-station ranging

Most consumer products combine at minimum Wi-Fi 6 or Wi-Fi 7 (PHY), WPA3 (security) and, often, EasyConnect for onboarding. Operator gateways and enterprise access points add Passpoint, EasyMesh, Vantage according to the targeted segments. A simple connected object can be limited to a Wi-Fi 6 certification (and WPA3 when upstream ecosystems require it).

The opening of the 6 GHz band for RLAN (Radio Local Area Networks) is the most structuring regulatory evolution for Wi-Fi 6E and Wi-Fi 7. It comes with a spectrum access framework divided into power and usage classes, regulated at the public level but reflected in the Wi-Fi Alliance Test Specifications.

ClassAcronymPowerUsage conditionsCoordination
Low Power IndoorLPILow, around 5 dBm/MHz EIRP density typicalIndoor only, mains powerNone, design restrictions
Standard PowerSPHigher, fixed or semi-fixedOutdoor or indoor, under AFC controlAFC mandatory, geolocation
Very Low PowerVLPVery low, portablePortable, indoor and outdoor, batteryNone, conformity by design

The Automated Frequency Coordination (AFC) is a database operated by approved providers (deployment underway in the United States, under discussion in the European Union) that dynamically assigns channels and power levels to a Standard Power access point based on its geolocation, in order to protect the primary users of the band (fixed services, satellites). A product claiming SP must implement the certified AFC mechanism and the associated radio conformity.

The open sub-bands in 6 GHz and the maximum power levels vary by jurisdiction. The European Union and the United States do not open the same blocks, and some countries do not open the band at all. The European harmonised standard EN 303 687 covers RLAN 6 GHz access in the EU. In the United States, FCC Part 15.407 covers the U-NII bands extended to 6 GHz. See RED standards for the European consolidation.

A multi-region Wi-Fi 6E or Wi-Fi 7 product must therefore manage its 6 GHz channels according to the jurisdiction of use, either via factory configuration per destination, or via embedded geolocation tied to a single firmware. Wi-Fi Alliance certification verifies compliance with the LPI / SP / VLP classes in the sense of the programme, but does not substitute for regulatory radio conformity.

In the European Union, Wi-Fi radio falls under article 3.2 of the RED directive ( 2014/53/UE ), which requires efficient use of the spectrum. Three harmonised standards apply per band:

  • EN 300 328 for the 2.4 GHz band (shared with Bluetooth, Zigbee).
  • EN 301 893 for the 5 GHz band, with DFS (Dynamic Frequency Selection) and TPC (Transmit Power Control) where the sub-band requires it.
  • EN 303 687 for the 6 GHz band, with LPI / SP / VLP management.

A report under EN 300 328, EN 301 893 or EN 303 687 covers no aspect of Wi-Fi Alliance certification. Conversely, Wi-Fi Alliance certification does not release the manufacturer from RED obligations. Both dossiers must exist, and their contents are largely disjoint:

  • An EN 301 893 report documents RF levels, DFS, TPC, spectrum occupancy.
  • A Wi-Fi Alliance dossier documents the 802.11 stack, the declared features and compliance with the Wi-Fi Alliance Test Specifications.

For the other applicable RED articles: 3.1(a) health (often covered by EN 62479 or EN 62311 for low power, EN 50385 for higher power), 3.1(b) radio EMC ( EN 301 489-17 for Wi-Fi), and 3.3 cybersecurity ( EN 18031 ) since August 2025. See RED standards for the detail.

Articulation with FCC Part 15.247 and Part 15.407

Section titled “Articulation with FCC Part 15.247 and Part 15.407”

In the United States, Wi-Fi radio falls under two sections of Part 15.

  • 47 CFR Part 15.247 covers unlicensed operations in 2.4 GHz (DSSS, digital modulations, FHSS), applicable to 2.4 GHz Wi-Fi.
  • 47 CFR Part 15.407 covers the U-NII bands (5 GHz and the 6 GHz extensions for Wi-Fi 6E and Wi-Fi 7), with DFS for radar sub-bands and rules specific to the LPI, SP, VLP classes in 6 GHz.

The Part 15.247 or Part 15.407 report, submitted to a TCB ( see FCC pillar ), yields an FCC ID. Here again, the FCC ID never substitutes for Wi-Fi Alliance certification, and vice versa.

The Wi-Fi Alliance provides, like most consortia, a reuse mechanism to limit the aggregate cost of a product family integrating the same Wi-Fi module.

  • Certified module or design by the silicon vendor or module maker, with a certification number covering a defined functional and radio scope.
  • Derivative product integrating that module without modification of the RF design (antenna, RF supply, sensitive layout) or of the Wi-Fi firmware. The manufacturer of the finished product declares the derivation in the member portal and goes through a reduced test scope centred on integration and added features.

This mechanism works as long as:

  • The module is used strictly in line with its integration note (identical or compatible antenna, ground plane, isolation distance).
  • The Wi-Fi firmware distributed by the module maker is not modified.
  • The features declared for the derivative product are a subset of the parent module.

Any deviation imposes a standalone certification. See Bluetooth SIG qualification for a comparable EPL reuse mechanism.

Using the Wi-Fi name without certification

Section titled “Using the Wi-Fi name without certification”

This is the simplest mistake to avoid and the most frequent. A product with a functional 802.11 radio cannot call itself Wi-Fi, use the logo, or mention "Wi-Fi 6" or "Wi-Fi 7" in its documentation, until a certification number is issued. Some manufacturers work around this by referring to "802.11 connectivity" or "wireless 2.4 GHz / 5 GHz connectivity", but the strategy erases the main commercial benefit of the technology.

Modifying a certified module without re-certification

Section titled “Modifying a certified module without re-certification”

A derivative product inherits a module certificate under a strong assumption: the module is used as is, without hardware modification (antenna, RF supply, layout) or firmware modification (802.11 stack configuration). Any deviation, for example an antenna change with a different gain, or a modification of the Wi-Fi firmware shipped by the module maker, invalidates the derivative certificate. The manufacturer must then switch to a standalone certification.

Confusing Wi-Fi Alliance certification with radio certification

Section titled “Confusing Wi-Fi Alliance certification with radio certification”

Many manufacturers discover late that RED or FCC certification does not cover Wi-Fi Alliance certification. The product schedule then slips, depending on ATL availability and the number of programmes targeted. To be budgeted at the design phase, with the same care as the radio itself.

Missing the channel rules in the 6 GHz band

Section titled “Missing the channel rules in the 6 GHz band”

The hardest trap in 6 GHz is the confusion between the LPI, SP and VLP classes. A product declared as LPI cannot operate on battery or outdoors. A product declared as SP cannot rely on static geolocation without the required AFC mechanism. A wrong declaration at the time of certification triggers a re-test, or even a removal from the listing.

Jumping from one Wi-Fi Alliance Test Specification version to the next

Section titled “Jumping from one Wi-Fi Alliance Test Specification version to the next”

Certification is tied to a given version of the CTS and CMM. Moving from one major version to the next (for example the addition of a mandatory test case, a change in a PER threshold) is not covered by the existing certificate. A formal update, or a full recertification, is required depending on the scope of the changes.

Underestimating the cumulative cost of multiple programmes

Section titled “Underestimating the cumulative cost of multiple programmes”

A consumer product can target four to six simultaneous programmes (Wi-Fi 6E, WPA3, EasyConnect, EasyMesh, Wi-Fi Aware, Miracast). Each programme represents a cost and a delay. A phased approach, prioritising the brands required by upstream ecosystems (Matter, telecom operators, distributors), avoids blocking the go-to-market on secondary programmes.

Forgetting the brand licence rules for sub-brands

Section titled “Forgetting the brand licence rules for sub-brands”

Wi-Fi 6, Wi-Fi 6E, Wi-Fi 7, WPA3, Passpoint, EasyConnect, Miracast each have their own usage rules in the Wi-Fi Alliance Brand Style Guide. A product can only display the Wi-Fi 7 logo if it is actually certified for that programme. Abusive use of a sub-brand without the corresponding certification is treated as abusive use of the main brand.

See also glossary for the LPI, SP, VLP, AFC, Passpoint definitions, and the guides Bluetooth SIG qualification, Matter certification together with FCC scope for radio coordination.

Sources & references

  1. Wi-Fi Alliance , Wi-Fi Alliance www.wi-fi.org/
  2. Wi-Fi Alliance certification programs , Wi-Fi Alliance www.wi-fi.org/certification
  3. Wi-Fi Alliance membership , Wi-Fi Alliance www.wi-fi.org/who-we-are/membership
  4. IEEE 802.11 working group , IEEE www.ieee802.org/11/
  5. ETSI EN 300 328, transmission systems in the 2.4 GHz band , ETSI www.etsi.org/deliver/etsi_en/300300_300399/300328/
  6. ETSI EN 301 893, 5 GHz RLAN , ETSI www.etsi.org/deliver/etsi_en/301800_301899/301893/