WebFloppy

An Amiga disk library that puts a disk in a real Amiga's floppy drive over WiFi. (The repository keeps the project's first name, webadf.)

Two halves that work together:

• A web app for keeping Amiga disk images. Add them, have them identified against TOSEC, OpenRetro and Demozoo, organise them into collections, browse and edit the files inside a disk, rewind a disk to any earlier version, and send files to and from the Amiga.
• A drive replacement. An RP2350 board plugs into the Amiga's floppy connector, behaves like a DD or HD floppy drive, and plays whichever disk you pick in the web app. When the Amiga saves, the changes go back to the library.

Run the web app two ways: use our hosted copy at https://webadf.vercel.app (on Vercel), or host your own with Docker on any amd64 or arm64 machine, a NAS included. A self-hosted copy has every feature the hosted one has. Firmware updates, the PaulaNET driver disk and the TOSEC catalogue arrive by themselves; see docs/self-hosting.md.

Pick a disk in the browser, or tap its NFC tag on the drive, and the Amiga reads it. Workbench 3.1 boots from the board, games load, and saves made on the Amiga show up in the web app as new versions of the disk.

Rev B, designed by Shanshe: 34-pin floppy header, floppy power connector, OLED display, buzzer, a 4-pin header (J4), and a Pimoroni Pico Plus 2 W. The KiCad project is in wifi-floppy/hardware/; check it with pnpm hw:verify before ordering. Rev B has been the bench board since October 2026.

Bugs and ideas

Found a bug, or want something WebFloppy does not do yet? Anyone can open an issue at https://github.com/stefanskotte/webadf/issues, for a bug report or a feature request alike. For a bug, say what you did, what you saw and, for a board, which firmware it runs (Devices shows it).

Quickstart

Choose where the web app runs. The board's first install is the same either way; only a self-hosted copy needs one extra step, pointing the board at your server.

Path A: the hosted web app (Vercel)

You need the board, a USB cable, a phone and an account on https://webadf.vercel.app (registration is by invitation). The board talks to this server out of the box.

1. Hold the BOOT button (the Raspberry Pi docs call it BOOTSEL) and plug the board into your computer over USB. A drive called RP2350 appears.

2. Download wifi-floppy-install-<version>.uf2 from the latest release and drag it onto that drive. The board writes it and restarts by itself; the drive disappears.

3. Get a pairing code in the web app. The code comes from the web app, not the board. Open Devices: with no board yet it lists the five steps (How pairing works shows them again at any time). Press Pair a device, give the board a name and press Get a code. The code lasts 30 minutes, and the page now walks you through the rest with the code filled in.

4. Give the board your Wi-Fi and the code. Power the board; its screen shows Setup needed and its own Wi-Fi network, wifi-floppy-XXXX. Join that network from your phone (password wififloppy). The setup page opens by itself; if it does not, browse to http://192.168.4.1/. Enter your home Wi-Fi name and password (a 2.4 GHz network with a password) and the code, and press Save.

5. Wait about a minute. The board's network disappears, the board joins your Wi-Fi and uses the code to register with the web app. Keep the Devices page open: it says Paired and shows the board by itself. If the board cannot join or register, its setup network comes back with the reason at the top of the setup page; join it again and fix that. Firmware updates now arrive over the air from the web app.

Path B: your own server (self-hosted, Docker)

You need a host with Docker and Compose v2, the board, a USB cable and a phone.

1. Install the stack, as docs/self-hosting.md describes: download compose.yaml and .env.example (as .env) from the newest web-X.Y.Z tag, set WEBADF_URL (for example https://192.168.1.10) and WEBADF_ADMIN_EMAIL in .env, then run docker compose up -d. Create the account with the link from docker compose logs app | grep 'first admin'.

2. Install the firmware as in steps 1-2 of Path A.

3. Override the server. The firmware points at the hosted app by default. Open the board's USB serial console (any serial terminal, firmware 1.13.0 or newer) and type:

   wf server set https://192.168.1.10
   wf server tls noverify
   YES
   wf reboot
   

   Use your own WEBADF_URL. tls noverify is needed because a board cannot trust the certificate Caddy makes for an IP address or a LAN name; with a public WEBADF_DOMAIN and a Let's Encrypt certificate, leave it out. wf server show prints the setting and wf server clear goes back to the hosted app. Changing the server forgets the board's Wi-Fi and pairing, and it refuses while a disk is mounted.

4. Pair it as in steps 3-5 of Path A, from Devices on your own server. Firmware updates come from your server too: it imports every signed release from GitHub daily.

This is the beginning of the README. Read the rest at the original. Read the full README ↗