Skip to content
← All docs

Performance and resource limits

Last reviewed 2026-10-23

Status: not available in the current build. No CPU, memory or GPU limit is active. This page will be updated when a release ships these controls and they are verified on Windows.

What is planned

  • CPU hard cap — limits processor time for the Discord/Rapcord process tree using a Windows Job Object.
  • Memory cap — limits committed memory for that same Job Object.
  • Hardware acceleration: On/Off — turning it off disables GPU acceleration after a restart and may increase CPU use.

How it will behave

  • Off by default. Values are validated and saved locally.
  • Applied at launch or restart. The settings page will show whether Windows accepted the limit.
  • If Windows rejects the assignment (for example Discord is already in an incompatible job or access is denied), the page will say not active.
  • A very low memory limit can make Discord or its renderer crash.
  • A Reset to unlimited button will remove limits.

What it is not

The GPU option is not a GPU power, wattage or percentage limit — Rapcord cannot promise a per-process GPU power cap. Lowering process priority or showing a warning is not a hard limit, and Rapcord will not label it as one.