Every emulator, in perfect order.
Emulator Studio starts your Android emulators, watches their screens and runs the tasks you build from plain steps. One window, whether you run one emulator or fifty.
- 01MuMu #0Running
- 02MuMu #1Running
- 03LDPlayer #0Waiting
- 04LDPlayer #1Starting
- 05MEmu #0Paused
- 06BlueStacksStopped
- 01Capture screen540 × 960
- 02Find template0.97 at 270, 652
- 03Tap on matchtap 270, 652
- 04Screen changed?yes
- 05Read text (OCR)“12”
- 06If / Elsea number: Yes
- 07Log message“Done: 12”
Link once. The address follows the emulator.
Point Emulator Studio at the emulators you already use. Link each instance to its player, and Start boots a closed emulator, reads the address it came up on, and connects to that one and no other.
- Create up to 200 instances in one go, named and linked as they're made.
- Start them in batches, a few now and the next few once those are ready, so twenty emulators don't all boot in the same minute.
- Show, hide or shut down the emulator windows from the same list.
- One card per instance, or a single table for the whole fleet.
A task is a short list of steps.
Each step does one job: find a picture, read the text in a box, tap, swipe, wait for the screen to change. Put them in order, add an If or a Retry where the screen might surprise you, and the task is ready. No code.
Find a picture, read text or a timer in a box, and notice when the screen changes.
Tap, swipe, type and press keys, or open and close an app by its package name.
Branch, repeat and retry, so a task copes when the screen surprises it.
Reuse tasks inside tasks, keep values for later, and write down what happened.
Find template
Looks for a picture you cropped, inside the box you set, and reports where it is and how close the match was.
Every step a task takes is written to the run's log, so you can see why it did what it did.
Tasks take turns. The plan picks whose turn it is.
Each emulator has one screen, so its tasks take turns on it. Give every task its days and a daily limit, and the plan works out what runs next.
Check in from your phone.
Start, stop, pause and switch profiles from your phone's browser, or type /remote in Discord. Share chosen instances with someone, and they see and control only theirs. Everything that happened is written down in plain words.
- Instance 01Running
- Instance 02Running
- Instance 03Waiting
- Instance 05 SharedPaused
The same controls answer /remote in Discord.
- Instance 01 started the example task.
- Found the picture and tapped it. The screen changed.
- Read the number in the box: 12.
- The example task finished in 7 s.
- Instance 05 was paused from a phone.
- Hourly check started on Instance 02.
Free while in beta.
When plans start, you'll pay for the instances you run, on one 30-day period with one renewal date.
Before you download.
How does it work?
It reads the emulator's screen with computer vision and taps, types and swipes through ADB, the way you would by hand. Between actions it waits for the screen to finish drawing, using each instance's own screen delay.
Which emulators does it work with?
MuMu, LDPlayer, BlueStacks and MEmu, on Windows 10 and 11. The tasks that come with the app expect the emulator set to 540 × 960 portrait at 120 DPI.
What can a task do?
Anything made of looking and touching: find a picture, read text or a timer, tap, swipe, type, press keys, open or close an app. Some apps forbid automation in their terms of service, so read those before you automate one.
Do my screens leave my PC?
No. Screens are read on your own PC. A screenshot leaves it only inside a bug report you choose to send.
Can I run it from my phone?
The app runs on your Windows PC. Once it's running, your phone can start, stop and pause it from the browser or from Discord.