Quality of Service decides what your router does when there is more traffic than bandwidth. That is the whole idea. When the connection is not saturated, QoS does nothing at all, which is why so many people enable it, see no change, and assume it is broken.
This guide covers what the settings mean, which ones matter, and the specific misconfiguration that makes QoS actively harmful.
What QoS actually does
Without QoS, your router forwards packets first-come first-served. A large upload and a video call are treated identically, so the upload fills the queue and the call degrades. QoS reorders that queue so latency-sensitive traffic jumps ahead of bulk transfers.
The critical consequence: QoS only helps at the bottleneck, and only when that bottleneck is your own connection. It cannot do anything about congestion inside your ISP's network or a slow server at the other end.
The one setting that matters most
Bandwidth limits. Almost every QoS implementation asks for your upload and download speed, and almost everyone enters the number from their ISP contract. That is the wrong number.
For your router to control the queue, the queue has to form on your router. If you tell it you have 100 Mbps and you actually get 94, the bottleneck sits in your modem or at the ISP, where your router has no control, and QoS silently does nothing.
- Run a speed test several times, at a busy hour, with nothing else using the connection.
- Take the lowest sustained figure, not the peak.
- Enter 85 to 95 percent of that value in the QoS bandwidth fields.
- Test a video call while running a large upload. If the call holds up, the ceiling is right.
Priority rules, and why presets disappoint
Most routers ship categories like Gaming, Streaming, Web Browsing and File Transfer. They classify by port and protocol, which was reasonable fifteen years ago and is mostly guesswork now. Almost everything is HTTPS over 443, so a 4K stream, a video call and a system update look identical to the classifier.
What to do instead
Prioritise by device, not by application. You know which machine is the work laptop and which is the media server. Device-based rules do not depend on guessing what a packet contains.
- Highest: VoIP handsets, work laptops in calls, games consoles in use
- Normal: phones, tablets, general browsing
- Lowest: NAS backups, cloud sync, update servers, anything unattended
Smart Queue Management: usually the better option
If your router offers SQM, fq_codel or CAKE, use it in preference to classic priority QoS. These target bufferbloat, which is the real cause of most "the internet feels slow" complaints, rather than trying to classify traffic by type.
Bufferbloat is oversized buffers holding packets instead of dropping them, so latency climbs from 20 ms to several hundred under load while raw throughput looks fine. Modern queue disciplines keep the queue short and latency stays flat. You still have to set the bandwidth ceiling correctly.
Settings you can usually leave alone
| Setting | Verdict |
|---|---|
| WMM / WiFi Multimedia | Leave enabled. It is the wireless-side equivalent and the default is right. |
| DSCP / ToS marking | Ignore unless you run managed switches that honour the marks. |
| Per-app port rules | Rarely worth it now that nearly everything rides on 443. |
| Bandwidth ceiling | Set this. It is the setting that determines whether QoS works. |
| SQM / CAKE / fq_codel | Enable if offered. Better results than priority classes. |
When QoS is the wrong tool
QoS reshuffles a queue. It cannot create bandwidth. If one device is consistently consuming most of your connection, reordering the queue is treating a symptom, and a hard per-device cap is the more direct fix.
Router QoS also gives you very little visibility. You can see aggregate throughput, but working out which device caused a 9pm slowdown usually means watching a live graph at the moment it happens. Per-device monitoring on the LAN answers that question directly, and tools like Perimetery PRO let you cap the offender without touching router configuration at all.
Frequently asked questions
Should I enable QoS on my router?
Enable it if your connection actually saturates and you notice calls or games degrading when someone uploads or streams. If you rarely hit your bandwidth ceiling, QoS will make no measurable difference.
Why did QoS make my internet slower?
Almost always because the bandwidth ceiling is wrong. Set too low, you cap yourself unnecessarily; set at or above your real line speed, the queue forms upstream where the router has no control. Measure your real throughput and set 85 to 95 percent of it.
What is the difference between QoS and bandwidth limiting?
QoS decides the order packets are sent when the link is congested. Bandwidth limiting sets a hard ceiling on a device regardless of congestion. QoS shares fairly under load; a cap enforces a maximum at all times.
Is SQM better than traditional QoS?
For most home and small office connections, yes. SQM targets bufferbloat and keeps latency low without needing to classify traffic by application, which has become unreliable now that nearly all traffic is encrypted.
See every device on your network
Perimetery PRO shows live upload and download per device, and lets you cap or block any of them in one click. Runs on one Windows machine, no agents to deploy.
See pricing