Analogue 3D 1.4.0: 4K Screenshots, 11 Builds Deep

Analogue sells hardware. What it actually ships, increasingly, is a subscription to its own changelog. The Analogue 3D — the company's $249.99 FPGA recreation of the Nintendo 64 — landed on November 18, 2025 running firmware 1.1.0 and a promise. Seven months later it is on 1.4.0, its eleventh public build, and the console sitting under your television today is not the one you unboxed at launch. That is either the strongest argument for buying modern retro hardware or the most tiring, depending on how you feel about copying a .bin file onto an SD card every three weeks.

The June 23, 2026 update — 1.4.0 — is the headline, and it is a strange one: after eleven builds, the console can finally take a screenshot. Press the Star button on the 8BitDo 64 controller and the 3D captures the frame in bit-perfect 4K HDR, files it into a new Gallery, and lets you export it losslessly in SDR or HDR. For a machine whose entire pitch is "your N64 games have never looked this good," it is faintly absurd that a save-state system and ten prior updates had to ship before the one feature every phone has had since 2007. But that is the shape of the Analogue 3D: the silicon was done at launch; the software is being finished in public.

This is the complete accounting — every build from 1.1.0 to 1.4.0, what each one changed, the cycle-accuracy fight that erupted in December, how to flash it without bricking anything, and where a sane person should put their money to play Ocarina of Time on a modern panel. With numbers, as always.

1.4.0: The Screenshot Update Nobody Rushed

Firmware 1.4.0 shipped on June 23, 2026, a 21.8 MB image (MD5 b7cfc37a0b1d4c92698cd57990868f90) like every build before it. Analogue's own copy frames the marquee feature with characteristic grandiosity: "Definitive recreations of original CRT displays, now captured for the first time in bit-perfect 4K HDR." Strip the varnish and it means the console can now screenshot itself.

What the Gallery Actually Does

The new Gallery lives in the main OS menu. Every capture is written to the SD card and can be exported in full lossless 4K, in either SDR or HDR — and, in a genuinely clever touch, you can change the display mode at export time. Shoot a frame under the 3D's CRT-mask emulation, then export a clean SDR copy for the web without re-capturing. Analogue is selling this as preservation: the console isn't just showing you GoldenEye, it is archiving what GoldenEye looked like on the display it was designed for. Time Extension summarized the update as "Capture, Preserve, and Share," which is Analogue's marketing verbatim, but the underlying feature is real and it works.

The Hotkeys and the Export Options

Capture is bound differently across controllers, which tells you something about the hardware Analogue expects you to own. On the first-party 8BitDo 64 pad it is the Star button; on a Nintendo Switch Online N64 controller it is Capture; on an original-style controller with no spare buttons, it is the three-finger salute Z + Start + R. The same 1.4.0 build also folds in a batch of quieter fixes: faster direct boot to cartridge, corrected I-cache and D-cache opcode behavior, a floating-point rounding regression fix, a repair for San Francisco Rush's multiple-Controller-Pak handling, and a fix for D-pad presses interfering with the new hotkeys.

The Missing Piece: There Is No WiFi

Here is the joke the feature can't escape: the 3D has no radio. To get a 4K screenshot off the console you eject the SD card and walk it to a computer, exactly as you would have in 2005. MMORPG.com's Joseph Bradford put the obvious wish on record: "I do wish that the A3D had a WiFi feature so I could simply upload the screenshots direct from the console." He is right, and no firmware update will fix it, because the antenna that would make it possible was never soldered on.

Eleven Builds in Seven Months

The 3D's update history is the most aggressive of any Analogue console to date. From the November 18, 2025 launch build to 1.4.0, Analogue pushed eleven public firmware images in barely seven months — a new build, on average, every three weeks. We have catalogued the full changelog separately; the condensed version is below.

The Cadence: One Build Every Three Weeks

