MiracleCast turns a Linux box into a Miracast screen, and it will take your network manager with it
Connect external monitors to your system via Wifi-Display specification also known as Miracast
At a glance
- What is it?
- albfan/miraclecast implements the sink side of Wi-Fi Display in C, so a desktop or an embedded board can receive a screen from a phone. The half that is finished is the receiving half, and it takes NetworkManager offline to do it.
- Who is it for?
- Adopt MiracleCast if you need a bare Linux board to receive a screen from a phone over Wi-Fi Direct and you own the machine's networking stack end to end. Do not adopt it for sending local content to another display, because that half is documented as not implemented and tracked in issue #4, and do not try it on a laptop whose only wired connection depends on NetworkManager.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Activity is slowing. The repository last received commits 8 months ago.
- What is it written in?
- Mainly C, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- albfan/miraclecast4,354 ★ · +12
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| albfan/miraclecast | 4.3k | 4.4k |
12 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The receiving half is the finished half, and the sending half is issue #4
Read the opening claim carefully. MiracleCast presents itself as compatible with the Wifi-Display specification also known as Miracast, and it says it implements the Display-Source as well as Display-Sink side. Two paragraphs later, attached to the source side, sits a note reading that this is not implemented yet, with a pointer to issue #4. What works today is the sink. Your Linux machine becomes the screen, and a phone or laptop with Miracast support sends to it.
The audience is narrow and specific. Someone with an embedded board, or a spare desktop under a desk, who wants a phone to project onto it without buying a receiver. The project's own phrase for this is that you can create wifi-capable external displays yourself, on embedded devices or on full desktops, to allow other systems to use your device as external display.
One more thing to know before reading further: the last push to this repository was on 2026-03-10, and the project tags no releases of its own, so anyone building it tracks the branch rather than a version.
The daemon spawns wpa_supplicant with a config it owns
The mechanism is a set of small command line programs rather than a single service. The README lists miracle-wifid as the wifi daemon and miracle-sinkctl as the sink control, and it describes miracle-wifictl as the wifi control used from the peer side. Underneath, the project does not implement a Wi-Fi stack of its own. It spawns wpa_supplicant with a custom config.
Everything else hangs off systemd. The dependency list names it first, calling it a system management daemon used for device management through udev, dbus management through sd-bus, and service management. The requirement is systemd 213 or newer, and the text adds that systemd 221 or higher works out of the box. Below 221, the project asks for a systemd built with --enable-kdbus, and it is candid about the oddity: even though kdbus is not used, only the independent, experimental sd-libraries are. That is a tell about how old this code is. It still carries a branch for systemd-219 because interface changes landed there.
A third piece, glib, exists only for the DHCP implementation. The README says outright that it will be removed once sd-dns gains DHCP server capabilities, so the dependency list itself records unfinished business.
NetworkManager and wpa_supplicant have to be stopped before the interface is free
This is the step that decides whether MiracleCast fits your machine. To use the sink you stop both the network manager and the supplicant, then start the daemon yourself. The commands are in the documentation verbatim:
$ systemctl stop NetworkManager.service
$ systemctl stop wpa_supplicant.serviceAfter that you start the wifi daemon in the background. On a laptop, that means no wired fallback and no automatic reconnection, and nothing in the documentation puts NetworkManager back afterwards.
The sink control then prints the links it found. The documentation shows the detected link number in the output, and you use that number as the argument to the run command:
$ sudo miracle-sinkctl
[ADD] Link: 3From the sink prompt, you run that link, pair your machine with the sending device, and the image arrives. Note that the example is a root daemon writing to your console, and that pairing is a manual step, not something the tool initiates.
Three build systems, and a dbus policy you copy by hand
MiracleCast offers autotools, cmake and meson as equal choices, with the detail pushed to a Building page on the project wiki. The repository top level shows that commitment rather than the usual single set of build files: CMakeLists.txt, configure.ac, common.am, meson.build and meson_options.txt all sit side by side, alongside separate Dockerfiles for autotools, cmake and meson, and further ones named for gcc14 and gcc15. That is a real signal, even if it is not a quality claim: the tree is set up to be compiled by several toolchains, which is what you want when your build host is not the machine the daemon will run on.
The manual step that gets missed is the dbus policy. You copy res/org.freedesktop.miracle.conf into /etc/dbus-1/system.d/. The README lists this copy step among the requirements.
If you want the interface picked automatically, there is a udev route. You add a rule with res/write-udev-rule.sh and then configure with the reliance flag:
$ ../configure --enable-rely-udevOtherwise you select the interface by hand with the --interface option on miracle-wifid. Two paths to the same decision, one automatic and one explicit.
Your distribution decides which branch of the install you get
The README splits the installation by Linux flavour, and the splits are real rather than cosmetic. On Ubuntu you start by checking what you have:
$ systemctl --versionIf the answer is 221 or above, kdbus is enabled and nothing else is needed. Below 221, the project points at a separate repository, albfan/systemd-ubuntu-with-dbus, built specifically to install systemd with dbus on that release. Below 219, you are told to use the systemd-219 branch of MiracleCast itself, because of interface changes in systemd. So one dependency takes three different answers across three Ubuntu generations, and the oldest path means compiling a patched init system.
Arch is shorter because a package exists. The README points at the miraclecast-git AUR package and notes you should enable kdbus on the systemd-git dependency if you are below 221:
$ export _systemd_git_kdbus=--enable-kdbusInstallation then goes through the AUR helper. For anything else, the project's advice is to lift instructions out of the Arch PKGBUILDs, with links given for both systemd-kdbus and miraclecast. Debian and Fedora appear nowhere in the documentation, and neither does any of the Raspberry Pi boards that people search for, despite the sink side being exactly the sort of thing those boards are bought for.
UIBC adds a back channel for mouse and key events, with a narrow scope
User Input Back Channel is the optional WFD feature that carries user input from a User Interface at the WFD Sink to the WFD Source. MiracleCast implements it behind one flag. You add --uibc at miracle-sinkctl startup, and the scope stated in the documentation is narrow: single mouse events and key events are implemented. No multitouch, no gestures, no streaming of anything more interesting than a click and a keystroke.
The peer side is thinner still. The README is candid that the commands there have nothing useful yet: p2p-scan locates nearby devices, and peer <mac> shows one device's info. Past that, it refers readers to issue #4, titled Using as peer, meaning the interactive shell is not where this project is finished.
Two diagnostic scripts ship alongside. res/test-viewer.sh checks that the gstreamer pieces needed to render the cast output are present, and res/test-hardware-capabilities.sh tests whether your adapter supports Wi-Fi Direct. Both are worth running before anything else, because the requirements section states plainly that although P2P Wi-Fi is widespread, some devices are not compatible with it.
Where MiracleCast differs from GNOME Network Displays
MiracleCast is a set of root daemons that want the P2P interface to itself, which is why it spawns its own wpa_supplicant and why the first documented step is stopping NetworkManager.
The README says the sink can be used on embedded devices or full desktops, and the User Input Back Channel is exposed through the --uibc flag. The cost is the one you read about above: root daemons, a hand-copied dbus policy, and a stopped network manager.
Licensing follows the fork history. The project is under GNU LGPL and points to ./COPYING, and it credits David Herrmann as the original maintainer with Alberto Fanjul maintaining this fork.
Editorial conclusion
Adopt MiracleCast if you need a bare Linux board to receive a screen from a phone over Wi-Fi Direct and you own the machine's networking stack end to end. Do not adopt it for sending local content to another display, because that half is documented as not implemented and tracked in issue #4, and do not try it on a laptop whose only wired connection depends on NetworkManager. Verify two things before anything else: that your adapter passes res/test-hardware-capabilities.sh, since the README states plainly that some devices are not Wi-Fi Direct capable, and what systemctl --version reports, because anything below systemd 221 means compiling a patched systemd or pinning the systemd-219 branch.
Frequently asked questions
Is MiracleCast available on Linux?
Yes. It is a Linux implementation of the Wifi-Display specification also known as Miracast, written in C, and it implements the Display-Sink side so a Linux machine can act as a wireless display.
How do I install MiracleCast on Linux?
The project offers autotools, cmake and meson builds, with details on its Building wiki page. On Arch there is an AUR package, and the listed requirements include copying res/org.freedesktop.miracle.conf to /etc/dbus-1/system.d/.
How do I use MiracleCast as a sink?
Stop NetworkManager and wpa_supplicant, launch miracle-wifid, then launch miracle-sinkctl and run the detected link number to start Wi-Fi Display on it. Pair your machine with the sending device and the screen appears on the Linux box.
Does MiracleCast work as a sender, streaming local content to another display?
No. The README marks the Display-Source side as not implemented yet and points to issue #4. The implemented direction is receiving, where your machine becomes the external display.
What is an alternative to MiracleCast for receiving a screen on Linux?
MiracleCast's README does not compare it with other receivers. What it documents is that MiracleCast spawns its own wpa_supplicant and that NetworkManager and wpa_supplicant must be stopped before use.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/albfan-miraclecast)Star history chart for your README
[](https://hysenlabs.com/projects/albfan-miraclecast)Was this useful?