Why does Paralives keep freezing?

Most freezes are memory pressure or an unstable framerate: cap the framerate at 60 fps, lower shadow distance, close background apps and keep the game on an SSD. If it only freezes when starting a new game or editing a Para, a Workshop mod is the usual suspect — disable all mods and re-enable in halves. Freeze reports have dropped with every patch since 0.1.2, so update first.

Paralives freezes for a few seconds, then unfreezes — is that a crash?

No. A freeze that recovers on its own is resource pressure or a mod hook, not a fatal error — the game never actually crashed. Run the same checklist (60 fps cap, lower shadows, close background apps, SSD), and know that the exact trigger of these micro-freezes is not officially documented.

Why does Paralives freeze when I open build mode?

A hard freeze on entering build mode is one of the crash-family symptoms tracked under the official crashes/freezes known issue — reduced with every patch since 0.1.2, not closed. Update to the latest build, then verify files, disable overlays and mods, and cap the framerate before re-opening build mode.

How do I unfreeze Paralives without losing my save?

Give a freeze 30 seconds first — many recover on their own. If it never comes back, force-quit and reload: since patch 0.1.5 the Load Game menu keeps the 3 last autosaves of each save, so a freeze rarely costs more than a few minutes. Quick-save with F5 before anything risky.

Where is my Paralives crash log?

Windows: C:/Users/[you]/AppData/LocalLow/Paralives/Paralives/Player.log — the path the studio's own repair guide gives. Mac: the studio doesn't publish one; as a Unity game Paralives follows Unity's standard macOS location, ~/Library/Logs/Paralives/Paralives/Player.log (engine convention, not official). Attach the log file itself to a Discord #bug-reports thread — the last lines before a crash usually name the cause.

Is Paralives crashing on startup caused by a mod?

Usually not. A crash before the main menu points first at drivers, a broken install, an admin/firewall block or an overlay — mods rarely get to load that early. Crashes when starting a new game or inside the Paramaker are the mod-typical ones: disable all Workshop mods, restart, and re-enable in halves. If a startup crash survives both the clean-mods pass and a file verification, it's an install or hardware problem, not custom content.

Save-safe fix

Fix Paralives crashing and freezing

If Paralives crashes on startup, freezes mid-session, or keeps freezing and unfreezing, work through this checklist in order. Save-safe — no console required.

Platform:: PC / Mac / Steam Deck
Last verified:: 2026-05-27

Symptoms

Crashing on startup — the game closes the moment you hit Play
Crash at launch before the studio splash or main menu appears
A Unity error dialog when launching
Crashes every time you start a new game
Keeps crashing — relaunch, crash, relaunch, crash
Hard freeze when opening build mode
Crash when saving from the main menu
Black screen after loading a household
Game freezes for a few seconds, then unfreezes on its own
Stuck on the loading screen after picking a save

Fix by when it crashes

Crashing on startup / at launch

A crash before the main menu is almost always drivers, a broken install, or an overlay injecting too early. Work in this order: update your GPU drivers; verify Steam files; run Paralives as administrator and allow it through your antivirus; disable Steam / Discord / MSI Afterburner overlays. On a Unity error at launch, delete the config folder so the game rebuilds it (see the checklist). Still crashing on startup after all that? Grab the crash log (below) and post it in Discord #bug-reports.

Crashing on a new game or in character creation (Paramaker)

If it only crashes when starting a new game or in character creation — editing a Para in the Paramaker — a Workshop mod or corrupt custom content is the usual cause. Disable all mods, restart, and reproduce; re-enable in halves to find the culprit. A fresh save without mods loading cleanly confirms it.

Stuck on the loading screen (no crash)

Four steps, in order. 1) Give it a few minutes — a slow first load can just be slow; the studio's repair guide doesn't prescribe a wait, but waiting costs nothing. 2) Disable every Workshop mod, restart and retry — mods that touch save data are the most common cause of a load that never finishes. 3) On a Mac, check the June 2026 save-path change: since the move, saves only load from ~/Library/Application Support/com.Paralives.Paralives. 4) If the bar hasn't moved for several minutes, stop waiting — force-quit (Alt+F4) and treat it as a save problem, not a crash: the recovery path lives on our save-stuck page.

Where is the crash log?

On Windows, Paralives writes its log to C:/Users/[you]/AppData/LocalLow/Paralives/Paralives/Player.log — the exact path the studio's own repair guide gives. Open it in a text editor and read the last lines before the crash. On macOS the studio doesn't publish a path; as a Unity game Paralives follows Unity's standard location, ~/Library/Logs/Paralives/Paralives/Player.log — likely correct, but treat it as engine convention, not an official path.