Discount the two launch-window stability builds (1.1.0 and 1.1.9) and the real feature cycle starts on January 30, 2026 with 1.2.0. From there Analogue held a metronomic pace: 1.2.1 on February 13, 1.2.2 on February 27, 1.2.3 on March 13, 1.2.4 on March 28 — a fortnight apart, almost to the day. That is not the cadence of a finished product receiving occasional maintenance. It is the cadence of a platform, and it is the same logic Sony applied when it shipped PSSR 2 to the PS5 Pro as a firmware drop: the box you bought is a substrate for features that did not exist when you paid for it.

Every Image Is 21.8 MB

A small tell: every one of these builds is exactly 21.8 MB. The FPGA bitstream, the OS, the CRT-emulation assets — the whole payload is a fixed-size image that Analogue overwrites wholesale each time. You are not patching the 3D; you are reflashing it. That is why a screenshot feature and a one-line D-pad fix ship in identically sized packages, and why there is no such thing as a partial or incremental update on this hardware.

Where the Version Numbers Jump

The jump from the 1.2.x line to 1.3.0 (May 15) and then 1.4.0 (June 23) is not cosmetic. 1.3.0 introduced save states — a structural change to how the console handles memory — and 1.4.0 added the Gallery. Analogue reserves minor-version bumps for genuinely new subsystems and spends the point-releases on fixes. It is disciplined semantic versioning, which is more than most hardware vendors manage.

What Each Update Actually Fixed

The changelog table flattens a lot of genuinely useful engineering. Here is what the builds that mattered actually delivered.

1.1.9 and 1.2.0: Overclock and Progressive Scan

The 3D ships with a baked-in overclock feature — four tiers, Auto / Enhanced / Enhanced+ / Unleashed, on by default at Auto — that raises the emulated CPU clock to smooth out the N64's notorious framerate dips. The November 1.1.9 build reworked those overclock modes and added a "Disable Texture Filtering" toggle for players who want the raw, unsmoothed texture look, plus manual region selection. Then 1.2.0, on January 30, delivered the feature the CRT crowd had been demanding: Force Progressive Output, which deinterlaces the N64's 480i modes into a clean progressive signal instead of leaving your 4K panel to mangle the fields. The same build turned on wireless controller support.

1.2.3 and 1.2.4: GameShark and the Flash-Cart Fix

1.2.3 (March 13) restored GameShark compatibility — the 3D reads original carts, and that includes the passthrough cheat devices of 1998 — alongside HDR-aware OS brightness and a fix for glitching controller LEDs. But the standout of the March run was 1.2.4 on March 28. Before it, a flash cart like an EverDrive 64 or SummerCart 64 appeared to the console as a single Library entry no matter how many ROMs it held. 1.2.4 added "Advanced Library detection," parsing each ROM's header so every game becomes its own tile with its own saves, rumble settings, and Controller Pak data. Notebookcheck's Rahim Amir Noorali described the result plainly: "switching between ROMs now automatically creates new entries." If you own a flash cart, this was the single most quality-of-life-improving build of the year. If you are still dumping your own carts, our Retrode 2 walkthrough covers the other half of that workflow.

1.2.5, 1.2.6, and 1.3.0: HDR, Flicker, and Save States

1.2.5 (April 10) was the display build — more on that below — and it quietly fixed automatic virtual Rumble Pak selection and alphabetical Library jumping. 1.2.6 (April 24) chased a progressive-output flicker bug that hit games like Resident Evil 2, added nine cartridge shell colors to the Library art, and refined Auto Overclock behavior. Then 1.3.0 (May 15) delivered "Memories," a save-state system spanning the roughly 900 cartridge variants the console recognizes — up to 20 states per game, with the oldest auto-pruned and pinned states preserved. Time Extension called it the console's most significant update yet, and for once the superlative held.

HDR, OLED, and the 1080p Bug

The Analogue 3D outputs up to 4K over HDMI 2.1 with HDR and VRR, and a meaningful slice of its firmware work has gone into making that pipeline behave across the chaotic reality of consumer displays. The 1.2.5 build was where most of that landed.

