Template Center

Pick a template by SDK and game shape.

One-save first, slots next, account restore after that. These templates keep examples account-first and facade-first so game code does not start from raw runtime endpoints.

JavaScriptUnityGodotstatic docs

JavaScript templates Unity templates Godot templates

SDK

Choose the SDK you are integrating.

Each SDK page includes one-save, multi-slot, and account restore variants with copyable starter code.

JavaScript

Browser games, Vite apps, and JavaScript engine wrappers using @persistlyapp/sdk.

Open JS templates Unity

Unity games using PersistlyGameSaves and engine-friendly async save helpers.

Open Unity templates Godot

Godot games using the Persistly addon facade and GDScript examples.

Open Godot templates

Game Shape

Start with the smallest save shape that fits.

The templates are ordered from easiest to most explicit: one current save, named slots, then signed-in account restore.

One Save

Use saveData, SaveDataAsync, or save_data for a single current save.

See example Multiple Slots

Use stable slot ids for manual saves, campaigns, or character selection.

See example Account + Slots

Restore known accounts with explicit account sessions from your own trusted account system.

See example

One Save: start here for idle, casual, prototype, and small single-save games.

Multiple Slots: use this when players choose saves, campaigns, characters, or manual slots.

Account + Slots: add this when your own sign-in system restores a Persistly account session across devices.

Rules

These templates keep beginner integrations on the public facade.

Keep normal game code on the PersistlyGameSaves facade.

Write local save data first, then sync from deliberate lifecycle or gameplay moments.

Export account sessions only when your trusted account system needs cross-device restore.