Skip to content
IoT Crest

5G RedCap: what it is and where it fits

Published , 7 min read

Short answer: 5G RedCap (Reduced Capability, also called NR-Light) is a slimmed-down class of 5G device defined in 3GPP Release 17. A RedCap device uses at most 20 MHz of bandwidth, one or two receive antennas and one transmit antenna, so its modem is smaller, cheaper and less power-hungry than a full 5G phone modem, with peak speeds in the same class as mid-range 4G. It is meant for wearables, video cameras, industrial sensors and routers that need more than LTE-M offers but far less than a phone. It works only on standalone 5G networks.

5G RedCap explained: what Reduced Capability 5G cuts from full 5G, how it compares with LTE-M, NB-IoT and Cat 1 bis, eRedCap, and which devices should use it.

This article covers what RedCap is and why 3GPP created it, what it removes from full 5G, speed and battery life in plain terms, the standalone 5G requirement, how it compares with NB-IoT, LTE-M, LTE Cat 1 bis and full 5G, eRedCap from Release 18, which devices suit it, and what to check before choosing a RedCap module. It does not cover the 5G radio layer in detail, coverage maps or prices for particular operators, or reviews of individual modules and routers.

5G RedCap is the version of 5G built for devices that are not phones. Full 5G modems are designed for peak speed: wide channels, four antennas, constant high data rates. A smartwatch, a security camera or a sensor on a factory line needs none of that and pays for it in size, cost and battery. RedCap, short for Reduced Capability, trims the modem down to what these devices use. It was specified by 3GPP in Release 17, completed in 2022, and operators began switching it on in 2024 and 2025. This guide explains what it removes, what it keeps and how it fits with the cellular IoT options already covered in the connectivity hub, especially NB-IoT and LTE-M.

Why RedCap exists

Before RedCap, cellular devices had two broad choices. At the low end sat NB-IoT and LTE-M, built for small, infrequent messages and years on a battery. At the top sat full 4G and 5G, built for phones and routers. The middle was covered by older 4G categories, mainly LTE Cat 1, Cat 1 bis and Cat 4.

As operators shut down 2G and 3G and plan for the day they reduce 4G, device makers want a mid-range option that belongs to 5G and will be supported for a long time. RedCap is that option. It gives mid-range devices a 5G modem with a cost and power draw much closer to a 4G one.

What RedCap removes from full 5G

The savings come from a handful of hardware limits written into the standard.

Full 5G device against a RedCap device (below 6 GHz) full 5G phone modem RedCap modem bandwidth up to 100 MHz 20 MHz receive antennas 4 (2 on some bands) 1 or 2 transmit antennas 1 or 2 1 data streams up to 4 down up to 2 down duplex full duplex half duplex allowed Result: a smaller, cheaper, lower-power modem; peak speed similar to mid-range 4G.
Diagram: a full 5G phone modem compared with a RedCap modem in the bands below 6 GHz. Full 5G handles up to 100 MHz of bandwidth, four receive antennas on most bands, one or two transmit antennas, up to four downlink data streams and full duplex. RedCap is limited to 20 MHz, one or two receive antennas, one transmit antenna and up to two downlink streams, and may use half duplex. The result is a smaller, cheaper, lower-power modem with peak speeds similar to mid-range 4G.

Narrower bandwidth. A RedCap device handles at most 20 MHz of spectrum in the bands below 6 GHz, against up to 100 MHz for a full 5G device. (In the millimeter-wave bands the limit is 100 MHz, against 400 MHz.) Less bandwidth means simpler, cheaper signal processing.

Fewer antennas. One or two receive antennas instead of four, and one transmit antenna. Every antenna removed saves a radio chain, board space and power, which matters a lot inside a watch or a small sensor.

Fewer data streams. At most two downlink streams instead of four, which follows from having fewer antennas.

Half duplex allowed. On paired spectrum, a RedCap device may transmit and receive at different moments rather than at once, which removes a costly filter called a duplexer.

Longer sleep. RedCap adds extended discontinuous reception (eDRX) and relaxed measurement rules for devices that do not move, so a device can sleep longer between checks with the network. That is what makes multi-day battery life practical on a wearable, and longer on a sensor that reports occasionally.

What it keeps is just as important: 5G security, network slicing, the 5G core’s management features, and lower latency than the older IoT technologies.

How fast is RedCap?

