Learn / Guide
Rainmeter CPU Usage Meters: Total, Per-Core and Frozen Readings
Understand Rainmeter CPU percentages, Processor selection and update timing. Separate system usage from Rainmeter process consumption and CPU temperature.
Rainmeter's built-in CPU measure reports processor usage from 0 to 100 percent. Processor=0, the default, measures the average across CPU cores; Processor=1, 2 and so on select a specific core. This is system activity, not the CPU consumed only by Rainmeter, and it is not processor temperature.
Scope: this is an interpretation and configuration guide based on the official CPU measure documentation. It does not benchmark any skin or guarantee identical numbers across Windows monitoring tools.
Pick the reading that answers your question
| Question | Relevant measurement | Do not substitute |
|---|---|---|
| How busy is the CPU overall? | CPU measure with Processor=0 | One core's reading |
| Is one core much busier? | Separate CPU measures with specific Processor values | The overall average alone |
| Is Rainmeter slowing the computer? | Rainmeter process usage in Task Manager | The desktop's system CPU percentage |
| How hot is the processor? | A supported sensor integration | A CPU usage percentage |
If Rainmeter itself is the suspected workload, follow high CPU usage diagnosis. For heat readings, use the separate CPU temperature and sensor guide. A percent sign and a degree symbol represent different measurements.
1. Find the underlying measure
- Open Manage → Skins, select the loaded configuration and choose Edit.
- Find the measure feeding the visible CPU meter. A built-in example uses
Measure=CPU; a third-party plugin requires its own documentation. - Check Processor. Missing or zero means the average; a positive number selects a particular core.
- Open About → Skins, select the configuration and inspect that measure's Number and Range alongside the displayed label.
A graphical meter is not the measurement itself. A correct underlying number with an implausible label points toward meter binding or formatting. If the measure is wrong or stopped, changing the display's font or graph color cannot repair its source.
2. Understand averages and per-core displays
A single busy core can coexist with a modest overall average. A panel labeled CPU may show the average, while a row labeled Core 1 shows a different slice of activity. Do not expect every row to match or add per-core percentages together and compare the sum with a 0–100 total.
Use processor identifiers supported by the running system rather than assuming a fixed suite matches every CPU. The Lines resource, for example, lists core-oriented displays but does not establish automatic adaptation to every core count. Source-listed appearance is not evidence of correct configuration on your hardware.
3. Inspect timing, smoothing and percentage formatting
The effective measure interval is the skin's Update multiplied by its UpdateDivider. Update=1000 with UpdateDivider=2 samples on a two-second schedule. A meter can also have its own divider, so the displayed text may refresh less frequently than the measure.
AverageSize smooths a measure over past values. Different update schedules and smoothing settings can produce visibly different readings during a changing workload. Compare the same time period and measurement type before deciding that a mismatch is a fault.
The CPU measure already provides a percentage value and its appropriate range. A String meter's numeric Scale option divides values; AutoScale formats units. Neither is needed simply to turn CPU activity into percent. Check an unexpected multiplier or divisor before changing the measure itself.
When the number is frozen or always zero
In About → Skins, check whether the measure is paused or disabled. A paused measure retains its previous value; a disabled measure returns zero in numeric contexts. A negative UpdateDivider updates only on load or refresh, which is inappropriate for a continuously changing usage readout unless the skin deliberately updates it through actions.
Confirm that you edited the active variant, saved the correct file and refreshed the skin. Back up files before editing using the customization workflow. If only a plugin-based per-process meter fails, this built-in CPU procedure does not establish the plugin's configuration or repair it.