Table of Contents
- What a Launcher Means Here
- The Browser Client Is Your Real Launcher
- Desktop Wrappers and Local Copies
- Setup Walkthrough
- Playing Offline
- Managing Several Versions
- Black Screen, Low FPS and Other Failures
- FAQ
What a Launcher Means Here
If you search for an Eaglercraft launcher expecting a program with a version dropdown and an install button, you will spend a lot of time on sites that are either advertising or outright malicious. The honest answer is that the project has no official launcher, because it does not need one. The browser is the launcher.
That is not a technicality. A launcher exists to solve problems that only desktop Minecraft has: picking a Java runtime, allocating memory, downloading and verifying the game jar, managing profile folders, injecting mods at the right moment. In a browser client, all of that is either baked into the page or handled by the browser itself. The client is a self-contained HTML file plus an asset pack. Opening it is launching it.
The Browser Client Is Your Real Launcher
Everything the launcher would do happens at load time, in this order:
- The page loads. A few hundred kilobytes of HTML, CSS and loader script.
- The asset pack is fetched. Tens of megabytes of textures, sounds and language files, cached by the browser so later visits skip it.
- The game module is prepared. The compiled JavaScript or WebAssembly is parsed and started. On slow machines this is the pause you see on the loading bar.
Understanding that sequence explains almost every symptom later. A black screen is the third step failing. A slow first launch is the second step. None of it is a launcher bug, because there is no launcher.
Desktop Wrappers and Local Copies
Two legitimate ways exist to run the client outside a normal tab.
A local copy. Save the client HTML and its asset pack into one folder and open the HTML file in your browser. That is it. You now have a permanent, offline-capable, version-pinned installation that no takedown, dead mirror or school filter can take away from you. If you also want it reachable from other devices, serving that folder as a static site is straightforward, and the file is exactly the kind of page you can generate or hand-edit, as covered in our guide to running Eaglercraft from HTML .
A browser-based wrapper. Progressive web app style shortcuts, kiosk mode, or a separate browser profile dedicated to the game. This gets you a window with no address bar, a dedicated cache that will not be wiped when you clear your main browsing data, and a desktop icon that behaves like an app. On Chromium browsers you can install a page as a shortcut, and adding a dedicated profile means your game cache survives routine cleanups.
What you should not do is run any .exe or .dmg that claims to be a launcher for this game. Those do not come from the project, they cannot, and giving an unknown binary full access to your machine is a terrible trade for saving one click.
Setup Walkthrough
- Pick your version. 1.8.8 for multiplayer and performance, 1.12.2 for newer content. The 1.8.8 guide and the 1.12.2 guide cover the trade-offs.
- Get the matched pair. One client file, one asset pack from the same source. Mismatched assets are the top cause of a client that loads and then dies.
- Put them in their own folder. Name it after the version, for example eaglercraft-1-8-8. Keep each version in its own folder so nothing overwrites anything else.
- Open the client and let it finish. Do not refresh. Walk away for a minute on the first run.
- Configure before playing. Render distance to 6 to 8, fancy graphics off on weak hardware. Set your controls now rather than mid-game.
- Make a shortcut. Bookmark it, or pin it as an app. This is your launcher entry.
- Back up your world. Use the client's export option if it has one, and note that clearing site data destroys your saves.
Playing Offline
Offline play is the strongest argument for keeping a local copy, and on a plane, in a car or behind a strict school filter it is the only thing that works. The requirements are simple:
- The client HTML and the asset pack must both be local, in the same folder, with the file path the client expects.
- You must have loaded it once successfully with a connection, so the browser has cached anything it fetches lazily.
If the client shows a loading bar that never moves while offline, check the browser console: it is almost always one asset request going to a remote URL instead of the local pack.
Managing Several Versions
| Approach | Good for | Weakness |
|---|---|---|
| One folder per version, opened by file path | Clean separation, offline, easy backups | You manage the list yourself |
| Self-hosted static page per version | Playing from several devices on a home network | Needs a machine running |
| Dedicated browser profile per version | Isolated caches, survives cleaning the main profile | More profiles to keep updated |
| Hosted client pages | Trying a version without downloading anything | Depends on someone else staying online |
Whichever you pick, write down the version and build of each client next to the folder. Six months later, when a server rejects you with a meaningless error, knowing that your 1.8.8 client is an older revision than the one the server expects is the difference between a two-minute fix and an hour of guessing.
Black Screen, Low FPS and Other Failures
Black screen after the loading bar
Almost always WebGL. Check that hardware acceleration is enabled in the browser, that your browser is not forcing software rendering, and that the graphics driver is not blocking WebGL for the page. The second most common cause is a mismatched asset pack. The third is an outdated browser that cannot run the compiled game module, so update first and debug second.
Low frame rate
- Render distance down to 6 chunks, then 4 if needed. This is the biggest single win.
- Fancy graphics, smooth lighting and heavy particles off.
- Close other tabs, especially video and design tools that compete for the GPU.
- Cap the frame rate. An uncapped tab wastes GPU budget rendering frames nobody sees.
- Use a newer build of the client. Later revisions are genuinely faster.
For connection problems specifically, the symptoms and their causes are catalogued in our guide to Eaglercraft servers , because a failed join is a network problem rather than a client one. If you are setting this up on a phone, the mobile guide covers the extra obstacles.
FAQ
Is there an official Eaglercraft launcher?
No. There is no official launcher, no official installer and no official desktop app. Any download presented as one comes from a third party, and there is no reason to trust it with access to your machine.
Can I play without internet?
Yes, with a local copy of the client and its asset pack, provided you have loaded it once while online. Singleplayer then works fully offline. Multiplayer does not.
Where are my worlds saved?
In the browser's own storage for the page, not in a folder you can browse. Clear your browsing data and they are gone, which is why exporting worlds you care about is worth the two minutes it takes.
Why did the game work yesterday and not today?
Common causes in order: a client page that was taken down, a browser update that changed WebGL behaviour, a cache that was cleared and now has to re-download assets, or a server that is simply offline. Test with a local copy to rule out the first two immediately.
Can I run several clients at once?
You can, but each tab is a full game instance competing for the same memory and GPU. Two tabs on a strong machine is fine. On a laptop, one at a time is the realistic limit.