Claude Cowork on Windows | Requirements, Setup, and Differences from macOS

Does Claude Cowork Work on Windows? — The Verdict and Official Scope

Anthropic's Cowork Getting Started guide explicitly lists "the latest version of the Claude desktop app for macOS and Windows" as supported platforms (source: Get started with Claude Cowork). Claude for Windows is available from the official download page and supports both x64 and ARM64 architectures (source: Download Claude for Windows).

The Claude mobile app for iPad and iPhone, and the claude.ai web interface in a standard browser, do not show the Cowork tab at all. Cowork is an outcome-focused agent designed to work across files, folders, and applications, which requires OS-level file access — making it a desktop-app-exclusive feature by design. If you own a Windows laptop or a Windows 11 desktop, you can use it as a Cowork host machine right away.

System Requirements — Windows 10 1809 or Later, x64 / ARM64

Claude for Windows is distributed on the official download page as installers for both x64 and ARM64, and requires Windows 10 version 1809 or later, or Windows 11 (source: Download Claude for Windows). Note that figures such as a 4 GB RAM minimum or 8 GB or more for long-running tasks are editorial recommendations for stable operation, not officially stated requirements — Anthropic's official documentation does not specify a minimum RAM figure. Actual memory needs depend on how many apps are running concurrently and the size of files being processed, so a configuration with comfortable headroom is advisable. ARM64 machines (Surface Pro X, Copilot+ PCs, etc.) run the app natively, so there is no x64 emulation overhead.

For networking, a continuous internet connection is required throughout a session. Cowork sends tasks to Claude models running in the cloud while the Windows desktop app handles local file and folder operations, so offline use is not possible. In a corporate proxy environment, HTTPS access to https://api.anthropic.com and https://claude.ai must be allowed.

Installation — Download from claude.ai/download and Sign In with a Paid Plan

Setting up Claude Cowork on Windows takes four steps.

1. Open https://claude.ai/download in a browser and download the Windows x64 or ARM64 installer.
2. Run the downloaded Claude-Setup.exe (or the ARM64 variant) and follow the on-screen instructions to complete installation.
3. Launch Claude for Windows and sign in with an account on a paid plan — Pro, Max, Team, or Enterprise. Signing in with a Free plan will mean the Cowork tab does not appear in the left sidebar.
4. After signing in, open "Cowork" in the sidebar and follow the initial guide to connect the folders you want to grant read and write access to.

If an older version of Claude for Windows is already installed, update it via the in-app update notification or the "Check for updates" menu option. Cowork explicitly requires "the latest version of Claude for Windows", and users have reported the Cowork tab not appearing on older versions (source: Get started with Claude Cowork).

Paid Plan Requirement — The Cowork Tab Does Not Appear on Free Plans

Anthropic restricts Cowork to paid subscriptions: Pro, Max, Team, or Enterprise. Signing into Claude for Windows on a Free plan shows only the standard chat interface in the sidebar — the Cowork tab does not appear. Pro is the fixed-price individual plan, Max is a higher tier with a relaxed usage limit, and Team and Enterprise are business plans with organizational management features. The Cowork feature itself is available at every paid tier.

For organizational deployments, the key point is that governance features such as role-based access control, spending limits, and connector approval are Team/Enterprise-only (source: Get started with Claude Cowork). For individual use, Pro is the natural starting point; for shared Cowork usage across multiple people, Team or higher is the baseline. Pricing changes over time, so always check the official pricing page for current USD rates before adopting.

Folder Connection Setup — Permissions and OneDrive Sync Considerations

Claude Cowork uses a permission model where only explicitly connected folders can be read from or written to. On a freshly installed Windows system nothing is connected, so you must open the Cowork tab and manually add target folders.

1. Open the folder management menu in the Cowork tab.
2. Click "Add folder" and specify a path such as C:\Users\<name>\Documents\Projects\.
3. If a Windows permission dialog appears in Explorer, click Allow, then enable "Read" and "Write" access on the Cowork side.
4. Add additional folders — such as Downloads or specific project folders — as needed.

One important caveat: be careful of path mismatches when connecting folders under OneDrive sync. Paths like C:\Users\<name>\OneDrive\Documents\... that are synced to OneDrive may differ between what Explorer displays and the actual underlying path, which can cause absolute paths pasted into MCP's claude_desktop_config.json to fail to resolve correctly. Starting your initial tests with a local folder outside OneDrive makes troubleshooting much easier (see Claude Windows Path Issues for details).

MCP Connector Configuration — JSON-Based Connections Work on Windows Too

