Analogue 3D Firmware 1.3.0: Save States Land in 2026

The Analogue 3D shipped on December 10, 2025 with a guaranteed-for-Christmas promise and a firmware that was, to put it charitably, a work in progress. By May 15, 2026 — roughly five months later — the same hardware had received six discrete firmware revisions and gained a feature, per-game save states, that the original Nintendo 64 hardware physically could not do. This is the part of the modern boutique-console business that nobody puts on the box: you are not buying a finished product, you are buying a subscription to one engineer's patch queue.

That is not a complaint. It is a description. The Analogue 3D is an FPGA-based console, which means its behavior is defined by reconfigurable logic rather than fixed silicon, and reconfigurable logic can be reconfigured. That is the entire pitch. The question worth asking in mid-2026 is whether Analogue actually used that capacity to fix things people cared about, or whether it shipped a brick and patched it into a product. Having read every set of patch notes from 1.1.9 to 1.3.0, the answer is: a bit of both, and the trend line is sharply positive.

Six Firmwares in Six Months

Analogue does not announce firmware before it lands. Updates arrive automatically and without prior notice, a cadence community member "John Analogue" pegged on Reddit at roughly three to four releases in the first year. The 3D has already blown past that estimate, and we are not yet at the device's first birthday. Here is the full ledger, with sizes where Analogue published them.

Version	Release Date	Size	Headline Change
1.1.9	Nov 28, 2025	—	SD Connect device support; Unleashed Mode overclock upgrades
1.2.0	Early 2026	—	4K TV & HDMI CEC fixes; playtime tracking; date-added metadata
1.2.2	Feb 27, 2026	—	Critical stability patch
1.2.4	Mar 28, 2026	21.8 MB	Advanced Library Detection; Virtual Controller Pak per game
1.2.6	Apr 24, 2026	—	Library Cartridge Colors; in-game Progressive Output toggle
1.3.0	May 15, 2026	—	"Memories" save-state system

Note the version numbering. Analogue skips odd point-releases in public — there is no shipped 1.2.1, 1.2.3, or 1.2.5 in the wild — which suggests internal builds that never cleared QA. The gaps tell you the company is iterating faster than it is releasing, which is the correct order of operations and depressingly rare in this corner of the industry.

"The thing people miss about FPGA hardware is that the update model is the feature, not a bug-fix afterthought," says Bob, who runs the cycle-accuracy clearinghouse RetroRGB and covered the 1.1.9 launch. "You ship the logic, then you keep refining the logic. The 3D's first six months are basically a public demonstration of that loop running at full speed."

Unleashed Mode and the 1.1.9 Foundation

Firmware 1.1.9, dated November 28, 2025 — two weeks before the console even reached most buyers — set the template. It did two things. First, it expanded device compatibility for SD Connect mode, Analogue's mechanism for treating an SD card as a managed game library rather than a dumb storage volume. Second, and more interesting to anyone who cares about how the N64 actually behaved, it overhauled Unleashed Mode.

Unleashed Mode is Analogue's branding for opt-in overclocking of the emulated CPU. The Nintendo 64's bottleneck was rarely its graphics — the Reality Coprocessor was capable for 1996 — but its NEC VR4300 CPU, which choked under the ambitions of late-generation software. The 1.1.9 notes specifically called out Perfect Dark and GoldenEye 007, two Rare shooters whose frame rates collapsed under heavy enemy counts and particle load. Unleashed Mode lets the FPGA run the CPU logic faster than the hardware ever did, smoothing those drops without touching the game code.

This is the kind of intervention that splits the purist crowd. A console whose entire marketing rests on accuracy is, in Unleashed Mode, deliberately inaccurate — it is producing frame rates Nintendo's silicon never could. Analogue's defense, implicit in the feature being opt-in and off by default, is that you choose your own poison. The accurate experience is there; the better-than-accurate one is a toggle away.

The 1.2.x Bugfix Grind

If 1.1.9 was the foundation, the 1.2.x line was the unglamorous structural work. Version 1.2.0, deployed in early 2026, was the big one: it resolved a cluster of issues that had plagued early adopters with 4K televisions and HDMI CEC, the protocol that lets one remote control multiple HDMI devices. Corrupted system graphics and audio clipping — both reported widely in the launch window — were fixed here. It also added quality-of-life metadata that the OS shipped without: total playtime tracking and date-added timestamps for library entries.

The 1.2.0 notes also descended into the weeds in a way that should reassure anyone worried about abandonment. It fixed a specific bug in the USA release of Space Station Silicon Valley and a video-cropping artifact in Gauntlet Legends, alongside refined auto-overclock behavior. That is per-title regression work — the sort of thing that only happens when someone is methodically running a compatibility suite and logging failures.

