Maybe you have a teenager who will happily consume the entire connection downloading games during your work call. Maybe a smart TV updates itself at the worst moment, or you run a guest-heavy house and want visitors capped so they cannot crowd out the family. Whatever the reason, limiting how much bandwidth a specific device can use is a standard router feature — once you know where it hides and what it is called this week.
This guide covers the two main ways routers limit devices (QoS by device and dedicated bandwidth control), walks through setup step by step, suggests sensible limits for common devices, and explains what limiting can and cannot do.
Two Different Tools: Understand the Difference
Bandwidth Control / Rate Limiting
This is a hard cap: you tell the router “this device may use at most 10 Mbps down and 2 Mbps up,” and the router enforces it absolutely, even when the network is otherwise idle. TP-Link calls it Bandwidth Control; other brands bury it in device management or parental controls. Hard caps are simple, predictable, and blunt.
QoS Device Priority
QoS does not cap a device — it deprioritises it. A low-priority device can still use full speed when nobody else needs it, but yields instantly when a high-priority device wants bandwidth. For most households, this is the smarter tool: the teenager’s downloads run at full tilt at midnight but never disturb your 2 p.m. meeting. If your router offers both, prefer QoS for fairness and hard caps for hard problems (a misbehaving gadget, a guest network ceiling, a lodging business). The distinction is explored further in Network Ustad’s QoS and bandwidth management guides.
Step-by-Step: Setting a Hard Bandwidth Limit
Step 1: Identify the Device
The router applies limits per device, identified by MAC address. Open the router’s connected devices list (192.168.0.1 or 192.168.1.1) and match the device by name; note its MAC address. Phones using randomised MAC addresses can break per-device rules — disable “Private Wi-Fi Address” for your home network on that phone, or reserve its IP so the router always recognises it.
Step 2: Open Bandwidth Control
Find “Bandwidth Control,” “QoS,” or “Device Priority” under Advanced settings. TP-Link’s Archer series places it under Advanced → QoS with per-device rules; ASUS Adaptive QoS lets you drag devices into priority tiers; many ISP routers expose simple per-device limits in their apps.
Step 3: Create the Rule
Select the device and enter the maximum download and upload speeds. Be realistic: a single HD stream needs about 5 Mbps, a 4K stream 15–25 Mbps. A sensible cap for a kid’s tablet might be 10 Mbps down / 2 Mbps up — plenty for video and schoolwork, incapable of swallowing the house. Save and apply.
Step 4: Test It
Run a speed test on the limited device and confirm it plateaus at your cap, then confirm on an unlimited device that the rest of the connection is unaffected. If nothing changed, check that the rule is enabled and the device is identified by its real, non-randomised MAC address.
Sensible Limits for Common Situations
For a child or guest device on a 100 Mbps connection, 10–15 Mbps down keeps everything they do smooth while preserving the household. For a smart TV you suspect of hogging with background updates, priority-based QoS beats a cap (a cap below 25 Mbps breaks its 4K streaming). For a lodger or Airbnb unit on a separate SSID, a hard cap of a quarter of your total speed is a fair, defensible rule. And remember upload: limiting upload to 1–2 Mbps on bulk devices prevents cloud backups from saturating the narrow upstream that calls and gaming depend on. Brand-specific menu paths differ; TP-Link’s official bandwidth control and QoS walkthrough shows one common layout in detail.
Parental Controls: The Friendly Front-End
Many routers wrap these same mechanisms in parental controls with friendlier language: pick the child’s profile, set a speed tier or a “bedtime” schedule, done. Some ecosystems (TP-Link HomeShield, ASUS AiProtection, ISP apps) make per-device limits a two-tap job. If your goal is managing children rather than engineering traffic, start there — it uses the same engine underneath and is far easier to maintain as devices change.
Limits for a Whole Network Segment: Guest and IoT Caps
Sometimes the unit you want to control is not one device but a whole group. Many routers let you apply a bandwidth ceiling to the guest network as a whole — for instance, guests collectively get 20 Mbps no matter how many of them connect — which is the graceful way to run hospitality Wi-Fi in a busy home, a rental unit, or a small café. On more advanced routers and mesh systems you can do the same for an IoT network, capping the entire smart-home segment so a malfunctioning camera uploading endlessly to the cloud cannot strangle the household. Setting a group cap involves the same logic as a device cap — find the network in the router’s QoS or guest settings, enter totals rather than per-device numbers — but test it with two devices at once, because a shared cap is divided among whoever is active, not multiplied per device. Group limits are also the honest answer when family members object to being singled out: the guest network has a speed, and that is simply the house rule.
Will the Limited Device Notice?
For everyday use, a sensibly chosen cap is invisible: web pages, messaging, music, and even HD video all fit comfortably inside 10 Mbps. The limit only becomes obvious during bulk activity — large downloads simply take longer — which is precisely the behaviour you are buying. If complaints arrive, the numbers let you negotiate like an engineer: show the household traffic graph, and adjust the cap rather than abandoning it.
Common Mistakes and Tips
Mistake one: capping a device so low that its normal use breaks — video calls need roughly 2–4 Mbps up and down with headroom, so a 1 Mbps cap sabotages school and work. Mistake two: fighting randomised MAC addresses — the limit “randomly stops working” because the phone presented a new identity; fix the identity issue, not the rule. Mistake three: capping by device when the real hog is one app on a shared PC — per-device rules cannot distinguish your spreadsheet from your son’s game download on the same machine; QoS application rules or schedules work better there. Tip: combine tools — QoS priorities for everyday fairness, a hard cap only for the guest network and any known problem device.
Conclusion
Limiting a device’s bandwidth is a five-minute router job once you find the right menu: identify the device by its MAC address, choose between a hard cap and QoS priority, set realistic numbers, and test. Used thoughtfully, it ends the nightly bandwidth wars — the downloads still finish, the calls stay clear, and nobody has to play network police.
Frequently Asked Questions
Will limiting one device make my own connection faster?
Only if that device was actually saturating the connection. Limits and QoS help under contention; on an idle network, a capped device changes nothing for anyone else.
What is a fair bandwidth limit for a child’s device?
On a typical home connection, 10 Mbps down and 2 Mbps up covers HD video, browsing, and schoolwork comfortably while preventing one device from consuming the whole house. Adjust proportionally if your plan is much slower or faster.
Why does my bandwidth rule stop working on my phone?
Phones rotate their Wi-Fi MAC address for privacy, so the router sees a “new” device outside your rule. Disable the Private Wi-Fi Address option for your home network in the phone’s settings.
Can I limit bandwidth only at certain times?
Yes, on routers with scheduled parental controls — a common setup caps or pauses kids’ devices at bedtime while leaving them unrestricted during the day. Basic QoS pages without scheduling cannot do this.
Does limiting upload speed matter?
Very much. Home connections have far less upload than download, and a single device saturating upload (cloud backup, torrent seeding) makes everything feel slow and ruins call quality. Capping upload on bulk devices is often the highest-value limit.
Leave a Reply