AmiFox: Giving Your Amiga a Window onto the Modern Web

A modern browser handles the complicated work elsewhere, while your Amiga keeps the screen, the mouse and the pleasure of being the computer you actually wanted to use.

An evening with an Amiga can take an unexpected turn when you need to look something up. You have the machine running, a project open and perhaps one small question about a piece of software. Then a website expects a browser several decades younger than the computer in front of you. Reaching for a laptop solves the immediate problem. It also interrupts the reason you sat down at the Amiga. Before long, the old machine is waiting patiently while the new one handles everything around it.

AmiFox, developed by ALB42 with the AmiDev team, offers another route. It lets the Amiga control a modern browser running on a server and displays the resulting pages as images. The demanding part of the web happens elsewhere; you carry on using the familiar machine. There is something satisfying about an Amiga delegating a job. After all these years of being told it needs an upgrade, it has found an assistant.

A modern browser does the work elsewhere

AmiFox builds on Web Rendering Proxy, usually shortened to WRP. A browser on the server opens the requested website, renders its contents and produces an image that the older computer can display. The AmiFox client sends mouse clicks and keystrokes back to that browser. Follow a link or enter a search, and the remote session responds. The Amiga receives another view of the result.

This arrangement moves the difficult work to a machine equipped to handle it. Modern page layout and JavaScript run in the remote browser. The Amiga concentrates on displaying the page and passing along your instructions. The distinction matters when describing what the program achieves. You are using the web from an Amiga, with a modern computer participating in the process. AmiFox has not somehow squeezed Chrome into a few megabytes of memory.

It also takes a different approach from reducing a website to plain text or simplified HTML. Its page display preserves a rendered view of the site, including the layout. That can help you recognise where things are, although everything still has to fit the screen you are using.

The picture can answer back

A page delivered as an image sounds rather limited until you consider what is happening behind it. The buttons and text fields still exist inside the browser on the server. AmiFox gives you a way to operate them. The adapted AmiFox server supports clicking and dragging, which is useful for scrollbars and selecting text. Selected text can be copied back to the client, and there is support for retrieving the remote clipboard when a website puts something there.

Those small interactions make a considerable difference. Reading a useful command is one thing. Being able to bring the actual text back to the Amiga makes it part of what you are doing. There is still a journey between your action and the updated picture. A reasonable expectation is that the experience will depend on the connection, the server and the Amiga’s ability to handle the images. A page of instructions gives you time to read between actions; an interface that constantly changes asks much more of the arrangement. The useful question is whether the particular task feels comfortable. Finding an answer and copying a paragraph is a perfectly respectable evening’s work.

Getting software onto the machine

The most convincing use for an Amiga browser may be finding something else to run on the Amiga. AmiFox’s development has paid attention to that connection. Version 0.3 added conveniences including detecting the link beneath the pointer and downloading from that URL. Its release notes also describe mouse-wheel support and sending longer passages of text to a page.

Later work addressed downloads from itch.io, where a download button can involve more than following an ordinary file link. That support arrived in version 0.5, alongside the ability to display the current URL as a QR code for opening on another device. This gives the project a practical purpose beyond the initial surprise of seeing a contemporary website on an old screen. You can look for a new game or utility and use supported download routes to bring it into the same working environment.

Downloads still deserve to be treated separately from page display. Seeing a page correctly does not guarantee that every protected download or complicated login sequence will work. Try the route you actually need before building a routine around it.

Give the Amiga a sensible starting point

As of 8 October 2026, the official download page lists version 0.6. Its release announcement dates from 26 February 2024 and describes preferred-language settings and a browsing-history feature. The download choices include separate builds for 68020-and-later Amigas and the 68000, plus several AROS targets. Choose the archive intended for your system. For the main 68020 build, the project guide specifies AmigaOS 3.x, 8 MB of RAM, MUI 3.8 or later and a TCP/IP stack providing bsdsocket.library version 4 or later. Those requirements should not be mistaken for a promise that an unexpanded Amiga can simply launch the program.

Image settings also deserve attention. AmiFox supports PNG, GIF, JPEG and IFF, with suitable datatypes needed for the first three. The guide notes that IFF support is built into AmigaOS 3.0 and later. Start with a modest page size and settings appropriate to the display. Capturing an entire long website produces a large image, which needs memory and time to process. Making the remote browser do the rendering does not remove the Amiga’s local limits. A readable page is a better starting point than an ambitious screenshot.

Some tasks still need another application

Video makes the limits of this approach particularly clear. A picture of a video player does not provide the experience of watching the video.

The AmiFox guide directs YouTube viewing to AmiTube, and AmiFox can pass YouTube URLs to that separate application. The documented integrations also include sending Google Maps and OpenStreetMap positions to Mapparium, with platform-specific restrictions. There is an appealing familiarity to this. One application helps you find something; another handles the job it was designed for. On a computer where resources matter, that division can be useful.

It also suggests a sensible way to approach AmiFox generally. Begin with reading, searching and supported downloads. Treat demanding web applications as experiments whose usefulness depends on their particular behaviour. A modern browser at the other end improves the possibilities. It cannot make every interaction equally comfortable on the machine at this end.

The server can live closer to home

The remote browser does not have to remain somebody else’s responsibility. ALB42 provides an AmiFox-specific version of WRP, with additions for the native client. These include IFF images, clipboard operations, downloads, encrypted connections and token-based access. The project has also offered server builds for Windows, macOS and Linux, including Raspberry Pi, alongside a Docker route. The host needs the appropriate supporting software, including a compatible Chrome or Chromium installation.

AmiFox can be pointed at your server through its icon tooltypes. The documented settings include WRPSERVER for the address and WRPTOKEN when the server requires an access token. For someone already running a suitable computer at home, this opens an interesting possibility: give that machine the browser workload and keep the Amiga as the place where you sit and work. Running the server also means maintaining it. The browser, operating system and access settings become part of the setup. That is a reasonable hobby project in its own right, especially if understanding how the pieces connect is part of the attraction.

Know where your browsing session lives

AmiFox’s security explanation is unusually direct about the trust involved. With AmiSSL installed, the client can use an encrypted connection to the server. The lower-right padlock indicates whether that connection is secured. Without AmiSSL, the documented behaviour is to fall back to an unencrypted connection.

Encryption protects that connection, but the browser session still runs on the server. The project explicitly acknowledges that administrators of the hosting system could theoretically access information inside it. That matters whenever you enter account details or open private information. The server operator is part of the trust decision, even when the padlock is closed.

For an initial experiment, public articles, documentation and software pages give you plenty to explore without introducing sensitive accounts. Hosting the server yourself changes who controls that part of the process, while leaving you responsible for looking after it. The arrangement is easier to use sensibly when you know where each piece of the work happens.

A reason to stay at the Amiga

There is a small but meaningful difference between keeping an old computer working and giving it something useful to do. A machine can be beautifully restored, carefully expanded and perfectly capable of running its familiar software, yet still sit outside the flow of an ordinary evening. Every missing convenience becomes another reason to turn to something else.

AmiFox offers a way to close part of that gap. A search, a set of instructions or a supported software download can remain part of the time spent at the Amiga. Whether that is enough depends on what you enjoy doing there. Start with something modest. Look up a utility, read about a new game or find the answer to the question that would normally send you to the laptop. Your Amiga has already waited long enough for you to come back.

More information: AmiFox on ALB42’s project page.