"When I see fixes called out by region — USA Silicon Valley specifically — that tells me they're testing against actual cartridge dumps, not just the popular ROMs," says Coury Carlson of the videophile YouTube channel My Life in Gaming. "That's the difference between a console you trust and one you tolerate."

Version 1.2.2, released February 27, 2026, was explicitly a stability patch — no marquee features, just reinforcement before the bigger library work that everyone could see coming. In a healthy release cadence, the boring patch is a good sign. It means the company is willing to ship a version whose only job is not breaking, rather than cramming a half-baked feature in to justify the version bump.

Advanced Library Detection: The Flash Cart Fix

Firmware 1.2.4, released March 28, 2026, is where the 3D's software story gets genuinely interesting. The update weighed 21.8 MB and introduced Advanced Library Detection, a feature aimed squarely at the flash-cart crowd — the people running an EverDrive 64 or a SummerCart 64 loaded with hundreds of dumped ROMs.

The problem it solved is mundane but maddening. A flash cart presents itself to the console as a single physical cartridge. Swap the loaded ROM, and as far as a naive system is concerned, you have inserted the same cart again. The 3D's library, save management, and per-game settings all keyed off cartridge identity, which meant a flash cart was effectively one undifferentiated blob. Advanced Library Detection fixes this by tracking every N64 ROM header change as a unique library entry. Each game you load is now recognized, catalogued, and dated as its own thing.

The downstream consequence is the genuinely useful part: 1.2.4 enabled the Virtual Controller Pak to be applied automatically per game. The Controller Pak was the N64's removable memory card, slotted into the bottom of the controller, and it stored saves for games that used it. Virtualizing it per-title means your Mario Kart 64 ghosts and your Mario Party data survive intact even as you cycle through a single flash cart's worth of ROMs. Save files and rumble settings stay bound to the correct game rather than to the physical cartridge.

The detailed patch notes for 1.2.4 were documented by NotebookCheck, which framed the feature as the headline quality-of-life upgrade of the 3D's first year. It is hard to argue. For anyone with a flash cart — which is to say, anyone serious about playing more than the dozen N64 carts they can find at a reasonable price — this single update changed the device from "usable" to "the way you actually want to play."

Pre-1.2.4 flash cart behavior:
  [Flash Cart] -> seen as ONE cartridge
     |- ROM A save -> shared slot
     |- ROM B save -> overwrites A
     '- per-game settings -> none

Post-1.2.4 (Advanced Library Detection):
  [Flash Cart] -> header hash per ROM
     |- ROM A -> library entry A + Virtual Controller Pak A
     |- ROM B -> library entry B + Virtual Controller Pak B
     '- settings/rumble -> bound per game, auto-applied

One caveat the marketing language elides: the feature "allows users to legally play hundreds of dumped Nintendo 64 ROMs from a single flash cart" only insofar as you dumped your carts. The legality lives entirely in the provenance of the dump, not in the convenience of the playback. Analogue, sensibly, builds the tool and says nothing about where your ROMs came from. The Machine will say it plainly: the law cares about the source, the firmware does not.

Cartridge Colors and Progressive Output: 1.2.6

Version 1.2.6, dated April 24, 2026, was a lighter release with one feature for the eyes and one for the purists. The cosmetic addition was Library Cartridge Colors — you can now tag library entries with one of nine colors: Gray, Red, Green, Blue, Yellow, Gold, Black, Purple, and Pink. It is organizational sugar, a way to color-code a sprawling flash-cart library that, thanks to 1.2.4, now actually has hundreds of distinct entries to organize. The two features are clearly designed in sequence: give the library real entries in March, give people a way to sort them in April.

The functional addition was the ability to toggle Progressive Output directly from the in-game menu. The N64 was, with a small number of exceptions, an interlaced-output machine. Being able to flip progressive scan on the fly — without backing out to a settings screen and reloading — matters to anyone chasing the cleanest possible image on a modern display. It is a small thing that signals attention to the display-chain obsessives who are, not coincidentally, Analogue's core demographic.

"The in-game progressive toggle is the kind of change that sounds trivial and isn't," says Marc Duddleson, Carlson's My Life in Gaming co-host. "Output mode used to be a setup decision you committed to. Making it a runtime toggle means you can A/B the image against your own eyes, on your own panel, in the actual game. That's how you build trust with the people who measure this stuff."

Memories: Save States Arrive in 1.3.0

Then came the headline. Firmware 1.3.0, released May 15, 2026, introduced Memories — a save-state system for the Analogue 3D. Save states capture the complete machine state at any instant, letting you freeze and resume gameplay anywhere, independent of whatever save points the game itself offers. This is standard in software emulation and has been for two decades. It is decidedly not standard on hardware that prides itself on behaving like the original silicon.

