OmniSave
github.com
Spec sheet
- Purpose
- OmniSave is a portable game save synchronization tool that redirects saves between a portable location and the system path a game expects.Read 10 Oct 2026 · github.com
- Audience
- The maker describes the tool as intended to let users carry a gaming session in one folder or drive across machines without manual save management.Read 9 Oct 2026 · github.com
- Integrations
- Documented compatibility includes CrossOver, Wine, GameHub, Winlator, and Box64.Read 9 Oct 2026 · github.com
- Support
- The repository page includes a “Support This Project” section but does not state a support service or response commitment.Read 9 Oct 2026 · github.com
- Compatibility
- The maker says it is designed for Windows and tested on Windows 10, macOS through CrossOver and Wine, and Android through GameHub with Winlator/Box64.Read 10 Oct 2026 · github.com
- Game monitoring
- Process polling lets OmniSave keep running when a game launcher detaches or spawns background child processes.Read 9 Oct 2026 · github.com
- Instance protection
- Mutex locking prevents multiple OmniSave instances from running at the same time to avoid save corruption.Read 9 Oct 2026 · github.com
- Intended use
- The maker says OmniSave is inspired by PortableApps and is intended to let users carry a game session’s saves between machines in one folder or drive.Read 10 Oct 2026 · github.com
- Launch options
- Its configuration supports arbitrary game launch arguments, including flags such as -nobattleye and -windowed.Read 10 Oct 2026 · github.com
- Linux support
- Native Linux and Steam Deck support with Proton prefix detection is listed as roadmap work.Read 10 Oct 2026 · github.com
- Notable limit
- Native Linux and Steam Deck support with Proton prefix detection is listed on the roadmap.Read 9 Oct 2026 · github.com
- Path configuration
- Configured paths support ~/ expansion for user profile directories and ./ for relative portable paths.Read 10 Oct 2026 · github.com
- Path support
- Configuration paths support ~/ expansion for user profile directories and ./ for relative portable paths.Read 9 Oct 2026 · github.com
- Portable storage
- Save data can live on a portable drive or in a cloud-synced folder while the game uses its expected local save path.Read 9 Oct 2026 · github.com
- Process monitoring
- OmniSave polls the process list so it can remain active when a game launcher detaches or starts child processes.Read 10 Oct 2026 · github.com
- Safety
- Version 0.2.0 changelog lists atomic file writes via temporary .omnitmp files and propagation of local save deletions to the remote path.Read 9 Oct 2026 · github.com
- Security and compliance
- The repository identifies the project as MIT licensed and does not state a security certification or compliance standard.Read 9 Oct 2026 · github.com
- Security and warranty
- The repository provides an MIT license that grants use, copying, modification, and distribution rights and supplies the software without warranty.Read 10 Oct 2026 · github.com
- Single-instance safeguard
- Mutex locking prevents multiple OmniSave instances from running at the same time to avoid save corruption.Read 10 Oct 2026 · github.com
- Storage
- The project describes portable drives and cloud-synced folders as possible locations for save data.Read 10 Oct 2026 · github.com
- Sync behavior
- Version 0.2.0 added atomic file writes and propagation of local save deletions to the remote path during post-sync.Read 10 Oct 2026 · github.com
- Workflow
- It syncs saves before launching a game, monitors the game process, then syncs saves back after the process exits.Read 10 Oct 2026 · github.com
Where Specifiction places it
- Game Save Managers#20 of 277.3