The 3GPP specifications set limits on hardware, not a single speed. In practice, a two-antenna RedCap device on a 20 MHz channel reaches peak rates in the same class as LTE Cat 4, the mid-range 4G category used in many routers and cameras for years. That means well above what LTE-M or Cat 1 bis can do, enough for HD video, quick firmware updates and a router that backs up a small office line, and far below a 5G phone.

As with any cellular link, real speed depends on signal strength, how busy the cell is and how the operator has configured it.

RedCap needs standalone 5G

This is the catch to check first. RedCap works only on standalone (SA) 5G, where the operator runs a full 5G core network. Much early 5G was non-standalone, using 5G radio with a 4G core, and RedCap devices cannot use that.

So a RedCap device is only as useful as its operator’s standalone 5G coverage. Several operators, including T-Mobile and AT&T in the United States, have launched RedCap on their standalone networks, but coverage varies a lot by country and operator. Many RedCap modules fall back to LTE when there is no standalone 5G, which protects you while coverage grows. Check whether a module you are considering has that fallback, and on which LTE categories.

RedCap compared with the other cellular IoT options

The cellular ladder for connected devices (not to scale) more data, more power NB-IoT meters LTE-M trackers, alarms Cat 1 bis 4G, one antenna eRedCap 5G, Rel 18 RedCap 5G, Rel 17 cameras, wearables above all of these: full 5G for phones and fixed wireless broadband
Diagram: the cellular options for connected devices arranged from least to most data and power, not to scale. NB-IoT, used by meters, is the smallest. LTE-M, used by trackers and alarms, is next, then LTE Cat 1 bis, a single-antenna 4G category. eRedCap from Release 18 sits above Cat 1 bis, and RedCap from Release 17, used by cameras and wearables, is the highest of the device-class options. Full 5G for phones and fixed wireless broadband sits above all of them.
NB-IoTLTE-MLTE Cat 1 bis5G RedCapFull 5G
Generation4G family, carried into 5G4G family, carried into 5G4G5G5G
DataSmall, infrequent messagesModerateSeveral Mbit/sSimilar to mid-range 4GHighest
BatteryYearsYearsMonths to years, depending on useDays on a wearable, longer on a sensorCharged daily
Moves while connectedPoorlyYesYesYesYes
Network neededNB-IoT enabled LTELTE-M enabled LTEAny LTEStandalone 5G5G
Typical devicesMeters, fixed sensorsTrackers, alarms, wearablesPoint of sale, trackers, telematicsCameras, wearables, routers, industrial devicesPhones, home broadband

Against NB-IoT and LTE-M. These remain the right choice for small battery devices that send little. RedCap does not replace them; 3GPP treats them as the low-power part of 5G and they will run for many years. Choose RedCap when the device needs video, large updates or quick responses that LTE-M cannot give. The NB-IoT vs LTE-M guide covers the low end in detail.

Against LTE Cat 1 bis. Cat 1 bis is the single-antenna version of LTE Cat 1, popular for its low module cost and the fact that it works on almost any 4G network today. For most devices shipping now, it is the safe mid-range choice. RedCap is the option with the longer future and more speed, and it makes sense where standalone 5G coverage is good or where the product will be sold for many years.

Against full 5G. If a device needs gigabit speeds, such as a home broadband router, it needs a full 5G modem. Everything below that is a candidate for RedCap.

eRedCap: the smaller version in Release 18

3GPP went further in Release 18 with enhanced RedCap (eRedCap). It cuts the device’s data processing bandwidth to 5 MHz and brings peak speeds down to around the level of LTE Cat 1 bis, with a matching drop in cost and power. It is aimed at the devices that use Cat 1 and Cat 1 bis today, so that they have a 5G path when 4G networks eventually shrink. Expect eRedCap modules and network support to arrive some time after RedCap.

Which devices suit RedCap

  • Wearables: smartwatches and health devices that need a cellular link and days of battery.
  • Video: security cameras, body cameras and dashcams that upload clips over cellular.
  • Routers and backup links: small routers that keep a shop or office online when the fixed line fails, or that serve a site with no wired connection. The IoT gateway guide explains where these sit in an industrial system.
  • Industrial devices: sensors and controllers that send more than small readings, such as vibration data or images for inspection.
  • Point of sale and kiosks: where Cat 1 bis is the usual choice today and a longer runway is wanted.

