X11 was designed so that the program and the screen it draws on don't have to share a machine. Developer Sergey Zorin has pushed that idea all the way down to a microcontroller. His open-source project Woodland X11 is an X server that runs on an ESP32-S3 and drives the display of an Elecrow CrowPanel Advance 4.3-inch board. X clients on another machine connect over Wi-Fi, and their windows (xclock, xeyes, xcalc) appear on an 800x480 touchscreen.
Hackaday covered the project on November 13, 2026. It describes Woodland X11 as a full-featured port of the X server with no extensions, and says Zorin wrote it with Claude. The project's own README is a useful read because it is unusually candid about what works, what doesn't, and how the author tested it.
The hardware target
Woodland X11 targets one board: the Elecrow CrowPanel Advance 4.3. The project README and Hackaday give the same key specs:
- SoC/module: ESP32-S3-N16R8
- Display: 4.3-inch, 800x480, RGB565 IPS
- Touch controller: GT911
Elecrow's wiki page for the CrowPanel Advance 4.3-HMI ESP32 AI Display lists the board as model DIS01943A. It documents UART, I2C, audio and battery connectors, plus 3.3 V outputs. None of these matter to the X server itself, but they show this is a general-purpose HMI panel and not a board built specifically for the project.
What "core protocol only" means here
The README states plainly that Woodland X11 implements the X11 core protocol and no extensions. Within that limit, it says all 119 core requests are handled. As evidence it cites results from XTS, the X Test Suite, for the Xproto tests: 384 PASS, 3 FAIL, 2 UNSUPPORTED. The README attributes the failures to ChangeHosts, SetAccessControl (host access changes are refused by design) and CopyPlane. That is a specific, checkable figure, and it is more than most hobby display projects publish.
The limits are just as specific. Per the README:
- Visuals: one TrueColor visual at depth 16 (RGB565), which matches the panel's native format.
- Fonts: a built-in 6x12 fixed font only. There is no Unicode font.
- Input: touch acts as pointer Button1, with two-finger scroll and tap. There is no keyboard input.
- Unsupported extensions: XKB, RENDER, XTEST, SHAPE and others.
The missing extensions decide what will actually run. Modern toolkits generally expect RENDER for anti-aliased text and compositing, and they expect keyboard handling. So the clients that work best are the old Xlib-era classics. That is why the demo programs Hackaday mentions are xclock, xcalc and xeyes, not a browser or a terminal emulator. With no keyboard, a terminal would be of little use anyway. Hackaday describes the interaction model the same way: your finger is the cursor, two fingers scroll, and there is no keyboard.
Two build profiles, two transports
The README describes two build profiles with quite different capacities:
| Profile | Toolchain | Max clients | Transport |
|---|---|---|---|
| Arduino | esp32 core 3.3.12 | 6 | Wi-Fi only |
| IDF64 | ESP-IDF v5.5.5 (plus Arduino-ESP32 3.3.12) | 64 | Wi-Fi, or an SPI link to a host |
Over Wi-Fi, clients connect to the standard X11 TCP port scheme, 6000 plus the display number, so on the client side it looks like any networked X display. The IDF64 profile adds an SPI link to a host as a second option, which lets a host computer use the panel as an attached X display without going through the wireless network. Hackaday notes its demo video uses a wired connection. Since the whole project is labeled experimental, treat that path accordingly.
Status and security: read the fine print
Zorin labels the current state release candidate 2 and calls the software experimental. We found no tagged GitHub releases on the repository. The latest push recorded on GitHub is dated November 13, 2026, the same day Hackaday's article appeared. Anyone building it today is building from the repository source, not from a packaged release.
Security is also described honestly. According to the README, there has been no security review beyond MIT-MAGIC-COOKIE-1 authentication and an authenticated OTA update protocol. MIT-MAGIC-COOKIE-1 is the shared-secret cookie scheme X has used for a long time. It is better than an open display, but it does not encrypt the X protocol traffic. In practice, this belongs on a trusted local network, not on anything reachable from the internet.
Why bother?
An X server on a microcontroller is not going to replace a Raspberry Pi running a full desktop. What makes it interesting is the architecture. With Woodland X11, the ESP32-S3 does no application work. It only handles rendering and input. The logic lives on whatever machine runs the client, and the panel becomes a thin display terminal that speaks a protocol nearly every Unix-like system already understands.
For the usual microcontroller HMI work, that is the opposite of the normal approach, where you write and flash a UI with a graphics library on the device itself. Here, in principle, a small Xlib program on a server can put a status window, a clock or a simple touch control on a wall-mounted panel, and you change it without reflashing anything. The limits in the README define the boundaries: 16-bit color, a single 6x12 font, single-button touch input, and no extensions.
The project is also a reminder of how much protocol fits on this class of hardware. Handling all 119 core requests and passing most of the XTS Xproto suite on an ESP32-S3 module is a solid engineering result. The Hackaday report that the code was written with Claude is a further data point in the ongoing discussion about AI-assisted embedded development. The published XTS numbers give readers a way to judge the result without relying on anyone's word for it.
What It Means for Makers
Who it's for: Linux and Unix tinkerers who already have an X-capable machine on the network, people interested in retro computing, and anyone who wants a touch panel that legacy X clients can draw on. It is also good reading for embedded developers curious about protocol implementation on the ESP32-S3, especially since the README documents its test results.
What it enables: a networked X display on inexpensive HMI hardware, where the panel only handles rendering and pointer input while the applications run elsewhere. It does not replace a full X server. With no keyboard, no RENDER, no XKB and only one fixed font, most modern GUI applications are out of reach. The demos Hackaday cites (xclock, xcalc, xeyes) are the realistic scope today.
What you need: the specific Elecrow CrowPanel Advance 4.3 board (model DIS01943A per Elecrow's wiki; ESP32-S3-N16R8, 800x480 RGB565 IPS, GT911 touch, per the README and Hackaday), plus either the Arduino esp32 core 3.3.12 (Arduino profile) or ESP-IDF v5.5.5 with Arduino-ESP32 3.3.12 (IDF64 profile).
Price and availability: Woodland X11 is free and open source under the Apache-2.0 license, and the source is on GitHub. It is at release candidate 2, marked experimental, with no tagged releases as of the November 13, 2026 push. None of the sources we used list a price for the CrowPanel hardware, so check Elecrow directly for current pricing. Because the only authentication is MIT-MAGIC-COOKIE-1, keep it on a trusted network.