Back to guides

How Yoto and Toniebox Cards Work — and What You Can Build With Tags

Yoto cards and Tonie figurines both use NFC, but neither one stores the audio you hear. Each carries a small identifier that the player looks up — one over WiFi, one from its own internal storage. Here's the real mechanics behind the tap, how that differs from an Amiibo, and how to build the same tap-to-play idea yourself with blank tags you own.

Published

What it is

A Yoto card and a Tonie figurine both use an NFC chip to trigger audio — but neither one is a tiny audio file in disguise. Each chip just holds a short identifier. The Yoto player reads that ID and fetches the matching track from Yoto's own servers over WiFi; the Toniebox reads the figurine's ID and pulls the matching audio from its own internal storage, once it's been downloaded there. Same basic trick: a tap resolves to content stored somewhere else. Two different somewheres.

How it actually works

Both systems ride on plain passive NFC — a chip with no battery, powered entirely by the reader's field, operating at 13.56 MHz over a range that rarely clears 10cm. A passive tag like this typically holds somewhere between 96 bytes and 8KB. Nowhere near enough for an audiobook, which is exactly why neither company tried to cram one onto the chip.

Yoto's path runs through the cloud every time a card is new to a given player: the chip's ID gets matched against Yoto's catalog over WiFi, the audio streams down, and the player caches it — up to 600 hours' worth — so it keeps playing without a connection afterward. Tonie's path front-loads that same work and then stays local. A teardown of the Toniebox found a Texas Instruments TRF7962A reader chip inside the lid that reads a figurine's ID the moment it's set down, downloads the matching audio once, and writes it to the box's own 8GB of internal storage — around 400 hours of capacity — rather than back to the figurine. That's the whole difference in a sentence: a Tonie you've played before works instantly with no WiFi in the room, while a card or figurine the player has never met still needs that first online handshake.

Where you'll see it

This "chip holds an ID, something else holds the content" pattern isn't unique to kids' audio players. NXP's own rundown of NFC in consumer toys describes the same design in plush toys, trading cards, and board-game tokens — an NTAG-class chip carries the ID, and an app, console, or box resolves it against data kept somewhere else. It's also why what's actually stored on an NFC tag is almost always a few bytes, not a file.

Amiibo figures are the one well-known exception, and they're worth naming because they flip the model entirely. An Amiibo's chip doesn't just carry an ID — it stores real game data directly on the tag, things like unlock flags or saved Mii information, and the console reads and writes that data in place. No server lookup involved. So tap a Yoto card, a Tonie, and an Amiibo against three different readers, and you're watching three answers to the same design question: put the data on the tag, or just put an ID on it and look the rest up elsewhere.

Tips, gotchas, and a quick how-to with NFCore

You won't get anywhere trying to make Yoto or Toniebox hardware accept a generic blank tag as new content. Both systems check the ID against their own servers or local pairing — which is exactly why Yoto sells blank "Make Your Own" cards and Tonies sells blank "Creative Tonies," each loaded through its own app. What you can build instead is the open version of the same idea, with tags you actually own.

Pick up a handful of blank NTAG213 stickers, open an NFC reader and writer app like NFCore, and write one NDEF record per tag: a deep link to a specific playlist, podcast feed, or audiobook, or an iOS Shortcut that opens one. Stick each tag to a card, a small block, or a shelf label, and tapping it does exactly what a Yoto card does — resolves an ID into something to play. It's basically the same tap-to-trigger idea already in use on plant-care tags, just pointed at a music library instead of a watering schedule. And if you ever want to check what kind of chip is inside a tag you already own — Yoto, Tonie, or otherwise — open NFCore and tap it. The tag-info screen shows the chip type and byte count in a few seconds.

Frequently Asked Questions

Do Yoto cards store the actual audio file?

No. The card's NFC chip holds a small identifier, not the audio itself. The Yoto player reads that ID, matches it to the right title, and fetches the audio from Yoto's servers over WiFi, then caches it locally so it still plays without a connection.

Does a Tonie figurine work without WiFi?

Only after the first play. The figurine's NFC chip carries a unique ID; the Toniebox downloads the matching audio once and stores it on the box's own internal storage, not the figurine. After that first download, that Tonie plays offline from the box.

Can I make my own Yoto or Tonie card at home with a blank NFC tag?

Not in the sense of getting the official hardware to accept it — both systems check the tag's ID against their own servers or app pairing, so Yoto's "Make Your Own" cards and Tonies' "Creative Tonies" are the supported paths for custom audio on those devices. What you can build with your own blank NFC tags is a separate, open system: a shelf of tags that each trigger a playlist, audiobook, or Shortcut on your own phone.

Is this the same technology as Amiibo figures?

Same radio technology, different architecture. An Amiibo's chip stores actual game data on the tag itself — unlock state, Mii data — that the console reads and writes directly. Yoto and Tonie tags store only a lookup ID; the content lives off-tag, in the cloud or on the player.

Conclusion

Tap a Yoto card or a Tonie figurine and you're not pulling an audio file off a chip. You're handing a player a short ID and letting it do the rest — one over WiFi, one from storage it already filled. The same NFC hardware sits inside blank stickers that cost a couple of cents each, so the tap-to-play idea isn't locked to either product. Open NFCore, tap a tag you own to see what's actually on it, and build your own version with tags you control.