eclipseemu.me

Eclipse runs games from seven classic systems — Game Boy, Game Boy Color, Game Boy Advance, NES, SNES, Sega Master System, and Sega Game Gear — on almost any device with a modern web browser. There is no hardware requirement beyond the browser itself, which is why the site notes it can't be revoked on iOS. More systems are planned, but none are confirmed yet.

Supported Game Systems

Eclipse currently plays titles from these platforms:

That covers the handheld Nintendo line from the original Game Boy through the GBA, the two main Nintendo home consoles of the 8- and 16-bit eras, and Sega's 8-bit home and handheld systems. Notably absent are later systems such as Nintendo 64, PlayStation, or Sega Genesis.

The site says additional systems are planned "as soon as possible," but it does not name them or give a timeline. Treat any specific future platform as unconfirmed until it appears on the site.

Device Requirements

The requirement is a modern web browser, not a particular piece of hardware. Because everything runs in the browser, the same library works across desktop and mobile devices without installing a separate app per platform.

• iOS and iPadOS: The site specifically calls out that Eclipse is web-based and therefore "can never be revoked on iOS" — a reference to the common problem of sideloaded emulator apps losing their signing certificate. Running in the browser sidesteps that entirely.
• Offline play: Supported, but only with games loaded from your local files. Games added to your Library from cloud sources require a connection.
• Controller support: Based on the JavaScript Gamepad API. A controller that the API or your operating system doesn't recognize will not work in Eclipse, regardless of the emulator's own settings.

Getting Games Into Eclipse

How you load a game affects whether it lands in your Library:

• Library games can be added from Google Drive, Dropbox, or the site's selection of Homebrew titles. These persist in your library so you can jump back into a game quickly.
• Local files can be loaded directly, but per the site, a ROM loaded this way "will not add to your Library." This is the route to use for offline play.
• Save files can be managed for any game, whether or not it's in your Library.

Input Methods

Eclipse supports touch, keyboard, and controller input, and default bindings can be edited in settings. If a controller isn't detected, check whether your OS and browser expose it through the Gamepad API before assuming the emulator is at fault — that dependency is the most common reason a working controller goes unrecognized.

What This Means for You

If your game is from one of the seven listed systems and you have a current browser, Eclipse should run it. If you're on iOS and want to avoid revoke issues, the browser-based approach is the main draw. If you need a system outside the list — Genesis, N64, or anything disc-based — Eclipse doesn't cover it today, and the site gives no date for when it might.

Eclipse lets you add games to your Library from Google Drive, Dropbox, or its homebrew selection, or load a ROM directly from local files without adding it to the Library. Save files can be managed for any game, whether or not it is in your Library. Offline play works only with local files, not with Library games.

Adding Games to Your Library

The Library is Eclipse's persistent game list, letting you jump back into a game quickly. You can add games from three sources:

• Google Drive — connect and pick games stored in your Drive.
• Dropbox — same idea, using files stored in Dropbox.
• Homebrew selection — choose from the homebrew games Eclipse offers directly.

Games added this way stay in your Library for later sessions.

Loading a ROM Without Adding It

You can also load a ROM directly from your local files. The trade-off is explicit: a locally loaded ROM will not be added to your Library. Use this route when you want to play a one-off file or need offline play (see below).

Managing Save Files

Eclipse lets you manage save files for games whether or not they are in your Library. That means a game you loaded from local files still gets save management — you are not locked out of saves just because you skipped the Library.

Playing Offline

Offline play is possible, but only through local files. If you are offline, load games from your local files instead of the Library. Library games depend on their source (Drive, Dropbox, or the homebrew selection), so plan ahead if you expect to be without a connection.

Supported Systems and Inputs

Eclipse supports Game Boy, Game Boy Color, Game Boy Advance, Nintendo Entertainment System, Super Nintendo, Sega Master System, and Sega Game Gear. More systems are planned.

For controls, Eclipse supports touch, keyboard, and controller input, and default bindings can be edited in settings. Controller support relies on the JavaScript Gamepad API — if your controller is not supported by that API or your OS, it will not be recognized.