Advanced HDR and Max Luminance

1.2.5 introduced an Advanced HDR mode tuned for OLED panels and a new Max. Luminance control under Settings > Display. The point is not raw brightness — it is calibration. The 3D's whole premise is recreating how these games looked on a Trinitron in 1997, and a consumer CRT's peak luminance was a fraction of a modern OLED's. Max Luminance lets you clamp the output so the CRT-mask emulation reads as period-accurate instead of blindingly modern. It is the kind of control that only matters to people who care a great deal, which is exactly Analogue's customer.

The ALLM/HDR Bug on 1080p Panels

A correction worth making, because it has been reported wrong elsewhere: the fix for ALLM (Auto Low Latency Mode) and HDR settings applying incorrectly on 1080p displays shipped in 1.2.5, not 1.2.6. Before the fix, 1080p panel owners could see HDR metadata and auto-latency flags negotiated incorrectly, producing washed-out or mistimed output on anything that wasn't a 4K set. 1.2.5 made the negotiation resolution-aware. If you run the 3D on a 1080p monitor — and plenty of people do — this is the build that made HDR usable.

Why This Matters for CRT Chasers

None of this is glamorous, and that is the point. The audience paying $249.99 for an FPGA N64 is, definitionally, the audience that notices when the gamma is off by a hair. Analogue's display firmware is a long, unsexy grind toward a target — the look of original hardware on a good CRT — that most buyers will never see in person again. The GamesRadar+ verdict that the 3D "sets a new bar for retro console remakes" rests substantially on this work.

The Cycle-Accuracy Fight

FPGA hardware is marketed on a single word — accuracy — and in December 2025 the 3D's claim to it got publicly challenged by someone with the standing to do it.

Kaze Emanuar's Teardown

Kaze Emanuar, a veteran N64 homebrew developer whose Super Mario 64 optimization work is genuinely famous in the scene, ran the 3D through a battery of timing tests and did not mince words. Via Notebookcheck, his conclusion: "This thing is nowhere near cycle accurate." His measurements put the emulated CPU running roughly 6% slow, the RSP — the N64's signal co-processor — around 30% slow, and the implementation missing a ninth megabyte of RDRAM that the real console addresses. Aggregate lag, in his testing, ran about 5% off, with specific titles like Diddy Kong Racing rendering frames roughly 4% slower than original hardware. Time Extension's write-up carried the blunt headline "They Lied."

What "Nowhere Near Cycle Accurate" Actually Means

Context matters here. "Cycle accurate" is a specific, demanding claim: that the FPGA reproduces the original silicon's behavior clock-for-clock. The N64 is a notoriously hard target — its RDRAM latency and RSP microcode are exactly the kind of thing that resists clean reimplementation. Analogue's 3D uses an Intel Cyclone 10 GX with roughly 220,000 logic elements, and Kaze's argument is that this budget, or the design built on it, does not fully capture the N64's timing. That is a real technical critique, not a rounding error.

Does It Matter in Practice?

For most players, on most games, no — a 5% aggregate deviation is invisible without a capture card and a reference console side by side. And the 3D's baked-in overclock modes can paper over the N64's framerate problems in a way real hardware never could, which is arguably a feature. But it complicates the marketing. If you want bit-exact behavior, the honest answer is that no current solution — not the 3D, not the software emulators we cover in our RetroArch cores guide — is perfect on N64. The 3D is excellent. It is not, by the strict definition, cycle accurate, and the firmware updates have not changed that.

Installing the Firmware

Analogue distributes every build as a single .bin file from its official support portal. There is no auto-update, no network check, no companion app — because, again, there is no radio. You do this by hand.

The .bin-on-SD-Root Method

The process is deliberately primitive and hard to get wrong. Download the correct .bin, drop it in the root of the 3D's microSD card — not a subfolder — reinsert, and power on. The console detects the image, flashes itself, and reboots. Start to finish it takes three to six minutes, most of which is the FPGA rewriting its bitstream.

