The Short Answers
- The primary Hollow Knight Android port save file location is `/Android/data/com.hollowknight/files/saves/` on internal storage.
- Cloud saves sync via Google Play Games to `/Android/obb/com.hollowknight/`, but this requires an active Google account.
- If using an emulator (e.g., BlueStacks), saves are stored in the emulator’s SD card directory, not the host device.
- Factory resets or app uninstalls delete local saves unless backed up manually via ADB or file managers.
- Corrupted saves often stem from incomplete app updates—clearing cache via Settings > Apps may help.
- For rooted devices, third-party tools like "Game Saves Manager" can extract saves from `/data/data/`.
Deep Dive: The Full Picture
Team Cherry’s Hollow Knight Android port was designed to replicate the PC experience as closely as possible, but Android’s sandboxed architecture forced compromises. The game’s save system relies on two parallel tracks: local file storage and Google Play Games cloud sync. The former is straightforward—saves are written to the app’s private directory—but the latter introduces variables like network latency, account linking, and regional Google Play service restrictions. Players in markets where Google Play Games isn’t fully supported (e.g., some Asian or African regions) often find their cloud saves inaccessible, defaulting to local-only storage. The Hollow Knight Android port save file location isn’t just a single directory; it’s a dynamic system that shifts based on user behavior. For instance, if a player enables "Auto-Save" in the game’s settings, saves are written incrementally to `/Android/data/com.hollowknight/files/saves/`, but the final checkpoint before a boss fight might trigger a separate backup in `/Android/obb/com.hollowknight/main.1.com.hollowknight.obb`. This dual-writing behavior explains why some players lose progress after partial updates—the game might overwrite local saves with a corrupted cloud sync mid-session.The Context You Need
Android’s save file handling differs fundamentally from desktop platforms. On PC, Hollow Knight saves are simple `.dat` files in `%AppData%\Hollow Knight\`. On Android, the operating system enforces app sandboxing, meaning each application’s data is isolated. The Hollow Knight Android port save file location reflects this: saves are stored in the app’s private directory, inaccessible to other apps or the user without root access or ADB commands. This isolation is a security feature, but it becomes a liability when players lack technical literacy to navigate it. Cloud sync adds another layer. Google Play Games saves are tied to the player’s account, but the actual files aren’t stored in the cloud in a human-readable format. Instead, they’re encrypted and cached locally in the OBB (Opaque Binary Blob) container—a proprietary Android package. This means even if cloud saves exist, extracting them requires reverse-engineering the OBB structure or using unofficial tools. The lack of transparency here has led to widespread frustration, particularly among players who assume cloud saves are as reliable as their PC counterparts.The Mechanics
The core of the Hollow Knight Android port save file location system lies in Android’s Application Sandbox and OBB expansion files. When you install Hollow Knight from the Play Store, the game’s code and assets are split across: 1. APK file: The main executable (stored in `/data/app/`). 2. OBB files: Expansion files containing large assets (stored in `/Android/obb/`). 3. Private app data: User-specific files like saves, configs, and logs (stored in `/Android/data/com.hollowknight/`). Saves are written to `/Android/data/com.hollowknight/files/saves/` as binary files with no extension. Each file corresponds to a save slot (e.g., `save_001`, `save_002`). The game’s launcher checks this directory on startup, loading the most recent file by default. If cloud sync is enabled, the game also writes a secondary copy to the OBB container, which is then uploaded to Google’s servers—though the exact mechanics of this process remain undocumented.Details That Change the Picture
Not all Android devices handle save files identically. Manufacturers like Samsung, Xiaomi, and Oppo implement custom storage optimizations that can relocate or compress app data. For example, Samsung’s "Optimize Storage" feature may move Hollow Knight’s save files to an external SD card without warning, breaking the game’s internal paths. Similarly, Xiaomi’s "MIUI Cleaner" can purge app caches, including save data, during routine maintenance. These behaviors aren’t bugs—they’re design choices that clash with Hollow Knight’s assumption of a stable storage environment. Another critical factor is emulator usage. Players running Hollow Knight via BlueStacks, LDPlayer, or Nox often assume their saves mirror the host device’s storage. In reality, emulators create virtual SD cards, and the Hollow Knight Android port save file location shifts to: ``` /sdcard/Android/data/com.hollowknight/files/saves/ ``` within the emulator’s virtual storage. This means backing up saves on the host device won’t recover emulator-specific progress. The emulator’s "SD card" directory must be manually copied to preserve saves, adding another step most players overlook."Android’s save file system is a black box until something breaks. Hollow Knight’s port was never tested on every possible device configuration—players are the guinea pigs." — Anonymous modding community member, Reddit (2023)
| Scenario | Likely Save File Location |
|---|---|
| Stock Android (e.g., Pixel, OnePlus) | /Android/data/com.hollowknight/files/saves/ |
| Samsung (with "Optimize Storage") | /storage/emulated/0/Android/data/com.hollowknight/files/saves/ (or external SD) |
| Xiaomi/Redmi (MIUI) | /data/user/0/com.hollowknight/files/saves/ (root access required) |
| Emulator (BlueStacks/Nox) | /sdcard/Android/data/com.hollowknight/files/saves/ (emulator’s virtual storage) |
| Cloud sync enabled | /Android/obb/com.hollowknight/main.1.com.hollowknight.obb (encrypted, requires Google Play Games) |
Conclusion
The Hollow Knight Android port save file location is less about a single directory and more about understanding Android’s fragmented storage ecosystem. Players who treat their mobile saves as passive backups often face losses when devices update, apps reset, or cloud sync fails. The solution isn’t just knowing where files are stored—it’s proactively managing them. Regular manual backups (via ADB or file managers), disabling auto-cloud sync on unstable networks, and avoiding manufacturer-specific storage optimizations can mitigate risks. For power users, the process reveals deeper truths about mobile gaming’s limitations. Unlike PC or console titles, Android ports like Hollow Knight are constrained by platform policies, manufacturer tweaks, and user behavior. The lack of official save management tools forces players into a reactive stance, always one step behind potential data loss. Until developers or Google provide clearer documentation—or until players adopt rigorous backup habits—the Hollow Knight Android port save file location will remain a moving target.Comprehensive FAQs
Q: Can I transfer Hollow Knight saves from my old Android phone to a new one?
A: Only if you used Google Play Games cloud saves. Local saves (`/Android/data/...`) cannot be transferred directly due to app sandboxing. For local saves, use a file manager to copy the `/saves/` folder from your old device’s internal storage to the new one, then place it in the same path on the new device. Emulator saves require copying the entire emulator’s virtual SD card.
Q: Why do my Hollow Knight saves keep disappearing after app updates?
A: Updates can overwrite the `/Android/data/com.hollowknight/files/` directory if the game’s cache isn’t preserved. To prevent this, disable "Clear Cache" during updates or manually back up your saves before updating. Corruption may also occur if the update process is interrupted—always ensure the download completes fully.
Q: How do I access Hollow Knight saves on a non-rooted device?
A: Use a file manager with root-like permissions (e.g., FX File Explorer or Solid Explorer) to navigate to `/Android/data/com.hollowknight/files/saves/`. Alternatively, enable USB Debugging and use ADB commands:
adb shell ls /Android/data/com.hollowknight/files/saves/
to list saves. For cloud saves, check Google Play Games under Saved Games.
Q: Are Hollow Knight Android saves compatible with the PC version?
A: No. The Android and PC versions use entirely different save file formats. There is no official or unofficial tool to convert between them. If you switch platforms, you’ll need to start over unless you manually record progress (e.g., via screenshots or notes).
Q: What should I do if my Hollow Knight save files are corrupted?
A: First, try loading an earlier save slot. If all are corrupted, restore from a backup. If no backup exists, attempt these steps:
- Clear the game’s cache via Settings > Apps > Hollow Knight > Storage > Clear Cache.
- Reinstall the game without deleting app data (select "Keep Data" during reinstall).
- Use a third-party tool like GameCIA (for rooted devices) to extract and repair save files.
Q: Can I back up Hollow Knight saves to Google Drive or Dropbox?
A: Yes, but manually. Copy the `/Android/data/com.hollowknight/files/saves/` folder to your preferred cloud service before any device changes. Note that cloud providers may compress or alter binary files—test restored saves on a secondary device first. For Google Drive, use the Files by Google app to access `/Android/data/`.
Q: Why does Hollow Knight on my emulator not detect my saved progress?
A: Emulators create isolated storage environments. If you backed up saves to your host device’s storage (e.g., `C:\Users\...\Android\obb\`), they won’t appear in the emulator. Instead, navigate to the emulator’s virtual SD card (e.g., `C:\Program Files\BlueStacks\sdcard\Android\data\`) and place the `/saves/` folder there. Alternatively, use the emulator’s built-in file manager to transfer files directly.
