How to Install Cursor on Windows, macOS, and Linux (2026)

Reviewed August 15, 2026. Cursor is a desktop code editor with AI-assisted features. Install it only from Cursor’s official download page, select the package that matches the operating system and CPU architecture, and review privacy, indexing, extensions, updates, and account controls before opening confidential repositories.

Download from the official source

Open cursor.com/download and confirm the hostname before downloading. Do not use repackaged installers, advertisements, unofficial repositories, or copied shell commands. Record the version and installer source for managed deployments.

Install on Windows

1. Download the official installer matching the device architecture.
2. Inspect the file’s digital-signature properties and publisher before running it.
3. Choose the installation scope allowed by organizational policy.
4. Launch Cursor, sign in through the approved account path, and verify the displayed version.

For managed fleets, test silent-install and update behavior in a device-management pilot. Do not invent deployment switches; obtain the supported command and enterprise terms from Cursor for the current installer.

Install on macOS

1. Choose the Apple silicon or Intel build that matches the Mac.
2. Open the downloaded disk image and move Cursor to the Applications folder.
3. Launch it through Finder so macOS can display the publisher and security prompt.
4. Verify the application version and remove the mounted installer image.

Administrators should test code signing, update behavior, permissions, and any endpoint-security prompts before broad deployment.

Install on Linux

Use the current official package for the distribution and architecture. Ubuntu users should follow the dedicated Cursor on Ubuntu guide, which covers .deb, AppImage, FUSE fallback, updates, and rollback. Other distributions should use the official RPM or AppImage option documented on the current download page.

Do not make an AppImage globally writable or run it as root. For managed endpoints, prefer a package format with clear ownership and a tested update process.

First-run privacy and security review

• Use a business-managed account when organization data is in scope.
• Review privacy mode and current information-handling terms for the selected plan.
• Decide whether codebase indexing is allowed and which repositories or paths must be excluded.
• Maintain repository ignore rules, but do not treat them as a complete secret-prevention control.
• Allow only reviewed extensions and remove stale credentials copied from another editor profile.
• Keep source-control review, tests, and secret scanning in the normal development workflow.

Validate and update

Open a non-sensitive test repository, confirm source control and terminal behavior, run the project’s tests, and verify that indexing and AI features follow the expected settings. Document how Cursor checks for updates, who approves new versions, and how the prior version can be restored if an update breaks required work.

The Cursor CLI is optional and has its own official installation documentation. Do not assume the desktop installer adds or governs the CLI.

Business rollout

Pilot with a small developer group. Measure accepted changes, defects, review effort, unsupported suggestions, policy exceptions, and support incidents. Define approved repositories, extensions, models, and account types before expansion. ITECS can help establish the rollout through AI consulting and strategy services.

Primary sources

• Cursor official downloads
• Cursor installation documentation
• Cursor privacy documentation
• Cursor security information
• Cursor CLI installation