Android Emulator on an External Monitor: Play Sharp on a Second Screen with a Mac

You plug your Mac into a big monitor, drag the Android emulator’s window onto it, and the picture is blurry or badly framed. In MACOS EMULATOR, everything is worked out on a single screen: the Mac’s main display. Here is how to make it your monitor, which display setting to keep, and what changes on an 8 GB Mac.

The emulator is set up on the Mac’s main display

To macOS, the main display is the one that carries the menu bar. That is the screen the launcher measures when the Android device starts: the panel size in “Screen fit”, the window’s starting size, the blur math in the (?) next to Resolution, and the detection of “More Space”.

Dragging the game window onto another screen afterwards recalculates nothing: the panel keeps the size planned for the main display, and the image is stretched for the other one. So the right order is the reverse: make your monitor the main display, then start the device.

Make your monitor the main display

1. 1Plug in the monitor and wait until macOS shows the desktop on it.
2. 2Open System Settings, then Displays, and select your monitor.
3. 3In the “Use as” menu, choose “Main display” for it: the menu bar and the Dock move over.
4. 4On macOS 12, it is System Preferences, then Displays, Arrangement tab: drag the white bar at the top onto the monitor.

To check, open the launcher’s Settings, then the orange (?) next to Resolution. Its first line, “Your main screen”, gives the pixels of the screen the launcher picked: your monitor’s, if all is well. A MacBook closed on its monitor has only that screen left, so it becomes the main display.

Then “Screen fit”, for a sharp picture

On a big monitor, “Fluid (1440x900)”, the base panel, is stretched to the size of the screen. The (?) next to Resolution puts a number on that stretch for your screen: “sharp” up to 1.2, “small details blurry” from 1.5. On a monitor 2560 pixels wide, Fluid is already stretched 1.78 times.

“Screen fit” sizes the panel to the usable area of the main display, menu bar and Dock excluded, and the game is drawn at scale 1: every pixel of the game lands on a whole number of monitor pixels, so nothing is blurry. The window opens at the top left of the main display, under the menu bar. Pick it in Settings, then Resolution (“Screen” segment), or with the logo at the bottom right of the Render card.

The guide to full screen in an emulator details this setting, and the “Full screen” switch that makes the window cover the whole screen.

Plugging in, unplugging: one longer start, once

With “Screen fit”, the panel is recalculated every time the device starts. If the main display has changed since your last session (monitor plugged or unplugged, Dock moved or resized), the launcher sets the new panel and throws away the quick-start snapshot: that start begins cold, so it takes longer. Your Google account and your games are not touched.

If you plug in the monitor while the device is running, the panel only changes at the next start: shut the device down with the red button in the toolbar, then start it again. The guide to an emulator that will not start explains what is normal during a cold start.

Your keys do not move: their positions are stored as fractions of the screen, not in pixels.

“Default” rather than “More Space”

In System Settings, then Displays, leave your monitor on the “Default” resolution. “More Space” makes macOS draw an image larger than the screen’s physical resolution, then scale it down every frame: measured during play on a MacBook Air M2’s screen, the macOS display server used 45% of a core. And with “Screen fit”, the game’s panel grows along with that area.

The launcher spots it on the main display, when macOS reports a Default setting: the “Performance” section of its Settings then shows a “Screen resolution” row, with the size being drawn, the size of “Default” and an “Open Displays settings” button. It changes nothing for you.

On an 8 GB Mac, the monitor’s size matters

On an 8 GB Mac, a panel above roughly 2.5 megapixels is brought back to Fluid (1440x900) at startup, and the (?) next to Resolution says so: “capped to Fluid on 8 GB”. A 2560x1440 monitor goes over that limit in “Screen fit”; a Full HD monitor (1920x1080) stays under it, like a MacBook’s built-in display left on its default setting.

Past the limit, the monitor is still usable: the image is stretched on it, so less sharp. The guide to the emulator on a MacBook Air M1 details what the launcher sets up on its own on 8 GB.

If it stutters on the big screen

A big panel asks more of the graphics chip and the processor, not more memory: leave your Memory setting alone for this. If busy scenes stutter in “Screen fit”, go back to Fluid (“Back to Fluid”, in the Render card’s sheet), the panel that costs the least to draw.

The performance report records the main display, in pixels, in points and with its Retina factor: support can see which screen you were playing on. If it lags even in Fluid, the settings for a slow Android emulator go through what really weighs on it.

Frequently asked questions