The MCP (Model Context Protocol) connector is available on Windows just as on Mac. The workflow of editing claude_desktop_config.json to connect external servers or custom scripts is the same; the only Windows-specific consideration is escaping path separators.

The configuration file is located at the path below. Paste it into the Explorer address bar and %APPDATA% will expand automatically, opening the folder directly.

%APPDATA%\Claude\claude_desktop_config.json

A minimal mcpServers entry looks like the following. Copy it as-is and replace only the command path with your own environment's path.

{
  "mcpServers": {
    "my-server": {
      "command": "C:\\Users\\<name>\\.local\\bin\\my-mcp-server.exe",
      "args": []
    }
  }
}

Windows paths inside JSON must consistently use one of the following two forms. A raw single backslash will cause a JSON parse error and Claude for Windows will fail to load the connector.

// Bad: single backslash (causes JSON parse error)
"command": "C:\Users\<name>\.local\bin\my-mcp-server.exe"

// OK (option 1): double backslash
"command": "C:\\Users\\<name>\\.local\\bin\\my-mcp-server.exe"

// OK (option 2): forward slashes
"command": "C:/Users/<name>/.local/bin/my-mcp-server.exe"

Restart Claude for Windows after editing for the changes to take effect. On Team and Enterprise plans, administrators can distribute pre-approved connectors to users, making it practical to roll out the same MCP configuration to everyone in an organization. SaaS connectors such as Zoom and Slack are also available on Windows, with nearly no feature gap compared to macOS.

In-Session Constraints — Keep the App Open and Prevent Sleep

Cowork requires Claude for Windows to remain open throughout task execution. Closing the app or allowing the PC to sleep will interrupt the session and cause long-running tasks to stop mid-way (source: Get started with Claude Cowork).

For stable long-duration Cowork sessions on Windows 11, configure these three settings:

1. Go to Settings → System → Power & battery and set "Sleep after" to "Never" when plugged in.
2. "Turn off the screen after" can be set to a short interval — the app continues running even with the screen off.
3. On a laptop, set "When I close the lid" to "Do nothing" so Cowork keeps running with the lid closed.

Background processing continues while the screen is locked, but switching to a different user account after locking can disconnect the session. For best results, the Cowork host machine should be dedicated to a single account for Cowork use.

Behavioral Differences from macOS — Core Features Are Identical; Only OS Integrations Differ

Claude Cowork shares the same core features on macOS and Windows — file organization, document creation, research integration, and data extraction. Anthropic develops and supports both platforms in parallel; Windows is not a lagging secondary release.

Differences only arise in OS-specific integrations. The macOS version has strong affinity with Spotlight search, Apple Notes, Shortcuts, and AppleScript, making it easy to write Cowork tasks that call apps within the Mac ecosystem. The Windows version, by contrast, pairs well with PowerShell, WinGet, Explorer, and Office applications. For example, a task like "summarize all Excel files in a specified folder into a single text document" works smoothly on Windows when combined with Office.

The Dispatch feature for iPad integration is macOS-only; remote control of a Windows host machine from an iPad is not officially available at this time (source: Using Claude on iPad with Cowork). Windows users should plan around a workflow of "using Cowork while seated at the PC."

Common Pitfalls and Fixes — Missing Cowork Tab, Dropped Connections

Here are three frequent issues when starting Cowork on Windows and how to resolve them.

1. The Cowork tab does not appear: You are likely signed in with a Free plan, or Claude for Windows is out of date. Update the app to the latest version and sign in again with a Pro-or-higher account.
2. A connected folder suddenly disconnects: The actual path may have changed due to OneDrive sync, or the folder was renamed. Remove the connection in the Cowork tab's folder management and re-add it.
3. An MCP connector does not respond: The path in claude_desktop_config.json is likely not properly escaped. Replace backslashes with \\ or / and restart Claude for Windows.

If the problem persists, suspect an issue with Claude for Windows itself rather than Cowork specifically, and try a diagnostic procedure equivalent to claude doctor or a full reinstallation. Detailed diagnostic steps are covered in How to Use Claude Code on Windows.

Summary — Windows Is a Fully Capable Cowork Host

Claude Cowork is officially supported on Windows alongside macOS, and with a Pro-or-higher paid plan and the latest version of Claude for Windows, setup takes just a few minutes. Master the three Windows-specific points — folder connection permissions, power settings for session continuity, and path escaping in MCP connectors — and you have an outcome-focused agent that can handle long-running tasks on par with the macOS version. If iPad integration via Dispatch is a requirement, the Mac version is necessary; but for desktop-only workflows, a Windows machine makes an entirely capable Cowork host.