栞Galdrive · Save backup and multi-device synchronisation
Continue on another PC with the progress you choose to keep.
- Desktop appNot applicable
- WebsiteNot applicable
On this page
Project overview · GalShelf · Galdex · Galguard
Galdrive is a separate tool for game saves: backup, version history, synchronisation, conflicts and restoration. It is not storage for entire games and does not replace GalShelf's metadata, library management or play records.
Status: core development is substantially complete; a standalone download is not available yet. Real-account, release-environment and cross-application availability follows the relevant acceptance and release notes. GalShelf 0.2.6 retains its existing cloud saves without requiring the separate application.
Organise saves by work#
Backups should not be an unrecognisable collection of folders. The workflow uses work identity, save location and backup version so players know which progress a backup represents and which files a restore will affect.
Interoperation with GalShelf uses VNDB work IDs. Renaming a folder should not invent another work, but editions, translations and patches still require save-compatibility checks.
Upload, synchronise and restore#
Upload backup saves this device's progress, without downloading over local saves first or forcing older progress over a newer remote branch.
Synchronisation compares content and version relationships, processing differences when the direction is clear. Identical content should not duplicate backups merely because it comes from another PC; divergent progress requires conflict handling.
Download and restore selects a specific version and checks its destination and compatibility. Reading status is separate from writing and must not quietly replace local saves.
History and multi-device conflicts#
Two PCs played offline can both hold progress worth preserving. Keep the divergent versions and let the player choose instead of deciding solely from device clocks or modification times.
Version history supports recovery and mistakes. A new backup must not sacrifice the only usable copy before it has safely completed.
Restoration protection#
Restoration checks whether the game is using the saves, whether the directory is correct, whether the content is complete and whether the result can be confirmed. Retain a safety copy of local progress being replaced and use restoration and rollback handling for interruption or failure.
Identity evidence and save-location proposals do not replace authorisation, safety conditions or compatibility checks.
Current storage backends#
| Backend | Usage | Important distinction |
|---|---|---|
| Local directory / sync folder | Write to a chosen directory, optionally transferred by the user's sync client | A completed local write does not prove an external cloud upload has finished |
| OneDrive | Connect directly to user-authorised cloud storage | Requires app registration, account authorisation and connectivity; implementation and public availability are separate |
| Google Drive | Connect directly to user-authorised cloud storage | Also depends on registration, authorisation and network access; actual availability follows release notes |
WebDAV, additional mainland-China drives, S3-compatible storage and officially hosted storage are not listed as supported here. This page does not offer hosted storage space.
Component relationships#
GalShelf handles the library, metadata and playing experience. Its existing cloud saves and independent Galdrive are related but distinct; one release's features or interface should not be presented as another's guarantee.
Galdex supplies verified identity and save rules. The save workflow still decides applicability, compatibility and write scope against actual local files.
Galguard handles file safety and integrity. A successful identity match or a sync request must not bypass a security finding. Shared state and file-use coordination depend on integration acceptance for the relevant versions.
Galdrive focuses on saves, not automatically uploading executables, entire games or arbitrary personal folders. Users choose storage; capacity, traffic and account rules depend on the backend. Standalone release notes on the release page (external link) will identify compatible versions and usable connection methods when downloads open.