What is the Carrier-to-Noise Ratio of a WIFI Module? WIFI Module
When I get an email from a customer asking about their Wi-Fi module’s dropped connections, the first question I ask isn’t “how far is the router?” or “are there walls in the way?”—it’s about carrier-to-noise ratio (CNR). Most folks outside our team have never heard the term, let alone know how critical it is to the performance of a Wi-Fi module. As someone who’s spent 12 years designing and supplying Wi-Fi modules for everything from smart thermostats to industrial sensors, I’ve seen how a single wrong setting on CNR can turn a reliable product into one that returns for support. Today, let’s break this down like I would with a new engineer joining our team: simple, practical, and tied to real-world products, not just textbook formulas.
First, let’s start with basics anyone working with Wi-Fi should know: a Wi-Fi signal has two parts, the carrier and the noise. The carrier is that specific radio wave your module is transmitting or receiving—for 2.4 GHz Wi-Fi, that’s a wave somewhere around 2.412 GHz to 2.472 GHz, and for 5 GHz, it’s in the 5.15 GHz to 5.85 GHz range. Every other signal floating around those frequencies is noise. That noise could be a microwave running in the next room, a neighbor’s Wi-Fi, a Bluetooth device, even power lines emitting electromagnetic interference.
CNR is just a ratio: how strong that useful carrier signal is compared to the background noise around it. It’s measured in decibels (dB), which means it’s a logarithmic scale, not a linear one. A CNR of 10 dB doesn’t mean “twice as good as 5 dB”—it’s actually 10 times the signal strength relative to noise, because each 3 dB jump is a doubling of the power ratio. That’s the first thing new customers mix up all the time; they see a CNR listed on our module’s datasheet and think a higher number is always better, which is true, but there’s a minimum that matters for their specific product.
Now, why does this matter for a Wi-Fi module? Because Wi-Fi relies on demodulating that carrier to pull out data. If the noise is too loud (meaning the CNR is too low), the module can’t tell the difference between a “1” and a “0” in the radio wave. Think of it like trying to hear someone whisper your name across a crowded room: if the room is quiet, you can hear it easily; if there’s a band playing, you can’t. CNR is the ratio of that whisper (your carrier) to the room’s noise. For Wi-Fi, that “hearing” gets harder the faster you’re trying to send data too. A module sending data at 1 Mbps can handle a much lower CNR than one sending data at 150 Mbps—same way you can pick up a whisper in a noisy room if you only need to catch a single word, but can’t follow a full conversation.
Let’s get into real numbers, because this is where datasheets and our module testing come in. For 802.11n and 802.11ac, the most common Wi-Fi standards today, the minimum required CNR for reliable communication ranges from about 10 dB for the slowest modulation schemes (QPSK, used for long-range, low-data tasks like sending a thermostat’s temperature every 15 minutes) up to 25 dB for the fastest schemes (256-QAM, used for high-data tasks like streaming video or updating a sensor with 10MB of data every second). I test every batch of our modules in our anechoic chamber (that room lined with foam that absorbs radio waves, so we don’t get false readings from external signals) to make sure they hit these numbers. Last month, we had a customer who built a smart irrigation controller that kept dropping connections when they moved it to a backyard far from their home router. They were using a module that hit 12 dB CNR at 10 meters, but needed 100 meters. We swapped in a module optimized for low-power, long-range applications that hit 11 dB CNR at 80 meters, and that fixed their issue. They thought the problem was antenna placement, but it was actually the module’s CNR threshold not matching their use case.
Wait, a minute—what’s the difference between CNR, SNR, and RSSI? That’s the second most common question I get, and it trips up even experienced product managers. RSSI is Received Signal Strength Indicator, which is just how strong the carrier is—usually measured in dBm, negative numbers, like -60 dBm means the signal is moderate. SNR is Signal-to-Noise Ratio, which is almost the same as CNR, but technically SNR includes all the signal (including any interference from other Wi-Fi signals or devices) while CNR specifically isolates the carrier frequency from the noise in that exact band. For our modules, we always report CNR because it’s the most accurate for our products, not the generic SNR you’ll see in a router’s Wi-Fi settings. When a user checks their phone’s Wi-Fi signal and sees “-70 dBm,” that’s RSSI, not CNR—you can’t tell if that signal is good or bad without knowing the noise level at that location. A -70 dBm signal next to a noisy microwave (noise level of -85 dBm) gives a CNR of 15 dB, which is fine. A -70 dBm signal with noise of -100 dBm gives a CNR of 30 dB, which is overkill. It all depends on context.
What affects a module’s CNR? Three big factors, and all are tied to how we design and test our modules, which is why our customers choose us over generic off-the-shelf parts. First, the module’s built-in receiver front end. We work with a specialized component supplier to pick low-noise amplifiers (LNAs) that boost the incoming carrier signal without adding extra noise of their own. A cheap module might use an LNA that adds 2 dB of noise, while our standard modules add less than 0.5 dB—over a long distance, that small difference pushes CNR up by 1.5 dB, which can double the effective range. Second, the antenna connection. Every module’s antenna trace and connector is hand-soldered and tested for impedance matching (we aim for 50 ohms, the standard for Wi-Fi) because a bad connection can reflect 20% or more of the signal back, reducing the carrier strength and lowering CNR. Last month, a customer sent us a faulty module that had a CNR of 8 dB at 5 meters, way below our 12 dB spec. We checked the antenna and found the connector was loose—re-soldering it brought CNR up to 14 dB immediately. Third, interference in the deployment environment, which is why we design our modules with built-in band selection. For example, our 5 GHz modules have less interference than 2.4 GHz, because more devices use 2.4 GHz (microwaves, Bluetooth, old Wi-Fi). A customer making a warehouse sensor network switched from 2.4 GHz modules to our 5 GHz low-CNR modules, and their packet error rate dropped from 12% to less than 0.1%—all because the warehouse’s metal shelves and forklifts created constant noise on 2.4 GHz, and the 5 GHz modules maintained a steady CNR of 18 dB even with those obstacles.
Now, what about CNR for different types of Wi-Fi modules? We make three main lines, and each has different CNR targets because they’re built for different uses. Our low-power IoT modules, for battery-powered sensors that run on AA batteries for 5 years, have a minimum CNR of 10 dB at a range of 50 meters. They use lower transmit power, so the carrier is weaker, but we optimize the receiver to pick up that weak signal without adding noise. Our high-performance industrial modules, used in factory automation where data needs to be reliable 24/7, have a minimum CNR of 14 dB at 100 meters, and we test each module at temperatures from -40°C to 85°C, because heat can make a receiver’s noise level rise and lower CNR. Our video streaming modules, for smart doorbells or security cameras, have a minimum CNR of 20 dB at 15 meters, because they need to send large amounts of data quickly, so they need a much higher CNR to use the faster modulation schemes.
I can’t tell you how many times I’ve seen a company’s product fail testing because they didn’t account for CNR in their module choice. Last year, a startup came to us with a smart doorbell that kept freezing when someone tried to stream live video. They’d picked a cheap module from a overseas supplier that had a 20 dB CNR spec, but that was at 1 meter—at 10 meters, it dropped to 15 dB, which is too low for the 802.11ac scheme they were using for video. We swapped in our video module, which hit 22 dB at 10 meters, and their stream worked perfectly. They’d assumed all modules with the same Wi-Fi standard performed the same, but CNR is where the difference shows up.
Another common myth: CNR only matters for receiving signals, but it matters for transmitting too. When your module sends data, it’s not just sending the carrier—it’s also generating its own noise that can interfere with other devices. A good Wi-Fi module will keep its transmit noise low, so other devices on the same network have a better CNR too. I test our modules’ transmit CNR in the chamber too, because a module that has high receive CNR but high transmit noise can cause problems for routers and other nearby devices. We’ve had a medical device customer use our modules in patient monitors, where they can’t interfere with other hospital equipment’s Wi-Fi—our low-transmit-noise design meant they passed all FCC and medical compliance tests on the first try.
So, what should you look for when choosing a Wi-Fi module based on CNR? First, match the minimum required CNR for your data rate and range. If you’re making a low-data, long-range sensor, don’t pay extra for a module that needs 20 dB CNR—you’re just wasting money on performance you don’t need. If you’re making a video doorbell, don’t use a 10 dB CNR module—you’ll get dropped streams. Second, look for modules with CNR specs measured under real-world conditions, not just at 1 meter in a lab. A lot of cheap modules list a 25 dB CNR, but that’s with a perfect antenna, no obstacles, and no interference—when you put them in a real home or warehouse, that number drops by 5 or 10 dB. Our module datasheets list CNR at the maximum distance for our three main use cases, so you can test it before you even buy a full production run.
At the end of the day, CNR isn’t just a technical number—it’s the backbone of reliable Wi-Fi performance. It’s what turns a “works in the lab” prototype into a product that customers can count on, whether that’s a thermostat adjusting your temperature overnight or a sensor sending data from a remote farm. Over the years, we’ve built our business on understanding that number, testing it rigorously, and adjusting our module designs to meet our customers’ exact needs. If you’re working on a product that uses a Wi-Fi module and you’re dealing with dropped connections, slow speeds, or compatibility issues, we can help you sort out the CNR requirements for your specific use case. We work with startups and enterprise teams alike, and we provide sample modules for testing so you can see exactly how our modules perform in your environment before you place a bulk order. Reach out to our team to discuss your Wi-Fi needs, and we’ll help you get the right CNR for your project.
Connection Conversion Cable References:
- IEEE 802.11-2020 Standard for Information Technology – Telecommunications and Information Exchange Between Systems – Local and Metropolitan Area Networks – Specific Requirements – Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications.
- Rappaport, T. S. (2002). Wireless Communications: Principles and Practice (2nd ed.). Prentice Hall.
- Silicon Labs. (2023). Wi-Fi Module Design Guide: Carrier-to-Noise Ratio Optimization for IoT Applications.
- Federal Communications Commission (FCC). (2022). Part 15 Radio Frequency Devices: Emission Limits and Measurement Procedures.
- Texas Instruments. (2021). Low-Power Wi-Fi Modules: CNR Tradeoffs for Long-Range Battery-Powered Devices.
GNS Components Limited
GNS Components Limited is one of the leading wifi module manufacturers and suppliers in China. We warmly welcome you to wholesale bulk cheap wifi module in stock here and get quotation from our factory. All our electronic components are with high quality and low price.
Address: Room 907, Building A, Shenfang Building, Huaqiang North, Futian Dist, Shenzhen China 518000
E-mail: sales@gnscomponents.com
WebSite: https://www.ictransistors.com/
