Android is now called TslaMirror
The iOS and Android apps were both previously called TeslaMirror. Both platforms now use the name TslaMirror; the Android app has been renamed to match iOS. Older guides and screenshots may still show TeslaMirror. The existing App Store and Google Play listings, support website, and platform-specific casting addresses remain the same. Read the app name FAQ.
What TslaMirror does
TslaMirror mirrors an Android device to a Tesla screen through the vehicle's built-in browser. It can display apps including Waze, Google Maps, YouTube, Apple Music, YouTube Music, TikTok, Plex, and more. TslaMirror was the first app on Google Play to support Tesla app mirroring.
Latest listed version: 10.10 (build 491). See the concise and detailed release notes for Now Playing in all three modes, Classic web screen controls, screen restoration, touch fixes and optional screen debug logs.
App and casting page languages
Version 10.03 adds 27 language options. Choose a language in Settings or follow your system language; the app and casting pages use the same language. Arabic and Hebrew also have improved right-to-left layouts. See the complete list of added languages.
Choose full-screen, Single-app, or Android Auto Casting
All three modes display content in the Tesla browser over your phone's hotspot. Choose the mode for the content you want to show, then follow its setup steps.
| Mode | What appears on Tesla | Setup requirements |
|---|---|---|
| Full-screen casting | Your phone's main screen. | Start screen broadcasting in TslaMirror and grant the screen capture permission. Remote Control additionally requires Accessibility permission. |
| Single-app Casting | One app on a separate display, while your phone's main screen stays available. Screen-off playback depends on the device and app. | Android 11 or later, wireless debugging pairing, and USB debugging enabled. No USB cable is needed. |
| Android Auto Casting | Android Auto with supported navigation and music apps. | TslaMirror 9.90 or later, Android 9 or later, a working Android Auto app, and its Head unit server. Wireless debugging pairing is not needed. |
Free plan, trial, and Premium
TslaMirror is free to download. During the trial, full-screen, Single-app and Android Auto Casting each have a separate allowance of 15 free minutes per day. After the trial, full-screen casting keeps 15 free minutes per day with default video settings; Single-app Casting, Android Auto Casting and custom video settings require Premium. Check the Premium page in the app for your trial end date.
Eligible new monthly subscribers receive a 6-day free trial. Unless cancelled before the trial ends, the subscription renews automatically each month at the price shown on the Google Play purchase screen. You can cancel at any time in Google Play.
Premium provides unlimited casting through either a monthly auto-renewing subscription or a one-time Lifetime Premium purchase.
The app's free access period and Google Play's monthly subscription trial are separate. Monthly subscription and auto-renewal status remain visible even with Lifetime access. Getting Lifetime access does not automatically cancel an existing monthly subscription. Use the app's Google Play management link to review or cancel it.
Version 10.03 improves purchase and promo-code recovery, including guidance for multiple Google accounts. If a recorded Lifetime purchase cannot currently be confirmed, saved casting settings are preserved for use after recovery. See purchase recovery help.
Requirements
- Use TslaMirror only while the vehicle is safely PARKED at 0 mph / 0 kph.
- The Android device must support a mobile hotspot.
- The Tesla requires MCU2 or MCU3 hardware. This includes Model 3 and Model Y, Model S or Model X built after March 2018, and vehicles upgraded from MCU1 to MCU2 or MCU3.
- Use a 5 GHz hotspot when possible. Do not use a Wi-Fi 6 hotspot because Tesla vehicles may not support that access-point mode.
- Update the Tesla infotainment system when an update is available.
How to mirror Android to a Tesla screen
- Connect the Tesla to the hotspot of the Android device that will be mirrored.
- Open TslaMirror and make sure Tesla Proxy is on.
- Tap Start to begin screen broadcasting.
- In the Tesla browser, open https://TSL6.com for MJPEG, H.264, or H.265.
- If needed, use the direct HTTPS address https://TeslaMirror.net:9999.
Once the updated casting page is open, starting, stopping, or switching between full-screen, Single-app, and Android Auto casting on the phone automatically shows the matching page or returns to the waiting screen. This reduces manual refreshes and improves reconnection after network interruptions, while retaining support for existing casting bookmarks.
Version 10.09 improves webpage caching. If page resources are incompatible or an automatic switch does not finish, follow the update message and use Reload page to return to the current casting page.
Auto-start and setup assistance for all three casting modes
Classic Mirroring (full-screen), Single-app, and Android Auto each offer an Auto-start button that combines preparation and startup. Assistance can turn on the phone hotspot, start Tesla Proxy, and handle wireless pairing or Android Auto head unit server preparation as needed. If one step cannot finish, other available steps continue and unfinished items are shown.
Tapping a mode's Auto-start button stops any other active casting mode and switches to your selection. Required system permissions still need your confirmation.
Start hotspot assistance from the casting checklist after reviewing the prompts. It uses your existing hotspot name, password, and band, and skips the action if the hotspot is already on. Once startup is confirmed, it tries to return to the original page with your position preserved. Results update with the latest system status.
Single-app and Android Auto include checks for the hotspot, vehicle connection, and mobile data. Progress distinguishes waiting for permission, phone readiness, and browser connection. Related guidance is updated across all 29 existing interface languages.
Optional startup on Bluetooth connection
Choose a paired Bluetooth device and a casting mode, then select automatic startup or a notification you can tap to continue on the next connection. This feature is off by default.
Automatic startup requires an awake, unlocked phone and a connected accessibility service. If Android restricts opening the casting page in the background, return to the app or tap the notification. Bluetooth triggers leave existing casts running; disconnecting Bluetooth does not stop an active cast.
Use Test now and view the latest result. Messages explain unsaved rules, disabled auto-start, disconnected devices, or missing permissions, with suggested next steps.
Single-app Casting: use your phone while an app plays on Tesla
Starting with TslaMirror 9.86, Single-app Casting runs one Android app on a separate virtual display using scrcpy, while the phone's main screen remains available. It supports H.264 and H.265 and requires Android 11 or later and wireless debugging pairing. Manually enable USB debugging in Developer options and keep it enabled while using offline casting. No USB cable is needed.
- First connect your phone to trusted external Wi-Fi and open the Single-app Casting page in TslaMirror.
- Follow the in-app A–E checklist to pair wireless debugging and wait for the local service to be ready. Then switch to the phone hotspot as instructed, connect the Tesla, and check the proxy and casting status.
- Choose an app on the phone, press both volume buttons together to move the current app into casting, or choose an app from the Tesla browser's App Launcher.
On compatible devices, playback can continue with the phone locked or its display off. Browser controls include touch, Back, text input, volume, and app switching. Compatibility varies by device and app; DRM-protected content may still block capture.
Single-app Casting defaults to 5 Mbps and a 30 FPS limit, with options up to 20 Mbps and 60 FPS. Lower the bitrate or frame-rate limit if playback is not smooth. See the 10.09 release notes for pairing and connection recovery improvements.
Step A includes a six-digit pairing video tutorial that opens in YouTube or your browser. With an existing pairing and an available connection, opening the Single-app page automatically prepares casting; tapping Start can wait for preparation to finish. After stopping casting, use Pair another Wi-Fi network in Single-app settings to add a pairing while keeping existing ones. If the current connection is not ready, Step A shows Pair / check connection again.
The app launcher groups running and recently opened apps, maps and navigation, music, multimedia, social, and productivity apps. Remove individual recent entries or clear the list. The launcher, control panel, and browser address bar also show the phone's battery level, including charging, external power, and low-battery status.
Optional notification forwarding is off by default. Enable Forward system notifications to the virtual screen in Single-app settings and grant notification access to briefly show new notifications at the top of the casting page. People viewing the page can see their contents. TslaMirror does not save notification history.
For first-time pairing and extra settings on Samsung, Xiaomi, OPPO, vivo, and other phones, follow the Single-app Casting permissions and settings guide by phone manufacturer.
From 9.90, switching cast apps can keep previous apps and background tasks running, such as playing music while navigation is displayed. One app is shown at a time, and the phone’s main screen remains available.
Wireless pairing assistance and connection recovery
After you approve an assistance attempt, TslaMirror can open Wireless debugging, enable it if needed, open the pairing window, read the six-digit code, and complete pairing. It then tries to return to the original page and continue preparation. Codes are processed only on your phone and are not saved or uploaded. If you need to open Wireless debugging manually, guidance is provided and assistance can continue afterward. Manual code entry remains available.
After network changes or temporary preparation failures, the app continues trying to recover and checks multiple previously successful connections. Temporary failures no longer all require new pairing; wireless debugging connection status and offline casting service readiness are shown separately.
Android Auto on Tesla: setup and requirements
Android Auto Casting displays supported navigation and music apps in the Tesla browser, with voice commands through your phone’s microphone. No wireless debugging pairing is needed.
It requires Android 9 or later and an installed, working Android Auto app. Follow the in-app instructions to start the Head unit server and grant microphone and other required permissions. Step A includes a developer mode and Head unit server video tutorial that opens in YouTube or your browser, with clearer server readiness and setup shortcuts.
Open apps through Android Auto's built-in app menu on the casting screen. TslaMirror's separate Android Auto app catalog and default startup app setting have been removed.
Choose a fixed 480p, 720p, or 1080p resolution; 720p is the default. Updating changes the old Automatic setting to 720p and keeps existing fixed selections. Browser resizing or zooming does not change the selected resolution. Adjust content size and 30 or 60 FPS independently, and choose H.264 or H.265 according to device capabilities. See the 10.09 release notes.
Complete Android Auto's initial setup and enable developer mode before using the new accessibility assistance to start the head unit server. You can also enable an automatic attempt when entering the Android Auto casting page; this option is off by default. Follow the page's manual guidance when assistance cannot finish.
Version 10.09 fits the picture to the browser's available area, improving spacing and touch alignment. It can readjust after the window changes size while preserving your selected resolution and other video settings. Fixes also address repeated picture reloads caused by audio bar changes on some Intel Atom vehicle systems and improve audio continuity during readjustment.
Casting webpage controls
Single-app and Android Auto initially show controls and audio buttons. Expand to find other actions, or use the separate settings button. Android Auto controls hide after 45 seconds without interaction and reappear when you interact with the page.
Version 10.10 fixes transparent areas along the left and bottom of Classic Mirroring intercepting touches after the toolbar collapses or hides automatically. This fix covers MJPEG, H.264 and H.265.
Now Playing information in all three casting modes
Classic Mirroring (full-screen), Single-app and Android Auto can sync the current media app’s title, artist, album and artwork to the browser’s media controls. Enable audio on the casting page and grant TslaMirror notification access. Notification banner forwarding does not need to be enabled. The information displayed depends on the media app and browser support.
Version 10.10 improves consecutive track changes, artwork changes within a track and text updates. If artwork fails to load, valid text remains visible with a default image while loading is retried. Sync can resume when the connection or notification access is restored. See Now Playing setup and troubleshooting.
Classic Mirroring: turn the phone display off from the web
Open Settings in the web toolbar to turn the phone display off while continuing to mirror, then turn it back on. This feature supports MJPEG, H.264 and H.265 and requires Android 11 or later, wireless debugging pairing and local service setup on the phone. Turning the display off through the web controls does not lock the phone.
Classic Mirroring attempts to restore the display when the web page closes, the connection drops, casting stops, the mode changes or the app exits. Mode changes wait for restoration confirmation. Reconnecting the page does not automatically turn the display off again.
On foldable phones, restoration continues to track the original screen that was turned off, including after folding, unfolding or switching screens. If restoration is unconfirmed, return to the original folded or unfolded position and select Retry screen restoration. Debug logs remain accessible during recovery. See screen restoration help.
Optional screen debug logs
In the app’s main Settings, find Debug logs below Language. Recording is off by default. When enabled, it records only information related to turning the display off, turning it on and restoring it. View, copy, share as text or clear the logs to help report a screen issue. Existing logs can still be exported after recording is disabled.
New web screen settings, screen status messages and debug log text are available across all 29 existing interface languages.
Automatic cleanup after 15 minutes without browser access
Single-app and Android Auto each have an automatic cleanup option, enabled by default and adjustable in their own settings. After 15 consecutive minutes without browser access, Single-app casting closes apps on the virtual screen while keeping the casting page available. Android Auto stops casting; tap Start to cast again.
A connected browser keeps casting active while you watch video or listen to audio, without requiring touch input. This timeout is separate from the daily free casting allowance.
Video modes and lossless audio
Full-screen H.264/H.265 casting uses higher bitrates for Extreme and Ultimate quality in 10.03 to preserve more picture detail. These settings need more local network bandwidth. Each casting settings page also explains how to choose H.265 or H.264.
- MCU3 (AMD Ryzen): H.265 at 720p/60 fps is recommended because 1080p requires more bandwidth. MCU3 supports up to 1080p/60 fps with H.264 or H.265.
- Tesla software 2025.38.11 and later: H.265 is recommended for both MCU2 and MCU3.
- MCU2 (Intel Atom): H.264 at 540p/30 fps is recommended only for very old Tesla infotainment software.
- Lossless audio on Android 10 and later: audio supports up to 96 kHz, stereo, 32-bit Hi-Res quality with compatible Android and playback hardware.
48 kHz is generally well supported on Android devices. 96 kHz compatibility depends on the device, Android version, TslaMirror version, and playback hardware.
Compatibility update — September 22, 2026: Pixel 9a running Android 17 with the latest TslaMirror app now supports 96 kHz audio in our testing. Earlier Pixel 9a tests did show problems; those results describe the older software combination, not a permanent hardware limitation. Pixel 5 also worked well in earlier tests.
An Android update may have improved the underlying audio support, but the cause has not been isolated from app updates. Update both Android and TslaMirror, then test 96 kHz on your own device. If audio is unstable or missing, use 48 kHz.
Local network and privacy
Mirroring traffic stays inside the Android hotspot network and does not pass through a public mirroring server. The Tesla may still use cellular data for its own online services while connected. The Android device can also use another nearby internet connection and does not require a SIM card solely for mirroring.
TslaMirror, its VPN component, and its Accessibility component do not collect personal information, usage statistics or analytics. Optional screen debug logs are off by default and record only display off/on and restoration information when enabled; you can view, copy, share or clear them.
Why TslaMirror requires VpnService
Tesla browsers block standard private-LAN ranges such as 192.168.*.*. TslaMirror still uses the virtual IP address 100.99.9.9 internally with a local VPN tunnel so the Tesla browser can reach the web server on the Android device. The Tesla browser no longer supports opening this IP directly, so it is not an address users should enter in the current app.
The VPN tunnel does not connect to a public VPN server. One endpoint is the Android device and the other is the Tesla. The local web server is not accessible from the public Internet, and TslaMirror does not redirect or manipulate network traffic from other apps. VpnService is a core requirement because the Tesla browser otherwise cannot reach the local server.
A third-party VPN may work alongside TslaMirror on some configurations. Follow the startup order and bypass rules in the FAQ, and make sure 100.99.9.9 is allowed through.
Remote Control and Accessibility
Remote Control lets you operate the Android device from the Tesla touchscreen or a mouse and requires Accessibility permission. Version 10.09 can also use accessibility assistance for wireless pairing, hotspot setup, and Android Auto head unit server preparation after you approve the assistance.
The app shows Accessibility permission and service status separately, with a shortcut to system settings. Bluetooth auto-start requires the service to be connected. Remote Control settings now stay in sync after authorization from another casting page.
Pairing codes are processed only on your phone and are not saved or uploaded.
Safety, download, and support
Use TslaMirror only while parked. Local laws may restrict use of a built-in vehicle browser. TslaMirror is not affiliated with or endorsed by Tesla, Inc.
The official Android version is available only from Google Play. This website does not distribute an APK. For help, email TeslaMirror@hustmobile.com.