AWeb 3.6 Beta 8 brings the classic Amiga web browser back to life

There is something wonderfully stubborn about a web browser for the Amiga receiving a new release in 2026. The modern web has become enormous, noisy and heavy, packed with video, web apps, JavaScript frameworks and browser engines that feel almost like operating systems in their own right. Against that backdrop, AWeb 3.6 Beta 8 feels less like a throwback and more like an act of preservation with a pulse. The latest release, AWeb 3.6 Beta 8, is listed by the amigazen project as arriving in May 2026. It marks the newest step in what the project calls a comprehensive fork and modernisation of the legendary AWeb browser for Amiga.

Why Beta 8 matters

This is not simply an old browser being dusted off and repackaged. AWeb 3.6 Beta 8 is part of a much bigger effort to rebuild AWeb for today’s Amiga users while keeping it true to the machine it came from. The update brings a long list of improvements, including full HTML 2.0 and HTML 3.2 support, many HTML 4.0 features, experimental CSS, a JavaScript 1.5 engine compatible with ECMAScript 3, XMLHttpRequest support, a rewritten HTTP client, Markdown rendering, XHTML 1.0 support and stronger HTTPS security through AmiSSL v5.25.

On a modern PC, that might sound modest. On a classic Amiga, it is a serious piece of work. The Amiga was built for a very different computing age, one where efficiency mattered, software felt close to the hardware, and a program did not need half the machine just to open a window. AWeb 3.6 Beta 8 understands that heritage. It does not try to turn the Amiga into a modern web appliance. It tries to make the Amiga better at being itself.

The web changed. The Amiga did not.

The problem facing any classic browser is not just page layout. It is connection itself. Over the years, the web has moved behind HTTPS, compression, certificates, newer server behaviour and layers of scripting that older browsers were never designed to understand. That is why one of the most important parts of this release is hidden in the plumbing. AWeb 3.6 includes a completely rewritten HTTP client with HTTP/1.1, gzip and chunked encoding support. It also adds enhanced HTTPS support with TLS 1.2 and 1.3, SNI and certificate validation.

These are not glamorous features, but they are the difference between a browser that belongs only in a screenshot and one that can still have a practical role. AWeb will not make today’s web lightweight again, but it gives Amiga users a better chance of reaching simpler modern pages, local documentation, retro-friendly sites and web services designed with older machines in mind.

Still unmistakably Amiga

What makes AWeb interesting is not only that it browses the web. It is that it does so in a way that feels native to the Amiga. The amigazen project points to AWeb’s deep integration with the Amiga environment, including ReAction, DataTypes, ARexx and the system’s modular BOOPSI and shared library architecture. That matters because the Amiga was never just another platform. It had its own way of doing things, and the best Amiga software always felt like it belonged there rather than being forced onto it.

Beta 8 continues that spirit. It builds against NDK 3.2 Release 4 and ReAction instead of ClassAct, includes P96 graphics support, runs as a Commodity manageable from Exchange, and adds a new about: URL system with pages for home, fonts, plugins and version information.

More than a browser

One of the most quietly useful additions is Markdown support. That might not sound spectacular, but it makes AWeb more useful beyond traditional web browsing. Markdown is now everywhere in software projects: readme files, documentation, release notes, manuals and developer notes. By adding Markdown rendering, AWeb becomes a native way to read modern documentation on an Amiga. The standalone AWebView tool pushes that idea further, offering a separate viewer for HTML and Markdown files. This is where AWeb 3.6 starts to feel especially smart. It is not only trying to visit websites. It is becoming part of the Amiga’s reading and documentation environment.

A realistic browser for a realistic retro world

The project is refreshingly honest about what AWeb 3.6 is not. It will not handle modern websites that depend on HTML5, CSS3, video content, heavy JavaScript, WebAssembly or WebGL. The page makes that clear. That honesty is one of the release’s strengths. Nobody benefits from pretending a classic Amiga can casually browse the modern internet like a current laptop. AWeb 3.6 Beta 8 is more interesting because it accepts the limits and works intelligently inside them. For Amiga-friendly pages, preserved web content, lightweight sites, local HTML, Markdown documents, retro proxies and carefully designed web services, AWeb still has a reason to exist. It occupies a space that modern browsers have abandoned: small, native, personal and understandable.

Installation keeps things simple

In true Amiga fashion, installation is straightforward. The current release does not require an installer script. Users can unpack the LhA archive and run AWeb from its folder. The latest Beta 8 release is also listed as CPU-optimised for 68020 CPUs. There are practical limits, of course. The project notes that while AWeb 3.6 keeps the same requirements as the original 3.4 release, many HTML 3 and HTML 4-era websites still need a meaningful amount of memory. It suggests that 8MB Fast RAM is probably a sensible minimum, and notes that some new defaults assume a more powerful Amiga than would have been common in the 1990s. That feels fair. Retro computing has always involved a little patience, a little compromise and a lot of affection.

Looking toward the 2008 web

The long-term goal is not to chase the full modern internet. Instead, the project aims to move AWeb toward support for features such as CSS and CSS2, HTML standards up to XHTML, XMLHttpRequest in JavaScript and a DOM. The stated ambition is to reach compatibility roughly equivalent to web content from around 2008 to 2010. That is a clever target. The web of that era was already useful and recognisably modern, but not yet as punishingly heavy as today’s framework-driven landscape. For the Amiga scene, that could be enough to open a meaningful middle ground: not the modern web as it exists now, but a sustainable retro web that old machines can genuinely enjoy.

Verdict: a browser revival with heart

AWeb 3.6 Beta 8 is not exciting because it makes the Amiga modern. It is exciting because it respects why the Amiga still matters. This release treats the platform as something alive, not something sealed behind glass. It improves the parts that matter, updates the foundations, adds practical document support, strengthens networking and keeps the browser rooted in the character of AmigaOS. For most people, AWeb 3.6 Beta 8 will be a curiosity. For Amiga users, it is warmer than that. It is proof that old software can still have a future, and that even a browser from another age can wake up, connect, render a page and remind us why this machine still has a community around it. AWeb 3.6 Beta 8 is not trying to win the browser wars. It is doing something better: keeping the Amiga online, one carefully rendered page at a time.

Spread the love