FlipperHTTP: giving a Flipper Zero WiFi and an HTTP client over an ESP32 board

A microcontroller on the Flipper's expansion pins, talking HTTP

FlipperHTTP is an HTTP library for the Flipper Zero, and the interesting part is where the HTTP client actually runs. The Flipper Zero has no WiFi radio of its own, so the project pairs it with an external board, most often an ESP32 variant, and puts the firmware on that board. The Flipper then drives it over the serial pins on its expansion connector.

The supported hardware list is long. The README names the WiFi Developer Board, the Video Game Module, the Raspberry Pi Pico W, the Pico 2 W, the Raspberry Pi Zero 2 W, the ESP32-S3, ESP32-C3, ESP32-C5, ESP32-C6, ESP32-Cam, ESP32-WROOM, ESP32-WROVER, the BW16, the PicoCalc and the Cardputer-ADV, each with its own directory in the repository and its own instructions page.

There is an internal inconsistency worth noticing, because it tells you how carefully the documentation is maintained. The Installation section says the firmware supports eight boards, and then lists fifteen. The repository tree backs the longer list rather than the shorter one, with a directory for each: BW16/, Cardputer-ADV/, ESP32-C3/, ESP32-C5/, ESP32-C6/, ESP32-Cam/, ESP32-S3/, ESP32-WROOM/, ESP32-WROVER/, PicoCalc/, Raspberry Pi Pico 2 W/, Raspberry Pi Pico W/, Raspberry Pi Zero 2 W/, Video Game Module/ and WiFi Developer Board (ESP32S2)/, plus a shared src/ directory, a tools/ directory, HELP.md and Development.md.

So the shared src/ tree is the library, and each board directory carries the firmware variant for that hardware. That structure is what makes the project practical: the code you write against the API is the same, and the per-board build is where the pin and radio differences are handled.

The audience is Flipper app and script developers. The README states that FlipperHTTP can be used in apps and scripts written in C, JavaScript and MicroPython, which is a broad surface for a device whose scripting story is otherwise limited.

Wiring that differs on every board

The wiring section is where most of the real work sits for a first-time user, and it is a per-board table rather than one diagram.

For the WiFi Developer Board the connections are crossed in the standard way, with TX on Pin 14 going to Pin 14 which is the Flipper's RX, RX on Pin 13 going to Pin 13 which is the Flipper's TX, 3v3 on Pin 9 going to 3v3, and GND on Pin 11 going to GND:

WiFi Developer Board -> Flipper
- TX (Pin 14) -> Pin 14 (RX)
- RX (Pin 13) -> Pin 13 (TX)
- 3v3 (Pin 9) -> 3v3
- GND (Pin 11) -> GND

The PicoCalc variant is different because its pins are numbered differently, with TX on GPIO 4 which is Pin 6 going to Pin 14, RX on GPIO 5 which is Pin 7 going to Pin 13, and GND going to Pin 11. The generic ESP32 entry drops the Flipper-side pin numbers on the board side, listing only TX to Pin 14, RX to Pin 13, 3v3 to Pin 9 and GND to Pin 11.

Two of the entries carry warnings. The ESP32-Cam entry says GND, do NOT use GND/R, going to Pin 11, because the Cam board has a second ground pin with a different purpose. The Raspberry Pi Pico W and Pico 2 W entry lists two optional debug lines, SWCLK on the left debug pin going to Pin 10 which is SWC, and SWDIO on the right debug pin going to Pin 12 which is SIO, and it also shows the power coming from 3v3 which is VSYS on Pin 39 rather than from a 3v3 pin.

That is the whole installation story in the README: pick your board, wire the four or six lines, flash the firmware for that board, and use the library. There is no package manager, no dependency list and no configuration file, which is a genuine advantage compared with a desktop-side toolchain, and also means the wiring table is the only setup documentation you get.

The app ecosystem that grew on top of the library

The README lists a dozen applications that integrate FlipperHTTP, and reading that list tells you what the library is actually good for.

Several are data-fetching apps that would be impossible without an HTTP client on the device. FlipWeather uses WiFi to fetch GPS and weather information on the Flipper Zero. FlipTrader fetches stock and currency pair prices. Web Crawler allows the Flipper Zero to crawl and interact with websites directly. FlipTelegram is a Telegram client, and FlipSocial is a social media platform for the Flipper Zero. The free and paid apps are all downloadable from a single page.

The other group is companion and platform apps. FlipperHTTP-App is described as the newest FlipperHTTP companion app, with WiFi scanning and connecting, credential syncing for all FlipperHTTP-enabled apps, and a WiFi connect status check. FlipDownloader is a marketplace for downloading and managing apps and software on the Flipper Zero. FlipMap finds other Flipper Zero users, FlipLibrary is a dictionary and random facts app, and there are two open-world multiplayer games, Free Roam in 3D and FlipWorld in 2D. One entry, FlipWiFi, is a companion app for captive portals, deauthentication and WiFi scanning.

