TinyWiiBackupManager v6.1.8 — Download and Guide for Windows, Mac and Linux
TinyWiiBackupManager v6.1.8, released on 20 October 2026 by mq1, is a free, open-source (GPL-3.0) backup manager written in Rust that runs natively on Windows, macOS and Linux. It manages Wii and GameCube games, converts between ISO and RVZ, splits large games automatically for FAT32 drives, verifies integrity, and pulls covers and title data from GameTDB. This hub page collects the verified download files and checksums for all three platforms, the feature list, and guidance on who should use TinyWii — and who is better served by the classic Windows program.
Release facts
Version 6.1.8 is the release this page documents, published on 20 October 2026. The project is maintained by mq1 on GitHub, where each release publishes its files together with their SHA-256 digests — the numbers in the table below are those published digests, so you can check a download yourself instead of taking any website’s word for it. TinyWii is a separate project from fig2k4’s classic Wii Backup Manager: different developer, different codebase, same core job. The current community guidance at wii.hacks.guide recommends TinyWii for WBFS splitting and directory structure, reflecting its place as the maintained tool in this space.
Verified downloads for all three platforms
| Platform | File | Size | Download |
|---|---|---|---|
| Windows (x64) | Executable (.exe) | 10,756,096 bytes | Download |
| macOS (Universal, 10.12+) | Disk image (.dmg) | 9,682,347 bytes | Download |
| Linux (x86_64) | AppImage | 8,509,944 bytes | Download |
SHA-256 checksums — Windows x64: 0be390f010f075ddd5fc42f4d740d21799cf170cd143efc4acf8ba4aee56616b. macOS: d497f759aee227d9afe0a7e4d87557f93d3afe503fb19e027cc1b381bc1d1196. Linux AppImage: 9786601fde020a0b2319399c77646baa1c9b53dcb443ea5edebb3cc873bd4f36. TinyWii also supports Windows on x86 and ARM64 in addition to x64. A secondary copy is available as TinyWii — Mirror (Terabox), and the project home is TinyWiiBackupManager on GitHub. Prefer the GitHub files as the primary channel precisely because their digests are published.
Installing on each platform
- Windows: Download the executable for your architecture (x64 for most machines) and run it. On Windows, TinyWii can also be installed with winget, Microsoft’s package manager, which suits users who prefer command-line installation and easier updates.
- Mac: Open the Universal DMG, drag the app to Applications, and on first launch use the right-click Open method described on our Mac page, since independently distributed apps can trigger a Gatekeeper prompt.
- Linux: Make the AppImage executable (
chmod +x) and run it, or install TinyWii through Flathub if you prefer Flatpak-managed software. Full steps are on our Linux page.
What TinyWii does: the feature list
- Formats: Works with ISO and RVZ game files, the two formats that matter for modern Wii libraries.
- Two consoles’ libraries: Manages both Wii and GameCube games in one application.
- Automatic splitting: Splits large games automatically for FAT32 drives, producing the multipart structure loaders expect — no manual file surgery.
- Archiving: Stores games as RVZ files compressed with zstd, a space-efficient way to keep a library on your computer.
- Integrity checking: Verifies that game data is complete and uncorrupted, so problems surface on the PC rather than at the console.
- Covers and titles: Uses GameTDB cover art and the wiitdb.xml database so your library shows proper names and artwork.
- Cheat codes: Includes support for managing cheat codes alongside your games.
- Homebrew: Manages homebrew applications and the Open Shop Channel from the same interface.
- Wiiload: Can send content to a Wii over your local network with Wiiload.
Who TinyWii is for
TinyWii is the obvious starting point if you are on a Mac or a Linux machine, because the classic program simply does not exist for those platforms. It is equally sensible on Windows if you value active development, published checksums, integrity checking and RVZ archiving, or if you manage a mixed Wii and GameCube library. Its workflow will feel familiar to anyone who used the classic program — add games, check the list, choose the drive, transfer — with the platform reach the classic tool never had.
Who should stay with the classic program?
If your library workflow is Windows-only, long established, and built around habits from the classic program, Build 78 still does its job and there is no forced migration: it is a final, stable release. Some users also keep both installed — the classic program for an existing routine, TinyWii for verification or for a second computer that is not running Windows. Our side-by-side comparison, Wii Backup Manager vs TinyWii, works through the differences in detail, and the classic program itself is on our Download page.
A typical first run
- Download the file for your platform from the table above and verify its SHA-256.
- Install or launch TinyWii using the platform note above.
- Add a small number of games first — one or two titles — and confirm they are recognised with correct titles and covers.
- Connect the drive intended for the Wii, double-check its identity, and transfer.
- Run an integrity check, eject the drive cleanly, and test on the console before migrating a whole library.
That small-batch habit applies to every tool in this category. Once the first drive tests cleanly on your Wii, scaling up to a full library is routine — and if anything looks wrong, you have only a couple of games to redo while you find the cause.
How TinyWii fits a modern library workflow
A backup library usually lives in two places at once: an archive on your computer, where games are kept safely and compactly, and a working copy on the drive connected to the Wii. TinyWii is built for exactly that split. On the computer side, RVZ files compressed with zstd keep the archive compact while preserving the game data, and integrity checking lets you confirm that the archive copy is still complete months or years later. On the console side, the same program prepares the drive copy with the folder structure and automatic splitting that loaders expect, so a large game does not become a manual file-handling project. Moving between those two states — archive to drive, drive back to archive — inside one application is what makes the workflow modern compared with the single-purpose converters many users started with, and it is why a mixed library of Wii and GameCube titles is practical to maintain in one place rather than across several ageing utilities, each with its own habits and its own unverifiable download source.