iPhoneMirror is an unsigned Windows x64 preview that will not install kernel drivers for you
Local Windows iPhone/iPad mirroring over USB and AirPlay with D3D11 preview, multi-device sessions, OBS output, and a standalone driver manager.
At a glance
- What is it?
- A GPL-3.0 local capture tool for mirroring an iPhone or iPad to Windows over USB and AirPlay, with per-device rounded windows, clean OBS output and separate wired modes. Its own warnings matter: no Authenticode signature, x64 only, a private Apple protocol underneath, and a driver manager that will download and unpack iTunes when Apple USB support is missing.
- Who is it for?
- iPhoneMirror is worth trying if you already have a Windows x64 machine, a cable, and patience for a preview build, and its separation of concerns is real: capture, UI, wireless host and driver work live in different processes, the main program never touches kernel filters, and screenshots come from decoded frames rather than a captured window. Read the warnings before you install rather than after.
- Can I use it commercially?
- Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- 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
- RayrenSX/iPhoneMirror1,864 ★ · +1,229
| Repository | 2026-09-17 | 2026-11-15 |
|---|---|---|
| RayrenSX/iPhoneMirror | 635 | 1.9k |
1,229 Stars in the last 59 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
No commercial signature, and no ARM64 build at all
The first block of the document is a warning box with three parts. This is a public preview without commercial Authenticode signing, so Windows may show SmartScreen or an unknown publisher prompt, and there is no supported way around that other than accepting it. Apple Screen Capture runs on a private protocol, so a future iOS update can require fresh adaptation. Official builds cover Windows x64 only, because the USB kernel driver and the wireless runtime have no ARM64 versions. The project is GPL-3.0 and mixes languages by design: a C++ core handles the Apple private USB protocol, QuickTime and CoreMedia parsing, H.264 decoding, D3D11 rendering and WASAPI audio, while a WPF program handles the device list, session control and the user interface, a separate wireless host handles AirPlay, and a third executable handles drivers. Tags move quickly for a preview: v1.8.1 on 2026-08-30, then v1.8.2 and v1.8.3 both on 2026-09-06.
The main program only reads driver state, and refuses to install filters itself
The driver story is split on purpose. `iPhoneMirror.exe` reads driver status and nothing more; installing, repairing and uninstalling all belong to `iPhoneMirror.Driver.exe` sitting in the same directory, and the main window's driver entry only activates an existing instance. When you press start mirroring on a wired device, the main program runs four checks against the selected device: that the Apple parent device is still `usbccgp`, that the device has the `libusb0` UpperFilter registered, that `libusb0.sys` and its service are healthy, and that `libusb0` can enumerate by the device's serial number. If any check fails, the launch is cancelled and the driver manager opens. A separate warning rules out a common shortcut: do not point Zadig at the Apple parent device to replace it with WinUSB or libusb, because detection is limited to the `libusb0` UpperFilter on the target Apple `usbccgp` instance, and the main program ships only the `libusb0.dll` userspace runtime needed to start.
Missing Apple USB support means the tool downloads and unpacks iTunes
The acquisition chain is the part to read carefully. If the machine has no Apple USB support at all, the driver manager first looks for a trusted `AppleMobileDeviceSupport64.msi` in its own directory or cache. Failing that, it downloads a standalone MSI from Apple's Software Update Catalog and verifies it. Only if that fails does it fetch the desktop iTunes installer from Apple's official HTTPS endpoint, verify it, and extract Apple Mobile Device Support from inside it. The Microsoft Store version of Apple Devices can still be installed by hand, and the project states that it does not redistribute Apple's proprietary binaries, so what travels over the network is Apple's own package pulled at build time rather than a copy hosted here. Two log locations are given for when this goes wrong: a driver interface log under `%LOCALAPPDATA%\iPhoneMirror.Driver\Logs\driver-ui.log` and an administrator operation log under `%ProgramData%\iPhoneMirror.Driver`. A full dependency list lives in `docs/DRIVER_DEPENDENCIES.md`.
The ZIP build trips a Windows image check, and the fix is a file property
There are two release packages and they are not interchangeable. The preferred one is `iPhoneMirror-Setup-v*-x64.exe`, an Inno Setup installer with Simplified Chinese, Traditional Chinese for Hong Kong and English, an optional install directory, an administrator install defaulting to `C:\Program Files\iPhoneMirror` with a Start menu entry and an optional desktop shortcut, and a per-user mode that uses the Windows user-level programs directory. The portable one is `iPhoneMirror-v*-win-x64.zip`, run as `iPhoneMirror.exe` after a full extraction. The documented failure is specific: Windows can reject the wireless DLL inside the ZIP as a damaged image with error `0xc0e90002`, and the instruction is to use Setup instead. If you must use the ZIP, you tick Unblock in the Properties of the downloaded archive before extracting, and not on the individual DLL after extraction. Both packages bundle the .NET runtime and the separate driver manager, and both are verified against the `SHA256SUMS.txt` published in the same release.
Only the installer writes the wireless firewall rule, and the portable build does not
The AirPlay path is where a firewall decision shows up. In an administrator install, the setup creates a local-subnet firewall rule named `iPhoneMirror Wireless AirPlay` for the wireless host, scoped to `WirelessHost.exe` and the local subnet for inbound TCP and UDP, and it permits the media ports that AirPlay negotiates per session through its SETUP exchange, so the port range is not fixed in advance. Uninstalling removes the rule. The portable ZIP build changes nothing, and the guide instead points you at manual commands, which means the rule's scope becomes whatever you type. Discovery itself needs no privileges and no extra service: wireless discovery uses the DNS-SD support built into Windows 10 and 11 rather than installing Bonjour. Reverse control over Bluetooth is separately bounded, since it depends on iOS AssistiveTouch and the Windows Bluetooth peripheral mode, cannot inject multi-touch, and needs no app on the phone and no jailbreak.
Three wired modes, and only one of them is recommended
A wired device is driven by one of three protocols, and the document is candid about the cost of each. Mode A, the default and the recommended one, sends `Valeria=true` with a native `DisplaySize` and mirrors the phone screen completely, with the catch that the status bar date, time and battery show Apple's demonstration values rather than the real ones. Mode B is the experimental AirPlay path, using native dimensions with orientation adaptation, which lets a video app switch to external playback but may crop the picture or show it incomplete. Mode C, the i4Tools compatibility mode, is fixed at 1565 by 1565, which is easier to predict and constrains the clarity of the source. The mode is chosen per wired device, an exclamation mark beside each option lists the full trade-offs, and switching to another device sends a QuickTime end control to the previous phone and restores the ordinary USB configuration, which also happens when the main window closes. The project also states that this private protocol may need adaptation after a future iOS release.
Reverse control comes in two paths with very different prerequisites
Bluetooth reverse control binds a BLE HID mouse and keyboard to a chosen device, with system navigation and configurable global hotkeys, and it works alongside iOS AssistiveTouch. The limitations are named rather than discovered: no multi-touch injection, and a dependency on the Windows Bluetooth peripheral mode. No application is installed on the phone and nothing is jailbroken, which is the honest way to describe an assistive-technology path. The USB and wireless reverse control is a different machine. It runs through a separate CoreDevice bridge and requires developer mode on the device, a matching driver interface package, and verification of the device HID service, with the details deferred to the tutorial. So the same menu entry, reverse control, means two mechanisms with different trust levels, one that rides AssistiveTouch and one that asks you to put the phone into a developer configuration.
Screen shapes are a visual fit, and the project says so
The claim that most needs a footnote is the device outline. The program reads Apple's `ProductType` and matches a screen radius, curve and crop configuration per device family, covering iPhone X, notch screens, mini, standard and Max, Dynamic Island, plus iPad Pro, Air, mini and full-screen base models, rather than applying one generic rounded rectangle. The same configuration drives the frameless standalone window, so dragging, proportional scaling, orientation changes and full screen all keep the device's shape, and a right-click menu can remove or restore the rounding. The disclosure is the important part: these radius values are a visual fit based on public appearance and picture aspect ratio, not industrial dimensions published by Apple. Unknown devices fall back conservatively from the aspect ratio so an iPad is not cropped like a phone. Two other details are worth knowing as design choices: a screenshot reads decoded frames directly, so it contains no program interface, and a frameless window is what OBS captures, with no separate streaming entry point.
Editorial conclusion
iPhoneMirror is worth trying if you already have a Windows x64 machine, a cable, and patience for a preview build, and its separation of concerns is real: capture, UI, wireless host and driver work live in different processes, the main program never touches kernel filters, and screenshots come from decoded frames rather than a captured window. Read the warnings before you install rather than after. Expect SmartScreen prompts you cannot click away without a signature, expect wired quality to depend on which of the three modes you pick, and expect a future iOS update to be able to break the capture path, since the protocol is private. Reverse control is the feature to read twice: the Bluetooth path is assistive-touch only, and the wired path wants developer mode on the phone.
Frequently asked questions
Why does Windows warn me about iPhoneMirror?
It is a public preview without commercial Authenticode signing, so SmartScreen or unknown publisher prompts are expected. The project does state that the main program never installs or enables a kernel filter driver itself, and hands all driver work to the separate iPhoneMirror.Driver.exe.
Does iPhoneMirror require iTunes from Apple?
It needs Apple USB support, from the Microsoft Store Apple Devices app or the desktop iTunes with Apple Mobile Device Support. If that is missing, the driver manager uses a trusted local AppleMobileDeviceSupport64.msi, then a verified MSI from Apple's Software Update Catalog, and only then downloads and verifies the iTunes installer to extract the component from it.
Can I run iPhoneMirror on a Windows ARM64 machine?
No. Official builds are Windows x64 only, because the USB kernel driver and the wireless runtime have no ARM64 versions available.
The iPhoneMirror ZIP build reports a damaged image or 0xc0e90002
That is the documented behaviour of the portable package's wireless DLL. Use the Setup installer instead, or, if you must use the ZIP, tick Unblock in the Properties of the downloaded file before extracting, rather than on the extracted DLL.
Does iPhoneMirror send screen content anywhere?
No project-run relay is involved: frames are decoded on the machine over D3D11 and Media Foundation, and a USB session needs no network at all. The app does check GitHub Releases in the background for updates, with separate controls for the startup check, automatic download and stable or Beta notifications.
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/rayrensx-iphonemirror)Star history chart for your README
[](https://hysenlabs.com/projects/rayrensx-iphonemirror)Was this useful?