Two things stand out. The first is that the games and the social apps are network multiplayer, which is only possible because the library gives the device a persistent WiFi link rather than a one-shot request. The second is the credential syncing in FlipperHTTP-App, which suggests the project has a model for how a Flipper identity and its WiFi credentials move between apps, and that model is being refined through real use rather than designed on paper.

The educational side is also part of the project. The README links a Flipper Zero video playlist, a collection of video tutorials for FlipperHTTP and related projects in a Tutorials.md file, and the project is sponsored by JBlanked and JBlanked, LLC, which also publishes the API documentation at jblanked.com.

A project with this much downstream use is worth reading for what it implies about the library's stability, since every one of those apps depends on the same API surface.

A warning about scope, and where the library stops

The library is narrow, and the narrowness is both its appeal and its limit.

What it provides is an HTTP client on a microcontroller the Flipper talks to over serial, with the API surfaced in C, JavaScript and MicroPython. What it does not provide is anything about the Flipper's own firmware, its UI, or the apps built on top. If you want to make a Flipper app, FlipperHTTP is a dependency you call, not a framework you build on.

The hardware requirement is absolute. Without one of the fifteen listed boards, or an equivalent ESP32 the maintainer supports, there is no network path, and the library has nothing to work with. That is a harder constraint than most software dependencies, because it means the project cannot be evaluated on a desk without buying hardware.

The related caveat is about what the library makes possible on the device. The README's disclaimer asks that the firmware be used responsibly and states that JBlanked and JBlanked, LLC disclaim all liability for any misuse, with the user solely responsible for their actions. The listed app ecosystem includes apps for WiFi scanning, captive portals and deauthentication, and a game that locates other Flipper devices. Those are separate applications with their own purposes and their own legal considerations, and the library is what gives them a network. A developer shipping an app should think about that before the library makes it easy.

For support, the README points to a HELP.md file in the repository for common bugs and their solutions, and to a Discord server, a YouTube channel and an Instagram account. There is no issue tracker mentioned for the library itself in this README, only for the apps.

On maintenance, the repository is not archived and the last push was on 2026-06-04. The releases are versioned, with v2.2.0 on 2026-06-04, v2.1.8 on 2026-05-21 and v2.1.7 on 2026-04-07, so the project ships patch releases steadily. The licence is MIT, held in a LICENSE file at the root, with no copyleft conditions described.

Firmware per board against one shared library source

The repository layout explains the build model, and it is the part to understand before you start.

At the top there is a src/ directory holding the shared code, a tools/ directory, and the per-board directories listed earlier, each with its own instructions. Two documentation files sit alongside them: Development.md, which is presumably about working on the library itself, and HELP.md for common problems. A Tutorials.md file collects the videos.

The consequence for a user is that the library is not a library you fetch at build time. It is firmware you flash onto the WiFi board, and the board then becomes an HTTP endpoint that the Flipper's app or script drives. That is a different integration model from a normal library, and it has real consequences for testing. A change to your app cannot be tested without the board flashed and connected, and a firmware update is a physical action on a device rather than a version bump in a manifest.

The upside is the same property seen from the other side. Once the board is flashed, the network capability is a stable, shared resource that every app on the Flipper can use, and the credential syncing in the companion app suggests the project treats that setup as a one-time thing per device rather than per app. For someone with several apps in mind, that is a much better deal than each app shipping its own network stack.

The three language bindings are worth a note. C is what a native Flipper app would use, JavaScript covers the scripting environment, and MicroPython covers the Python-flavoured scripting path. The README says the details are in the Flipper Zero directory of the repository, so the API documentation is organised per platform rather than in a single reference, which is another sign that the binding layer is the part with real variety in it.

Editorial conclusion

FlipperHTTP fits a developer writing Flipper Zero apps that need to fetch data over the network, because the per-board firmware directories remove most of the hardware guesswork and the API is exposed in C, JavaScript and MicroPython. It is the wrong choice if you want a general purpose Flipper app platform or a stable long-lived firmware, since the project has no tagged releases beyond the version tags and the last push was on 2026-06-04, and it is the wrong choice for a device without one of the fifteen listed boards. Before you flash anything, read the board directory that matches your hardware, check the wiring table for the pins your board actually uses, and note that the library gives the Flipper a way to reach the network rather than any guarantee about what a given third party app does with it.

Frequently asked questions

Official sources

1. jblanked/FlipperHTTP on GitHub
2. License: MIT
3. Project website
4. README
5. Releases