# Cross-Device Copy & Paste

This guide walks you through completing your first cross-device clipboard loop: copy a test string on device A -> see it arrive in clipboard history on device B -> paste it on device B exactly.

Before starting this test, make sure both devices have successfully completed [Installation](/getting-started/installation) and [Copy & Paste](/getting-started/first-steps) local verifications.

## Before You Start

*   Octoclip is installed on both devices, and each can load its local clipboard history.
*   You have decided to use **Nearby Sync** or **Cloud Sync**. If you are not sure, refer to the comparison table below:

| Network Environment | Recommended Sync Method | Preparation |
|---|---|---|
| Both devices are on the same local network (e.g., home or office Wi-Fi) | **Nearby Sync** | Enter "Nearby Devices" on both sides and pair them |
| Devices are on different networks (e.g., cellular data or separate locations) | **Cloud Sync** | Configure the same WebDAV or S3 service on both sides |
| Unsure of your network conditions | Read [Sync Overview](/features/sync-overview) first | - |

> [!WARNING] Do not mix sync paths
> Both devices must be configured to use the **same** sync method. If one device is configured for Nearby Sync and the other is configured for Cloud Sync, clipboard sync will not work.

## Steps

:::steps
:::step{title="Verify connection readiness"}

Confirm that sync switches are enabled on both devices and they are configured to use the same method (paired or connected to the same WebDAV/S3 bucket).

:::
:::step{title="Copy the test snippet on device A"}

Copy the unique test string in the block below:

```text title="Test string" noLineNumbers
octoclip-first-cross-device-001
```

:::
:::step{title="Verify receipt on device B"}

**Success sign:** Wait a few seconds, then open the clipboard history on device B (pull down to refresh on iOS). Verify that the test string `octoclip-first-cross-device-001` is recorded as the top clip card.

:::
:::step{title="Paste on device B"}

Paste the clip into any input field (like a text editor or chat window) on device B, and confirm that the pasted string matches device A exactly.
:::
:::

Once successful, you can continue exploring [Recording Expectations](/getting-started/clipboard-record-expectations) or enable [Clipboard Background Monitoring](/features/source/background-monitoring/).

## If the Test Fails, Check

:::accordion{multiple}
:::item{label="Device B does not receive the test clip"}

1.  **VPN or proxy interference (Nearby Sync):** If you are using Nearby Sync, active VPNs, network proxies, or routing rules can block local network discovery. Try **disabling your VPNs temporarily** on both devices and test again.
2.  **Enterprise Wi-Fi AP isolation:** Many corporate networks and public hotspots enable "Access Point (AP) Isolation," which prevents local devices from communicating with each other. If isolated, test using a mobile hotspot instead, or switch to Cloud Sync.
3.  **Mismatched system clocks (Cloud Sync):** Cloud storage providers (especially AWS S3 or S3-compatible backends) strictly validate request timestamps. If one device's system clock is skewed by a few minutes, sync requests will fail authentication. Enable **Set time automatically** in your system settings.
4.  **Not captured on device A:** Confirm that the copied text actually appears in the local history of device A. If not, the clip was never captured locally.

:::
:::item{label="Clip is received in history, but cannot be pasted"}

1.  Try pasting into a simple plain-text editor (such as Notepad or TextEdit).
2.  Your system might be blocking clipboard write operations. Ensure that Octoclip is allowed to write to the clipboard in system permissions.
3.  Double-click (or double-tap) the history card on device B to force a re-copy, then try pasting again.

:::
:::item{label="Sync works only in one direction"}

1.  Check the sending device to ensure its background processes aren't being aggressively suspended by the OS (especially on Android and iOS).
2.  Ensure that all system permissions (clipboard access, autostart, background execution) are fully granted on both devices.

:::
:::

## Specific Troubleshooting Pages

If your sync issue persists, click one of the cards below for targeted debugging:

:::cards{cols=2}
:::card{title="Device Discovery Failed" icon="lucide.scan-search" href="/advanced/troubleshooting/device-discovery-failed"}
Follow this guide if devices cannot see each other on the local network.

:::
:::card{title="Sync Failed Troubleshooting" icon="lucide.refresh-cw" href="/advanced/troubleshooting/sync-failed"}
Debug WebDAV/S3 configuration credentials, network blocks, or clock skew.
:::
:::

## Still Not Solved

If you still cannot get clipboard sync working, please provide the following details when asking for help in the community:

*   **OS & Versions:** (e.g., Device A: macOS 14.1, Device B: Android 13)
*   **Sync Method:** (Nearby Sync / Cloud Sync)
*   **Network Setup:** (e.g., same home Wi-Fi / corporate network / VPN enabled / mobile hotspot)
*   **Failed Direction:** (A to B fails / B to A fails / both directions fail)