macOS · Windows
Prepare the SD card, build your ROM catalog, update the cartridge firmware and flash it all in one go. No command line, no guessing which cluster size to pick, no wondering whether it worked.
Also available for macOS (x64) Windows
What it does
Pick the card, pick the plan, confirm. Studio partitions and formats it with the right filesystem and cluster size, copies the default content, and then verifies the result — partition size, filesystem type, cluster size, label — and tells you what it checked. Nothing is written before you have read a plain-language summary and typed a confirmation.
Drop your ROMs in, reorder them, and let Studio detect the mapper and the MSX generation for you — or override it yourself when you know better. The size bar tells you exactly how much of the cartridge you have left before you run out of room.
Studio finds the cartridge in bootloader mode, shows you which firmware versions exist and which one is recommended, and downloads it from the official manifest. You can also point it at a local file when you are building your own.
The catalog never goes to the cartridge on its own. Studio composes firmware and catalog into a single UF2, validates it before writing anything, shows you exactly what is about to be flashed and to which cartridge, and only then does it write.
A message board that thinks it is running on an MSX. Say hello, show what you built, complain about mappers. It is the closest thing this project has to a clubhouse.
Download
Pick your platform. Every build is published with its size and its SHA-256, so you can check that the file you got is the file we built.
SHA-256 cb385099…53a17221 cb3850999de5bbacf0351984ef1d83c87c1d1e1bb48145144441988253a17221
SHA-256 d06dd153…581a760e d06dd1532d353fed5d1a68d9f32e8cea75124740b86e2a2c15047480581a760e
SHA-256 ae1bb704…9c2f4d94 ae1bb7041eb7bb5431d810522805fc5d5ae9f0259dcd2a19f7bc03f69c2f4d94
Installing
The macOS build is signed and notarized by Apple. It opens like any other app — no warnings, no right-click trick, nothing to work around.
Why does Windows do this? Because the app is not code-signed. A certificate that satisfies SmartScreen from day one costs several hundred dollars a year, which is hard to justify for a project this size. SmartScreen is not telling you the app is malware — it is telling you it does not recognize the publisher, which is true. If you would rather verify what you downloaded than take our word for it, the SHA-256 of every file is published: run Get-FileHash in PowerShell and compare.
Requirements
FAQ
Sign-in is what lets Studio give you the official firmware and catalog manifests, keep The Wall from filling up with spam, and tell you when there is an update. Studio never sees your Google password — the sign-in happens on Google's own page, and Studio only receives your name, e-mail and profile picture.
Yes. No trial, no license key, no locked features. If it earns its keep, the app has a Support the Project button under Settings — donations cover the server bills and the hours that keep it improving. Nothing is locked behind them.
No. Windows says it does not recognize the publisher, which is a different thing — the app is not code-signed, because the certificate is expensive for a project this size. The Installing section walks you through SmartScreen step by step, and every download is published with its SHA-256 so you can verify the file you got is the file we built.
Not yet. The app is built to be portable, and Linux is planned once the macOS and Windows builds have settled. Nothing to announce yet.
Your ROMs and your catalogs stay on your machine — they are never uploaded anywhere. What leaves your computer is your sign-in with Google, whatever you choose to post on The Wall, and anonymous diagnostics that help find crashes.
In the app, open Settings > About and click Report a Problem. Tell us what you did, what you expected and what happened instead — and if a wizard failed, the log panel has the detail we need.
