Install Project: Home!: platforms, saves & troubleshooting
A package-aware checklist for installation, first launch, backups and common problems.

Choose a trusted package
Use a source on the Project: Home! download page, then read that source’s release notes. Choose the correct OS and CPU architecture; an ARM build and an x64 build are not interchangeable. Stores may offer a different edition or price from the project download.
Windows
For a publisher installer, run the downloaded installer and follow its prompts. For a portable ZIP, extract the entire archive to a folder you can write to, then open the game executable there. Do not launch from inside the ZIP. If a security warning appears, verify the publisher, download origin and any published checksum; do not disable your protection just to proceed.
macOS
Select an Apple silicon or Intel package matching your Mac, or a universal build. Open the publisher’s DMG and copy the app to Applications if instructed; unpack ZIP downloads first. For an unsigned app warning, follow the publisher and Apple’s documented verification steps instead of bypassing security blindly.
Linux
Follow the publisher’s distribution-specific instructions. A package-manager install, AppImage and archive require different steps. Extract archives before launching. Only give executable permission to a verified application when its instructions require it. Check graphics drivers and runtime dependencies against the release notes.
First launch & controls
Start with the default settings, choose your language and adjust resolution, audio and input. Test a short session before changing mods or importing saves. If performance is uneven, reduce resolution and effects; review the minimum requirements before assuming the download is broken.
Save, back up & update
Save locations depend on the operating system and release. Find the path in the publisher’s documentation or in-game settings. Close the game and copy the complete save/configuration folder to a separate location before upgrading, reinstalling or adding mods. Keep a copy of the old version when its license and source permit it. Confirm save compatibility in release notes before opening old saves in a new version.
If something goes wrong
For an incomplete archive, download it again and compare a publisher checksum when offered. For a missing runtime, install it from its official provider. For launch failures, check OS/architecture, drivers and logs using the project’s support instructions. Multiplayer peers may need the same release and mods. Report a broken site link with its source name; send game-specific bugs to the publisher with the OS, game version and error text.