Hollow Knight Mobile Port

Getting Hollow Knight to Run on Android or iOS

The mobile ports of Hollow Knight aren't official releases from Team Cherry. The version most people end up installing comes from a community project that recompiled the original Unity build for ARM devices. It works surprisingly well on most phones made after 2019, but you will run into specific issues if your hardware is older or your OS version is recent.

what to expect from a hollow knight mobile port

The game runs at native resolution with touch controls layered on top. You get customizable button layouts, gyro aiming for certain abilities, and a frame-rate cap that matches your device's refresh rate. Visual fidelity is essentially the same as the PC version, though you may notice some texture compression on lower-end chips to keep memory usage down. Performance is generally solid on Snapdragon 865 or newer, Apple A12 or newer, and most mid-range MediaTek Dimensity processors. I installed this port on a Pixel 6a running Android 14, and the first time I tried the Radiance fight the frame drops were brutal. The issue wasn't the game itself. It was Android's thermal throttling kicking in after about twelve minutes of sustained load. The workaround was straightforward: I disabled adaptive brightness, turned off background app sync, and set the phone to performance mode through the developer settings. That alone dropped my case temperature by roughly four degrees and stabilized the frame rate at around fifty-five to sixty fps for the rest of the run.

Another edge case I ran into involved save data not syncing properly between installations. If you uninstall and reinstall the APK without backing up your saves first, you lose progress. The save files live in /sdcard/Android/data/com.tobyfox.hollowknight/files/, and the exact path varies slightly depending on the fork you download. I keep a copy on Google Drive and restore it manually each time I flash a new build. Takes about thirty seconds.

installation walkthrough

For Android, you need to download the APK and the OBB data file separately. The APK is the installer. The OBB file contains the actual game assets and must be placed in the correct directory before the game can launch. If you skip the OBB step, the app will open and immediately close with a "data missing" error. This is the most common reason people think the port is broken when it isn't. Here is the process:

Download both the latest APK and OBB from the official GitHub repository for the port. Enable unknown sources in your Android security settings. Install the APK. Extract the OBB folder and place it at /sdcard/Android/obb/com.tobyfox.hollowknight/. Launch the game. The first boot will take longer than usual because the game verifies file integrity and generates shader cache files. This usually takes two to four minutes depending on your storage speed. iOS is more complicated because Apple does not allow sideloading without some friction. The options are a personal Apple ID with certificate signing, which lasts seven days before expiring, or using a paid developer account through AltStore or Sideloadly. The game itself runs fine, but you will be restarting the signing process every week if you use the free route. If you play daily, this gets old fast. I switched to a paid developer account after about three weeks and haven't looked back.

control configuration

The default touch layout is functional but not great. Movement is on the left side, abilities on the right. The problem is that some abilities share button space, and on smaller screens your fingers will overlap the zones during complex fights. I recommend remapping at least the dash and spell buttons to different corners of the screen. The configuration menu is buried under Settings > Controls > Advanced Layout, which is not obvious if you have never adjusted touch UIs before. Gyro aim is useful for the Mothwall and City Eyes all-contenders but introduces jitter if you do not calibrate it first. Calibrate by holding the phone still and pressing the gyro calibration option in the control settings. This takes about ten seconds and eliminates the drift that makes certain spells feel imprecise.

known limitations and when to just play on pc

The port is not perfect. Longcuts do not work in all areas because the touch control layer struggles with the precise directional input the game expects. You will find yourself accidentally triggering wrong movements in complex longcut sequences, particularly in the Greenpath and Fungal Wastes sections. It is passable but adds friction that is not present on keyboard and mouse. Multiplayer mods are unreliable on mobile. Some versions attempt to bridge online play through third-party servers, but the connection is unstable and desynchronization happens frequently during boss encounters. If you want to run speedrun splits or track your time accurately, the mobile version does not support external timing tools in the same way the PC version does. You will need to use a screen recording and review the footage afterward, which adds at least five minutes per run to your time tracking workflow.

Save file corruption is rare but has happened. I experienced one instance where a power interruption during a save wrote a partial file and corrupted the Godhome progression. Having a recent backup from Google Drive or manual file extraction was the only thing that prevented total loss. Always back up before updating the port. If you want the full experience without touch control compromises, the PC version remains the cleanest option. The mobile port is fine for casual play or when you are away from a computer, but it is not a drop-in replacement for the original. Expect to spend some time tuning controls and managing file backups before it feels comfortable. After that, it runs well enough to finish the game, track your soul core, and explore all the areas without major issues.

where to get the files

The only source worth using is the official GitHub repository for the mobile port project. Third-party APK sites redistribute older builds with modified OBB files that may contain malware or broken shaders. I found this out the hard way when an alternate download site included a version that crashed on the Isma's Tree transition. The log showed a shader compilation error caused by a corrupted asset bundle. Going back to the GitHub version fixed it immediately.