5G RedCap Explained: Why Release 17 Changes IoT Connectivity
5G RedCap is a purpose-built cellular standard for IoT devices that need more throughput than LTE-M can deliver, but not the cost or complexity of full 5G NR. Here is what it actually offers, where UK networks have got to, and when it is worth specifying.
5G RedCap, formally Reduced Capability and standardised in 3GPP Release 17, is not a marketing term for a budget 5G phone. It is a deliberately simplified device class, defined so that IoT hardware can attach to a 5G Standalone network without carrying the cost, power draw and radio complexity of a flagship handset.
Understanding where it sits in the connectivity hierarchy, and what it depends on to work at all, is now a practical requirement for anyone specifying cellular hardware with a three to five year service life.
The gap RedCap fills
The 3GPP cellular IoT stack has a wide gap in the middle. Below it sit NB-IoT at roughly 250 kbps and LTE-M at roughly 1 Mbps, both excellent for tiny payloads and long battery life. Above it sits standard 5G NR, capable of hundreds of megabits but expensive, power hungry and physically large.
A very large proportion of real IoT deployments sit between the two. Industrial sensors, video surveillance, wearables, smart meters, EV charge points, digital signage and fixed wireless access for premises with no fibre option all need more than a kilobit trickle and far less than a gigabit.
What RedCap actually drops
RedCap is defined by subtraction. Compared with a full 5G NR device it uses a maximum channel bandwidth of 20 MHz in FR1 rather than 100 MHz or more, which dramatically simplifies the RF front end. It reduces receive branches to one or two rather than four. It drops carrier aggregation and dual connectivity, the two most power-hungry features of flagship 5G. And it is sub-6 GHz only, with no mmWave.
What it keeps is the part that matters. A RedCap device is a native 5G Standalone client. It attaches to the 5G core, it can use network slicing, it inherits the 5G NR security architecture rather than the legacy LTE model, and it benefits from 5G NR positioning. That is the strategic difference between specifying RedCap and simply deploying another LTE device.
Specification summary
| Parameter | 5G RedCap (Release 17) |
|---|---|
| Peak downlink | Approximately 150 Mbps |
| Peak uplink | Approximately 50 Mbps |
| Max channel bandwidth | 20 MHz in FR1 |
| Receive antennas | One or two |
| Spectrum | Sub-6 GHz only, no mmWave |
| Carrier aggregation | Not supported |
| Network requirement | 5G Standalone. Falls back to LTE where SA is unavailable |
| Battery life | Up to a year on appropriate duty cycles. Not an LPWAN substitute |
| Module cost today | Roughly 30 to 50 US dollars, still a premium over LTE Cat-4 |
On module pricing. A figure of 5 to 15 dollars per module circulates widely. That is an industry target for volume maturity, not a price you can buy at. Early RedCap modules are currently in the 30 to 50 dollar range, which is above equivalent LTE Cat-4 hardware. The cost case for RedCap today rests on longevity and 5G core features, not on the bill of materials.
RedCap, eRedCap and what comes next
The terminology has evolved across 3GPP release cycles, and precision matters when you are writing a specification.
RedCap (Release 17) is the original standard and what almost everyone means by “5G RedCap”. Roughly 150 Mbps peak downlink, up to two receive antennas, aimed at wearables, industrial sensors, surveillance and CPE.
eRedCap (Release 18) is enhanced RedCap, part of the first 5G Advanced release. It goes considerably further than a bandwidth reduction. Channel bandwidth drops to 5 MHz, the device is restricted to a single receive antenna, and half-duplex FDD is supported. Peak downlink lands around 10 Mbps. The target market is not wearables but LTE Cat-1 replacement, which is by some distance the largest segment of the installed cellular IoT base.
Release 19 continues the trajectory, with non-terrestrial network integration as the defining new capability. We use the shorthand “Ultra RedCap” for this direction on our sister site. It is our own term rather than official 3GPP language, and it should not be treated as a synonym for eRedCap.
The 5G Standalone prerequisite
This is the single most important practical fact about RedCap, and it is frequently glossed over. RedCap requires a 5G Standalone core. It will not work on 5G Non-Standalone, which uses a 4G core underneath. Where SA coverage does not exist, a RedCap device falls back to LTE, and the fallback behaviour is specified in the standard.
That turns “is RedCap available?” into “is 5G SA deployed at my sites?” In UK city centres and major business parks, increasingly yes. In secondary towns, industrial estates and rural areas, SA coverage remains a 2026 to 2028 proposition.
UK network deployment status
The picture has moved considerably. As of 2026, EE and Vodafone have commercial RedCap live, both having completed UK trials during 2025. Three has confirmed active testing with commercial launch anticipated during 2026, though it has the smallest 5G SA footprint of the four operators. O2 and VMO2 are building SA capability, with post-consolidation scale giving them the resources to close the gap.
| Operator | RedCap status | Notes |
|---|---|---|
| EE | Commercial RedCap live | Broadest UK 5G SA footprint |
| Vodafone | Commercial RedCap live | IoT-specific tariffs in development |
| Three | Active testing | Commercial launch expected 2026 |
| O2 / VMO2 | 5G SA buildout in progress | Strong enterprise IoT relationships |
Globally the UK sits in the active testing tier alongside Finland, South Korea and Saudi Arabia rather than the commercial launch group, which is consistent with two operators being live but the market not yet at scale.
Where the real UK activity is. Private 5G networks. When you control the core, you can deploy Standalone from day one regardless of what the public networks have done. That removes the SA coverage constraint entirely, which is why the most immediate commercial RedCap deployment in Britain is happening on private networks rather than public ones.
Specification note. If you are choosing hardware for a deployment that will run for three to five years, specify RedCap capability in the modem even where SA coverage has not reached your sites. The device falls back to LTE in the meantime, the incremental cost at module level is modest, and you avoid a hardware refresh when coverage arrives.
The corollary: do not wait for eRedCap. Release 17 hardware is mature and shipping now. eRedCap modules are a 2027 proposition with volume from 2027 to 2028. Unless your application is severely power constrained, deploying RedCap today is the right call.
The eSIM angle
RedCap devices built for long service lives and geographically diverse deployment are strong candidates for SGP.32-based eSIM. A device that will outlast several network generations, sited somewhere a truck roll is expensive, benefits enormously from remote SIM provisioning.
The combination of RedCap capability with SGP.32 remote provisioning is likely to become the default architecture for industrial IoT designed to last. It also mitigates the coverage problem: a multi-network profile with LTE fallback covers the gap between today’s patchy SA footprint and tomorrow’s.
The verdict
RedCap is a genuinely useful standard rather than a rebadge. It gives IoT hardware a native 5G Standalone attachment, network slicing, better positioning and modern security, at a fraction of the radio complexity of full NR.
The caveats are timing and dependency. Modules cost more than LTE Cat-4 today. Coverage depends entirely on 5G SA, which in the UK means cities now and everywhere else later. And the standard’s real long-term significance may turn out to be eRedCap, which is aimed squarely at the enormous LTE Cat-1 installed base rather than at the wearables and sensors RedCap was originally pitched for.
For a deployment starting today, the answer is straightforward. Specify RedCap, design in LTE fallback, and use eSIM to keep your options open.
Related reading on IoTPortal
External resources
Last reviewed July 2026. UK operator positions reflect publicly available information and change frequently. Module pricing is indicative and moves with volume. “Ultra RedCap” is our own shorthand for the Release 19 direction and is not official 3GPP terminology. Verify network support and band coverage with your target operator before committing to hardware.