Quick Reference

Common Snags

• Game missing from Library after loading — expected if you loaded it from local files; only Drive, Dropbox, and homebrew additions populate the Library.
• Controller not detected — check whether the JavaScript Gamepad API or your OS supports it; unsupported controllers will not be recognized.
• Offline play fails — switch to local files; Library sources require a connection.

Eclipse is a browser-based emulator that runs Game Boy, Game Boy Color, Game Boy Advance, NES, SNES, Sega Master System, and Sega Game Gear games on any device with a modern web browser. You don't install a native app: you open the site and play in the browser, which means iOS and iPadOS users avoid the app-revocation problem that affects sideloaded emulators. The trade-off is that you supply your own game files, either from cloud storage, the site's homebrew selection, or your device's local files.

What Eclipse actually is

Eclipse is a web app, not a downloadable emulator package. Its own description frames the core benefit plainly: it runs on "almost any device that has access to a modern web browser," and on iOS or iPadOS it "can never be revoked."

That distinction matters if you've dealt with emulators on iPhone before. Sideloaded apps depend on signing certificates that Apple can invalidate, which kills the app until you re-sign it. A browser-based emulator sidesteps that entirely because there's no installed app to revoke.

Supported systems

Eclipse lists seven supported platforms:

The site says more systems are planned, but only these seven are confirmed as supported.

How you get games into it

Eclipse offers several routes, and they behave differently:

• Library — a persistent collection you manage on the site. You can add games from Google Drive or Dropbox, or pick from the site's selection of homebrew games. Library games are the ones you can jump back into quickly.
• Local files — you can load a ROM directly from your device. Per the site, a locally loaded ROM does not get added to your Library, so you'd reload it each time.
• Save files — you can manage save files for any game, whether it's in your Library or not.

The offline detail is worth noting: Eclipse says you can still play offline, but only by using games from your local files rather than the Library. If offline play matters to you, plan on keeping ROMs on the device.

Controls and input

Eclipse supports touch, keyboard, and controller input, and you can rebind keys in settings if the defaults don't suit you.

Controller support runs on the JavaScript Gamepad API. That's a real constraint: if your controller isn't recognized by that API or by your operating system, Eclipse won't see it. Before buying a controller for this, check that it works as a standard gamepad in your browser.

Who this suits, and who it doesn't

Eclipse fits well if you:

• Use an iPhone or iPad and want to avoid revoke headaches
• Already have ROM files, or are happy with homebrew titles
• Want quick browser access without installing anything

It may not fit if you:

• Expect a built-in game catalog beyond the homebrew selection — you bring your own files
• Need systems outside the seven listed
• Rely on a controller your browser or OS doesn't expose through the Gamepad API

One practical caveat: the site itself links to a troubleshooting page for loading issues, so if the emulator doesn't start, that's the first place to check rather than assuming your device is unsupported.

Getting started

1. Open eclipseemu.me in a modern browser on your device.
2. Choose how to load a game: sign in to add from Google Drive or Dropbox, browse the homebrew selection, or load a ROM from local files.
3. If you want the game saved for later, add it to your Library; local-file loads won't persist there.
4. Adjust bindings in settings if you're using a keyboard or controller.
5. Verify it works by loading a game and confirming input responds — if the page won't load at all, use the site's linked troubleshooting page.

The main thing to internalize: Eclipse gives you the emulator, not the games. Your setup is only as good as the files you bring to it.

Eclipse supports three input methods: touch, keyboard, and controller. You can use any of them to play the supported systems (Game Boy, Game Boy Color, Game Boy Advance, NES, SNES, Sega Master System, and Sega Game Gear), and if the default bindings don't suit you, you can edit them in settings. The one hard limit is controller support: it depends on the JavaScript Gamepad API, so a controller your browser or operating system doesn't recognize won't work in Eclipse at all.

The Three Supported Input Methods

Touch

On phones and tablets, including iOS and iPadOS, Eclipse presents on-screen controls you tap to play. This is the default way to play on a touchscreen device and requires no setup.

