Does macOS Screen Sharing work over the internet?

You turned on Screen Sharing in System Settings, connected to your Mac from another room, and it was perfect. Then you tried the same thing from a cafe, and nothing happened at all. This is the single most common point of confusion about Apple's built-in remote access, and the answer is more useful than a plain yes or no.

The short answer

No. macOS Screen Sharing does not work over the internet on its own. It is designed for your local network, and outside that network it will not find your Mac at all. It is not broken and you have not misconfigured it - reaching across the internet is simply not something it does by itself. Everything below is about the four ways people bridge that gap, and what each one costs you.

Those four are: forwarding a port on your router, running a VPN back home, a mesh VPN such as Tailscale, or an app that traverses NAT for you - Screens, Jump Desktop, RustDesk or Servey, which is the app we make. Three of the four are worth your time and one of them is not, and the comparison below says plainly which is which.

Why it stops at your router

Two separate things have to happen for a screen sharing session to start: your device has to find your Mac, and then it has to open a connection to it. Screen Sharing fails at both once you leave the house.

Discovery uses Bonjour, Apple's local network service discovery. It is what makes your Mac appear in the Finder sidebar automatically, and it is deliberately confined to the local network - Bonjour announcements do not cross a router. Once you are on a different network, there is nothing to discover.

The connection itself runs over VNC on port 5900. On your own Wi-Fi that is a direct hop. From outside, your Mac is sitting behind your router's NAT with no public address of its own, so an incoming connection has nowhere to land. If you are on mobile data, your phone is usually behind carrier-grade NAT too, which means neither end has a reachable address. That is the whole problem, and it is a networking problem rather than an Apple one.

Apple used to solve this, then removed it

If you remember this working years ago, you are not misremembering. Back to My Mac did exactly this job: it used your iCloud account to find and reach your Mac from anywhere, with no router configuration. Apple discontinued it in macOS Mojave in 2018 and pointed users toward third-party alternatives. Nothing built into macOS has replaced it since, which is why this question keeps being asked.

One thing that does still work over the internet is asking to share screens through Messages with another Apple ID. That is built for helping another person with their Mac, and it needs someone at the other end to accept the request - so it is no use for reaching your own machine while you are out.

Does Apple Remote Desktop fix it?

No, and this catches people out because the name sounds like it should. Apple Remote Desktop is a paid admin tool on the Mac App Store, built for managing a room full of Macs - software distribution, reporting, running commands across many machines at once. It speaks the same underlying protocol and hits the same NAT wall. Buying it does not give you internet access to your Mac; it gives you fleet management on a network you can already reach.

The third name in this family is Remote Management, the separate checkbox in Sharing settings. That is the toggle Apple Remote Desktop uses. It is not a different way of reaching your Mac from outside either.

The four ways to actually reach it from outside

• Only ever on your own Wi-Fi: plain Screen Sharing is fine, and free.
• Comfortable running infrastructure: a VPN or Tailscale, then Screen Sharing over it.
• You want it to just work from a phone: a purpose-built remote access app, and if you need one working today rather than soon, buy Screens or Jump Desktop.
• Never: forwarding port 5900 to the internet.

How Servey handles this

Servey was built for precisely the gap Back to My Mac left behind. There is no router configuration at any point - no port forwarding, no VPN to maintain, no dynamic DNS, no static IP. You sign in with Google on your Mac and on your iPhone or iPad, and your Mac is simply there. It works out which path to use on its own: on your own Wi-Fi it streams a direct hardware-encoded HEVC feed, which is sharper than the VNC picture Screen Sharing gives you and stays legible when you pinch to zoom into small text. Away from home it switches by itself to a private peer-to-peer connection, end-to-end encrypted between your own two devices, that goes direct whenever your network allows it - and its NAT traversal is built to hold up on strict carrier networks and CGNAT, exactly where port forwarding cannot help you.

The other thing Screen Sharing cannot do is give you a shell. Servey puts a genuine terminal on your Mac one tap away from the mirrored screen, so when the answer is a command you type it, and when the answer is a dialog box only the GUI can dismiss, you are already looking at it. Servey is Apple-only and it reaches your own Mac rather than any machine anywhere, which is a trade we made deliberately.

Bottom line

macOS Screen Sharing is excellent software with one hard boundary: your local network. Apple has not shipped a built-in way across that boundary since 2018, so every solution is either infrastructure you run yourself or an app that handles it for you. If you are happy maintaining a VPN, Screen Sharing over Tailscale is a perfectly good answer. If you would rather sign in once and have your Mac appear on your phone - with a real terminal beside the screen - that is what Servey is for, and it launches soon from $1.99 a month, or ₹99 in India.