← Back to Performance Tests

This diagnostic tool needs JavaScript to access your camera and microphone and run the live test. Please enable JavaScript in your browser settings, then reload this page.

Render Path, Not Encoder Path

Stream Overlay & FPS Stability Stressor

Different from the Hardware Stress Test, which loads your encoder. This loads the render and compositing path directly with increasing numbers of animated overlay graphics, and measures your real achieved frame rate as that load climbs — the subsystem actually stressed by heavy stream overlays, alerts, and browser-source graphics in OBS-style setups.

Camera off

Controls

Overlay Elements 0

Drag the slider to load manually, or click Start then "Run Full Sweep" for an automatic step-through.

Current FPS: —

Result

Overlay Elements	Measured FPS

Notes

Why this is a different stress test than the other one

Video encoding and screen rendering are handled by different parts of your system, and a machine can be strong at one while struggling with the other. The Hardware Stress Test answers "can my CPU sustain encoding for a long call." This answers a different, equally real question: "can my system keep rendering smoothly when I add heavy visual overlays on top of my stream" — relevant to streamers running alerts, animated graphics, or browser sources in OBS.

Reference

Target Frame Rates for Streaming

Use case	Target FPS	Why
Standard video call	24 – 30 fps	Smooth enough for talking-head video.
Gaming or fast-motion streaming	60 fps	Noticeable stutter below this for fast-moving content.
Overlay-heavy production streams	60 fps sustained	Alerts and animated graphics amplify any dropped frames.

General streaming targets, not thresholds this specific tool grades against — your achieved FPS at each overlay level is the real, direct measurement to compare against these targets yourself.

Step-by-Step

How to Run the Test

Click "Start" and allow camera access when prompted.
Drag the overlay slider manually to see FPS change in real time, or click "Run Full Sweep" for an automatic step-through.
Read the results table showing measured FPS at each overlay element count.
Find where your FPS drops below your target for your actual use case — 30fps for calls, 60fps for gaming or fast motion.

Common Issues

Improving Render Performance

Camera access blockedClick the camera icon in your browser's address bar to confirm this site is allowed, or check your OS's camera privacy settings.

FPS drops sharply even at low overlay countsCheck whether hardware GPU acceleration is enabled in your browser's settings — some browsers default to software rendering on certain systems, which is dramatically slower.

Want better overlay performance while streamingSimplify animated overlay graphics, reduce their update frequency, or close other GPU-intensive applications running at the same time.

Common Questions

Frequently Asked Questions

How is this different from the Hardware Stress Test?

The Hardware Stress Test sustains ENCODER load — it stresses your CPU by encoding video for two minutes straight. This stresses a different subsystem entirely: the render and compositing path, by drawing increasing numbers of animated overlay graphics every frame, which is what heavy stream overlays and browser-source graphics in OBS-style setups actually load.

Why would my FPS drop with overlays but not during plain video calls?

Rendering many animated graphics every frame is GPU and compositing work, separate from video encoding. A machine with plenty of encoding headroom can still stutter under heavy overlay graphics if its rendering path is the bottleneck instead — this isolates that specific case.

What counts as a good result here?

Whatever holds your target frame rate for your actual use — 24-30fps is enough for a standard call, while gaming or fast-motion content benefits from sustaining 60fps even under overlay load. There is no single universal pass/fail number, since it depends on what you're actually producing.

Does this simulate real OBS browser sources exactly?

Not exactly — it uses animated canvas particles as a standardized, repeatable render-load generator rather than replicating any specific overlay software. It reliably demonstrates your system's genuine render-path headroom, which is the same underlying capacity real overlays draw on.

Why does "Run Full Sweep" briefly change my overlay slider?

The automatic sweep steps through several preset overlay counts in sequence to measure FPS at each one, moving the slider itself so you can watch the correspondence between overlay load and measured frame rate directly.