⟋⟋ Download

Choose the right platform and prepare a controlled local deployment

OpenClaw runs locally so execution, configuration, and working data remain closer to your own environment. The buttons below are template placeholders and should be replaced with signed production release links before launch.

🪟
Windows
Windows 10/11 · x64 & ARM
Get Windows build
🍎
macOS
macOS 14+ · Universal Binary
Get macOS build
🐧
Linux
Ubuntu / Debian / Fedora
Get Linux build
📱
Mobile
Android & iOS
Get mobile app
Typical setup path
A common rollout starts with installation, onboarding, platform connection, and operating policy review. Once those elements are in place, task delegation and execution can move into day-to-day workflows with fewer interruptions.
openclaw onboard
openclaw connect --platform wechat
Recommended operating defaults
Enable confirmations for sensitive actions, restrict readable and writable directories, assign model budgets by task type, and define fallback behavior so runtime interruptions do not break critical workflows.
View FAQs
⟋⟋ macOS

macOS installation and storage guidance

This section highlights common installation and data locations to support deployment review, storage verification, and troubleshooting in macOS environments.

Supported versions
  • macOS 12 or later is recommended for stronger compatibility and security.
  • Apple Silicon and Intel systems are supported, subject to the release package provided.
  • If Gatekeeper prompts on first run, review the source in System Settings and continue only after confirming the package is from an authorized release channel.
Install and data paths
After the application is moved into Applications, the common program location is:
/Applications/OpenClaw.app
Configuration, cache, and log data are commonly stored under:
~/Library/Application Support/OpenClaw
⟋⟋ Windows

Windows installation and storage guidance

This section outlines common installation paths, storage locations, and operating checks for Windows environments.

Supported versions
  • Windows 10 and Windows 11 are recommended, with current security updates applied.
  • The installation package should match the device architecture, typically x64 or ARM64.
  • If Microsoft Defender SmartScreen appears on first launch, verify the publisher and release source before proceeding.
Install and data paths
System-wide installations commonly use the following location:
%ProgramFiles%\OpenClaw
Per-user installations commonly use the following location:
%LOCALAPPDATA%\Programs\OpenClaw
Configuration, cache, and log data are commonly stored under:
%APPDATA%\OpenClaw
%LOCALAPPDATA%\OpenClaw
⟋⟋ Linux

Linux installation and storage guidance

This section summarizes common package formats, executable expectations, and directory conventions for Linux deployment and troubleshooting.

Supported packages
  • Common release formats include .deb, .rpm, AppImage, and Flatpak, subject to the actual distribution channel used.
  • For AppImage or standalone binaries, execute permissions typically need to be added manually.
  • If startup fails, review architecture compatibility, dependency availability, and file permissions, then run from a terminal to capture error output.
Install and data paths
After package-manager installation, the binary is commonly available at:
/usr/bin/openclaw
User data directories often follow the XDG Base Directory specification:
~/.config/OpenClaw
~/.local/share/OpenClaw
~/.cache/OpenClaw
~/.local/state/OpenClaw
⟋⟋ Android

Android installation and storage guidance

This section covers common installation considerations, permission expectations, and storage paths for Android environments.

Supported versions
  • Android 8.0 (API 26) or later is recommended for stronger compatibility and security.
  • Trusted release channels such as official stores or verified release pages are preferred; sideloaded APKs should be verified by source and signature.
  • App-specific internal storage provides stronger default isolation and is the better location for sensitive runtime data whenever possible.
Install and data paths
Android applications are usually installed in internal storage, while operational data is placed in app-specific directories that are typically removed on uninstall.
Internal app-specific storage paths are commonly structured as:
/data/data/<package-name>/files
/data/data/<package-name>/cache
External app-specific storage paths may appear in the following form depending on the device:
/sdcard/Android/data/<package-name>/files
/sdcard/Android/data/<package-name>/cache

Ready to deploy OpenClaw in a real operating environment?

Move from installation to controlled execution with local-first deployment, clear storage boundaries, and runtime policies suited to professional workflows.