scrcpy-plus: a desktop GUI for scrcpy and adb

A shell around a tool that already exists

SCRCPY+ is described in the repository description as a simple GUI for SCRCPY and other ADB functions, and that description is the whole product in one line.

The distinction matters. The project is not a fork of scrcpy and not a reimplementation of it, it is a desktop application that assembles the scrcpy command line for you and runs it. The readme makes the lineage explicit in a credits section, pointing at the project it is based on, the Genymobile scrcpy repository, and thanking them. The application is MIT style open source under the GPL 3 licence, and the downloads live on a site of the author's own, with the current release linked from the readme.

The technology choice is the modern desktop one. Version 3.0 upgraded the project to Nuxt 4 and Tauri 2, which means a web front end rendered in a native window, with the Rust side of Tauri doing the work of launching processes. The primary language in the repository is therefore Vue, with the application code in an application directory and a src-tauri directory inside it holding the Tauri side and the icons.

The readme also carries a thank-you line for 175K downloads, which is a number about reach rather than about quality, but it does tell you the application is used by a community rather than being a weekend experiment.

The 3.0 release is mostly about settings

The list of what is new in 3.0.0 is the best description of what the application does, because the changes are almost entirely about the launch configuration.

The launch menu was redesigned, and the display settings panel covers custom window name, crop, display ID, virtual display, rotation lock, screen recording and a no-video mode. Every one of those is a scrcpy command line flag, and the value of the application is putting them in a form with a label rather than in your shell history.

There is a setting to hide the on-screen keyboard so you can type with a physical one through the uhid mode, and a custom flags drawer where you can pass any other scrcpy flag that the interface does not model. That drawer is the escape hatch that makes the rest safe to rely on, because the application does not have to know about every flag scrcpy has, only the ones it has a field for.

Two more settings are about convenience over time. The application can remember your launch options and restore them on the next start, and the wireless connection can be improved by disconnecting from the app and remembering the last IP address, so you do not retype the address every time the phone changes network.

The last of the 3.0 features is the one with a security angle. Devices that are waiting for USB debugging approval are labelled as unauthorized, which removes a genuinely confusing failure where the device is connected, the list shows it, and nothing happens.

Bring your own binaries on Windows

There is one installation detail that deserves a section of its own, because it is the one place where the application does not insist on its own choices.

On Windows, the application lets you pick your own scrcpy.exe and adb.exe in Settings. Everywhere else the bundled or installed binaries are what you get, but on Windows the project allows you to point at whichever versions you already trust or need.

The reason to support that is version compatibility. scrcpy moves quickly, new flags appear with new releases, and a user who needs a flag that the bundled binary does not have can supply a newer one instead of waiting for a new application release. The same argument applies to adb, where a specific version may matter for a particular device.

It also means the application is not a closed bundle. It is a front end over two executables, and on Windows at least it is willing to say so, which makes the upgrade path for the whole tool obvious: update scrcpy, or update the application.

The Linux and Mac story is the opposite, and the readme is explicit about it. On those systems both scrcpy and adb need to be installed to your computer per your distribution's instructions, so the application expects an environment where those tools already exist and simply drives them.

Some options need a recent scrcpy, and the readme lists which

This is the practical detail to check before you install, and the readme states it as a small table of requirements.

The keyboard option, the one that types through a physical keyboard with the uhid mode, needs scrcpy 2.4 or newer. The virtual display option needs scrcpy 3.0 or newer and Android 10 or newer, which is a stricter requirement than the others because it needs the operating system as well as the tool. The audio features need scrcpy 2.0 or newer.

The consequence is that the application exposes settings whose behaviour depends on what is installed underneath, and there is no way for the front end to guarantee they will work. If you are on an older scrcpy, the panel still shows the options.

This is a general truth about wrapper tools and it is best stated plainly: the front end can only present what the underlying tool supports, so the versions of scrcpy, adb and, for the virtual display, the Android version on the phone, together decide what you can actually use. The readme at least names the minimum versions rather than leaving you to discover them from an error message.

The three requirements are also the fastest way to understand what the 3.0 release is trying to do. The virtual display and rotation lock options are the newer scrcpy features, and they are the ones that need the most recent tool.

Device information, wireless connections and three languages

Beyond the launch configuration, the readme lists three features that describe the everyday use of the application.

Device information gives the model information about the active device, which is the first thing you want when a connection misbehaves, since it tells you which phone the application is actually talking to.

Wireless connectivity connects to a device on your WiFi network, and with the 3.0 improvement the application can disconnect from the device while remembering the last IP address, so the pairing is a click rather than a form to fill in. The underlying mechanism is adb over the network, which is the same one scrcpy itself uses.

Multi-language support covers English, Italiano and Japanese, so the interface can be used in your native language. That is a modest list, and it is notable that the translation set is a deliberate part of the distribution rather than something the community adds afterwards, which is a different maintenance story from a project with a translation platform.

The summary line for the whole feature set is that it supports most scrcpy options, and the readme also points to a BUILDING.md file for anyone who wants to build it from the source rather than download a binary. The repository layout supports that story, with an application directory for the app itself, a buildtools directory and an extras directory beside it.

A desktop app that keeps up with the tool it wraps

The release history is short and recent, which tells you the project is actively being worked on rather than maintained in the sense of receiving occasional fixes.

Version 3.0.0d1, named 3.0.0-MacOS, was published on 2026-09-27, version 3.0.0 on 2026-10-13 and version 3.1.0 on 2026-10-17, with the last push to the repository on the same day as the newest release. Three releases in three weeks, and the numbering goes from a 3.0 line to a 3.1 line inside that window.

The 3.0 release is the one that changed the stack, with the move to Nuxt 4 and Tauri 2, and 3.1 came a few days later, which suggests the port landed and was then refined.

The packaging of that choice is visible in the repository. A Tauri application keeps a Rust core and a web front end, and the icons live in the src-tauri directory inside the application directory, which is the standard Tauri layout. The build tools sit in their own directory, so the packaging scripts are separated from the application code, and the extras directory suggests that additional tools or resources are kept outside the main bundle.

The last thing to note is the licence. The project is GPL 3, which is the same licence as the scrcpy project it credits, and that is a deliberate choice for a tool whose whole purpose is to sit in front of another GPL tool. For a personal utility it hardly matters, and for anyone thinking of distributing it the obligation is the same one they already carry from scrcpy itself.

Editorial conclusion

scrcpy-plus fits someone who drives scrcpy from the command line and has memorised a long set of flags, because the application turns that command line into a form with named fields, a device list and a remembered set of launch options. It is the wrong choice if you want scrcpy itself, since the project is a front end and not a server implementation, and it is the wrong choice if you cannot install scrcpy and adb yourself, because on Linux and Mac they are prerequisites rather than bundled dependencies. Before you rely on it, check the version requirements listed in the readme, since the virtual display option needs scrcpy 3.0 and Android 10, and on Windows be aware that the application can be pointed at your own scrcpy.exe and adb.exe rather than the ones it ships with.

Frequently asked questions

Official sources

1. Frontesque/scrcpy-plus on GitHub
2. Issues
3. License: GPL-3.0
4. README
5. Releases