1. Download the .bin (e.g. analogue-3d-1.4.0.bin) from
   analogue.co/support/3d/firmware
2. Copy the .bin to the ROOT of the microSD card
   (NOT inside a folder)
3. Reinsert the card and power the console ON
4. Wait 3-6 min: Power LED = yellow, Controller LEDs blink
   -> DO NOT remove power
5. Console auto-reboots when the flash completes
6. Confirm the new version under Settings

Recovery: hold RESET + POWER until the LED turns green
          -> enters USB-C recovery mode

The Boot Sequence and LED Codes

During the flash, the Power LED holds yellow and the Controller port LEDs blink — that is the console writing, and you do not want to cut power here. When it finishes, the 3D reboots on its own and the LEDs return to normal. Verify the version in Settings afterward; the whole point of a fixed 21.8 MB image is that a successful flash is all-or-nothing.

USB-C Recovery Mode

If a flash fails or the console won't boot, there is a hardware recovery path: hold the reset and power buttons together until the LED turns green, which drops the 3D into a USB-C mode for recovery over a cable. It is the closest thing the console has to a safety net, and in seven months of near-fortnightly updates, it has rarely been needed — the SD method is robust precisely because it is dumb.

FPGA Rivals and the Emulation Question

The 3D does not exist in a vacuum. There are three other credible ways to play N64 in 2026, and the firmware cadence is part of what separates them.

MiSTer: The Open-Source Alternative

The obvious FPGA rival is MiSTer, the open-source platform whose N64 core is community-developed and free. It runs on a DE10-Nano board (roughly $225 bare) or a purpose-built unit like the MiSTer Multisystem 2, which starts around £216. MiSTer's strength is breadth — one board plays dozens of systems — and its N64 core has matured impressively. Its weakness against the 3D is polish: no original-cartridge slot, no 4K output, no CRT-mask preservation pipeline, and a setup process that assumes you enjoy the setup process. The 3D is the appliance; MiSTer is the workshop.

Software Emulation on a Handheld or PC

Software emulation remains the cheapest and most flexible route — free, on hardware you likely already own, upscalable past 4K, and endlessly configurable. It is also the least authentic: it inherits your PC's latency, and, as the cycle-accuracy fight underlines, N64 emulation is imperfect everywhere. A modern handheld or a RetroArch install will play the library well; it will not read your original carts or emulate a Trinitron's phosphor mask.

The Comparison Table

The trade-offs, laid out with what each option costs and what it actually delivers:

How Analogue Got Here

The 3D is not Analogue's first rodeo, and the firmware discipline on display is the product of a decade of doing this.

From the Nt to the Pocket to the 3D

Analogue built its reputation on FPGA recreations that court the purist: the Nt and Super Nt (NES and SNES), the Mega Sg (Genesis), the Duo (PC Engine/TurboGrafx), and the runaway hit Analogue Pocket (Game Boy line), which turned firmware updates into a running feature drip of its own. The through-line is a refusal to use software emulation — every Analogue console reimplements the original chips in programmable logic. The 3D is the company's first crack at the N64, and by consensus its most ambitious, because the N64 is the hardest of these machines to get right.

The Three-Year Road to Launch

Analogue announced the 3D on October 16, 2023. It then slipped repeatedly — from an original 2024 window into Q1 2025, then July, then late August, then Q4 — before finally shipping on November 18, 2025 at $249.99. A November 24 restock bumped to $269.99, which Engadget attributed to tariff pressure rather than a price change. For context on the accessory ecosystem: the first-party 8BitDo 64 wireless controller is $39.99, and a compatible EverDrive 64 X7 flash cart runs roughly $175-215 — the cart costs most of what the console does.

Why FPGA, Not Emulation

