QoS: Deciding Who Goes First on Your Network

The complaint almost always takes the same shape: the video call breaks up exactly when someone at home starts a large download. The subscription speed hasn't changed, and a speed test still looks fine when run at a quiet moment.

What changed isn't the speed. It's the queue.

A network is a queue, not a pipe

The "pipe" image suggests bandwidth is shared evenly and smoothly. What actually happens looks more like a service counter: data arrives in small pieces, and when it arrives faster than it can be sent out, the rest waits in the router's buffer.

A large download doesn't wait politely. It sends as much as it's allowed to, and within seconds that buffer is full. Your video call's packets then join the back of a long line, they still arrive, just late.

Half a second late means nothing to a file being downloaded. To a voice, it's an audible break. The difference between the three measurements people routinely confuse is covered in the guide to bandwidth, latency, and throughput.

This symptom has a name of its own: bufferbloat: oversized buffers making latency spike precisely when the network is busy. And that is what QoS actually fixes.

What QoS actually does

QoS does two things, and both need understanding so the expectation is right:

• It holds back slightly below capacity. The router deliberately sends a little slower than the line can manage, so that the queue that matters sits in your router, not in the provider's equipment, which you can't configure.
• It reorders that queue. Once the queue is under its own control, the router can put small time-sensitive packets ahead of large ones that don't mind waiting.

The trade is honest: you give up a little peak speed for steadiness. Downloads may drop two to five per cent. Video calls stop stuttering. For nearly every household, that trade is worth making.

Three forms you'll meet

Menu names differ between brands, but what's underneath falls into three forms.

Per-device priority

You choose which device goes first, the work laptop, say, ahead of the television. Easiest to reason about, hardest to get wrong, and enough for most homes. It requires the device to be recognised consistently; some phones randomise their MAC address, so that needs turning off on the home network or the rule quietly stops applying. That behaviour is covered in the guide to MAC address filtering.

Per-traffic-type priority

The router tries to identify what's a video call, what's a game, what's a download. Tidy in theory. In practice nearly all traffic today is encrypted, and the router's guess often misses, a work meeting mistaken for entertainment streaming, then placed at the back.

Smart queueing with no rules at all

Names vary: Smart Queue, SQM, Adaptive QoS, or fq_codel on open firmware. It asks you to write no priority list whatsoever. The router simply prevents any single flow from dominating the queue for long.

For most people this third form is the one that helps most: and demands the least upkeep. If your router has it, start there and leave everything else alone.

Setting it up

1. Measure the real speed first at a quiet time, and note both the download and upload figures.
2. Open the router's admin page and look for QoS, Bandwidth Control, or Traffic Management.
3. Enter roughly 85–90 per cent of those figures as the limit. That number is what moves the queue into your router. Entering 100 per cent leaves QoS doing almost nothing.
4. Prioritise the upload side. On home connections upload is far smaller and fills first, and it's what ruins video calls. The reason is covered in the guide to why upload is slower than download.
5. Test it deliberately. Start a large download, then make a video call on another device. If the call stays clear, the setting is right.

If your measured speed varies, common on wireless and cellular links, pick a figure near the worst case, not the best.

When QoS won't help

Several situations look like priority problems and aren't:

• Weak Wi-Fi signal. QoS manages the queue on the internet side, not the air between router and device. What to check is in the guide to full signal but slow internet.
• Congestion at the provider. If it slows at the same hour every day across every device, the queue isn't in your house, the guide to internet slow at certain hours covers how to tell.
• Too many devices for one router. The limit there is device count, not ordering.

One more thing worth stating plainly: router QoS only governs traffic passing through that router. It cannot ask a service out on the internet to send faster.

Closing notes

QoS adds no speed. It moves the queue somewhere you can control, then makes sure small time-sensitive things don't end up behind a large download.

If your router offers smart queueing, switch that on and stop there. If not, per-device priority is enough for almost any home, and the side that most needs managing isn't download but the much narrower upload.

And if the network never felt congested to begin with, QoS will change nothing. Turning it on only adds one more setting to remember on the day something behaves oddly.

Frequently asked questions