Figma Mirror Sync Failures: Diagnostic Guide for Mobile Connectivity Issues

Figma Mirror stops updating or shows a disconnected state when the mobile app cannot maintain a live HTTPS session to Figma’s servers. The useful takeaway is to verify server health and network path first, then app and device state, then file-specific factors. Mirror only runs on supported mobile OSes; macOS and Windows are not supported.

Recognizable failure modes

A green status indicator in Mirror means a live connection. A red or grey indicator, stale frames, or repeated "syncing" with no progress are the recognizable conditions. The file may open in a browser on the same network but not update in Mirror, or Mirror may fail to load a specific file while others load.

Cause to symptom table

Ordered diagnostic checks

1. Confirm Figma service and file accessibility

Open a web browser on the same mobile network and load the file directly in Figma. This confirms the file is accessible and current, and that the network can reach Figma. If the browser cannot load the file, the issue is network or account, not Mirror.

Check Figma’s public status page for reported incidents. A global outage will affect all Mirror sessions regardless of device.

2. Verify network path for Mirror

Mirror uses HTTPS. Verify the mobile device has stable Wi-Fi or cellular connectivity. Temporarily disable VPNs and corporate firewalls that may block outbound HTTPS to Figma. Ports 443 and 80 are commonly required for web traffic.

Risk: disabling VPN reduces privacy on public networks. Re-enable after testing.

3. Validate app and device state

Ensure Mirror is updated to the latest release from the App Store or Google Play. Older builds can contain sync bugs.

Confirm the device OS meets documented minimums. Current documentation references iOS 13+ and Android 9+ as minimums; verify the exact requirement in Figma’s official docs for your release.

Sign out and sign back in to refresh the session token. On iOS, offload and reinstall the app to clear stale session data. On Android, clear storage for the Mirror app via Settings → Apps → Mirror → Storage. Reinstalling removes local preferences.

4. Isolate file-specific factors

Very large files or files with many layers can delay sync. Create a diagnostic decision: open a different, smaller file in Mirror on the same device and network. If the smaller file syncs and the large file does not, the problem is file-specific.

If the file is shared with a restricted or private team, confirm the signed-in account has view and sync permission for that file. Permission issues appear as missing files in Mirror while visible in the web app for other accounts.

5. Use in-app diagnostics

In Mirror, open Settings → Diagnostics. The diagnostics view shows network reachability information and recent HTTPS request attempts. Use it to confirm requests are reaching Figma’s servers from the device.

Observe the status indicator after each change. Green indicates a live connection; red signals a sync failure.

Fixes tied to findings

• Network block found: adjust firewall/VPN rules to allow HTTPS to Figma, or switch networks.
• Outdated app found: update Mirror, then sign in again.
• Cache corruption found: clear app storage or reinstall, then sign in.
• OS too old found: update the device OS or use a supported device.
• File-specific delay found: work with a simplified version for review, or reduce complexity in the source file.
• Permission missing found: request access from the file owner or switch to an account with access.

Escalation criteria

Escalate when the same failure persists across multiple devices, networks, and files after updating the app and clearing cache, and Figma status shows no incident. Collect device model, OS version, Mirror version, network type, and whether the file loads in a browser. Do not escalate for unsupported platforms; Mirror does not support macOS or Windows.

Limitations and verification

Mirror behavior can vary by release. Version assumptions above should be verified against current Figma documentation before use. A practical verification is to complete the ordered checks and confirm a green status indicator and real-time updates for a known good file on the same network.