Run an APK in your browser.
Upload a universal .apk or .aab, pick an Android profile, and drive the running app from any browser. There is no SDK to install, no USB cable and no local emulator to keep alive.
At a glance
- Upload
- Universal .apk or .aab up to 512 MB; split APKs are not supported
- Device
- Android 12 to 16 on a phone or tablet; Android 14 phone is the default
- Controls
- Touch, keyboard, Home, Back, Recents, rotation and screenshots
- Debug
- Live Logcat beside the running screen
- Share
- A revocable link lets someone outside the workspace try the build
What you need
A universal .apk or .aab, a browser, and a SpawnDroid workspace. You do not need the Android SDK, a local emulator, hardware virtualisation, or a phone on your desk. Uploads are accepted up to 512 MB. An .aab is converted to a universal APK on the device host; split APKs are not supported.
Upload and start a session
- Upload the buildFrom the console, open Artifacts and upload a universal .apk or .aab. The manifest is decoded and the build is stored; nothing boots yet.
- Pick a profileChoose Android 12 to 16 on a phone or tablet. Android 14 on a phone is the default, and the console remembers your last choice.
- Start the sessionSpawnDroid creates the device, installs the build and opens the live screen in the console. The first boot usually takes well under a minute.
- Drive the appTap, type and scroll. Input is forwarded to the running app, not a recording. Open Live Logcat when you need to see what it is doing.
What the session gives you
- Touch and keyboard input forwarded to the real app.
- Home, Back, Recents, power, volume and rotation controls.
- Live Logcat with level filters and search.
- Screenshots, plus a retained screen recording on Personal and above.
- The same build can be handed to a hosted Appium runner in CI.
Share a build without an invite
An admin can create a share link for one build. The recipient opens it in a browser and presses Launch live demo; they do not need an account, a workspace invite or a seat. The link covers that one build, expires on the schedule you choose and can be revoked at any time. Hobby allows one active link for 24 hours, Personal five, and Team unlimited links that can be password protected.
Shared links show the app, not the console: there are no device controls and no Logcat. Clicking the link does not start a device; a runner starts only when the visitor presses Launch.
Limits worth knowing
- The Hobby plan includes one parallel runner. A second live session is rejected with a concurrency error until the first is stopped.
- Sessions are isolated containers and are destroyed when the session ends.
- Every session has a maximum lifespan and idle sessions are reaped: Hobby sessions last 15 minutes with a 3-minute idle stop, and the plan includes 200 device-minutes a month.
- SpawnDroid runs Android 12 to 16 only. There is no iOS runtime.
Run it from CI instead
The same build can be uploaded from a pipeline with a scoped API key and handed to a hosted Appium 3 runner. The test owns the app lifecycle, and the final logcat, screen recording and pass or fail result are retained.
Frequently asked questions
No. The app runs on a device in SpawnDroid's cloud and the screen is streamed to your browser. You do not need the Android SDK, an emulator or a phone.
Keep reading
Start free
Put your APK in a browser.
Upload a universal APK and open a real Android session. The Hobby plan includes one parallel runner and 200 device-minutes a month, and needs no card.