Leave more room for everything else.
Best while gaming, streaming, editing, or running other demanding apps. Heavy processing may take longer.
- Lower resource pressure
- Good for multitasking
- Monitoring continues normally
Help Center / PerformancePerformance
Use your PC your way while Cliprr works.
Choose how aggressively Cliprr uses your computer during heavy processing. Balanced is the recommended default; Low Impact leaves more headroom for games and demanding apps.
Processing Performance
Pick the mode that matches what your PC is doing.
The setting primarily changes heavy work such as transcription, local AI title generation, and video rendering. It does not turn ordinary monitoring or uploads off.
Good speed without monopolizing the PC.
The default choice for most users. Cliprr limits heavy work while keeping resources available for normal desktop use.
- Recommended starting point
- Memory-pressure protection
- Local AI released after use
Prioritize processing throughput.
Best when Cliprr is the main workload and the computer has enough headroom for more processing resources.
- Faster heavy processing
- More resource use
- Best on a dedicated/high-headroom PC
If your build does not show Settings → Processing Performance, update to the latest available Cliprr build before relying on this selector.
Resource protection
Waiting can be intentional.
Cliprr checks system pressure before starting more heavy work. When the PC is already busy, delaying the next render is safer than stacking everything at once.
Why is a clip queued?
Another heavy job may already be running, available RAM may be temporarily low, or Cliprr may be limiting concurrency to keep the computer responsive.
Why does Cliprr use CPU?
Transcription, rendering, audio processing, encoding, and some AI work are local compute tasks. CPU use can rise temporarily when a clip is actually being processed.
Why does Cliprr use RAM?
Local transcription, video processing, and AI models need memory. Cliprr can wait before starting more heavy work when memory pressure is high.
Why is Ollama running?
Cliprr can use a local model for title suggestions. Resource behavior depends on the selected processing mode, and normal Balanced/Low Impact behavior is designed to avoid keeping the local model resident longer than needed.
Gaming & multitasking
Use Low Impact when responsiveness matters more than render speed.
Monitoring Twitch is much lighter than transcription, AI inference, rendering, and encoding. Your PC can look mostly idle while monitoring, then get temporarily busier when a clip needs heavy processing.
Gaming / streamingLow Impact
Browsing / normal workBalanced
Cliprr is the main workloadMaximum Speed
Not sureBalanced
Advanced resource diagnosticsFor support and deeper troubleshooting.
Cliprr has a resource diagnostic that can report the active processing mode, available memory, process memory, active heavy jobs, and long-form worker activity. This is support information—not something most users need during setup.
If performance still feels wrong after changing modes, capture the resource diagnostic and current Clipping Health state before changing unrelated settings.