Intel CPU Power Limits: PL1, PL2, Tau, PBP, and MTP Explained

Intel processor power discussions often mix product-page specifications with firmware controls as if they were interchangeable. They are related, but they answer different questions. Processor Base Power (PBP) and Maximum Turbo Power (MTP) are specification fields used on current Intel product pages. PL1, PL2, and Tau are part of the platform power-control model exposed in Intel technical documentation. A motherboard can also add its own firmware policy within the capabilities and constraints of a particular processor and platform.

That distinction is essential when interpreting monitoring software or BIOS settings. A 125 W Processor Base Power entry is not a promise that package power will always be 125 W. A Maximum Turbo Power value is not a whole-PC wall-power specification. Likewise, seeing PL1 or PL2 in firmware does not mean every Intel generation implements the same values or timing behavior. Exact processor and platform documentation takes precedence over a generic rule.

Intel platform datasheets describe Power Limit 1 as part of package average-power control. The processor can move above or below a configured PL1 as workload, turbo state, electrical limits, temperature, and the power-control algorithm interact. PL1 therefore should not be read as a claim that a CPU draws exactly that number whenever it is busy.

On many Intel processor lines the recommended PL1 value aligns with the listed Processor Base Power, but that relationship must be checked for the exact platform rather than assumed globally. Intel’s current Core Ultra 200S documentation, for example, lists a 125 W Processor Base Power configuration with a recommended 125 W PL1. That is a documented configuration example, not a rule that every Intel CPU maps PBP and PL1 identically under every firmware policy.

Intel describes PL2 as opportunistic higher average processor power of limited duration, with its behavior controlled together with the PL1 Tau mechanism. This is the power-control layer commonly associated with heavier turbo operation. A workload still has to create enough demand, and other electrical, thermal, frequency, and firmware constraints can prevent package power from reaching the configured PL2 value.

The difference between PL1 and PL2 also varies by product. In Intel’s Core Ultra 200S datasheet, one 125 W 8P+16E configuration lists recommended PL1 at 125 W and PL2 at 250 W, while a 125 W 6P+8E configuration lists 125 W PL1 and 159 W PL2. Intel’s 13th/14th Gen desktop documentation includes configurations where PL1 and PL2 can be equal. Those examples are why a generic formula such as “PL2 is always twice PL1” is incorrect.

Tau is frequently simplified into “the number of seconds the CPU may run at PL2.” Intel’s own documentation is more precise: PL1 average power is controlled through an algorithm using the PL1 Tau time constant, and a larger Tau allows higher-power behavior to influence the average over a longer window. That makes Tau part of an average-power control mechanism rather than a stopwatch promising a fixed period at exactly PL2.

The practical consequence is that you cannot predict a processor’s package-power trace from PL1, PL2, and Tau alone. Workload intensity can change during the window, the processor may hit another limit first, and platform firmware can use generation-specific behavior. Intel also publishes different recommended Tau values across processor lines. Current Core Ultra 200S documentation, for example, lists 56 seconds for several 125 W desktop configurations and 28 seconds for a 65 W desktop configuration. Treat those as exact documented platform values, not universal Intel defaults.

Processor Base Power and Maximum Turbo Power make current Intel product specifications easier to read without requiring a buyer to decode every programmable register. They still describe processor power specifications, not AC input at the wall. Motherboard conversion losses, memory, graphics, storage, fans, peripherals, the PSU itself, and other components all contribute to whole-system consumption.

PBP is also not a universal thermal prediction. Two processors with the same PBP can differ in die configuration, voltage-frequency behavior, workload efficiency, cooling interface, firmware policy, and actual package power over time. MTP similarly should not be converted into an expected gaming draw or a guaranteed all-core workload number without measurement of the exact system.

PBP and MTP did not make PL1, PL2, and Tau obsolete as technical concepts. Intel’s Core Ultra 200S and 200HX datasheet continues to publish Power Limit 1, Power Limit 2, and Power Limit 1 Time (PL1 Tau) values alongside Processor Base Power configurations. The product-page labels and the platform controls are therefore best understood as different views of related power behavior rather than old terminology being mechanically renamed one-for-one.

The relationship is also generation- and segment-dependent. Mobile systems give the OEM much more reason to tune behavior around chassis cooling, acoustics, battery operation, and form factor. Intel explicitly tells system designers to adjust Tau to cooling capability when the thermal design cannot support the performance setting. Desktop motherboard firmware can likewise expose controls or policies that alter behavior from what a user expects from a headline specification alone.

Start with the exact CPU, processor line, and motherboard firmware. Check Intel’s specification page for PBP and MTP, then use the matching Intel platform datasheet when you need PL1, PL2, or Tau detail. In firmware, determine whether a displayed value is an Intel default or recommendation, a motherboard preset, an automatic value, or a manual override. Motherboard enhancement modes should not silently be described as Intel stock behavior.

During a workload, monitor package power together with clocks, temperature, and reported limit reasons where reliable tooling exposes them. Reaching a temperature limit, current limit, voltage/frequency boundary, or workload bottleneck can change observed behavior before a nominal power limit is reached. Conversely, seeing package power below MTP does not prove that turbo is malfunctioning; MTP is a specification ceiling for the product, not a target every workload must hit.

For cooler selection, firmware tuning, performance testing, or troubleshooting, avoid carrying one generation’s PL1/PL2/Tau values into another. Intel’s own datasheets show different recommended limits and Tau values by processor configuration and segment. BIOS revisions and motherboard policies can add another layer, so record those settings when comparing measurements between systems.

The durable model is simple: PBP and MTP are processor specification fields; PL1 and PL2 are package power-control limits; Tau influences the PL1 average-power control window; and real package power is the result of workload demand interacting with those controls plus thermal, electrical, frequency, and firmware constraints. Keeping those layers separate avoids most of the misleading claims built around “TDP,” turbo duration, and CPU wattage.