Have you ever experienced a situation where your Wi-Fi network is unstable despite a strong signal? Packets are being dropped, ping fluctuates, and data transfer speeds suddenly drop—especially when connecting multiple devices? This could be due to incorrectly configured RTS threshold (Request to Send) in your router settings. This little-known setting can either save a network from collapse or completely paralyze it if set incorrectly.
Most Wi-Fi optimization guides either don't mention RTS at all or limit themselves to vague phrases like "set it to 2347 and everything will work." In practice, however, choosing the RTS threshold depends on number of connected devices, type of traffic (games, streaming, file sharing), Wi-Fi standard (802.11n/ac/ax) and even physical environment (walls, interference from neighbors). In this article, we'll look at how RTS affects network performance and what values are relevant for modern routers in 2026, and we will give clear recommendations on how to configure it for different scenarios.
Let us warn you right away: changing the RTS threshold is advanced settings, and mindlessly copying values from the internet can make things worse. But if you understand the principles of Wi-Fi or are willing to experiment, a detailed guide with examples, tables of optimal values, and step-by-step instructions for popular router models awaits you.TP-Link, ASUS, Keenetic, MikroTik).
What is RTS (Request to Send) and why is it needed in Wi-Fi?
Threshold RTS (Request to Send) — is a mechanism for controlling access to the transmission medium in Wi-Fi standards, designed to reduce the number of collisions (packet collisions) in busy networks. When a device wants to transmit data, it first sends a short request RTS access point, indicating the time required for transmission. If the channel is free, the router responds CTS (Clear to Send), and only then does the transmission of the packet itself begin.
By default, most routers have the RTS threshold disabled (value 2347 or Disabled), which means the RTS/CTS mechanism is not used, and devices transmit data "blindly," risking collisions with packets from other clients. This works fine in networks with 1-2 connected devices, but in dense loading (10+ devices, streaming video, online games) problems begin:
- 📉 Packet loss — due to collisions, data has to be retransmitted, which increases delays.
- 🐢 Speed drop — the channel becomes clogged with broken packets, and the useful throughput decreases.
- 🎮 High ping — critical for online games and video calls, where stability is more important than speed.
Enabling RTS with the correct threshold forces devices to "negotiate" on transmission times, which reduces the number of collisions. However, excessively low RTS threshold (For example, 500) will lead to excessive signaling (RTS/CTS), which in itself will load the channel and degrade performance. Finding a balance is important here.
Technical details about RTS/CTS
The RTS/CTS mechanism was borrowed from the 802.11 standard to solve the "hidden node problem," where two devices cannot "see" each other's signals but are both attempting to transmit data to the same access point. In such cases, RTS/CTS acts as a "traffic light," synchronizing channel access. In modern networks with MIMO and OFDMA (Wi-Fi 6/6E), the role of RTS has somewhat diminished, but it remains useful in high-interference environments or with a large number of legacy devices (802.11b/g).
How the RTS threshold affects Wi-Fi speed and stability
To understand which RTS threshold value to choose, you need to understand how it affects the network under different conditions. The basic rule:
- 🔼 High Threshold (2000–2347) — RTS/CTS is rarely used, only for very large packets. Suitable for low-load networks with 1-5 devices.
- 🔽 Low threshold (500–1500) — RTS/CTS is triggered more frequently, preventing collisions. Relevant for dense networks with 10+ devices or in conditions of severe interference.
- ❌ Disabled — the mechanism isn't used at all. It might work under ideal conditions, but it's risky in real-world scenarios.
Here's how changing the threshold affects key network parameters:
| RTS threshold | Number of RTS/CTS packets | Transfer speed | Stability (packet loss) | Latency (ping) | Recommended scenario |
|---|---|---|---|---|---|
Disabled |
No | Maximum | Low (risk of collisions) | Low | 1-3 devices, no interference |
2347 |
Minimum | High | Average | Low | 5-10 devices, mixed traffic |
1500 |
Moderate | Average | High | Average | 10–20 devices, interference from neighbors |
500 |
Frequent | Low | Very high | Tall | 20+ devices, strong interference |
Key takeaway: The RTS threshold is a compromise between speed and stability.Too high a value will result in collisions, too low a value will result in excessive signaling. The optimal value depends on:
- 📱 Number of connected devices (the more, the lower the threshold).
- 📶 Interference level from neighboring networks (checked in Wi-Fi Analyzer).
- 🎮 Type of traffic (Games require low latency, file sharing requires high speed).
- 🔄 Wi-Fi standard (V Wi-Fi 6 RTS is less critical due to OFDMA).
What RTS threshold value should be set in 2026: recommendations for scenarios
There is no universal "best" RTS threshold value—it depends on your specific network. Below are some guidelines: current recommendations for typical scenarios taking into account modern realities (the spread of Wi-Fi 6, the growth in the number of IoT devices, and the increase in network density in cities).
1. Home network with 1–5 devices (smartphones, laptops, TV)
If you have a small number of gadgets and there are no obvious connection problems, there is no need to change the RTS threshold. Leave the default value:
- 📌
Disabledor2347- for most routers (TP-Link Archer AX6000, ASUS RT-AX88U). - ⚠️ Exception: If you notice packet loss in games (for example, in CS2 or Valorant), try
1500.
2. An office or home with 10–20 devices (lots of IoT, smart home)
In networks with a large number of devices (cameras, sensors, speakers), collisions become noticeable. Recommended values:
- 🏢
1000–1500- balance between speed and stability. - 🔄 If you use Wi-Fi 6 (AX routers), you can leave
2347, but turn onOFDMAin the settings.
3. Apartment building with strong interference (many neighboring networks)
In densely populated areas (such as in a panel building), interference from neighboring routers can completely clog your channel. RTS can help:
- 🏘️
500–1000- a low threshold will reduce the number of collisions. - 📡 Additional: Change the channel to
149–165(5 GHz) or use 160 MHz (if supported by the router).
4. Gaming PC or console (low ping is critical)
The main thing for online games is stable delay, not the maximum speed. Optimal settings:
- 🎮
1000–1500- will reduce packet loss. - 🔌 Connect your console or PC via cable (if possible) - this is better than any RTS.
- ⚡ Turn on
QoSin the router and prioritize game traffic.
5. File server or NAS (high transfer speed)
When copying large files (movies, backups) RTS may worsen speed due to excessive delays. It's better here:
- 💾
2347orDisabled- Disable RTS for maximum throughput. - 🔗 Use 5 GHz or Wi-Fi 6E (6 GHz) to minimize interference.
Find out the number of connected devices in DHCP Client List
Check the interference level in the app Wi-Fi Analyzer (Android) or NetSpot (macOS/Windows)
Determine your primary traffic type (gaming, streaming, file sharing)
Make sure your router firmware is up to date (especially for Wi-Fi 6)
-->
How to change the RTS threshold in your router settings: step-by-step instructions
Now let's get practical. You can change the RTS threshold in the router's web interface. Instructions for popular models:
1. TP-Link routers (Archer, Deco, Omada)
For most models TP-Link the path is this:
- Open the control panel at
192.168.0.1ortplinkwifi.net. - Go to
Advanced → Wireless → Wireless Settings. - Find the field
RTS Threshold(may be in the sectionProfessional). - Enter the desired value (for example,
1000) and save the settings (Save).
⚠️ Attention: In new firmware TP-Link (2026+) The RTS setting may be hidden. If you don't see it, try enabling it. Advanced Mode in the top menu.
2. ASUS routers (RT-AX, RT-AC, ZenWiFi)
In routers ASUS the setting is here:
- Go to
192.168.1.1(usually with login/passwordadmin/admin). - Open
Wireless → Professional. - Scroll to the block
RTS Thresholdand set the value. - Click
Applyand reboot the router.
3. Keenetic (Giga, Ultra, Hero)
IN Keenetic the path is a little different:
- Log in to the web interface at
192.168.1.1. - Go to
Wi-Fi network → Additional settings. - Find the option
RTS thresholdand change the value. - Save the changes and wait for the reboot.
4. MikroTik (hAP, RB4011, Hex)
For MikroTik will be required WinBox or WebFig:
- Open
Wireless → Interfaces. - Select your Wi-Fi network and click
Advanced Mode. - Tab
HT→ fieldRTS Threshold. - Set the value and apply (
Apply).
⚠️ Attention: IN MikroTik RTS values are specified in bytes, and not in conventional units! For example, 500 V MikroTik = ~2347 in other routers.
5. D-Link, Zyxel, Mercusys
In these routers, the setting is usually hidden in the section Advanced Wireless or Expert SettingsIf you can't find it, check the documentation for your model or update the firmware.
What to do if there is no RTS option in the settings?
In some budget routers (for example, Tenda or Totolink) the RTS setting may be missing. In this case:
1. Check if there is an alternative firmware (for example, OpenWRT).
2. Try changing Fragmentation Threshold — this is a related setting that also affects collisions.
3. If nothing helps, optimize the network in other ways (change the channel, reduce the transmission power).
How to check that the RTS threshold is set correctly
Changing the value is only half the battle. You need to make sure the new setting actually improves network performance. Here's 3 ways to check:
1. Speed and ping test
Use services like Speedtest.net or Fast.comto measure:
- 📊 Download/upload speed — should not sag more than 10% of the maximum.
- 🎯 Ping - launch
ping 8.8.8.8 -tin the command line and look at the stability (there should be minimal fluctuations).
2. Packet loss monitoring
In Windows, open a command prompt and run:
ping 192.168.1.1 -n 100
If you see lines in the results Lost = 0 (0% loss) — no losses. If losses are >1%, try reducing the RTS threshold by 200–300 units.
3. Wi-Fi traffic analysis
Install the application on Android Wi-Fi Analyzer or on PC - WiresharkPlease note:
- 📡 Interference level (must be below -70 dBm).
- 🔄 Number of retransmitted packets (V Wireshark filter by
wlan.fc.retry == 1).
If after changing RTS:
- ✅ The speed has increased and the ping has stabilized – the setup was successful.
- ❌ Speed has dropped, but ping has improved - try increasing the threshold by 200-500.
- ❌ Nothing has changed - please return to the default value (
2347).
Common RTS Setup Mistakes and How to Avoid Them
Even experienced users sometimes make mistakes when working with the RTS threshold. Here top 5 misses and how not to repeat them:
- 🔧 Blindly copying values from the Internet
Many people advise to put
2307or1000"For all occasions." This only works if your network matches the advice's author's conditions (which is unlikely). Always test! - 📉 Ignoring other Wi-Fi settings
RTS is not a panacea. If you have chosen the wrong
channel, obsolete included802.11bor channel width20 MHzinstead of80 MHz, RTS won't help. - 🔄 No router reboot after changes
Some settings (especially in MikroTik or OpenWRT) require a reboot to apply. Always do this
Reboot! - 📡 Setting RTS only for 2.4 GHz, ignoring 5 GHz
If your router is dual-band, adjust the RTS threshold for each band separately. 5 GHz typically has less interference, so you can leave the threshold higher.
- 🚫 Using RTS in Wi-Fi 6 (802.11ax) networks
In modern networks with OFDMA And MU-MIMO The RTS mechanism is less efficient. It's better to optimize it here.
Target Wake Time (TWT).
⚠️ Attention: If after changing the RTS the network performance has become worse and rolling back the settings has not helped, reset the router to factory settings (Reset button for 10 seconds) and configure from scratch. In rare cases, incorrect RTS values can cause router freezes.
Alternatives to RTS Tuning: When is it Better to Optimize Your Network in Other Ways?
The RTS threshold isn't the only tool for improving Wi-Fi. In some cases, much more effective apply other methods:
| Problem | RTS alternative | When to apply |
|---|---|---|
| Low speed | Change channel to 5 GHz or 6 GHz (Wi-Fi 6E) |
If there is little interference and the devices support high frequencies |
| High ping | Turn on QoS and prioritize gaming traffic |
For online gaming and video calls |
| Constant breaks | Decrease DTIM Interval (from 3 to 1-2) |
If your devices often fall asleep (laptops, smartphones) |
| Poor coverage | Add Mesh system or repeater | If the signal is weak in some rooms |
| Interference from neighbors | Use 160 MHz or 6 GHz (if supported) |
In apartment buildings with a large number of networks |
If you are not sure that the problem is due to collisions, first check:
- 🔌 Cable from the provider — perhaps the problem is on the Internet side, not Wi-Fi.
- 🔋 Router overheating - if it is hot, try to cool it down (for example, with a fan).
- 📱 Wi-Fi adapter drivers - update them on your PC/laptop.
FAQ: Frequently asked questions about the RTS threshold in Wi-Fi
❓ What happens if I set the RTS threshold too low (for example, 100)?
If the RTS threshold is too low (below 500), the network will littered with office bags (RTS/CTS), which will result in:
- A sharp drop in speed (up to 50% of maximum).
- Increased delays (ping can increase by 2–3 times).
- Unstable operation of devices (constant connection breaks).
Such a threshold only makes sense in extreme conditions — for example, in an office with 50+ devices on one channel.
❓ Do I need to configure RTS separately for 2.4 GHz and 5 GHz?
Yes, if your router is dual-band. Recommendations:
- 2.4 GHz: there is more interference and devices here, so the RTS threshold can be lowered to
1000–1500. - 5 GHz: there is less interference, so leave it
2347orDisabled.
Exception: If you also have a lot of devices in 5 GHz (for example, 4K streaming to 10+ clients), lower the threshold to 1500.
❓ Why did the speed drop after changing the RTS?
This means that you have installed too low threshold, and the network is flooded with service traffic. Try:
- Increase the threshold by 300–500 (for example, from
500to1000). - Check if both are turned on at the same time
CTS Protection Mode(sometimes it conflicts with RTS). - Roll back the settings and optimize the network in other ways (change channel, QoS).
❓ What RTS threshold should I set for Wi-Fi 6 (802.11ax)?
In the networks Wi-Fi 6 The RTS mechanism is less critical thanks to technology OFDMA And MU-MIMO, which effectively manage access to the channel themselves. Recommendations:
- If all devices support Wi-Fi 6 - leave it
Disabledor2347. - If there are legacy devices on the network (802.11b/g) - install
1500. - Turn on
Target Wake Time (TWT)in the router settings - this is a modern alternative to RTS.
❓ Is it possible to set up RTS on a smartphone or tablet?
No, the RTS threshold is adjustable. only on the routerOn mobile devices you can:
- Select a less busy channel manually (in Wi-Fi settings).
- Enable mode
5 GHz(if supported). - Use network analysis applications (eg. NetMaster).
If Wi-Fi problems occur only on one device, it's likely not the RTS that's at fault, but rather the device's drivers or hardware limitations.