Use release tags and asset details to verify what you install.
Downloads →Find your way
around the Void.
Practical guidance for using the website, checking builds, working with browser tools, and understanding what the current project does — and does not — do yet.
Understand Social Hub beta accounts and current safety limits.
Social Hub →See how catalog availability and ownership are represented.
Feature Store →Launchers, builds and compatibility.
Use verified repository releases as the source of truth for installable launcher builds. A website concept or roadmap entry is not a release artifact.
Where to find a build
Open the downloads page and follow the official GitHub Releases link. Confirm the release tag, file name and release notes before installing.
Open downloads →When a build won't install
Check the device's Android version, free storage, APK integrity and Android's install permission for the file source. Never ignore an Android package warning solely to test a preview.
Crashes and logs
Record the launcher build, Android version, Minecraft version, renderer and the first relevant error. Remove private tokens or account data before sharing logs publicly.
Find support options →Sign in and profile basics.
Your username is part of your website profile. Keep it distinct from your Microsoft, Xbox and Minecraft credentials.
Create an account
Open Sign in, choose Create account, enter a username, email and a strong unique password, then submit. The site should show an error if the account service cannot complete the request.
Open account sign-in →Review your profile
The profile page checks the active website session and shows account information returned by the server. Your website role grants no permissions on GitHub, Cloudflare, Microsoft or Minecraft.
Open profile →Password recovery
Recovery depends on email delivery being configured and verified. If the flow reports the service is unavailable, no recovery code has been sent or verified; don't trust anyone asking you to reveal your current password.
Password recovery →Understand listings before using them.
Check the status chip, compatibility, source information and package availability on each listing. A card in the catalog does not mean a feature is installed in the launcher.
Preview: concept or metadata only, not an installable release. Available: a release package exists and the listing is public. Paid purchases additionally require secure checkout and server-confirmed ownership.
What local tools can do.
Some pages work inside this browser without installing an Android package. Their data and controls do not automatically alter Minecraft's game files.
Advanced Mod Manager
Imports and organizes JARs in this browser's local IndexedDB library. Export a file to move it elsewhere; browser clearing or site-data cleanup may erase the library. It does not directly write into launcher-private storage.
Open Mod Manager →Theme Studio
Changes the website's colors using browser-local preferences. It does not change in-game textures, shaders, resource packs or Minecraft settings.
Open Theme Studio →Server State
Check server status on demand. A status request sends the server address to the public mcsrvstat.us service. Saved server addresses remain in this browser.
Open server tools →Ownership, payment and equip are separate steps.
Only server-confirmed purchase entitlements unlock the Equip button. The current Equip option applies to the Creeper Launcher website profile only.
A few good habits matter.
Be cautious with downloads, account links and files from unknown creators.
Use unique passwords
Never reuse your email or Microsoft password for a beta service. Creeper Launcher staff will never need your current password or one-time code.
Check files and licences
Review the source, licence, compatibility and publisher of a mod or community submission. A listing being published does not mean the package was automatically scanned or signed.
Report a problem
Share the affected page, steps to reproduce and a redacted error message. Never include passwords, session tokens or private messages in a public bug report.
Support and reports →
A browser chat beta.
Social Hub supports friend requests and private messages between accepted friends in its current staging service.
Beta account is separate
Website sign-in and Social Hub login currently use separate authentication systems. Matching branding does not merge credentials. Use a unique password in each service.
Safety and privacy limits
Email verification, password recovery, push notifications and end-to-end encryption are not implemented in the beta. Avoid sending personal or sensitive information in messages.
Use the safety tools
Available beta controls include removing a friend, blocking a user and submitting a report. The service is still staging software, not a production security guarantee.
Go to Chat & Friends →