⏱️ Reading time: 9 min
Floppy3.5 takes a 3.5-inch slimline floppy disk drive and turns it into a WiFi NAS: inside the shell sit two microcontrollers, a lithium battery and a microSD slot, according to the project’s GitHub repository (bigcrimping/floppy3.5). The goal is simple: read photos off 1.44 MB FAT12 floppy disks, the kind used by old digital cameras like the Sony Mavica, and display them in a browser with no cables and no desktop computer involved.
📑 En este artículo
- From Mavica Cameras to a WiFi NAS That Fits in Your Hand
- Two Microcontrollers and a Protocol Inherited From Greaseweazle
- The Steps to Build the Board and Flash the Firmware
- What Happened When We Cloned the Repo in a Sandbox
- What the Community Discusses on Hacker News
- What This Means If You Build Embedded Hardware
- Floppy3.5 vs. Greaseweazle and the Traditional USB Adapter
- Real Limitations Before Ordering the Board
- References
From Mavica Cameras to a WiFi NAS That Fits in Your Hand
The project is maintained by GitHub user bigcrimping. It reads any 1.44 MB FAT12 floppy disk, shows the files in the root folder on a web page, and lets you copy them to a microSD card so you can keep shooting without running out of space, according to the official repository. The use case that drove the design is digital cameras from the 1990s and 2000s that recorded directly onto 3.5-inch floppy disks, such as Sony’s Mavica line: anyone who still has those floppies stored away can recover the photos without relying on a USB floppy reader plugged into a laptop.
For an embedded developer or an open hardware hobbyist, the interest goes beyond recovering old photos. Floppy3.5 is also a complete reference design (PCB, schematic, firmware for two different architectures and a 3D-printed enclosure) published under an open license, something uncommon in gadgets this size.
Two Microcontrollers and a Protocol Inherited From Greaseweazle
All the electronics live on a single board, according to the schematic published in the repository. An RP2354A controller talks directly to the floppy drive over a 26-pin cable. It uses the Greaseweazle host protocol, the reference project for reading and writing floppy disks from a computer. That is why the same controller can also connect over USB and be used with the gw tool, just like a regular Greaseweazle adapter.
An ESP32-S3-WROOM-1 bridge (16 MB of flash, 8 MB of PSRAM) receives data from the RP2354A over a dedicated SPI link, decodes the disk and serves the photos on a web page reachable at floppy.local. The rest of the board handles power and status: a BQ25180 charger, a MAX17048 fuel gauge, an LTC2954 power button controller, two regulators (TPS63020 for 3.3 V and TPS61022 for the 5 V the floppy drive needs) and an RV-3028-C7 real-time clock. Both firmwares (the RP2354A’s, built with pico-sdk, and the ESP32-S3’s, built with ESP-IDF) update over OTA, so there is no need to open the case to install a new version.
flowchart LR
A["3.5-inch slimline floppy drive"] -->|"26 pins"| B["RP2354A: controller"]
B -->|"SPI"| C["ESP32-S3: WiFi bridge"]
C -->|"WiFi"| D["Browser at floppy.local"]
C --> E[("microSD DISKnnnn")]
The Steps to Build the Board and Flash the Firmware
The repository does not sell a kit: you have to manufacture the board, source the components and assemble it by hand, according to the official guide. The documented steps are:
- Order the PCB using the Gerber files included in the repository.
- Buy the components and solder them following the schematic and the assembly diagram.
- Install the LiPo battery before powering the board: without it, the voltage drops too much when only USB is connected and the board will not boot.
- Flash the self-test firmware (
firmware/esp32-bringup/) and confirm over the serial port that all tests pass. - Install the final firmware, available on the repository’s Releases page.
- 3D print the two case halves and the button sheet, put insulating tape over the floppy drive, and join the pieces with M2.5 screws over heat-set inserts.
⚠️ Caution: the repository itself warns that connecting the LiPo battery with reversed polarity can damage it, and a damaged battery can cause a fire. Check the connector twice before powering the board.
What Happened When We Cloned the Repo in a Sandbox
Before writing anything, we tested the repository in an isolated environment, as we do with any repo or package that enters the editorial tournament. The environment ran on Linux, Python 3.12.16, Node v18.20.4 and git 2.39.5, with no additional network access enabled.
In our test (2026-11-20) we ran this command:
$ git -c protocol.allow=never -c protocol.https.allow=always -c core.hooksPath=/dev/null clone --depth 1 --single-branch --no-tags -- https://github.com/bigcrimping/floppy3.5 /tmp/lab-runs/lab-3d5n1nyw/w/repo
Cloning into '/tmp/lab-runs/lab-3d5n1nyw/w/repo'...
The clone finished in 1.21 seconds, the repository weighs 9.4 MB, and the process used a peak memory of 56.1 MB. Nothing unusual so far. But the next step, automatically detecting what software stack needs to be installed or built, returned “no supported stack detected”: the lab found nothing it recognized as an installable package.
That failure is, in itself, the most useful data point from the test. floppy3.5 has no pip install or npm install that leaves it running: it is a PCB design (Gerber files and schematic) plus two firmwares for different architectures, pico-sdk for the RP2354A and ESP-IDF for the ESP32-S3, which first need a physical, soldered board before they can be flashed. Our sandbox is built for software repos and packages; an open hardware project like this correctly falls outside its scope.
What the Community Discusses on Hacker News
The project reached the Hacker News front page twice, with separate threads for each version of the announcement (thread and thread). The comments raise nuances the repository does not mention.
User sandworm101 says they tried several router-based options for sharing a drive over WiFi among multiple devices, and none held up past about ten simultaneous users. In their experience, the bottleneck is not WiFi but the USB interface, which is why they believe an NVMe-based option would perform better (comment). This is one user’s opinion, not a verified fact, but it is relevant when thinking about the limits of any USB-based homemade WiFi NAS, including floppy3.5.
Another comment, from netsharc, raises a power problem when copying photos from an old phone connected over USB OTG: with a phone from that era, not even a powered USB hub could keep it charged during the copy, because the phone only had USB 2.0 (comment). User away0g agrees that nobody makes modern versions of this type of file-recovery gadget today (comment), which explains part of the attention a project designed and built by a single person received.
What This Means If You Build Embedded Hardware
For someone who already works with ESP32 or RP2040-style microcontrollers and wants to see a complete reference design, floppy3.5 is worth studying for its SPI link pattern between two MCUs with separate responsibilities: one talks to the mechanical peripheral, the other exposes WiFi. The schematic and Gerber files are open, so the design can be studied without ordering the board.
If the goal instead is to recover photos from your own floppy disks, the practical decision is simpler: find a compatible 26-pin slimline floppy drive (the repository uses a Sony MPF920-type unit as reference) and weigh whether soldering a full board is worth it or a USB floppy adapter plus a nearby computer is enough. Before ordering the PCB, check the LiPo battery connector twice, given the repository’s own polarity warning.
And if the idea is to scale this into a WiFi NAS for several people, sandworm101’s comment is the most concrete warning in this whole piece: the real limit of a homemade USB-based NAS is usually the USB interface, not WiFi, so adding more antenna does not fix anything if the bottleneck is in the data bus.
Floppy3.5 vs. Greaseweazle and the Traditional USB Adapter
Floppy3.5 is not a replacement for Greaseweazle: it is a standalone variant built to share photos over WiFi without a nearby computer, built on the same host protocol that project uses. The table below summarizes the differences between the three ways to get files off a 3.5-inch floppy disk today.
| Project or method | Needs a connected computer | How files are accessed | Power |
|---|---|---|---|
| Floppy3.5 | No | WiFi, from any browser at floppy.local | Its own LiPo battery, charged over USB |
| Greaseweazle | Yes | USB cable to a computer running the gw software | Powered by the host USB port |
| Traditional USB floppy adapter | Yes | USB cable, the operating system mounts the disk | Powered by the host USB port |
The core difference is that Greaseweazle and traditional USB adapters depend on having a computer nearby and powered on. Floppy3.5 trades that dependency for a battery and a WiFi radio, at the cost of a more complex board and manual assembly. According to away0g on Hacker News, almost no modern alternatives remain in this niche, which leaves floppy3.5 with almost no direct competition outside the two categories in the table.
Real Limitations Before Ordering the Board
- FAT12 1.44 MB only. The repository says it reads any 1.44 MB HD FAT12 floppy disk; it does not mention support for 720 KB double-density formats or for file systems other than FAT.
- A very young project. The repository’s commit history on GitHub showed only two commits as of 2026-11-20, a sign that documentation and community support are still limited.
- Not an installable software stack. As our sandbox test showed, replicating it requires manufacturing a PCB, soldering components and flashing two different firmwares: there is no single command that gets it running.
- Real battery risk. The repository itself warns about the fire risk if the LiPo is connected with reversed polarity.
- No confirmed performance under multiple simultaneous files. Neither the repository nor our test measured how fast it copies to the microSD with several users connected at once; sandworm101’s comment on Hacker News suggests that has historically been the weak point of this kind of device.
References
- floppy3.5 repository on GitHub: project description, component list, schematic and assembly guide.
- Board schematic (hardware/schematic.pdf): values for each component and connections.
- Repository Releases page: ready-to-install firmware for the RP2354A and the ESP32-S3.
- Hacker News thread about floppy3.5: community discussion of the project.
- Comment from sandworm101 on Hacker News: experience with homemade USB NAS setups and the interface bottleneck.
Featured image: Foto de Akshat Sharma en Unsplash
How each article is made (sources, testing and editorial criteria): How we work.
Did it work for you? Got a different error? Say so below: questions get answered and help the next reader.
Leave a comment
0 Comments