This article contains affiliate links — if you download through them we may earn a commission at no extra cost to you.
Discord makes an official Windows program. It is free, it comes straight from discord.com, and for almost everyone reading this it is the correct answer — native voice, proper screen sharing, global hotkeys, and no emulator sitting underneath. If you can install it, install it and skip the rest of this page.
This guide is for the cases where you cannot, or where you specifically want the phone app. Three come up. You want a second account signed in at the same time as the one already open in the desktop client. Your machine runs a Windows version the desktop client has dropped. Or you administer a server and want to see exactly what your members on Android see, which the desktop layout will not show you.
How do I set it up?
You need an Android emulator; this walkthrough uses LDPlayer. It runs on Windows 7 through 11 in either architecture, wants around 2 GB of memory as a floor and roughly 10 GB of disk, and works the same on a laptop as on a tower.
Open it, then let the Play Store app that lives in the emulator sign you in to a Google account. That step is skippable — the bundled LD Store carries Discord and asks for no account, and the APK route works too. The listing is at Get Discord on Google Play if you would rather open it directly. Log in with your existing credentials and every server, DM and role is already there, because none of it lives on the device.
Why does a second account work here when it does not in the desktop app?
Because the emulator is a separate device as far as Discord is concerned. The native client signs one account in at a time, so a moderator running a personal account and a bot-testing account has to keep logging out. The emulator holds the second session independently, and both stay connected. This is the reason most people end up doing this at all.
What does the Android build not do?
Screen sharing is the big one, and it is worth being precise: the app inside the emulator can only see the emulator's own virtual screen. Sharing from there broadcasts that window, not your desktop or your game. If sharing your screen is why you are here, this route cannot do it — the native client can.
Global hotkeys are the second. Push-to-talk in the native app works while you are focused on a game; inside an emulator the key only registers while the emulator window has focus, which defeats the purpose during play.
Voice itself works, but there is an extra audio layer between the microphone and Discord, so expect slightly more latency than the native client and a microphone setup that takes a few attempts to get right in the emulator's audio settings.
Is either one paid?
No. Discord is free and so is the emulator. Nitro behaves exactly as it does on a phone if you have it — the account carries it, not the install.
What if it runs badly?
A chat client is light enough that sluggishness points at the emulator's own allocation long before it points at your hardware — give it another core and another gigabyte and the problem usually disappears. The performance guide lists what is worth changing, and the troubleshooting notes cover a window that opens black or closes on launch.