Poor fits are tiny battery sensors that report a few bytes a day, which belong on NB-IoT or LTE-M, and anything installed where the operator has no standalone 5G and no plans to build it.

Before you choose a RedCap module

  • Check standalone 5G coverage from your operator where the devices will actually sit, not just a national map.
  • Check LTE fallback in the module, so devices keep working outside standalone coverage.
  • Check the SIM and plan. Your SIM and data plan must allow RedCap and standalone 5G. The IoT SIM card guide and the MNO vs MVNO guide explain what to ask a provider.
  • Check certification with the operators and countries you plan to sell in, which can take time for a new module category.
  • Test in place. As with every cellular technology, test the real module in the real location before ordering in volume.

For the rest of the cellular picture, read the NB-IoT vs LTE-M comparison, the IMEI and IMSI explainers, and the other connectivity guides.

Written by the IoT Crest editorial team. Facts in this article follow the editorial policy: only well-established behavior is stated and no figures are invented.

More from Connectivity

  1. What is LPWAN? Low-power wide-area networks

    What LPWAN is, what it gives up for range and battery life, how NB-IoT, LTE-M, LoRaWAN and Sigfox differ, who runs each network and how to choose.

  2. Wi-Fi HaLow (802.11ah): range, speed and uses

    Wi-Fi HaLow explained: how 802.11ah uses sub-1 GHz bands for long range, what speed and battery life to expect, how it compares with LoRaWAN, and where it fits.

  3. What is an IMEI number? Digits, checks and uses

    What is IMEI: the 15-digit ID of a phone or cellular module, how its TAC, serial and check digit work, how it differs from IMSI and ICCID, and where to find it.

  4. What is IMSI? The international mobile subscriber identity

    What is IMSI: the subscriber identity on every SIM, its MCC, MNC and MSIN digits, how networks hide it with temporary IDs and SUCI, and IMSI vs IMEI vs ICCID.

  5. What is an MNO? Mobile network operators vs MVNOs

    MNO meaning in telecoms: what a mobile network operator owns, MVNOs, MVNEs and MVNAs, what a PLMN is, and how to compare an MNO and an MVNO for IoT SIMs.

  6. 2.4 GHz vs 5 GHz: which Wi-Fi band IoT devices need

    2.4 GHz vs 5 GHz Wi-Fi for IoT: range, speed, channels 1, 6 and 11, why smart devices need 2.4 GHz, and how to fix pairing on a dual-band router.

  7. ICCID number explained: the SIM serial, digit by digit

    The ICCID number explained: what the SIM serial is, how its digits break down, how it differs from IMSI and IMEI, and where to find it on phones and modules.

  8. What is an M2M SIM card? How M2M and IoT SIMs differ from phone SIMs

    What an M2M or IoT SIM card is, how it differs from a regular phone SIM, where it is used, activation, the 2FF to MFF2 form factors, M2M eSIM and iSIM.

  9. IoT protocols explained: the radio, network and messaging layers

    IoT protocols explained layer by layer: radio and link protocols, the network and transport layers above them, messaging on top, and how to combine them.

  10. MQTT vs CoAP: which IoT messaging protocol to use

    MQTT vs CoAP compared for IoT devices: publish-subscribe over TCP against a REST-like protocol over UDP, delivery guarantees, power and when each one fits.

  11. MQTT explained: topics, QoS levels and retained messages

    MQTT explained: how a broker, publishers and subscribers fit together, how to name topics and use wildcards, what QoS levels promise and retained messages.

  12. LoRaWAN explained: range, data rates and when to use it

    LoRaWAN explained: how LoRa radio and the LoRaWAN network layer differ, what range to expect, how spreading factors work, and when to pick it.

  13. NB-IoT vs LTE-M for cellular IoT devices

    NB-IoT vs LTE-M for cellular IoT devices: bandwidth and latency, mobility, power saving modes, coverage inside buildings, and which one to pick.

All connectivity articles

Sponsor an article in this topic

Sponsored articles and in-article link placements for IoT vendors, agencies and SEO buyers. Every sponsored piece is labeled, edited to the same standard as the rest of the site, and placed in the hub its readers already visit. Rates on request.

Ask a question

Ask a question

Spotted an error, or want a topic covered? It goes straight to the editors, who reply by email, WhatsApp or SMS.