A USB-C hub may advertise a high-wattage power input yet deliver less power to the laptop connected through it. Plugging in a flash drive, Ethernet adapter, or other peripheral can also change how much power remains available elsewhere. The missing power is not necessarily a fault. A hub is an active device with its own power requirements and a finite power budget.
Passthrough charging adds another layer. Power enters the hub through one USB-C port, some of it operates the hub and its attached devices, and the remaining capacity can be offered upstream to the computer. The exact result depends on the hub design, charger, cable, connected loads, and the power contract negotiated over USB Power Delivery.
The hub sits inside the power path
A passive cable mainly connects two endpoints. A hub contains electronics that switch USB data among ports and may also provide Ethernet, display output, card readers, audio, or other functions. Those circuits require power.
A powered USB-C hub can receive energy from an external charger and distribute it between its internal electronics, downstream ports, and the host-facing connection. USB terminology separates data roles from power roles: a port’s position in the data topology does not by itself dictate whether that port is currently supplying or consuming power.
USB Power Delivery supports negotiated power roles and power levels. A compatible source advertises capabilities, and a sink requests an operating point that both sides support. The resulting contract is a limit for that connection, not a promise that every watt entering a multiport hub can be forwarded to one attached device.
This distinction is visible in hubs sold with a dedicated USB-C power-input port. The input rating describes what that port and the hub are designed to accept under supported conditions. The host-facing charging capability is a separate property.
Input power and host charging power can differ
Suppose a hub accepts power from a USB-C charger while also powering its own controller, an Ethernet interface, and several downstream devices. The hub cannot forward energy that its own operation and downstream loads already consume.
USB-IF guidance for upstream-facing-port-powered hubs states that a hub’s total draw must remain within the power contract negotiated with its source. It also calls for the hub’s own consumption, including internal product loads, to be represented in its power descriptors. That reflects a basic constraint: distribution happens inside the amount the source has agreed to provide.
Manufacturers can implement that distribution in different ways. A hub may reserve a fixed allowance for itself, manage downstream capacity dynamically, or impose product-specific limits on particular ports. A label such as “100 W input” therefore should not be read as “100 W to the laptop” unless the product documentation explicitly states that host output under the relevant conditions.
Conversion also matters. Internal power circuitry may need to regulate voltage for hub electronics and peripheral ports. Real conversion is not lossless, so electrical input and usable output cannot be assumed to match exactly.
The charger and cable set the outer boundary
A hub cannot create a USB Power Delivery mode that the source does not offer. Connecting a hub rated for a high input level to a lower-rated charger leaves the system bounded by the charger’s supported capabilities.
The cable can matter as well. USB-C describes the connector shape, while supported power and data capabilities depend on the cable and connected products. Higher USB Power Delivery levels require suitable components across the connection. A hub’s maximum rating therefore describes capability under compatible conditions rather than the result of every USB-C charger-and-cable combination.
USB Power Delivery currently supports power levels extending well beyond the original low-power USB use cases. That broader range does not remove negotiation. Source, sink, cable, and product implementation still determine the contract that can actually be established.
This is also a reason that swapping only the charger may not change the laptop’s charging rate. If the hub’s host-facing output is the limiting element, extra source capacity remains unavailable to the computer through that path.
Downstream devices consume part of the budget
USB peripherals are not electrically free just because they are small. Storage devices, network interfaces, receivers, card readers, phones, and other accessories can draw power from downstream ports when the hub supplies it.
A bus-powered hub has a particularly direct constraint because its upstream connection supplies both the hub and downstream loads. A hub with a separate power input has more room to distribute energy, but it still operates within negotiated and product-specific limits.
USB-IF guidance for powered hub designs also treats downstream ports as managed power outputs rather than an unlimited common rail. Individual port limiting and overcurrent protection are part of the design considerations. For a user, the practical implication is that the sum of attached loads matters even when each device works normally on its own.
This can produce behavior that looks inconsistent. A portable drive may work when it is the only substantial load, while a combination of several devices may expose a hub’s downstream power limit. The exact response is implementation-dependent: a product might restrict a port, reduce available charging capacity, or fail to support a particular load combination.
Data capability is separate from charging capability
USB-C ports that look identical can expose different functions. One port on a hub may be intended only for charger input. Another may carry data to the host. Downstream USB-C ports may support data and source power but not accept power for the hub.
The connector alone does not reveal those roles. USB Type-C defines source, sink, and dual-role power behavior separately from downstream-facing, upstream-facing, and dual-role data behavior. USB Power Delivery can also support role changes in products designed for them.
That separation explains several common surprises. A charging-input port may not enumerate a storage device. A data-capable downstream port may provide only the power level implemented for that port. A host-facing cable connection can carry data in one direction while negotiated electrical power flows toward the host.
Port markings and the product specification are therefore more informative than connector shape. Terms such as PD input, host, upstream, downstream, data, and charging output describe distinct capabilities even when every receptacle is USB-C.
Passthrough charging is a chain of negotiated limits
It is tempting to treat passthrough charging as a simple extension cable with extra ports attached. Electrically, it is closer to a chain of power relationships with an active device in the middle.
The charger establishes what it can supply. The cable must support the relevant connection. The hub accepts a supported input, consumes and distributes part of that budget, then offers supported power toward the host. Attached peripherals can add their own demands. The computer finally decides what power it requests and accepts within the capability presented to it.
As a result, the most useful specification for a hub is not its largest wattage number in isolation. The relevant figures are the supported charger input, the stated host charging output, any downstream power limits, and the conditions attached to those ratings. When those values are documented separately, they describe the actual power path far more clearly than the connector type alone.