{
  "schema": "https://storagestudio.us/schema/wiki-page.v1",
  "title": "Trying a transfer first with Dry run",
  "slug": "dry-run",
  "url": "https://storagestudio.us/wiki/dry-run",
  "markdown_url": "https://storagestudio.us/wiki/dry-run.md",
  "category": "Data Transfers",
  "category_url": "https://storagestudio.us/wiki/data-transfers/",
  "tags": [
    "data transfers",
    "dry run",
    "sync"
  ],
  "summary": "Tick Dry run (preview only) in New Transfer to rehearse a copy, move or sync. It works out what would be copied, moved or deleted and lists it in the transfer's Log, without changing a single file.",
  "published_at": "2026-10-01T06:15:22.000Z",
  "updated_at": "2026-10-01T05:33:50.000Z",
  "headings": [
    {
      "level": 2,
      "text": "Running one",
      "id": "running-one"
    },
    {
      "level": 2,
      "text": "Reading the result",
      "id": "reading-the-result"
    },
    {
      "level": 2,
      "text": "Doing it for real",
      "id": "doing-it-for-real"
    },
    {
      "level": 2,
      "text": "Things to know",
      "id": "things-to-know"
    }
  ],
  "links_out": [
    {
      "slug": "sync-again",
      "label": "Sync again and Run again",
      "exists": true,
      "url": "https://storagestudio.us/wiki/sync-again"
    },
    {
      "slug": "transfer-schedules",
      "label": "Scheduling a transfer",
      "exists": true,
      "url": "https://storagestudio.us/wiki/transfer-schedules"
    },
    {
      "slug": "two-way-sync-first-run",
      "label": "Two-way sync and the First run box",
      "exists": true,
      "url": "https://storagestudio.us/wiki/two-way-sync-first-run"
    },
    {
      "slug": "glossary-dry-run",
      "label": "dry run",
      "exists": true,
      "url": "https://storagestudio.us/wiki/glossary-dry-run"
    },
    {
      "slug": "copy-move-sync-or-two-way-sync",
      "label": "Copy, Move, Sync or Two-way sync",
      "exists": true,
      "url": "https://storagestudio.us/wiki/copy-move-sync-or-two-way-sync"
    },
    {
      "slug": "data-transfers",
      "label": "Data Transfers",
      "exists": true,
      "url": "https://storagestudio.us/wiki/data-transfers"
    },
    {
      "slug": "a-transfer-failed",
      "label": "A transfer failed",
      "exists": true,
      "url": "https://storagestudio.us/wiki/a-transfer-failed"
    }
  ],
  "links_in": [
    {
      "slug": "copy-move-sync-or-two-way-sync",
      "title": "Copy, Move, Sync or Two-way sync",
      "url": "https://storagestudio.us/wiki/copy-move-sync-or-two-way-sync"
    },
    {
      "slug": "copying-between-two-cloud-accounts",
      "title": "Copying between two cloud accounts",
      "url": "https://storagestudio.us/wiki/copying-between-two-cloud-accounts"
    },
    {
      "slug": "data-transfers",
      "title": "Data Transfers",
      "url": "https://storagestudio.us/wiki/data-transfers"
    },
    {
      "slug": "glossary-dry-run",
      "title": "Dry run",
      "url": "https://storagestudio.us/wiki/glossary-dry-run"
    },
    {
      "slug": "google-photos",
      "title": "Google Photos: what's possible and the Takeout route",
      "url": "https://storagestudio.us/wiki/google-photos"
    },
    {
      "slug": "glossary-one-way-sync",
      "title": "One-way sync",
      "url": "https://storagestudio.us/wiki/glossary-one-way-sync"
    },
    {
      "slug": "transfer-schedules",
      "title": "Scheduling a transfer",
      "url": "https://storagestudio.us/wiki/transfer-schedules"
    },
    {
      "slug": "sync-again",
      "title": "Sync again and Run again",
      "url": "https://storagestudio.us/wiki/sync-again"
    },
    {
      "slug": "two-way-sync-first-run",
      "title": "Two-way sync and the First run box",
      "url": "https://storagestudio.us/wiki/two-way-sync-first-run"
    },
    {
      "slug": "icloud-photos-of-another-apple-id",
      "title": "iCloud Photos of another Apple ID",
      "url": "https://storagestudio.us/wiki/icloud-photos-of-another-apple-id"
    }
  ],
  "diagrams": [
    {
      "kind": "flowchart",
      "caption": "Using a dry run before the real transfer",
      "outline": "- Set up the transfer\n  - leads to Tick Dry run and start it\n- Tick Dry run and start it\n  - leads to Read the Log in its details\n- Read the Log in its details\n  - leads to Does the list look right?\n- Does the list look right?\n  - Yes: leads to Click Run again or Sync again to do it for real\n  - No: leads to Fix the source or destination and try another dry run\n- Fix the source or destination and try another dry run\n  - leads to Tick Dry run and start it\n",
      "source": "%% caption: Using a dry run before the real transfer\nflowchart TD\n  A[Set up the transfer] --> B[Tick Dry run and start it]\n  B --> C[Read the Log in its details]\n  C --> D{Does the list look right?}\n  D -->|Yes| E[Click Run again or Sync again to do it for real]\n  D -->|No| F[Fix the source or destination and try another dry run]\n  F --> B"
    }
  ],
  "images": [],
  "screenshots_pending": [
    {
      "alt": "The bottom of the New Transfer sheet with the \"Dry run (preview only)\" checkbox ticked next to the Start Transfer button",
      "caption": "Turning on Dry run"
    }
  ],
  "faqs": [],
  "text": "A dry run rehearses a transfer without changing anything. Storage Studio looks at the source and the destination, works out what it would copy, move or delete, and writes that into the transfer's Log — but no file is copied, moved or removed. It's the safe way to check a Sync (one-way) before it deletes anything at the destination. Running one In Data Transfers , click New Transfer and set up the transfer as you normally would. Tick Dry run (preview only) at the bottom of the sheet, next to Start Transfer . Click Start Transfer . The dry run appears in the list like any other transfer and usually finishes much faster than the real thing, because nothing is sent. It still has to look at both sides, so a very large folder can take a little while. Reading the result Select the finished dry run and look at the Log at the bottom of its details. It lists each file the transfer would have touched, each one noted as skipped because this was a dry run. Look in particular for: Files you didn't expect to be included — check the source path is the folder you meant, not its parent. Deletions — for a Sync (one-way) or a Bidirectional sync , any file listed as deleted would really be removed on a real run. If something there should be kept, it's in the destination but not the source: copy it into the source first, or choose a different destination folder. Nothing at all — the two sides already match, or the source path is empty or wrong. The Log keeps only the most recent lines, so for a big folder it may not show every file — try a dry run on a smaller sub-folder if you need to see everything. Your Mac's files and the destination are exactly as they were before the dry run. Using a dry run before the real transfer Flowchart outline: Using a dry run before the real transfer Set up the transfer leads to Tick Dry run and start it Tick Dry run and start it leads to Read the Log in its details Read the Log in its details leads to Does the list look right? Does the list look right? Yes: leads to Click Run again or Sync again to do it for real No: leads to Fix the source or destination and try another dry run Fix the source or destination and try another dry run leads to Tick Dry run and start it Doing it for real When you're happy with the preview, select the dry run and click Run again (or Sync again for a sync). A repeat run always switches Dry run off, so it performs the transfer for real with the same source, destination and settings. See Sync again and Run again . Things to know A scheduled dry run stays a dry run. If you tick Dry run and also pick a Schedule , every scheduled run is a rehearsal too, and nothing is ever transferred. Set up the real schedule without Dry run . See Scheduling a transfer . Files can change in between. A dry run describes the folders at the moment it ran. If files change before the real run, the real run works from what's there then. Large downloads aren't split into pieces during a dry run , because nothing is downloaded. The first run of a two-way sync is the exception. A dry run with First run for this pair ticked is a sensible check, but don't use Sync again afterwards: a repeat never carries the First run for this pair box. Instead, set the transfer up again with that box ticked and Dry run off. See Two-way sync and the First run box . See dry run in the glossary. More answers are in the Storage Studio FAQ . See also: Copy, Move, Sync or Two-way sync · Data Transfers · A transfer failed",
  "markdown": "A **dry run** rehearses a transfer without changing anything. Storage Studio looks at the source and the destination, works out what it would copy, move or delete, and writes that into the transfer's **Log** — but no file is copied, moved or removed. It's the safe way to check a **Sync (one-way)** before it deletes anything at the destination.\n\n## Running one\n\n1. In **Data Transfers**, click **New Transfer** and set up the transfer as you normally would.\n2. Tick **Dry run (preview only)** at the bottom of the sheet, next to **Start Transfer**.\n3. Click **Start Transfer**.\n\nThe dry run appears in the list like any other transfer and usually finishes much faster than the real thing, because nothing is sent. It still has to look at both sides, so a very large folder can take a little while.\n\n## Reading the result\n\nSelect the finished dry run and look at the **Log** at the bottom of its details. It lists each file the transfer would have touched, each one noted as skipped because this was a dry run. Look in particular for:\n\n- **Files you didn't expect to be included** — check the source path is the folder you meant, not its parent.\n- **Deletions** — for a **Sync (one-way)** or a **Bidirectional sync**, any file listed as deleted would really be removed on a real run. If something there should be kept, it's in the destination but not the source: copy it into the source first, or choose a different destination folder.\n- **Nothing at all** — the two sides already match, or the source path is empty or wrong.\n\nThe **Log** keeps only the most recent lines, so for a big folder it may not show every file — try a dry run on a smaller sub-folder if you need to see everything. Your Mac's files and the destination are exactly as they were before the dry run.\n\n```mermaid\n%% caption: Using a dry run before the real transfer\nflowchart TD\n  A[Set up the transfer] --> B[Tick Dry run and start it]\n  B --> C[Read the Log in its details]\n  C --> D{Does the list look right?}\n  D -->|Yes| E[Click Run again or Sync again to do it for real]\n  D -->|No| F[Fix the source or destination and try another dry run]\n  F --> B\n```\n\n*Flowchart — Using a dry run before the real transfer. Outline:*\n\n- Set up the transfer\n  - leads to Tick Dry run and start it\n- Tick Dry run and start it\n  - leads to Read the Log in its details\n- Read the Log in its details\n  - leads to Does the list look right?\n- Does the list look right?\n  - Yes: leads to Click Run again or Sync again to do it for real\n  - No: leads to Fix the source or destination and try another dry run\n- Fix the source or destination and try another dry run\n  - leads to Tick Dry run and start it\n\n## Doing it for real\n\nWhen you're happy with the preview, select the dry run and click **Run again** (or **Sync again** for a sync). A repeat run always switches **Dry run** off, so it performs the transfer for real with the same source, destination and settings. See [Sync again and Run again](https://storagestudio.us/wiki/sync-again).\n\n## Things to know\n\n- **A scheduled dry run stays a dry run.** If you tick **Dry run** and also pick a **Schedule**, every scheduled run is a rehearsal too, and nothing is ever transferred. Set up the real schedule without **Dry run**. See [Scheduling a transfer](https://storagestudio.us/wiki/transfer-schedules).\n- **Files can change in between.** A dry run describes the folders at the moment it ran. If files change before the real run, the real run works from what's there then.\n- **Large downloads aren't split into pieces during a dry run**, because nothing is downloaded.\n- **The first run of a two-way sync is the exception.** A dry run with **First run for this pair** ticked is a sensible check, but don't use **Sync again** afterwards: a repeat never carries the **First run for this pair** box. Instead, set the transfer up again with that box ticked and **Dry run** off. See [Two-way sync and the First run box](https://storagestudio.us/wiki/two-way-sync-first-run).\n\nSee [dry run](https://storagestudio.us/wiki/glossary-dry-run) in the glossary.\n\nMore answers: https://storagestudio.us/faq\n\nSee also: [Copy, Move, Sync or Two-way sync](https://storagestudio.us/wiki/copy-move-sync-or-two-way-sync) · [Data Transfers](https://storagestudio.us/wiki/data-transfers) · [A transfer failed](https://storagestudio.us/wiki/a-transfer-failed)\n"
}