Meta Quest casting to a phone depends on three parts working together: the headset, Meta Horizon mobile app, and local Wi-Fi network. When casting fails, the useful question is not which generic fix to try next. It is how far the connection gets.
Open the Meta Horizon app and check whether your Quest headset appears under the device area.
Then try a cast and match the result:
- Headset does not appear in Meta Horizon: fix the phone-to-headset connection first.
- Headset appears, but casting stays on Connecting: investigate the local Wi-Fi path.
- Cast starts and immediately stops or freezes: focus on network stability and load.
- Web casting works but phone casting does not: the phone or Meta Horizon app is the stronger suspect.
- Casting fails only inside one game or app: the content itself may restrict casting.
This approach avoids resetting a Quest that is actually working normally.
Headset Does Not Appear in Meta Horizon
Casting cannot work reliably when the mobile app is not communicating with the headset.
Start here before changing router settings.
Confirm the Meta account
Check the account signed in to Meta Horizon on the phone and the active account on the headset.
This matters especially when:
- several people use the Quest;
- the headset was originally configured by someone else;
- you recently switched accounts;
- Meta Horizon was reinstalled;
- you have multiple Meta profiles.
Use the account that is associated with the headset and casting session.
Leave Bluetooth enabled
The cast stream itself depends heavily on the network, but Bluetooth remains important to the relationship between the phone, Meta Horizon, and Quest.
Turn Bluetooth on, then fully close and reopen Meta Horizon.
On Android, check:
Settings > Apps > Meta Horizon > Permissions
Allow the relevant Nearby devices or Bluetooth permission when shown.
On iPhone, open the Meta Horizon app settings and make sure Bluetooth access is allowed. Also enable Local Network access when iOS presents that permission.
Permission wording can vary by OS version.
Update both sides
Update the Meta Horizon mobile app from Google Play or the App Store.
Also check the Quest for an available Horizon OS update.
Restart the phone and headset after updating, then check whether the Quest appears in Meta Horizon before attempting another cast.
Do not remove a working headset association as a routine first step. Re-pairing adds another variable and is more appropriate when the app genuinely no longer recognizes the headset.
Headset Appears, but Casting Stays on Connecting
This result shifts attention toward the local network.
Meta’s current platform documentation describes Quest casting as streaming to another device on the same network.
Check the Wi-Fi network name on the phone and headset.
They should be on the same private local network.
For example, this is a problem:
Phone: HomeWiFi
Quest: HomeWiFi-Guest
Both devices may have internet access while being prevented from talking directly to each other.
Guest and public Wi-Fi are poor tests
Guest, hotel, airport, school, and workplace networks commonly isolate connected devices.
Home routers can do the same through settings named:
- AP isolation;
- client isolation;
- wireless isolation;
- guest isolation.
When isolation is active, the phone and Quest can both reach the internet without being able to discover each other locally.
Move both devices to the normal private network.
On routers that expose separate 2.4 GHz and 5 GHz network names, put both devices on the same band while troubleshooting. A faster 5 GHz or 6 GHz connection is preferable for casting when supported and signal strength is good.
Temporarily remove a VPN from the test
A VPN, firewall, DNS filter, or parental-control system can interfere with local discovery.
Temporarily disconnect the phone VPN and retry the cast.
If that solves it, look for a setting that allows local-network or LAN access rather than permanently abandoning the VPN.
Do not disable the router firewall or general network security just to make casting work.
Prove Whether the Router Is Responsible
A second private Wi-Fi network is one of the strongest tests available.
Connect both the Quest and phone to another suitable private network and retry casting.
Casting works there
The headset and phone have demonstrated that they can cast together.
Return to the original router and investigate:
- guest/client isolation;
- separate network segments;
- mesh-node behavior;
- VPN routing;
- filtering;
- weak Wi-Fi;
- router firmware.
A factory reset of the Quest would not address that evidence.
Casting still fails
The original router is less convincing as the sole cause.
Return to Meta Horizon permissions, account state, software versions, and another casting destination.
Web Casting Works but Phone Casting Does Not
This is another useful split.
When the Quest can cast successfully to a supported web destination but not to the phone, the headset has already demonstrated that its casting function can work.
Concentrate on the mobile side:
- Meta Horizon app version;
- Bluetooth and local-network permissions;
- phone Wi-Fi;
- correct Meta account;
- app state.
At this point, reinstalling Meta Horizon becomes more reasonable.
Before uninstalling it, make sure you know the correct Meta account credentials.
After reinstalling, sign in, grant the required connectivity permissions, and confirm that the headset appears in the app before trying to cast.
Do not factory reset the Quest merely because the phone app needed reinstalling.
Web Casting Also Fails
When multiple casting destinations fail, repeatedly clearing the mobile app is unlikely to be enough.
Check the common parts:
- Quest system software;
- local network;
- Meta account;
- whether the current VR app permits casting.
Restart the router normally and allow it to come back online completely before reconnecting both devices.
Also restart the headset rather than only putting it to sleep.
If casting fails across multiple destinations and multiple networks, Meta support becomes more useful than destructive resets.
Casting Starts but Immediately Stops
A cast that starts proves more than one stuck forever on Connecting.
The devices have discovered each other and begun the session. Network stability now becomes more important.
Move the phone and headset closer to the router and pause large downloads, cloud backups, or other heavy network traffic.
If the headset is recording video at the same time, stop the recording and test casting by itself.
Keep the Quest sufficiently charged during a longer casting session.
Restart the router when the problem affects multiple casting attempts, especially when it worked normally before.
A cast that works reliably on another Wi-Fi network points back to the original network rather than the headset.
Casting Works but Is Laggy or Freezes
Some delay is inherent to wireless casting because the headset has to encode the view, transmit it, and the receiving device has to display it.
Severe freezing is different.
For an unstable stream:
- use strong 5 GHz or 6 GHz Wi-Fi where supported;
- keep the Quest and phone within good router coverage;
- avoid isolated or congested public networks;
- stop simultaneous headset recording;
- pause bandwidth-heavy traffic;
- test another Wi-Fi network.
When the phone is smooth near the router but freezes farther away, treat signal quality as evidence rather than reinstalling Meta Horizon.
Casting Fails Only in One Quest App
Test another game or the Quest home environment.
Meta’s platform documentation allows developers to control sharing features, and licensed or protected content can restrict what appears during casting.
When other Quest content casts normally, your network, phone, and general casting path are already functioning.
Do not reset network settings or factory reset the headset for a problem isolated to one title.
Check that app’s own support information or restrictions instead.
Start the Cast From the Headset Again
When the phone and headset already recognize each other, stop the failed session and initiate a fresh cast from the Quest interface.
The exact labels can change as Horizon OS evolves, but use the headset’s Camera/Cast or Sharing/Cast controls and choose the mobile destination when offered.
Then follow the prompt in Meta Horizon.
Avoid relying on old tutorials that still refer to the Oculus mobile app. Meta’s current mobile companion is Meta Horizon.
Android Phone Sees the Quest but Cannot Cast
When Meta Horizon lists the headset correctly on Android, do not spend time re-pairing first.
Check the local-network conditions and the app’s Nearby devices permission.
Also make sure Android has not heavily restricted Meta Horizon’s background activity during the attempt.
Temporarily keep Meta Horizon open on screen while starting the cast.
If the phone itself is having broader Wi-Fi trouble, WiFi Connected but No Internet on Android can help separate the phone’s network problem from Quest casting.
iPhone Sees the Quest but Cannot Cast
On iPhone, the headset appearing in Meta Horizon tells you pairing is at least partly intact.
Check the Meta Horizon permissions in iOS, especially Bluetooth and Local Network when available.
Keep the app open during the test and make sure the iPhone has not switched away from the Wi-Fi network being used by the Quest.
If Web casting succeeds while the iPhone continues to fail, reinstalling Meta Horizon is a more proportionate step than resetting the headset.
A Phone Hotspot Is Not a Good Baseline
A hotspot can provide internet while handling local device-to-device communication differently from a conventional home router.
That makes it a poor first network for diagnosing Quest casting.
Use a normal private Wi-Fi network where possible.
When casting works on home Wi-Fi but not through a hotspot, the result does not show that the Quest casting feature is broken.
For a broader Android tethering failure, see Android Hotspot Not Working? Here’s How to Fix It.
Do Not Factory Reset a Quest That Only Has a Casting Problem
A factory reset is disproportionate when:
- games run normally;
- Wi-Fi works;
- the headset appears in Meta Horizon;
- tracking and controllers work;
- only phone casting fails.
Those signs show that much of the headset is already functioning.
A reset becomes a support-guided last resort when the headset has broader system problems or casting fails across known-good networks and destinations after account and software checks.
Meta’s current developer documentation confirms that Quest sharing supports casting the headset view to other devices on the same network, while its casting troubleshooting material also notes that protected content can be restricted during casting.
The most useful result is usually where casting stops. A missing headset in Meta Horizon is a phone-to-headset problem. Endless Connecting points toward local networking. A cast that starts and then collapses points more toward stability. And successful Web casting sharply reduces the reason to keep changing the Quest itself.
