Duet Display, Sidecar, Luna Display, Spacedesk, Deskreen — None of Them Worked on Tesla

I wanted to use my Tesla’s touchscreen as a second monitor for my Mac. I tried every screen sharing and display extension app I could find — Duet Display, Sidecar, Luna Display, Spacedesk, Deskreen. None of them worked. Here’s why.

When I decided to use my Tesla as a mobile office, the first problem was screen real estate. Working on a single MacBook, switching between a code editor, Slack, email, and a browser, has its limits. Being able to use the large touchscreen inside the car as a second monitor would have been perfect.

I had no intention of building this myself. There are plenty of apps that extend or share your screen. Lots of people use an iPad as a second display. There are free tools that connect Windows PCs and tablets. I figured one of them would work with the Tesla screen too.

I tried them all. None of them worked.

This is the setup I wanted from the start.

What’s interesting is that the reason each one failed was different. And when you put those reasons together, you start to see why the Tesla environment is so difficult.

Three constraints of the Tesla environment

When you trace why each existing app gets blocked, it all comes down to three structural constraints of the Tesla environment.

First, you can’t install apps. Tesla’s infotainment system has no app store. Sideloading isn’t possible either. There’s essentially nothing a user can install, and the only way to communicate with the outside world is through the built-in browser.

Second, modifying the vehicle is risky. Attaching or connecting any external hardware to the car requires some form of vehicle modification, which can void your warranty and may cause the vehicle to malfunction. That’s a big risk to take just to set up a mobile office.

Third, there are network policy restrictions. The Tesla browser blocks access to private IP ranges (local addresses like 192.168.x.x) at the policy level. Even if you’re on the same Wi-Fi network, you can’t reach your MacBook’s local IP from inside the Tesla browser.

Because all three of these constraints exist at once, screen sharing solutions that work fine in normal environments hit walls one after another inside a Tesla.

Why each Tesla second monitor app fails

Duet Display is a polished screen extension app built by former Apple engineers. It supports both Mac and Windows, and the latency is very low. For anyone wanting to use an iPad or iPhone as a secondary monitor, it’s pretty much the standard choice.

But Duet requires native apps to be installed on both the sending and receiving sides. There’s no way to install an app on a Tesla, so it stops there.

Apple Sidecar is a feature built into macOS. You can use an iPad as a Mac’s extended display with no extra installation, the integration is smooth, and it’s free. For people who use a Mac and an iPad together, it’s one of the best options available.

But it only works inside the Apple ecosystem. Tesla isn’t a target, and Windows users can’t use it either.

Luna Display is a hardware-and-software combo solution from Astropad. You plug a small dongle into your computer, the OS sees it as an external monitor, and you can send the display to an iPad or another Mac. Latency is very low and image quality is good.

There are two problems. One is that you have to keep the dedicated dongle plugged into your computer at all times. The other is that the receiving side also needs a dedicated app, which can’t be installed on a Tesla.

Spacedesk is an old free solution on Windows. It creates a virtual display and sends the extended screen to tablets or smartphones. It also offers an HTML5 viewer, so you can connect through a browser. The “no app needed on the receiving side” part initially looked like it might be the closest fit for Tesla.

But two issues. First, the sending side is Windows only. Mac users aren’t part of the picture. Second, it’s LAN-based — the receiving device has to connect directly to the sending PC’s private IP, and the Tesla browser blocks exactly that.

Deskreen is an open source free app, and the receiving side just needs a browser. It supports Mac, Windows, and Linux on the sending side. The “browser only” part also looked promising at first.

But again two problems. First, for Deskreen to function as a true extended display, you need additional hardware like a Dummy HDMI Adapter to create the virtual display. Having to keep that connected to your computer all the time is a burden. Second, Deskreen is also LAN-based, so it hits the same private IP block as Spacedesk.

Tesla’s built-in Zoom is a different kind of attempt. The idea is that you could use Zoom’s screen sharing feature to send your laptop screen to the Tesla display. No installation needed, and it’s already there.

Get SideDisplay’s stories in your inbox

Join Medium for free to get updates from this writer.

Remember me for faster sign in

But there are a lot of limitations. It doesn’t support full screen — the meeting participant view is always there. The traffic goes through Zoom’s servers, so latency is high. If you’re using phone tethering for internet, it continuously consumes cellular data. And above all, it’s mirroring or single-app sharing — not a true extended display. Just because a video conferencing tool has a screen sharing feature doesn’t make it an extended monitor.

Putting it together: why all five apps fail

Look at why each product fails, and they all hit at least one of Tesla’s three constraints.

• Duet Display and Apple Sidecar are blocked by the app installation constraint
• Luna Display is blocked by both the app installation and the hardware constraint
• Spacedesk is blocked by the network constraint and the sending-side OS limitation
• Deskreen is blocked by both the hardware and the network constraints
• Tesla’s built-in Zoom isn’t an extended monitor tool to begin with

Each of these is a well-built product. They just weren’t designed for the Tesla environment. That’s not a flaw in any of them — it’s the result of being designed for different environments.

So what would actually work?

Reverse-engineering from the analysis above, you can derive what a screen extension solution for Tesla would have to look like.

• No app installation required on the receiving side (browser only)
• No additional hardware required on the sending side (virtual display in software only)
• Able to bypass the private IP block
• No cellular data consumed while screens are shared
• Supports both Mac and Windows
• A real extended display, not mirroring
• Low enough latency for real-time work

Nothing met all of these conditions.

So I built it.

How SideDisplay solves the Tesla second monitor problem

SideDisplay was designed to address each of these constraints head-on.

It uses WebRTC to run directly in the browser. WebRTC is a standard that’s already built into the Tesla browser, so the receiving side needs no app. The private IP block is bypassed by using macOS Internet Sharing or Windows Mobile Hotspot.

The virtual display is created in software. No Dummy HDMI Adapter needed. Your MacBook’s desktop actually extends, and you can drag windows over to the Tesla screen. It’s a real extension, not mirroring.

The Tesla screen running independent content — not a mirror of the laptop.

It supports both Mac and Windows. The latency is low enough that coding, document work, Slack, and email all feel real-time.

These days I work from my Tesla once or twice a week using this setup. Working from a car for half a day or more also depends a lot on where you park, which I covered in a separate post.

Building a new app isn’t an easy decision. If good solutions already exist, the rational thing is to use them. But the specific combination of constraints the Tesla environment creates — no app installation, hardware modification being unrealistic, the private IP block — meant nothing on the market could pass all of them.

So I built it myself. That’s SideDisplay.

SideDisplay — turn your Tesla screen into a wireless extended monitor.