outboundctl limit

outboundctl limit caps how fast one app can upload or download over TCP. Speed limits covers the same limits in the app.

outboundctl limit <app> <rate> [--up|--down]
outboundctl limit list [--json]
outboundctl limit clear <app>
outboundctl limit clear --all

Setting a limit

<app> is the app’s signing identifier, or the absolute path to the app or its executable. Write the rate with its unit: Kbit/s, Mbit/s or MB/s. A capital B means bytes, so 1 MB/s is the same as 8 Mbit/s.

outboundctl limit com.example.app "2 Mbit/s"
outboundctl limit com.example.app "500 Kbit/s" --up

Without --up or --down, the rate applies in both directions. --up changes only the upload limit and keeps the download limit; --down does the opposite.

What a limit covers

Limits apply to TCP. Traffic on UDP port 443 (QUIC) falls back to TCP, so it is limited too; other UDP traffic is unchanged. VPN and tunnel apps are exempt. Limits stay on while Outbound is paused.

Listing and clearing

limit list shows each app’s caps in bytes per second, with “Off” for a direction that has no limit. With --json, a direction without a limit is null. limit clear <app> removes one app’s limits, and limit clear --all removes every limit.

Setting and clearing limits are changes, so they follow outboundctl changes in Settings › Security.