Freezing or crashing mid-session

Mid-game hard freezes point at memory pressure or an unstable framerate. Cap the framerate at 60 fps, lower shadow distance, close background apps to free RAM, and keep the game on an SSD. Autosave often so a freeze never costs a household.

Back up your save first

Before any deep fix, duplicate your save from the load-game menu (or copy the whole .saved folder out of MySavedGames.mod). Startup crash loops and Unity errors can touch save data, so a backup means a bad fix never loses your family.

Keeps freezing, then unfreezes (no crash)

A freeze that recovers after a few seconds is resource pressure, not a fatal error — the same causes as mid-session freezes: uncapped framerate, high shadow distance, background apps eating RAM, or a hard drive instead of an SSD. The studio has never documented a specific trigger for these periodic micro-freezes, so treat the checklist as the fix and autosave often.

Try in order

1Verify Steam files: Steam → right-click Paralives → Properties → Installed Files → Verify integrity. Fixes most startup crashes.
2Update GPU drivers. Nvidia: GeForce Experience; AMD: Adrenalin; Intel Arc: Driver Assistant.
3Run Paralives as administrator and allow it through your firewall / antivirus — a common cause of crash-on-launch.
4For a Unity error on startup, delete the config folder at C:/Users/[you]/AppData/LocalLow/Paralives/Paralives so the game regenerates clean settings — but keep the MySavedGames.mod subfolder, that's where your saves live.
5Disable all Workshop mods, restart, reproduce. If stable, re-enable in halves to bisect the bad mod (fixes new-game and Paramaker crashes).
6Turn off Steam overlay (Settings → In-Game → uncheck 'Enable the Steam overlay while in-game') and any Discord/Afterburner overlay.
7Cap framerate at 60 fps in Paralives graphics settings; uncap can crash on older drivers.

The loading screen hangs with a save selected? That's the save-recovery path →

Crashing & freezing FAQ

Why does Paralives keep freezing?: Most freezes are memory pressure or an unstable framerate: cap the framerate at 60 fps, lower shadow distance, close background apps and keep the game on an SSD. If it only freezes when starting a new game or editing a Para, a Workshop mod is the usual suspect — disable all mods and re-enable in halves. Freeze reports have dropped with every patch since 0.1.2, so update first.
Paralives freezes for a few seconds, then unfreezes — is that a crash?: No. A freeze that recovers on its own is resource pressure or a mod hook, not a fatal error — the game never actually crashed. Run the same checklist (60 fps cap, lower shadows, close background apps, SSD), and know that the exact trigger of these micro-freezes is not officially documented.
Why does Paralives freeze when I open build mode?: A hard freeze on entering build mode is one of the crash-family symptoms tracked under the official crashes/freezes known issue — reduced with every patch since 0.1.2, not closed. Update to the latest build, then verify files, disable overlays and mods, and cap the framerate before re-opening build mode.
How do I unfreeze Paralives without losing my save?: Give a freeze 30 seconds first — many recover on their own. If it never comes back, force-quit and reload: since patch 0.1.5 the Load Game menu keeps the 3 last autosaves of each save, so a freeze rarely costs more than a few minutes. Quick-save with F5 before anything risky.
Where is my Paralives crash log?: Windows: C:/Users/[you]/AppData/LocalLow/Paralives/Paralives/Player.log — the path the studio's own repair guide gives. Mac: the studio doesn't publish one; as a Unity game Paralives follows Unity's standard macOS location, ~/Library/Logs/Paralives/Paralives/Player.log (engine convention, not official). Attach the log file itself to a Discord #bug-reports thread — the last lines before a crash usually name the cause.
Is Paralives crashing on startup caused by a mod?: Usually not. A crash before the main menu points first at drivers, a broken install, an admin/firewall block or an overlay — mods rarely get to load that early. Crashes when starting a new game or inside the Paramaker are the mod-typical ones: disable all Workshop mods, restart, and re-enable in halves. If a startup crash survives both the clean-mods pass and a file verification, it's an install or hardware problem, not custom content.

If it still happens

Collect the crash log — C:/Users/[you]/AppData/LocalLow/Paralives/Paralives/Player.log on Windows, or ~/Library/Logs/Paralives/Paralives/Player.log on Mac (Unity's standard location, not officially published) — and attach it to a Discord #bug-reports thread.

Report on the Paralives Discord →