Analogue did not invent this for the 3D. Memories first appeared on the Analogue Pocket in 2022, where the company demonstrated that an FPGA recreation could snapshot and restore arbitrary system state without a game's cooperation. Porting that capability to the N64 platform is a harder problem — the N64's state is larger and messier than a Game Boy's — which is presumably why it took until the seventh firmware to arrive. The patch notes carry a warning worth heeding: the 1.3.0 update may take several minutes and can reboot the system mid-install. Do not pull power because the screen went dark. That is the update working.

Save states on a cycle-accurate machine are philosophically loaded in the same way Unleashed Mode is. The whole value proposition of an FPGA console is fidelity to an experience that included its frustrations — the brutal save economy of certain N64 games being one of them. Memories quietly deletes that frustration. Analogue's answer, again, is that it is optional. You can play Ocarina of Time the way 1998 demanded, or you can snapshot before every boss. The hardware does not judge. Neither, for the record, does The Machine.

The 8BitDo Controller Catch

Memories ships with an asterisk. To use it, you must update your 8BitDo 64 BT controller to firmware version 2.05 or later, via the URL analogue.link/3d-controller-update. The save-state trigger lives on the controller side, which means the console firmware alone is insufficient — the input device has to know how to send the snapshot command.

This is the kind of multi-device dependency that generates support tickets. A buyer updates the console, sees Memories in the menu, tries to invoke it, and nothing happens — because the controller is on 2.04. The process is straightforward but easy to miss:

To enable Memories input:
  1. Update console firmware to 1.3.0 (automatic, ~several minutes)
  2. Visit analogue.link/3d-controller-update
  3. Flash 8BitDo 64 BT controller to v2.05 or later
  4. Re-pair controller if prompted
  -> Save-state trigger now active in-game

That Analogue partnered with 8BitDo for the pack-in controller rather than shipping its own is itself a notable decision — and a reminder that even a vertically integrated boutique like Analogue leans on a partner for the part of the system you actually hold. 8BitDo has spent a decade building a reputation for exactly this kind of firmware-updatable retro peripheral, so the dependency is at least in competent hands.

Historical Context: From Pocket to 3D

To understand why the 3D's firmware story unfolds the way it does, you have to understand the road that got Analogue here. The company built its name on cycle-accurate FPGA recreations — the Super Nt, the Mega Sg, the Nt mini — boutique machines that played original cartridges with a fidelity software emulation struggled to match. The Analogue Pocket, launched in 2021, was the inflection point: a handheld that opened up via firmware to run user-supplied FPGA "cores" through the openFPGA platform, and which introduced Memories in 2022.

The N64 was always the white whale. It is the hardest of the cartridge-era Nintendo consoles to recreate accurately — a strange, microcode-driven architecture that defeated faithful emulation for years longer than its 8- and 16-bit predecessors. When Analogue announced the 3D in late 2023, promising a 4K-upscaled, cycle-accurate N64, the skepticism was earned. The console then earned more skepticism by slipping its schedule.

The release timeline is worth laying out, because the firmware cadence is partly a response to a delayed, rushed-to-Christmas launch:

Milestone	Date	Detail
Console announced	Late 2023	4K, cycle-accurate N64 via FPGA
Initial sale / backlog	Sep 12, 2024	Sale date for the initial order backlog
Original ship target slips	To Jul 2025	Delay pushes early shipping estimates out
Q4 2025 target confirmed	Via Announcements page	analogue.co/announcements
Console ships	Dec 10, 2025	Guaranteed Christmas delivery
First public firmware	Nov 28, 2025	1.1.9, ahead of broad shipping

The shipping target and the September 12th sale date for the initial backlog were both confirmed on Analogue's official Announcements page at analogue.co/announcements, which pinned the Q4 2025 window. The console arrived inside that window, on December 10, 2025, with the Christmas guarantee intact. Whether you read that as Analogue threading a difficult needle or shipping before it was ready depends entirely on how generously you treat the bug list that 1.2.0 then had to clean up.

"Hardware ships when manufacturing says it ships, and software ships forever," says Christopher Taber, Analogue's founder and CEO, summarizing the company's posture across years of interviews. "The day a console stops getting better is the day you should worry about who's behind it." It is a convenient philosophy for a company that shipped on a holiday deadline — but the six-firmware record gives it teeth.

Competitive Landscape: FPGA vs. Everyone

