Tokens
Tokens are the physical objects you scan to trigger actions in Zaparoo: NFC cards, QR codes, barcodes, NFC toys like Amiibo figures, discs, and USB drives. Readers are the hardware that scans them. Software sources such as the API, MQTT, and the file reader can also act as tokens without any hardware; see readers.
Writable tokens hold a small piece of text, like a game title or ZapScript command, not the game itself. Read-only tokens, such as some NFC toys or product barcodes, are matched to ZapScript with mappings. Terms like NFC, NDEF, and UID are defined in the glossary.
Most people start with NTAG215 cards: they hold enough for any normal ZapScript, work with every NFC reader, and are cheap in bulk.
From left: cards by Karl Fayeton from Community Showcase #5, then NFC coins by Foolz and floppy-style tokens by Suiren from Community Showcase #6.
The Zaparoo Shop stocks premium NFC cards with pre-printed designs ready to use with Zaparoo. Community members also sell custom cards and labels; ask in the Discord to find someone near you.
Token types
| Token | Storage | Writable | Reader needed | Notes |
|---|---|---|---|---|
| NFC cards and tags | Varies by chip (NTAG215: 504 bytes) | Yes | NFC reader | Cards, stickers, key fobs |
| PCB cards | NFC sticker | Yes | NFC reader | Custom PCBs with NFC stickers |
| NFC toys | UID | No (mapped) | NFC reader | Amiibo, Skylanders, and similar |
| QR codes | Text or URL | Printable | App, camera, or scanner | Free to create, no special hardware |
| Barcodes | Barcode value | Printable | App or barcode scanner | Works with existing product barcodes |
| Online cards and decks | Short URL on an NFC tag | Yes, and editable online | NFC reader | Change what a card does without rewriting it |
| Discs | Disc ID | Burned discs only, as a zaparoo.txt file | Optical drive | Launch from real CDs, DVDs, and Blu-rays |
| USB sticks and SD cards | Text file on the drive | Yes | External drive reader | Removable media as tokens |
Using tokens on multiple devices
The token's contents determine how portable it is:
@System/Titleis the preferred cross-device format. Each device resolves the title against its own indexed library, so filenames and folder layouts can differ.- A relative system/path token can work on another device when both devices use compatible internal folder structures.
- An absolute filesystem path is generally specific to one device and platform.
- Mappings live on Core rather than the physical token, so create the mapping on each destination device as well.
The destination device still needs compatible media and a launcher for the requested system. See ZapScript path formats for examples and matching behavior.
Storage
See token storage for binders, cassette cases, Nintendo Switch replacement cases, and other ways to keep a collection on the shelf.