Paralives Field GuideParalives Field Guide

Save-safe fix

Fix low FPS in Paralives

Paralives laggy, stuttering or stuck below 60 fps? Shadow distance first, then reflections, resolution scale and a frame cap — the fix walk, in order.

Platform:
PC / Mac / Steam Deck
Last verified:
2026-10-08

Symptoms

  • Stable 60 fps in build mode, 25 fps in live mode
  • Stutters every time a Para crosses a district boundary
  • Mountain district halves your framerate
  • The game feels laggy overall — clicks land late even though the fps counter looks fine
  • Sudden lag spikes in live mode: a half-second freeze every few minutes

Fix by when it crashes

Build mode is smooth, live mode stutters

Live mode simulates Paras, needs and routing on top of the render, so it always costs more than build mode's static shell. Shadow distance is the setting that moves live-mode FPS the most — take it to medium before touching anything else.

A freeze at every district boundary

Crossing a district boundary streams in a new prop set, which shows up as a one-off hitch. Cap the framerate at 60 so the spike has headroom, and keep resolution scale at 90% so the burst of loading is not competing with a full-res frame.

Only the Mountain district drops

The mountain is the heaviest district to render — tree cover plus long sightlines from elevation. If only Mountain halving your framerate describes you, lower shadow distance and reflections there first and leave the other districts' settings alone.

Laptop: fine for ten minutes, then slow

That curve is thermal throttling, not the game. Cap the framerate at 60, and force the discrete GPU for Paralives.exe in the Nvidia or AMD control panel so the iGPU never takes over.

Feels laggy even when the fps looks fine

Lag is how poor performance feels; fps is how it measures. When clicks land late or the world hitches without the number dropping, you are seeing stutter spikes, not a slower GPU — and the same fixes apply. Run the FPS cheat while it happens to see what the number actually does.

Lag spikes in live mode

This one is officially acknowledged: live-mode stutter has been on the studio's known-issues list since patch 0.1.2, and the work is not finished — patch 0.1.8 optimized animation loading, newspaper generation and camera-occlusion fading specifically to reduce stutters. Cap the framerate so each spike has headroom, and follow the tracker on the known-issues page.

Try in order

  1. 1Lower shadow distance to medium and disable real-time reflections in Graphics settings.
  2. 2Cap framerate at 60 fps to stop GPU thermal throttling on laptops.
  3. 3Set resolution scale to 90% — gives back ~15-20% headroom with minimal visible loss.
  4. 4Disable any Paralives mods that touch lighting or props until the next update.
  5. 5On laptops: force the discrete GPU via Nvidia/AMD control panel (Paralives.exe → High-performance).
Best settings: every panel, screenshot by screenshot

Low FPS and lag FAQ

Does Paralives have a built-in FPS benchmark?
Yes. The BENCHMARKFPS cheat command measures performance, and CAPFPS 60 caps the framerate. Both run from the cheat console — Ctrl+F1 on Windows, Cmd+F1 on a Mac.
Which graphics settings matter most for FPS?
In order: shadow distance, real-time reflections, then resolution scale. Dropping scale to 90% typically returns 15-20% headroom with almost no visible difference — the best-settings guide walks every panel.
Why is the Mountain district slower than the rest of Melino?
Dense tree cover and long sightlines from elevation make it the heaviest district to render. It is the right place to stress-test your settings: if Mountain holds, the rest of town will too.
Can mods cause stuttering?
Yes. Mods that touch lighting or props are the usual suspects. Disable them entirely until the next update, then add them back one at a time so the culprit is identifiable.
Why does Paralives lag spike when a Para crosses a district boundary?
Crossing a boundary streams in a new prop set, and that burst shows up as a one-off lag spike. A 60 fps cap and 90% resolution scale give the spike headroom, which is why both sit high in the checklist. Spikes that hit mid-street, far from any boundary, are the acknowledged live-mode stutter instead.
Why is Paralives so laggy on my laptop after a while?
That curve is thermal throttling, not the game getting heavier. Cap the framerate at 60 and force the discrete GPU for Paralives.exe in the Nvidia or AMD control panel — if a fresh boot runs fine and it degrades over a session, heat is the cause.
Is there a lag fix, or a mod that removes lag?
There is no official lag-fix command — the console tools are CAPFPS, BENCHMARKFPS and FPS. Patch 0.1.8 reduced some stutter sources, and the studio says optimization continues. Steam Workshop has performance mods, but no lag claims from mods are verified here — browse the workshop hub and test one change at a time. Patch 0.1.9 (October 2026) moved the game to Unity 6 for up to 15% better framerates — the largest official performance change so far; it does not claim to fix stutter.

If it still happens

Run the in-game CAPFPS 60 cheat and the BENCHMARKFPS command, then share the result in the Paralives Discord performance channel.

Report on the Paralives Discord →

Paralives feels laggy or stutters?

“Laggy” and “low fps” are two descriptions of the same problem: fps is the measurement, lag is the feel — stutters, spikes, clicks that land late. Every step in the checklist above targets both, and shadow distance plus a 60 fps cap do the most for how the game feels. To tell which case is yours, open the cheat console (Ctrl+F1, Cmd+F1 on a Mac) and run FPS while the lag happens: a dropping number is a framerate problem; a steady number that still feels laggy is the officially acknowledged live-mode stutter.

What nobody can honestly promise you is a cause. Mods that touch lighting or props are the usual suspects and worth ruling out first, but beyond that no verified root-cause list exists for Paralives lag — not memory, not drivers, not any single setting. What is on the record: the studio lists live-mode stutter as a known issue and keeps optimizing (0.1.8's stutter-reduction pass is in the patch notes), while 0.1.8b shipped with no performance fixes. Watch the known-issues page for movement, and treat every “lag fix” mod claim as unverified until you have tested it yourself. Update (patch 0.1.9, 8 October 2026): the game now runs on the Unity 6 engine, which the studio says improves framerates by up to 15% — the stutter issue itself stays open on the tracker.

Related guides