Which devices work with your maps?

Your maps run in a web browser — there's no app to install. The 2D Map is light and works on nearly anything; the 3D views stream a lot of data and lean on your device's graphics chip, so how smooth they feel scales with the device in your hand.

What you need

• A current browser — Safari, Chrome, Edge or Firefox. The 3D views use WebGL 2, which all four have had for years, so keeping your browser up to date is enough.
• For 3D on a phone or tablet — a device from roughly the last four years with 4 GB of memory or more, on iOS 17 or newer or Android 12 or newer. What we've tested runs iOS 26 and Android 13–17.
• A decent connection for the first load — Wi-Fi or good cellular for the first look at a large property. What you've already looked at is kept, so coming back to it is quick.

Which 3D views this covers

The results below were measured on the streaming 3D model of the property — the Oblique tab — on our own properties: a 40-acre ranch with two dozen points of interest, and the demo project. The Gaussian Splat, the Flyover and the 360 walkthrough (when your project includes it) stream and scale the same way. Two tabs behave differently on a phone: the 3D Model tab offers a download link on a phone rather than rendering, and the Point Cloud tab renders a streamed, tiled point cloud right on the phone while a large single-file cloud offers a download link instead. View your maps on a phone or tablet has the details.

What we've tested on

iPad Pro 12.9 (M2, iPadOS 26)

The best handheld experience. It opens in Earth mode with on-screen joysticks for the walk and fly modes, and it has been working great.

iPhone 15 (iOS 26)

Smooth — about 45–59 frames per second across the demo property, and it never closed the tab on us. Close to the ground beside a dense cluster of points of interest it dips noticeably; back at height it's smooth again.

Pixel 8 Pro (Android 17, Chrome)

Smooth, at about 54 frames per second on the ranch. Close to the ground while tiles are still streaming in, the phone's processor is the limit rather than its graphics chip, and it can stutter for a moment.

Pixel 6 (Android 17)

Works well, a step behind the Pixel 8 Pro.

Pixel 4 XL (2019, 6 GB, Android 13)

Works, with stutter while tiles stream in (roughly 16–20 frames per second) that settles once the view has loaded. The phone runs warm, and Android closes background apps to free up memory. Fine for looking around; not ideal for a long session.

Macs with Apple silicon (M1 Pro and up), in Chrome and Safari

Smooth at full quality.

Not a fit for the 3D views

• 3 GB iPhones on iOS 16 or older — the iPhone X, XS and 8. On our iPhone X the 3D view closed within seconds of opening: that class of phone doesn't have the memory the 3D views need.
• Androids with under 4 GB of memory, or on Android 11 or older.

On both, the 2D Map still works.

Windows laptops

Measured on one machine so far — a high-end gaming laptop (Core Ultra 9, RTX 5080, 64 GB) running Chrome — on both of its graphics chips:

• On its NVIDIA chip: smooth at full quality — about 56 frames per second on the demo property and 30 on the ranch with its two dozen points of interest.
• On its integrated Intel chip, which is what Windows gives a browser by default on a laptop that has both: about 50 frames per second on the demo property and 30 on the ranch, with a heavier stutter tail. Still comfortable.

If your laptop has both chips, Windows lets you put your browser on the faster one: Settings → System → Display → Graphics, add Chrome or Edge, choose High performance, then restart the browser. A lighter laptop with only an integrated chip hasn't been measured yet — a recent one running Chrome or Edge is expected to work, and if yours doesn't we'd like to hear about it — contact us with the model and what you saw.

If it feels slow

• Let the first load finish before you fly. Detail sharpens as tiles arrive, and moving around before they've landed is where most stutter comes from.
• Close other tabs. Every open tab competes for the same memory.
• Turn the surroundings off on a slower phone. The Google 3D terrain around your property is context, not your scan. Open Viewer settings (the sliders icon next to Tips) and under Horizon → Surroundings tap Off, and the phone spends everything on your property.
• Keep the phone cool. A hot phone slows itself down to protect itself.
• The 2D Map is always the light option. When 3D isn't cooperating, switch tabs — the map opens on nearly anything.

Tip: Not sure about your device? Open the 2D Map first, then try the 3D view. If it struggles on a device that isn't listed here, tell us which one and what you saw.