Keyboard

On a desktop or laptop, you can play with your keyboard. Eclipse ships with default key bindings, so you can start playing without configuring anything first.

Controller

Eclipse accepts game controllers through the JavaScript Gamepad API. Two conditions decide whether your controller works:

• The browser must expose it through the Gamepad API. Eclipse reads controllers through this API, not through any separate driver of its own.
• Your operating system must recognize it. If the OS doesn't see the controller, the browser can't pass it to Eclipse.

If either condition fails, the controller "will not be recognized" — this is a limitation of the API and OS, not a setting you can toggle inside Eclipse. A controller that pairs and works in other browser-based tools is a good sign it will work here.

Changing the Default Bindings

Eclipse states that if you don't like the default bindings, you can easily edit them in settings. This applies to the input methods you use — so if a keyboard layout feels awkward or a controller button mapping doesn't match your habits, adjust it there rather than adapting your play style. The site doesn't publish a step-by-step mapping guide, so treat the settings area as the place to look and test each change by pressing the button in a game.

Choosing an Input Method

Practical Notes

• Test your controller before committing to it. Load a game and press a button; if nothing registers, the device isn't being exposed through the Gamepad API on your setup.
• Offline play doesn't change input support. When you play offline using games from your local files instead of the Library, touch, keyboard, and controller all remain available.
• Bindings are worth revisiting per game. Some titles lean on buttons that feel unnatural on a given layout; a quick remap in settings is faster than fighting the default.

In short: pick touch on mobile, keyboard on desktop, and a controller if you want a more tactile feel — but confirm your controller is recognized by your browser and OS first, since that's the one input path Eclipse can't work around.

Start with the site's own troubleshooting page: Eclipse links to a dedicated help page ("Having issues loading Eclipse? Check here.") from its homepage, and that should be your first stop before changing anything on your device. If the page still won't load, work through the basics below — confirm you're on a modern browser, rule out device-level restrictions, and remember that offline play depends on local game files rather than the Library.

Check the Basics First

Eclipse is a web-based emulator, so a failed load is usually a browser or network problem rather than a broken emulator. Before digging deeper:

• Use a modern browser. Eclipse states it runs on "almost any device that has access to a modern web browser." An outdated or embedded browser (for example, one built into an older app) may not meet that bar.
• Reload the page once. A single failed request is common on flaky connections.
• Try another network. If you're on a restricted network (school, office, public Wi-Fi), the site may be blocked at the network level rather than failing on your device.
• Try a second browser on the same device. If it loads there, the problem is your original browser's settings or cache, not Eclipse.

Rule Out Device and Browser Compatibility

Eclipse's main compatibility claim is about iOS and iPadOS: because it runs in the browser, it "can never be revoked on iOS." That's a statement about how the emulator is delivered, not a guarantee that every browser will load it. If the page is blank or stuck:

1. Update your browser to its current version.
2. Disable content blockers or aggressive privacy extensions for this site, then reload.
3. If you're using an in-app browser (opened from a social app or messaging app), copy the address into a full browser instead.

If the site loads in one browser but not another on the same device, you've isolated the issue to the browser — no further device troubleshooting is needed.

Don't Confuse a Load Failure with Offline Setup

Eclipse supports offline play, but only under a specific condition: you "just need to use games from your local files instead of the Library." The Library pulls games from Google Drive, Dropbox, or the site's Homebrew selection — all of which require the site to be reachable. If you're trying to play without a connection and nothing appears, that's expected behavior for Library games, not a loading bug. Load a ROM directly from your local files instead.

Quick Reference

The controller row is worth noting because it's a documented limitation rather than a load issue: Eclipse's controller support is "based on the JavaScript Gamepad API; if your controller is not supported by it or your OS, it will not be recognized." No amount of reloading will fix that — switch input methods instead.

When to Stop Troubleshooting

If the site's help page is reachable and you've confirmed a modern browser, a second browser, and a second network, you've covered the checks the site itself points to. At that point the failure is most likely outside your control (a network block or a temporary site problem), and retrying later is more useful than further changes on your device.