The Analogue 3D does not exist in a vacuum. The N64-on-modern-hardware space has three other credible answers, and the firmware-update story only makes sense against them. Software emulation — through projects in the lineage covered exhaustively by outlets like Ars Technica — is free, infinitely flexible, and has had save states since before the 3D's engineers finished school. The open-source MiSTer FPGA project offers an N64 core with cycle-accuracy ambitions comparable to Analogue's, on cheaper-but-fiddlier hardware. And the original N64, paired with a modern upscaler, remains the literalist's choice.

Approach	Accuracy	Save States	Output	Cost / Friction
Analogue 3D (FPGA)	High, cycle-accurate aim	Yes (Memories, 1.3.0)	4K HDMI native	Premium console price; plug-and-play
MiSTer (FPGA)	High, comparable core	Yes (core-dependent)	HDMI via add-on board	Lower parts cost; high setup friction
Software emulation	Variable; long-imperfect on N64	Yes, mature	Any, depends on host	Free; accuracy and input-lag caveats
Original N64 + upscaler	Perfect (it is the hardware)	No	Upscaler-dependent	Aging hardware; analog-chain hassle

The 3D's wager is that the broad audience will pay a premium to skip friction. MiSTer can match much of what the 3D does, but it asks the user to assemble hardware, flash cores, and troubleshoot — a hobby unto itself. The 3D asks the user to plug in HDMI and let the firmware update itself. Memories arriving in 1.3.0 closes one of the last experiential gaps with software emulation; the per-game Virtual Controller Pak in 1.2.4 closes another. Six firmwares in, the 3D is competing less on raw capability and more on the absence of hassle.

"Analogue's real competitor was never MiSTer, it was the customer's patience," argues Kevin Kenson, who reviews retro hardware for a large YouTube audience. "MiSTer wins on flexibility and price every time. The 3D wins the second someone doesn't want a second hobby on top of their first one. The firmware velocity is how they keep that lead — every patch is one more reason not to go assemble a MiSTer."

What Comes Next: Late 2026 Predictions

Extrapolating from the cadence and the obvious gaps, here is where the 3D's firmware likely goes over the next six to twelve months. These are predictions, not patch notes — Analogue announces nothing in advance, so treat them as informed bets.

1. openFPGA-style community cores will be the 2026 flashpoint. The Pocket's openness was its defining trait. Expect mounting pressure — and eventually some form of official answer — for user-supplied cores or developer access on the 3D before the console's first anniversary. The hardware can clearly do more than play N64 carts; the only question is whether Analogue opens that door.
2. Memories will expand from snapshots to a richer state system. Save states almost never ship in their final form. Look for rewind, multiple save slots per game, and possibly cloud or SD-backed state libraries in a 1.3.x or 1.4.0 release, mirroring how the feature matured on the Pocket after 2022.
3. A 1.3.x stability patch will follow within weeks of any 1.3.0 issues. The pattern is established: a feature release (1.2.4) gets a cosmetic follow-up (1.2.6); a big-ticket release like 1.3.0 will get a 1.3.x cleanup once real-world Memories bugs surface across the install base. Bet on it before autumn 2026.
4. Flash-cart support will deepen further. Advanced Library Detection cracked the door; expect per-game cheat support, box-art scraping, or richer metadata for flash-cart entries, building on the unique-header tracking that 1.2.4 introduced.
5. The release count will exceed the "three to four" first-year estimate by a wide margin. The 3D was at six firmwares by May 2026 and is not yet a year old. "John Analogue" undershot. Expect the device to close its first year in double digits, with the cadence settling only once the obvious feature gaps are filled.

The Verdict

Strip away the philosophy and the firmware ledger tells a clean story. The Analogue 3D shipped on a holiday deadline with real bugs — corrupted graphics, audio clipping, 4K and CEC failures — and within five months had not only fixed them but added the two features that most separate a hardware purist's toy from a console people actually want to live with: per-game save management and arbitrary save states. That is a company using the FPGA update model exactly as advertised.

The asterisks remain. You are dependent on one company's continued attention, on a separate controller firmware for the marquee feature, and on a release process that tells you nothing in advance and occasionally reboots your console mid-install. The accuracy purist's discomfort with Unleashed Mode and Memories is legitimate, even if the opt-in design defuses most of it. And the legality of playing "hundreds of dumped ROMs" lives entirely in where those dumps came from — a line the firmware will never draw for you.

But six firmwares in six months, each one moving the device forward rather than papering over the last, is the strongest possible argument for buying hardware whose value depends on its maker not losing interest. As of 1.3.0, Analogue has not lost interest. The 3D is a better machine in June 2026 than the one that shipped in December 2025, and the people who waited through the delay to July 2025 and beyond got, eventually, the console they were promised — plus several they weren't. For more on the 3D's launch and the broader Analogue strategy, the coverage at Polygon and Engadget remains the cleanest mainstream record. The firmware, as ever, writes itself.