Key point

Cloud script sync works across your devices signed in to the same account, with active Pro membership and an unrestricted device session. Use a version that provides Cloud Sync. With a network connection, return to the script library in the foreground and leave this device unpaused. Local saving and cloud sync are separate: a saved edit is not proof that another device has received it.

What syncs

• Script titles, bodies, in-document formatting, structured cues, hotwords and pronunciations, and groups sync together. Compatible outline-capable versions also retain chapter outlines.
• Reading position, scroll speed, display font size, mirroring, transparency, search and filter state do not sync. Formatting applied inside the script differs from prompt display settings.
• Recognition recordings, captured videos, extracted audio and other media are not uploaded through script sync. Built-in sample scripts are excluded.
• Deletion, restore and permanent-deletion states also sync for account-owned scripts. Confirm the target rather than treating the action as affecting only this phone.
• Eligible unowned local scripts join the current account when sync eligibility is first confirmed. Scripts are isolated by account: signing out or switching accounts hides the previous account's scripts; sign back into that account to see them. They are not handed to another account.

First sync and changing devices

1. Confirm login and active Pro membership in My on both devices, using the same account. Resolve any device-security restriction first.
2. Connect to the network, return to the script library, and open Cloud Sync beside the group selector. Check the status and pending/action-needed counts.
3. If this device is paused, choose Resume Sync; otherwise use Check Now. On clients that provide this feature you can also pull down when the list is at the top and its header is fully expanded.
4. Keep the library in the foreground until checking and syncing finish. Leaving it stops new polling and downloads, but already-sent requests may still complete.
5. After the source device reports Synced, check sync in the other device's library and open the script. If missing, select All groups and clear the search first.

Status and pausing

Checking compares updates; Syncing processes tasks; Pending means work remains; Action Needed requires reading the details. Check the last-sync time as well. List Refreshed is not cloud-sync completion: while signed out, a pull-to-refresh updates only the local list. Pause This Device affects this account on this device, not every device. Resume explicitly; refreshing, signing in again or renewing membership does not undo your pause choice.

Connection and eligibility problems

• No network or incomplete sync: restore Wi-Fi or mobile data, return to the library and use Check Now or Retry Sync when offered. If Wi-Fi and mobile data are off, reconnect before syncing.
• Unavailable or stuck pending: confirm the library is foreground, unpaused and connected. Check Action Needed items, or try later if the service is unavailable. Repeated refreshes may not bypass retry delays.
• Signed out or Pro required: check login and membership in My; if the session expired, follow the prompt to sign back into the same account. If My shows signed in, return to the library and check again, or reopen the app. Do not clear app data as the first fix.
• Device needs attention: follow Account and Security to resolve device/session restrictions. Changing networks alone does not remove them.

Quota, content and version problems

• Cloud script limit reached: the limit is 1,000 scripts including Trash. Review Manage Trash. Moving a script into Trash does not immediately release its slot; permanently delete only items you no longer need, since that cannot be undone.
• Monthly sync allowance exhausted: wait for allowance recovery; local scripts remain. This differs from the script-count limit. Emptying Trash or repeatedly retrying does not restore monthly allowance.
• Content or group name needs changes: open Items Needing Attention, inspect the reported field/position, choose Edit or Rename Group, save, and retry from the library. Titles, cues and hotwords can be flagged too. Tool allowlists or ignored findings do not guarantee upload approval.
• Content checks unavailable: reopen or update the app and retry. Checking has not completed; this is not approval and should not be bypassed by disabling checks.
• Invalid script format: inspect and save the script again. The current sync-body limit is 20,000 characters; preserve historical oversized originals before splitting into shorter scripts. Persistent structure errors should be reported with local content retained, not fixed by uninstalling, clearing data or downgrading.
• Update required, or the cloud script now has an outline: update participating clients to a compatible version and check again from the library. Pending edits are retained and may become a conflict copy on recovery. Do not force an old version to overwrite the cloud script or delete local work to make syncing proceed.

Conflict copies, Trash and membership expiry

Editing the same script on multiple devices before sync finishes can produce a conflict copy. Let processing finish, compare original and copy, then retain and reconcile the required text. Do not delete solely because titles match. Sync before switching devices to reduce conflicts.

Cloud Trash retains deleted scripts for 30 days; Restore still requires the applicable sync eligibility. Permanent deletion cannot be undone. Membership expiry does not clear local scripts, but cloud scripts are retained for 90 days after expiry and then cleaned under the retention policy. Cloud-expiry cleanup does not remotely erase local content that must be kept. Sync is not permanent version-history backup; keep a separate copy of important scripts.

Sync and privacy

Sync submits script content to the account service and private cloud storage. Uploads receive local prechecks and, when enabled, cloud content review. On-device AI recognition and cloud script sync are separate; local speech recognition does not mean a synced script never leaves the device. Pausing stops new sync work but may not withdraw requests already submitted.

When to send feedback

Retain local scripts and report the device, app version, failure time, sync state, detail message and whether another device received the content. Provide only what is needed; never include passwords or verification codes. Review diagnostic material before actively sharing it.