Nanolathe RTS Engine ⚡ Total Annihilation Online Demo (2026)
Play the Total Annihilation browser demo with the Nanolathe RTS engine—3 missions online. Try the open-source RTS engine or install the Nanolathe native beta.
Nanolathe Brings Total Annihilation to the Browser - and Opens the Engine
Real-time strategy games are easy to remember and surprisingly hard to run again. Old files, odd compatibility quirks, and dated display settings can turn a quick "just one mission" return into an actual setup project. Nanolathe takes a different approach: it's an open-source 2.5D engine that lets you play three original Total Annihilation demo missions in a desktop browser - no game folder required.
That browser demo is just the entry point. Nanolathe also has a native beta for Windows, Mac, and Linux. If you provide the game files from a copy you own, you can access more single-player content, including skirmishes and online play. The project also publishes its engine code and details of its clean-room research so people can study and extend it.
Below is what you get in the browser, what changes in the native beta, what the rendering and camera differences actually mean, and where the beta's limits show up - so you can decide whether to install or contribute.
What Nanolathe is - and what it isn't
Nanolathe is an independent, open-source engine that aims to reimplement Total Annihilation. It uses clean-room research: the project studies how the original game behaves and the documented structure of its files, then builds an engine that can work with the original game data. Its code is MIT licensed, so developers can inspect, modify, and build on it.
Here's the key separation: the MIT license covers Nanolathe's code, not Total Annihilation's original assets. The browser demo includes the original three-mission demo, which is why you can try it without providing a game folder. For the full native experience, you'll still need the game files from a copy you own - such as a GOG or Steam release, or your original CDs.
Nanolathe isn't an official release, remaster, or endorsement from the game's owners. It's a community technical project that uses separately supplied original data. That matters because it tells you what you can do: play with the engine, and use the engine as a codebase to explore.
A playable project, not just an engine experiment
A lot of open-source engines make you imagine the final experience from a repo, a build guide, and a few screenshots. Nanolathe lets you test the engine against actual missions - units and effects included - before you decide whether to install the beta or dig into the code.
The project's focus is straightforward: play it, understand it, and build on it. Players can use the browser demo to get a feel for controls and presentation. Developers can examine the engine's design, read about game formats, and follow the documentation behind its behavior. Modders can experiment with the engine, and contributors can work on an implementation that's already tied to a playable game.
That said, "playable" doesn't mean "complete." The beta still has bugs, some missing features, and differences that can depend on the content you load. The upside is that you can test the current state directly, rather than waiting for a promise about what the engine might become later.
Why the distinction matters to players and developers
If you're a player, the question is simple: do you just want to try the included demo, or do you want access to the full native experience? The demo is the low-friction option. The native beta is the path to more content, but it requires your own game data and comes with the realities of beta software.
If you're a developer, licensing and provenance are the real issue. An MIT-licensed engine is inspectable and adaptable, but it doesn't automatically grant rights to the original game's art, audio, or other content. Nanolathe's clean-room approach and documentation are part of the project's technical foundation - and also part of why you should read the material carefully if you plan to build anything that relies on its implementation or data workflow.
Visit Nanolathe to try the demo and explore the project's engine and research material.
How the browser demo and native beta differ
The browser version is built for a quick first test. Use the site on a desktop computer in Chrome, Edge, or Safari. Then use a keyboard and mouse, pick a demo mission, and start playing. The demo files download when you begin and are cached for later visits. You don't install the full game, and the browser doesn't need you to point it at a game folder.
The boundary is also clear: the browser demo only includes the original three-mission demo, not the complete campaign or the native beta's wider mode set. It's a way to try Nanolathe, not a replacement for the full game.
Firefox, phones, and tablets haven't been verified, so it's risky to assume it will work well on touchscreen devices just because it runs in a browser.
What you get in the browser
Use the browser version if you want to check the engine's feel before committing to a larger install. You can test the closer camera, compare Modern and Classic presentation, and play the included missions on supported desktop browsers.
A few practical points:
- You need a desktop computer, keyboard, and mouse.
- Chrome, Edge, and Safari are the supported desktop browsers listed by the project.
- Firefox and mobile or tablet play haven't been verified.
- The demo includes three original missions and doesn't require a game folder.
- The demo can't be used for online multiplayer.
- Demo files download when you start playing and are cached for your next visit.
That's a reasonable split: it lowers the barrier to trying the engine without giving the impression that you're getting the full game repackaged as a no-install web app.
What the native beta adds
The native beta runs on Windows, Mac, and Linux. With your own Total Annihilation game files, it supports a broader set of modes, including campaign, skirmish, and Survival. The project describes single-player skirmish, Survival, and campaign as broadly complete - but that still doesn't guarantee every mission, save, or content pack behaves identically.
The native beta is also where online battles come in. Players can create or join games using their own game data. The bigger scope also brings the usual beta trade-off: more you have to install and configure, and more room for compatibility issues depending on the mission or content pack you run. Save compatibility is still being refined.
| If you want to... | Use... | Keep in mind... |
|---|---|---|
| Try Nanolathe with minimal setup | Browser demo | Three missions; no online play |
| Play broader single-player content | Native beta | Requires game files you own; beta limitations apply |
| Play with friends | Native beta | Everyone needs their own game files |
| Study or extend the engine | Open-source project | Engine license and game-content rights are separate |
The decision isn't really "browser vs native" in the abstract. It's whether you want a quick, bounded demo - or the more complete experience that depends on game files and a beta install.
Modern rendering, closer camera, and comparison details
Nanolathe's Modern presentation is meant to make the original isometric battlefield easier to read at a closer scale. You can zoom in on units and action, and lighting/glow plus extra visual detail aim for a more contemporary look. If you'd rather keep the original style, there's Classic.
This choice matters because visual changes aren't automatically improvements for everyone. A brighter effect or sharper sprite can make things easier to track, but it can also shift the mood and the "feel" of what you remember. Having a Classic option lets you stick to the presentation you prefer rather than getting locked into one interpretation.
What the comparison is showing
Nanolathe uses a same-scene comparison to show differences between rendering paths. The project says the comparison was captured with engine revision 617540c5 on October 4, 2026. It also notes that Modern includes supersampling and its default presentation effects - so you're comparing full rendering paths, not just a single isolated toggle.
The project also explains how the images were prepared. It starts with original 32-by-32 game tiles, then makes synthesized 64-by-64 tiles. "Healthy" tree sprites use real 2× synthesized feature banks; shadow or missing variants fall back to the engine's normal behavior. The staged display clears authored dead stumps. Per the project, the screenshots weren't cropped, retouched, or resampled, and the WebP exports decode to the exact captured pixels.
Those details help you interpret the comparison. A modern-looking result isn't automatically proof that someone just enlarged and touched up a screenshot. The point is that different rendering paths produce different output - and the documentation tells you where synthesized assets and fallback behavior show up in the pipeline.
What zoom changes - and what it doesn't
A closer camera affects how you inspect the battlefield. Units and impacts take up more of the screen, and lighting effects are easier to notice. That can make the action feel more immediate, but it doesn't magically turn Total Annihilation into a different genre or remove the information-management demands of real-time strategy.
What you should check is whether the presentation helps you follow the action without making the battlefield harder to scan. If part of what you like about Total Annihilation is the original isometric view, Classic gives you a way back. If you want more visual detail, Modern is available without forcing you to treat it as the only "correct" version.
For developers, the comparison also gives a concrete view into the project's work on rendering and asset handling. It's not a substitute for reading the code or technical documentation, but it can be a helpful reference point - rather than just a promotional claim that "it looks better."
Multiplayer, maturity, and practical limitations
The native beta supports online skirmish and Survival when everyone uses their own game files. The browser demo's three missions don't support online play. That's a real difference: if your goal is to play with friends, you'll need the installed native beta as part of the requirement.
To start an online game, choose MULTI from the main menu, create a game, and share the game code with friends - or join using a code someone sends. Skirmish supports two to ten players. Survival supports two or three. The host can pick Modern, Community 3.9, or Strict 3.1 rules, and can add computer-controlled players. In battle, players can chat, share, and form alliances.
What to check before inviting a group
Everyone needs their own Total Annihilation game files. The host's game code doesn't replace that requirement, and the browser demo isn't a shortcut for guests who don't own the data. If you're setting up a first session, confirm that everyone has the native beta installed and their game files ready before you schedule a longer match.
The rules options are useful, but they also add a coordination step. Pick the rules before the match and tell players what to expect. It's small, but it avoids a common multiplayer problem: assuming everyone is joining the same configuration when the host selected something else.
Every skirmish and Survival battle is recorded as a replay. Replays help you revisit a match, check what happened, and share a battle after the session. They're especially handy in an evolving beta, where it's easier to review a recorded game than to reconstruct events from memory.
Treat it as a beta, not a finished compatibility layer
The project describes campaign, skirmish, and Survival as broadly complete in single-player, but it also notes bugs, smaller missing features, and compatibility variation. A mission that works on one setup or content pack may behave differently on another. Save compatibility is still being refined.
That's not a reason to avoid the project - it's a reason to calibrate expectations. Use the browser demo when you want a quick, low-risk introduction. Use the native beta when you want the larger game experience and you're ready to troubleshoot occasional issues. If a specific mission or save is essential for you, test it early rather than assuming compatibility based on the feature list.
And if you're evaluating Nanolathe as a development project, the same principle applies: check what's implemented, read the documentation, and test the specific content you care about. "Open source" is an invitation to verify and contribute, not a guarantee that every edge case is already handled.
Conclusion
Nanolathe makes Total Annihilation easier to try and easier to inspect if you're the sort of person who wants to look under the hood. The browser demo gives you three missions without a game folder; the native beta expands the experience for people who own the original game files. Modern and Classic rendering give you a choice in presentation, while the open-source engine and research provide a starting point for developers and modders.
The trade-off is simple: the fastest path is deliberately limited, and the full path is still beta software. If you just want to see how it feels, start with the desktop demo. If you want campaigns, skirmishes, or online play, check the requirements, bring your own game data, and expect the occasional rough edge. Then, if the project interests you, dig into the code and decide whether you want to build on it.