5G RedCap: Where It Fits in the Future of Critical IoT Connectivity

For years, the cellular market has had a gap. At one end, full 5G delivers high performance, but often with a level of device complexity, cost and power demand that many IoT deployments simply do not need. At the other, NB-IoT and LTE-M remain highly relevant for low-bandwidth, low-power applications with long service lives. RedCap changes the conversation because it introduces a mid-tier 5G option for devices that need more capability than LPWA, but less complexity than traditional 5G New Radio.

That positioning matters. RedCap was introduced in 3GPP Release 17 and followed by the even leaner eRedCap in Release 18. Both are based on the 5G Standalone architecture, and both are designed to serve use cases that sit between low-power wide-area connectivity and full-performance 5G NR. For organisations planning long-life connected estates, that creates a more practical path into 5G than a simple jump from LPWA to full broadband-grade 5G.

RedCap has moved beyond standards work and into real operator activity. According to GSA’s April 2026 industry update, 42 operators in 27 countries are investing in 5G RedCap, although many of those programmes remain in the trial phase. At the same time, GSA’s March 2026 RedCap market webinar summary says 95 operators in 53 countries have already launched a 5G Standalone service, which matters because RedCap and eRedCap depend on 5G SA availability.

RedCap reflects a broader industry reality: not every connected device needs maximum throughput, but many need more than LPWA can comfortably offer. Just as importantly, GSMA’s current positioning is clear that RedCap and eRedCap are not replacement technologies for LTE-M and  NB-IoT. Those LPWA technologies remain part of the 5G family and are expected to stay relevant well into the 2030s. RedCap should therefore be seen as an additional option within the connectivity toolkit, not as a universal successor that makes every other technology obsolete.

Indeed, 4G will remain a mainstay for most IoT deployments for some time, particularly where coverage, roaming maturity and installed-base stability matter most. The opportunity with RedCap is to provide a capability and roadmap for mid-tier IoT devices as, when and where 5G standalone availability improves.

RedCap is most compelling where organisations need a balance of throughput, latency, power efficiency and device cost. Typical examples include:

• smart wearables
• wireless industrial sensors
• moderate-bitrate video surveillance and connected cameras
• smart grid monitoring
• industrial panels and connected field equipment
• mid-tier industrial gateways, routers and telematics devices

In these scenarios, RedCap can offer a better commercial and technical fit than either LPWA or full 5G NR. It supports stronger performance than NB-IoT and LTE-M for richer data exchange, lower-latency interactions and more capable device behaviour, while avoiding much of the hardware and radio complexity associated with traditional 5G NR devices.

RedCap is not the right answer for every IoT deployment. Where an application is fundamentally low-bandwidth, deeply power-constrained and designed for infrequent communications, NB-IoT or LTE-M may still be the better option. Equally, where an estate genuinely needs sustained high throughput, demanding router-class performance, or sustained high-bitrate multi-stream video, a full 5G NR implementation may still be more appropriate.

That is why connectivity decisions should not be framed as a race between old and new. The better question is more specific: what level of capability does this device actually need, and how resilient does the service need to be in the field?

From a hardware perspective, RedCap simplifies 5G device design. In broad terms, RedCap devices use less bandwidth, less processing power and a simpler transceiver architecture than full NR. RedCap supports one transmit antenna and may be implemented with one or two receive branches depending on configuration and frequency range, which helps reduce cost, size and power consumption without requiring any exotic new antenna technology. The practical requirement is not a specialist antenna class, but a well-designed cellular antenna system matched to the deployed bands and the target link budget.

From a performance perspective, RedCap sits firmly in the mid-tier. In theory, it can reach up to 226 Mbps downlink and 120 Mbps uplink under specific conditions, but real-world throughput will depend on spectrum allocation, network configuration, device design, signal strength and overall cell load. That is why it is better to think of RedCap as a right-fit profile rather than a single fixed speed claim.