Analogue's whole thesis is that programmable logic, configured to mirror the original circuitry, produces lower latency and higher fidelity than software chasing the same target on a general-purpose CPU. The 3D's design — original cartridge slot, 4K analog-style output, CRT emulation — is that thesis made physical. Kaze's critique is the counterargument: FPGA is not automatically accurate, only potentially so, and the gap between potential and delivered is where the December fight happened.

What the Reviewers Actually Said

The 3D reviewed extremely well at launch, and the firmware cadence has, if anything, improved the proposition since. The scores clustered high.

The Scores: 8/10 to 9/10

IGN's Seth G. Macy gave it 8/10, calling it "the best possible way to play your N64 library outside of the original hardware hooked up to a CRT." Wired's Matt Kamen went 9/10; Time Extension also landed at 9/10; Digital Foundry called it "the most impressive Analogue 'FPGA' console yet." These are not marginal endorsements — they are the specialist press broadly agreeing the hardware delivers.

The Praise and the Caveats

The most-quoted verdict is also the most honest. Engadget's Tim Stevens summed the tension in one line: "Your Nintendo 64 games never looked so good, but Analogue's greatest system yet can't fix some of the N64's inherent flaws." That is the whole review in a sentence — the 3D perfects the presentation of a library that was, in places, technically compromised on day one in 1996. No firmware can make the N64's fogged draw distances or 20fps dips into something they weren't.

The One Line Everyone Quotes

What the firmware run has done is close the gap between "excellent hardware" and "complete product." At launch the 3D had no save states, no screenshots, no per-ROM flash-cart Library, and a display pipeline with rough edges. Seven months and eleven builds later it has all of those. The reviews were written against the launch firmware; on 1.4.0, the caveats are fewer, even if the fundamental one — you cannot out-engineer 1996 — still stands.

What Happens Next: 6-12 Month Predictions

Eleven builds in seven months is a data set, and it lets us make some grounded bets about where the 3D's firmware goes through mid-2027. Five predictions, in descending confidence.

The Cadence Slows

First: the near-fortnightly pace breaks. The launch-to-1.4.0 sprint cleared the obvious feature backlog — progressive scan, save states, screenshots, flash-cart Library. With those shipped, expect Analogue to settle into six-to-eight-week intervals through the back half of 2026, punctuated by faster point-releases only when a regression demands one. The metronome was a catch-up mechanism, not a permanent state.

Screenshot Transfer Gets Solved — Without WiFi

Second: Joseph Bradford's WiFi wish will be answered, but not with WiFi, because the hardware has no radio. The likeliest fix is USB-C mass-storage export — mount the 3D as a drive over the same cable used for recovery and pull screenshots without ejecting the card. Bet on a 1.4.x or 1.5.0 build addressing screenshot transfer through the port that already exists rather than a radio that doesn't.

Another Accuracy Pass

Third: Kaze Emanuar's teardown left a mark, and Analogue has a history of responding to technical critique in firmware. Expect at least one build in the next year that revisits RSP timing or overclock behavior and is framed, explicitly or not, as an accuracy response. It will not make the console cycle accurate — that ship may have sailed at the silicon level — but it will narrow the measured gap.

The "Memories" System Expands

Fourth: the 20-save-states-per-game cap and the lack of any export path for saves are obvious next targets. A build that raises the cap, adds save export/import over USB-C, or both, is a safe call for late 2026. Preservation is Analogue's stated religion, and locking saves inside the console contradicts it.

The Price Holds — But Restocks Don't

Fifth and least glamorous: the $249.99 MSRP stays, but tariff-exposed restocks continue to surface at $269.99 or higher. The console's price is now a function of trade policy as much as Analogue's intent, and nothing in the firmware changes that. If you want one at MSRP, buy it in a calm week.

The larger point outlasts any single build. Analogue has quietly redefined what "buying" an FPGA console means: you are not purchasing a finished object but a seven-months-and-counting relationship with a changelog. Whether that is a feature or a treadmill depends entirely on how you feel about copying a 21.8 MB file onto an SD card — which, on current evidence, you will be doing again in about three weeks.