Where Does Winlator Store Containers and Saves?
Winlator keeps Windows containers as directories under its internal home folder, sideloaded outside the Play Store.
Last updated
Winlator stores each container as a directory with its own Wine prefix and virtual C: drive. Container configs save as JSON files inside their root folders. Games install into those prefixes like on a real PC.
Direct file access needs root on most builds, so manage containers through the app UI. The D: drive mapping is the practical bridge for getting installers in and saves out without root.
Where Winlator stores this, by platform
/data/data/com.winlator/files/imagefs/home/xuser-{id} (root needed)
Sideloaded APK with containers under its internal home folder. Each container holds a Wine prefix plus config JSON. Back up container dirs; direct access needs root.
Frequently asked questions
How do I back up Winlator containers?
Back up the container directories from internal storage, since game installs and saves live inside them. Reinstalling Winlator without that backup loses every container. Copy the folders back before launching.
Where do I put games for Winlator?
Put installers in shared storage and map it as the D: drive. Containers read it as a normal Windows drive. Internal UFS storage beats SD cards for texture streaming stutter.
Notice an outdated path? Let us know.