Install
How to Install ChibiChu Mod
Windows or Android, the order is the same: back up, get the right file, install, then read the tutorial. Here is the version with the errors people actually hit.
Before you start
Three things, five minutes:
- Back up everything. In Gacha Life, export the characters you care about as PNG or PSD, copy them to Drive or a PC, and save your share codes.
- Check the space. Windows needs about 1 GB free after the download; on Android keep roughly 1.3 GB, because the installer unpacks on top of the file it just downloaded.
- Know the source. The Windows archive and the Android APK both come from the project's own pages. There is no ChibiChu build on Google Play or the App Store, and there is no iOS version at all.
ChibiChu Mode is a beta. The Android build is 0.1.0-rc1 and the Windows build is version 1.0, and a beta can change its save format between versions.
Windows: four steps
- Download the Windows archive from the project's download section. It is about 600 MB.
- Right-click the archive and extract it to a folder you can find again — for example
C:\\Games\\ChibiChu. Do not run it from inside the zip viewer; the game needs the files next to the executable. - Open the extracted folder and run
ChibiChu.exe. If Windows SmartScreen shows a warning about an unknown publisher, that is normal for a small fan project with no code-signing certificate — the file is unsigned, not necessarily unsafe. Choose the option to run it anyway, but only if the file came from the project's pages. - Let the game create its data folder on first run, then read the tutorial.
You need Windows 10 or 11 on a 64-bit system with a DirectX 11 graphics card. If the game opens to a black window, update your graphics driver first — that is the usual cause on integrated laptop GPUs.
Android: five steps
- On your phone, open the project's download page in the browser. Check that the build shows 0.1.0-rc1 and a size around 615.3 MB before tapping.
- Keep the screen awake until the download finishes. A dropped connection means starting the 615 MB over, so do it on Wi-Fi and leave the phone alone rather than switching apps mid-transfer.
- Allow installs from the browser you downloaded with. The path on most phones is Settings → Apps → Special access → Install unknown apps; on Android 8 and 9 the same switch sits under Settings → Security → Unknown sources instead.
- In your file manager, open Downloads, tap the APK, and wait. Progress stalls for a while while the resources unpack, and that gap is not a freeze. Expect a few minutes of unpacking on a mid-range phone before the first screen appears.
- Open the app. When the import tool asks for file access, allow it. Then go back and switch the unknown-sources permission off again — you do not need it day to day.
The APK needs Android 8.0 or newer. A separate OBB folder is not involved; it is a single file.
First launch: the Studio tools are not where you left them
That is the one thing worth knowing before you tap in. ChibiChu kept Gacha Life's screens but redrew and rearranged the controls, so years of muscle memory take you to the wrong place for the first few minutes. The background button is the one people cannot find again.
The tutorial is the shortcut, and it is skippable — a close arrow sits in the top corner. Skip it and the mod still runs; you will simply spend longer hunting. Read pages four to six even if you know Gacha Life well, because those are the pages that show where Studio keeps its tools now. The rest you can skim.
What you are looking at once the tutorial ends:
- The title screen carries the mod's own name and a BETA label, so you can tell at a glance that you opened the right app.
- The character stands in the centre of the screen.
- Down the right side is the Dress Up panel, split into eight tabs: Presets, Body, Hair, Face, Clothes, Other, Props, Profile.
- Down the left side are your character slots, the FPS counter, and the PNG, PSD and SVG export buttons.
- Along the bottom is the main navigation: Home, Studio, Options.
Everything you came for — poses, imported images, per-piece outlines — is in that right-hand panel. The custom poses guide takes over from there.
When the install goes wrong
Sorted by how often each one turns up. Every entry is three lines: what you see, what causes it, the shortest way out.
1. "App not installed", right at the end of the Android install. Cause: an older ChibiChu copy is still on the phone under a different signature, or the download stopped early and the file is short. Fix: uninstall every ChibiChu build, reboot, check the file size against the listing on the download page, install again.
2. The progress bar freezes just short of the end, then the install reports a failure. Cause: not enough free space to unpack the resources on top of the download. Fix: clear about 1.3 GB, delete the partial file, retry.
3. Windows: SmartScreen blocks ChibiChu.exe. Cause: the build is unsigned — a project this size has no code-signing certificate. Fix: confirm the file came from the project's own pages, then take the "run anyway" option. Never do this for a file from a mirror site.
4. Windows: there is no ChibiChu.exe in the folder you extracted. Cause: the archive was opened from inside the zip viewer instead of extracted, or it unzipped one level too deep, so the exe sits inside a nested folder beside its data files. Fix: extract the whole archive into an empty folder and look one level down before deciding the download is broken.
5. The app closes the moment Studio opens. Cause: memory pressure from imported assets — one heavy image is enough to take the scene down. Fix: close background apps, then remove the last few images you imported.
6. Imported images never appear in the resource library. Cause: file access was denied, or the file is a format the editor does not read — SVG and other vectors will not load as resources. Fix: grant the permission, convert the image to PNG or JPG, then force-stop and reopen the app so the library rebuilds.
7. A few Studio labels are still English or half translated. Cause: this is the release candidate, not a broken install. Strings change between builds. Fix: nothing to fix on your side. It will differ in the next build.
8. A new build refuses to install over the old one. Cause: the signing key changed between versions, so Android treats the two as different apps. Fix: export your characters as PNG or PSD and write down your share codes first, uninstall the old build, then install the new one. Same routine as below.
And the one that is not an error at all: a download called "ChibiChu mod menu" asking for contacts, storage or payment permissions is not ChibiChu. The mod has no menu to unlock and nothing to pay for — the download page explains how these packs borrow the name.
Updating later
There is no auto-update inside the app. Every build is a manual download, and installing one over the old one can fail on the signature mismatch in item 8, so keep the routine: export characters as PNG or PSD, copy down share codes, uninstall, install fresh. On Windows it is simpler — extract the new archive into a new folder rather than over the old one, and your old folder stays as a rollback.
Checked against the project's own listings in November 2026. Version numbers and file sizes move with each build — if something here disagrees with the project's page, the project is right and this page gets corrected.