Coverage should be treated in the same way. There is no single universal RedCap range figure. In practice, coverage depends on the deployed band, network design and link budget. GSMA’s framing is more useful than headline distance claims: where RedCap is available, its coverage performance is broadly similar to LTE Cat.4 and is best understood through maximum coupling loss and overall radio design rather than a simple one-line range number.

For video specifically, RedCap is well suited to mid-tier video applications such as connected cameras where throughput needs are moderate, but sustained high-bitrate video workloads remain better suited to full 5G NR.

Release 18’s eRedCap goes further on simplification. It is FR1-only, caps peak throughput at 10 Mbps, and reduces complexity again for more constrained IoT use cases. Importantly, the commonly cited 5 MHz point should be understood carefully: eRedCap can achieve an equivalent baseband bandwidth of 5 MHz through PRB limitation, while the maximum RF bandwidth part can still remain up to 20 MHz. That makes eRedCap a leaner, lower-throughput 5G option rather than simply a narrower version of RedCap.

For critical IoT buyers, the real issue is not whether RedCap is attractive on paper. It is whether the surrounding ecosystem is ready where they operate. RedCap and eRedCap depend on 5G Standalone, which means readiness is shaped by SA rollout, operator configuration, chipset and module availability, roaming arrangements, and the specific policies each network applies to these device categories.

That is why resilience still matters more than radio labels. A better device class is valuable, but it does not remove the need for fallback strategy, network diversity, careful device selection, secure provisioning and long-term lifecycle planning. For mission-critical, business-critical and life-critical applications, the architecture still has to carry the risk, not just the access technology.

Rather than asking when everything can be replaced with RedCap, organisations should ask four better questions:

1. Which devices in our estate are currently over-specified for the job they do?
2. Which applications are likely to outgrow LPWA, but do not need full 5G broadband performance?
3. Where is 5G Standalone actually available across the operators and markets we depend on?
4. How will we preserve resilience while the RedCap ecosystem and roaming model continue to mature?

For many organisations, the answer will be phased adoption. Keep proven LPWA and LTE technologies where they remain the best fit. Introduce RedCap selectively where the use case justifies it. Treat eRedCap as a further optimisation for constrained 5G SA scenarios rather than as a blanket upgrade path. And build around operational resilience from day one.

RedCap is an important step forward because it makes 5G more relevant to real-world IoT. It fills a longstanding gap between low-power cellular and full-performance 5G, and it creates a clearer migration path for a broad set of legacy applications that do not sit comfortably at either extreme. But the bigger lesson remains unchanged: success depends less on chasing the newest connectivity label and more on choosing the right-fit technology inside a resilient, secure architecture.

The future of critical IoT connectivity will not be built on one bearer, one network or one acronym. It will be built on resilient design, disciplined migration planning and technology choices that match operational need. RedCap deserves a place in that conversation, but only where it genuinely improves the outcome.

• 5G SA (5G Standalone): A 5G architecture that uses a native 5G core network rather than relying on a 4G core.
• 5G NR (New Radio): The radio interface used by 5G networks.
• RedCap (Reduced Capability): A 3GPP Release 17 profile that reduces 5G device complexity for mid-tier IoT and similar use cases.
• eRedCap (enhanced Reduced Capability): A leaner Release 18 evolution of RedCap designed for lower throughput and lower complexity use cases.
• LPWA (Low Power Wide Area): A class of connectivity designed for long battery life, wide coverage and relatively low data rates.
• LTE-M: A 3GPP LPWA technology for IoT that supports mobility and moderate data rates compared with NB-IoT.
• NB-IoT: A narrowband LPWA technology optimised for very low power, deep coverage and infrequent communications.
• FR1: The lower 5G frequency range, broadly covering sub-7.125 GHz spectrum.
• PRB (Physical Resource Block): A basic unit of radio resource allocation in LTE and 5G scheduling.
• MIMO: Multiple-input multiple-output antenna techniques used to improve throughput, capacity or resilience.
• Link budget: The overall accounting of radio gains and losses that determines whether a wireless connection can be sustained.
• Maximum coupling loss (MCL): A coverage-related measure of how much signal attenuation a system can tolerate while still maintaining communication.