How to FaceTime Android from iPhone: The Link Is the Call

FaceTime works with Android in 2026, but the phrase “FaceTime Android” can create the wrong expectation. There is no Apple FaceTime app for Android and the Android user does not place a normal FaceTime call from a contact card. The cross-platform object is the FaceTime link: an Apple-device user creates it, the Android user opens it in a supported web browser, and the call happens there.

That distinction explains most of the setup. It also explains most failures. If the Android user never receives a valid link, browser permissions are irrelevant. If the join page opens but the camera is black, recreating the link is usually the wrong layer to troubleshoot. And if you need an Android user to initiate spontaneous calls to you without an Apple-created link, FaceTime is simply not the right cross-platform calling system.

In iOS 27, create the invitation from New Call

Apple’s current iPhone guide puts link creation inside FaceTime’s New Call flow. On the iPhone, open FaceTime → New Call → Create Link, then share the link through Messages, Mail, or another messaging service. You can also put a FaceTime link into a Calendar event when the call needs a scheduled meeting point.

This is worth calling out because older instructions often show a large Create Link button on FaceTime’s main screen. That was correct for earlier software, but it is not the clearest path for the current iOS 27 interface.

The recipient does not need an Apple Account to join from Android. Apple says a non-Apple participant can join one-to-one or Group FaceTime from a WebRTC-capable browser without signing in.

The Android side is a browser session, not an Apple account setup

For the Android participant, the clean path is short:

1. Open the FaceTime link.
2. Use the latest version of Google Chrome or Microsoft Edge.
3. Enter the name that should appear in the call.
4. Allow the browser to use the microphone and camera when prompted.
5. Tap or click Join.
6. Wait for the Apple-side host to admit you.

Apple’s current support requirements are deliberately modest: an Android or Windows device, a stable Wi-Fi or cellular connection, and a current Chrome or Edge browser. Sending video also requires H.264 video-encoding support. You do not need to install an APK, create an Apple Account, or move your phone number into an Apple service.

“Waiting to be let in” is not a connection failure

The web participant enters a waiting state until the host admits them. That is a security boundary, not evidence that FaceTime is stuck. On the Apple device, watch for the join request and approve the participant.

This matters when helping a less technical family member. If their screen already shows the FaceTime room and a waiting message, do not have them clear Chrome data, reset networking, or repeatedly request new links. The browser has already reached the call. The next action belongs to the host.

For a family call, it is often easiest to send the link first, ask the Android user to open it, and remain in FaceTime long enough to approve the request. Apple supports browser participants in both one-to-one and Group FaceTime calls; Group FaceTime on iPhone supports up to 32 participants, subject to regional availability.

A working FaceTime link has three separate permission layers

When the page opens but audio or video fails, identify which layer is actually broken.

The link opens, but nobody can see the Android user

Check the browser’s camera permission for the FaceTime site and make sure the correct camera is enabled in the call controls. If the browser was denied camera access earlier, refreshing the page without changing that permission may reproduce the same black-video result.

The Android user can see everyone but cannot be heard

Check microphone permission and the microphone control inside the FaceTime page. A valid link does not override Android or browser privacy permissions.

The link does not reach the FaceTime join page

Move one layer outward. Open the URL directly in a current Chrome or Edge build, verify the network is working, and ask the Apple user to copy or share the FaceTime link again if necessary. Do not start with camera permissions when the FaceTime page itself never loads.

This symptom-based order is safer than treating every failure as “FaceTime not working.” It preserves the part of the chain that has already proved itself.

Web FaceTime deliberately has fewer features

An Android participant is joining FaceTime on the web, not receiving the full FaceTime app. Apple explicitly says SharePlay and screen sharing are not available in FaceTime on the web. If a cross-platform meeting depends on an Android participant sharing their screen, that limitation should decide the platform before the call starts.

The absence of a feature in the browser should not be diagnosed as a permissions bug. A missing SharePlay or screen-sharing control is a product boundary. Likewise, Apple-device features elsewhere in FaceTime should not be assumed to have Android equivalents just because basic camera and microphone calling works.

The Android user can share the link, but that is not the same as owning the call system

Apple’s current web interface lets a participant copy or share the FaceTime link with another person. That is useful for getting another guest into the same room. It does not turn Android into a native FaceTime endpoint with the same calling identity, contact integration, or Apple-device workflow.

This is the subtle point many “FaceTime for Android” guides miss. Cross-platform FaceTime is best understood as a link-addressed room. Once the link exists, people can use it to gather. The Apple side remains the place where the native FaceTime experience and host admission live.

Use the same link when the room is the thing you want to preserve

You do not need a fresh URL for every troubleshooting attempt. If the link reaches the join page and the host can see the request, it is already doing its job. Reuse it while you fix camera, microphone, browser, or network issues so you change one variable at a time.

For recurring family conversations, a FaceTime link in a Calendar event can also be easier than explaining the setup again each time. The important thing is that participants treat the URL like an invitation: share it with the people you intend to invite rather than posting it publicly.

Mainland China is a hard regional exception

Apple states that FaceTime links are not supported in China mainland. Apple also says creating a FaceTime call link is not supported on iPhone models purchased in China mainland. That is not the kind of failure a browser reset or a different Wi-Fi network can fix.

Region-specific service availability should therefore be checked before spending time on device troubleshooting. FaceTime audio and Group FaceTime also have availability differences across countries and regions.

If the iPhone cannot create the link, diagnose the Apple side first

On current iOS, FaceTime itself is configured under Settings → Apps → FaceTime. Make sure FaceTime is turned on. Apple allows FaceTime to use an Apple Account, a phone number, or both depending on setup.

If the FaceTime app was removed from the iPhone, reinstall it before expecting the normal FaceTime workflow. If FaceTime works normally but Create Link is missing, confirm the iPhone’s software and regional/device restrictions rather than changing anything on the Android phone. The Android participant cannot repair a link that the Apple side cannot create.

Do not use destructive fixes for a browser-call problem

Three common pieces of advice are disproportionately disruptive here:

• Do not reset all iPhone network settings just because one Android guest cannot join. First establish whether other FaceTime calls work and whether the link opens.
• Do not sign out of the Apple Account as an early FaceTime-link fix. Current FaceTime can even be configured with just a phone number in supported setups; account sign-out changes far more than this call.
• Do not erase browser data or the phone before checking the specific site permission, current browser, link, network, and host-admission state.

A good control test is smaller: create one link, open it on the Android device in an updated Chrome or Edge browser, allow camera and microphone, tap Join, then confirm whether the host sees the request. That sequence tells you exactly how far the call path gets.

Know when FaceTime is the wrong cross-platform tool

FaceTime links are excellent when the Apple user is the organizer and the Android participant only needs to join a conversation. They are also convenient for scheduled family calls because the guest does not need an Apple login.

They are a poor fit when both sides need equal app-native calling, when the Android user must initiate calls independently without relying on an Apple-created room, or when the Android participant needs web features Apple does not provide, such as screen sharing. In those cases, a service with full native clients on both platforms is structurally better than trying to make FaceTime behave like one.

The most reliable mental model is simple: FaceTime does not move onto Android; the Android user enters a FaceTime room through the web. Once you know which side owns the link, which side is waiting for admission, and which controls belong to the browser, the setup becomes much easier to explain—and much harder to troubleshoot at the wrong layer.