ROM Storage
Bit-Exact
EMUBANK: LOCAL-FIRST EMULATOR LIBRARY
Build a library, insert local games, play in your browser where supported, and back up real in-game saves automatically while ROM files stay on your device.
ROM Storage
Bit-Exact
Library Flow
Insert + Play
Safety Layer
Rollback Saves
Main run ยท 6 revisions
Cloud save ready
Local ROM inserted
External player
Rollback available
Optional when supported
Smart module preview, library-first core
Newsroom
Latest snapshot and target-save ownership are now explicit across mutation flow.
Compatibility
Built for mainstream save formats and extensive ROM hack save ecosystems with validation-first guards.
Live Roadmap
Direct snapshot pull/push endpoints are now available for plugin-level integration.
Search a game authority source, choose the correct platform result, and import canonical metadata, artwork references, and emulator mapping defaults.
The browser hashes your selected ROM or disc image locally. EmuBank records filename, size, hash, and mapping metadata, never ROM bytes.
Create playthroughs like Main, Challenge, Romhack, Randomizer, Speedrun, or Living Dex so saves and settings stay attached to the right run.
Upload real in-game save files, keep revision history, and restore or download snapshots without locking your data behind payment.
Smart modules only appear when the game or save supports them. Non-Pokemon games stay in the normal library and save-management flow.
CLOSED BETA
Closed beta gives early access to the library shelf, game authority imports, local file metadata, save revision history, and emulator sync APIs.
COMPATIBILITY CURTAIN
Library support matrix + current boundaries
Library Platforms
Save Workflows
Smart Modules
Build a personal emulator shelf where ROM files stay on your device while EmuBank tracks metadata, platform choices, playthroughs, and save continuity.
Search for games by name, choose canonical records, and attach artwork, descriptions, platform mappings, and emulator defaults without manual filing.
EmuBank records hashes and local metadata for organization, but does not upload, store, sell, or distribute ROM binaries.
Keep real in-game hard saves backed up with restore paths, revision history, and manual export always available.
Track normal runs, challenges, romhacks, speedruns, and other playthroughs as first-class library state.
Launch supported games directly from the shelf after inserting local files, while external-only platforms remain cleanly organized.
Optional modules like PokeVault can unlock deeper tools only when a game or save context supports them.
Redis-backed notifications and Recyclr partial refreshes keep library, save, scanner, and module state moving without heavy page reloads.
Internal admin tools manage users, invites, game records, scanners, settings, and system health safely.
May 16, 2026
The EmuBank home flow now centers on searchable game shelves, local ROM metadata, playthroughs, and attached save actions.
May 16, 2026
Game search can import canonical metadata, platform details, artwork records, and local first-party fallbacks before users attach files.
May 16, 2026
Realtime notifications and partial UI refreshes are wired through Redis-backed updates for a sturdier app shell.
Canonical game records, platform mappings, artwork, aliases, external IDs, and curated EmuBank metadata in one shared database.
Browser-play support for compatible platforms with local file insertion and minimal player chrome.
Steam-style shelf interactions with attached panels for ROMs, playthroughs, saves, settings, and module actions.
Redis stream updates and Recyclr fragments for save scans, module changes, invitations, and account events.
A modal-heavy internal panel for users, invites, game records, scanners, settings, and system inspection.
Paid features focus on storage, automation, deep history, and social power while basic ownership and export stay free.
Allowed upload formats: .sav, .srm, .dsv, .dat, .gci, .bin, .raw, .main.
ROM binaries and game images are blocked and never stored by EmuBank.
Patch artifacts (.ips/.ups/.bps/.xdelta and similar) are blocked and never stored.
Device-scoped API keys with revocation, rate limits, and audit trail per emulator client.
Pull latest approved snapshot for a save, push updated save bytes, and receive immutable snapshot references.
Structured responses for compatibility blockers and salvage actions so emulator UX can guide user decisions in real time.
Search by title, choose the matching platform record, import metadata, then optionally attach a local ROM hash and initial save.
Choose a local file in the browser, hash it on-device, and let EmuBank remember filename, size, platform, and emulator mapping without uploading ROM bytes.
Attach runs like Main, Nuzlocke, Randomizer, Romhack, Challenge, Speedrun, or Living Dex to a single game entry.
Open a game context panel, review hard-save revisions, and download or roll back to the selected checkpoint.
When a save or game supports a module, enable it from the game context panel and keep unrelated saves in the normal library flow.
Use EmuBank for metadata, launch flow, and save continuity while your game files remain local.
Upload in-game battery saves rather than emulator save-states so revisions remain portable between tools.
Separate Main, Challenge, Romhack, and Speedrun contexts so saves and settings stay understandable later.
Download your own saves whenever you want. EmuBank should make recovery easier, never trap your data.
When emulator sync is enabled, device-scoped keys make automation easier to revoke and audit.
Let normal game saves stay in the library unless a module like PokeVault is relevant to that game or playthrough.
No. ROM files stay on your device. EmuBank stores library metadata, local file hashes, save files, and revision records.
Yes. Manual export and basic save ownership are core free features, not paid lock-in.
Yes. The library, metadata, playthrough, local ROM metadata, and save revision systems are general emulator-library features.
Only for supported Pokemon games/saves or when you explicitly force PokeVault registration for a game or playthrough.
For supported platforms, yes. Browser play uses local files inserted by the user; unsupported platforms remain organized for saves and metadata.
Convenience, automation, more history, more storage, advanced recovery, and social power-user features. Basic ownership remains free.