Key — Amiibo Encryption
Nintendo’s encryption design relies on not one but two master keys. They are the true secrets behind amiibo security.
Hardware pieces like the AmiiboLink , Pixl , or Puck allow users to load hundreds of Amiibo files onto a single digital device. For these devices to work, or for backup apps to read .bin files properly, the software must utilize the official encryption keys to pack and unpack the data exactly how a Nintendo console expects it. Preservation of Rare Figures
Used to encrypt and decrypt the dynamic, writeable data saved by the console.
use these keys to translate the raw hex data from an amiibo into a readable format. Writing to Tags:
Every Amiibo is an NFC tag based on the chip. While this is a standard chip, Nintendo built a custom cryptographic layer on top of it. The data stored on the tag is split into two main parts, protected by two distinct master keys. amiibo encryption key
Together, these files are referred to in the emulation and backup communities as the . When combined with a tool like TagMo (Android) or AmiBoss (iOS), these keys allow software to decrypt an Amiibo dump, modify it (or register a new character), and re-encrypt it so a Nintendo console will accept it. The Role of the Key in Emulation and Backups
The community generally considers the use of these keys ethical for backing up figures you already own or for educational purposes regarding NFC technology. Key Maintenance and Management
The memory on an Amiibo chip is divided into distinct sections:
As with many reverse‑engineering endeavours, a delicate balance exists between the rights of the copyright holder and the rights of the user to tinker with lawfully purchased goods. The DMCA’s interoperability exception provides a legal safe harbour for much of this activity, but it is not an unlimited license. The responsible course is to use the acquired knowledge for personal, educational, and non‑commercial projects, respecting both the law and the hard work of the original creators. Nintendo’s encryption design relies on not one but
Used to decrypt the core character data, such as determining whether the figure is Mario, Link, or a rare Gold Mario.
The amiitool repository, hosted on GitHub under the MIT license, became the foundation for nearly all subsequent Amiibo‑related homebrew projects. Its syntax is simple:
The security of an Amiibo relies on a master seed, often referred to in the modding community as the "Unfixed Inferno" seed. This is a static byte array used as the root secret for generating keys.
The first few bytes contain a hardcoded, manufacturer-defined serial number unique to that specific piece of silicon. For these devices to work, or for backup apps to read
Because the data is encrypted, the console can instantly verify if an Amiibo is authentic. If a user alters even one single bit of data on the tag without using the correct encryption key, the resulting cryptographic signature becomes invalid. The console will then reject the tag as corrupted. The Two Parts of the Amiibo Key
: The specific configuration files ( unfixed-info.bin and locked-secret.bin ) contain proprietary, copyrighted data belonging to Nintendo. Hosting or sharing these files violates copyright laws, which is why homebrew tools require users to provide their own keys.
The NTAG215 chip provides a few built‑in security mechanisms. One of them is the system: a 32‑bit password that must be presented via the PWD_AUTH command before the host device can write to the encrypted NFC pages. This password is derived from the 7‑byte UID (Unique Identifier) of the tag. The derivation algorithm takes specific bytes of the UID, performs XOR operations with the constants 0xAA and 0x55, and combines the results to form the final 32‑bit password. Because the password depends solely on the UID, it remains the same throughout the life of the tag, even when game data is updated.
While the keys themselves are small snippets of code, they are copyrighted material owned by Nintendo. Most reputable software will require you to provide your own key files rather than including them in the download. Once an amiibo is written to an NFC tag