Best case
Recent laptop or desktop browser
This is where the richest motion, color, and layering tend to show up, especially on newer hardware with stable graphics drivers.
Before you start
Stims starts fast with demo audio, then adjusts to your browser and hardware. This page tells you what to expect before you dive in.
Best case
This is where the richest motion, color, and layering tend to show up, especially on newer hardware with stable graphics drivers.
Expected fallback
If Stims eases back on rendering load, the preset keeps running while resolution, feedback buffers, or visual density may become lighter.
Fastest first run
Demo audio avoids permission friction and gets everything moving immediately. Microphone and tab capture are optional upgrades.
What to expect
| Setup | Expectation |
|---|---|
| Newer desktop browser | Richest detail and the best shot at the heaviest rendering stack. |
| Older laptop or integrated graphics | Stims may ease back to keep motion stable. |
| Phone or tablet | Expect a cleaner, lighter run with touch-friendly controls. |
| TV-style browser | Use the default quick looks first and keep extra tuning minimal. |
When things look simpler
Quick fixes
Measured, not universal
Stims compares code changes in a real browser while holding the preset, audio, viewport, renderer, and quality step constant. In one equation-heavy WebGPU stress case on an Apple M1 Max, a JIT hot-loop change reduced average frame work from 17.56 ms to 15.31 ms at 4× CPU throttling, while median delivered FPS moved from 58.14 to 59.88.
That result is evidence for one preset on one host, not an FPS promise for every device. The full method and the noisy tier that was not promoted are documented in the repository's runtime performance evidence .
First steps