WindowsLinux

Where Are Lil Gator Game Save Files Located?

Lil Gator Game splits storage: saves live in Steam userdata remote while settings sit in LocalLow MegaWobble plus registry.

Last updated

Lil Gator Game divides its footprint cleanly. Story progress lives in Steam userdata remote per account while settings and registry sit in LocalLow MegaWobble. Neither half substitutes for the other.

AppData hunters find options without progress and assume the worst. Copy userdata remote for the story and the Settings side for preferences. Filenames inside remote stay unlisted, so folder copies rule throughout.

Where Lil Gator Game stores this, by platform

Windows
<Steam-folder>\userdata\<user-id>\1586800\remote

Progress files per account ID for App ID 1586800 with unverified inner names. Copy whole with Steam closed. LocalLow holds settings only, never saves.

Windows
%USERPROFILE%\AppData\LocalLow\MegaWobble\Lil Gator Game\Settings

Options side with Settings plus registry keys under the studio path. Keep with userdata copies on migration. Store builds use their own clouds.

Linux
<SteamLibrary>/steamapps/compatdata/1586800/pfx/

Steam Play prefix for App ID 1586800. The userdata remote tree syncs through Cloud on Deck and Linux with settings read from the same relative layout.

Frequently asked questions

How do I back up Lil Gator Game?

Copy <Steam-folder>\userdata\<user-id>\1586800\remote with Steam closed for progress, plus the LocalLow MegaWobble Settings side for options. The two halves live apart by design, so one without the other restores half the game.

Where are the actual Lil Gator saves?

In userdata remote, not AppData. The LocalLow tree holds Settings plus registry only, which misleads folder hunters. Inner remote filenames stay unverified, so copy the remote folder whole.

Does the Xbox version share PC saves?

It uses Cloud on its own path while the local store build stays undocumented. DLC shares the base App ID tree rather than adding save roots. Keep PC and console progress separate.

Notice an outdated path? Let us know.