How to Migrate from IntelliJ IDEA to Zed

This guide covers how to set up Zed if you're coming from IntelliJ IDEA, including keybindings, settings, and the differences you should expect.

Install Zed

Zed is available on macOS, Windows, and Linux.

For macOS, you can download it from zed.dev/download, or install via Homebrew:

brew install --cask zed

For Windows, download the installer from zed.dev/download, or install via winget:

winget install Zed.Zed

For most Linux users, the easiest way to install Zed is through our installation script:

curl -f https://zed.dev/install.sh | sh

After installation, you can launch Zed from your Applications folder (macOS), Start menu (Windows), or directly from the terminal using: zed . This opens the current directory in Zed.

Set Up the JetBrains Keymap

If you're coming from IntelliJ, the fastest way to feel at home is to use the JetBrains keymap. During onboarding, you can select it as your base keymap. If you missed that step, you can change it anytime:

1. Open Settings with Cmd+, (macOS) or Ctrl+, (Linux/Windows)
2. Search for Base Keymap
3. Select JetBrains

This maps familiar shortcuts like Shift Shift for Search Everywhere, Cmd+O for Go to Class, and Cmd+Shift+A for Find Action.

Set Up Editor Preferences

You can configure most settings in the Settings Editor ({#kb zed::OpenSettings}). For advanced settings, run zed: open settings file from the Command Palette to edit your settings file directly.

Settings IntelliJ users typically configure first:

Zed also supports per-project settings. Create a .zed/settings.json file in your project root to override global settings for that project, similar to how you might use .idea folders in IntelliJ.

Tip: If you're joining an existing project, check format_on_save before making your first commit. Otherwise you might accidentally reformat an entire file when you only meant to change one line.

Open or Create a Project

After setup, press Cmd+Shift+O (with JetBrains keymap) to open a folder. This becomes your workspace in Zed. Unlike IntelliJ, there's no project configuration wizard, no .iml files, and no SDK setup required.

To start a new project, create a directory using your terminal or file manager, then open it in Zed. The editor will treat that folder as the root of your project.

You can also launch Zed from the terminal inside any folder with: zed .

Once inside a project:

• Use Cmd+Shift+O or Cmd+E to jump between files quickly (like IntelliJ's "Recent Files")
• Use Cmd+Shift+A or Shift Shift to open the Command Palette (like IntelliJ's "Search Everywhere")
• Use Cmd+O to search for symbols (like IntelliJ's "Go to Class")

Open buffers appear as tabs across the top. The Project Panel shows your file tree and Git status. Toggle it with Cmd+1 (just like IntelliJ's Project tool window).

Differences in Keybindings

If you chose the JetBrains keymap during onboarding, most of your shortcuts should already feel familiar. Here's a quick reference for how Zed compares to IntelliJ.

Common Shared Keybindings (Zed with JetBrains keymap ↔ IntelliJ)

Different Keybindings (IntelliJ → Zed)

Unique to Zed

How to Customize Keybindings

• Open the Command Palette (Cmd+Shift+A or Shift Shift)
• Run Zed: Open Keymap Editor

This opens a list of all available bindings. You can override individual shortcuts or remove conflicts.

Zed also supports key sequences (multi-key shortcuts).

Differences in User Interfaces

No Indexing

If you've used IntelliJ on large projects, you know the wait: "Indexing..." can take anywhere from 30 seconds to 15 minutes depending on project size. IntelliJ builds a comprehensive index of your entire codebase to power its code intelligence, and it re-indexes when dependencies change or after builds.

Zed doesn't index. You open a folder and start working immediately. File search and navigation work instantly regardless of project size.

IntelliJ's index powers features like finding all usages across your entire codebase, understanding class hierarchies, and detecting dead code. Zed delegates this work to language servers, which may not analyze at the same depth.

How to adapt:

• For project-wide symbol search, use Cmd+O / Go to Symbol (relies on your language server)
• For finding files by name, use Cmd+Shift+O / Go to File
• For text search across files, use Cmd+Shift+F—this is fast even on large codebases
• If you need deep static analysis for JVM code, consider running IntelliJ's inspections as a separate step or using standalone tools like Checkstyle, PMD, or SpotBugs

LSP vs. Native Language Intelligence

IntelliJ has its own language analysis engine built from scratch for each supported language. For Java, Kotlin, and other JVM languages, this engine understands your code thoroughly: it resolves types, tracks data flow, knows about framework annotations, and offers dozens of specialized refactorings.

Zed uses the Language Server Protocol (LSP) for code intelligence. Each language has its own server: jdtls for Java, rust-analyzer for Rust, and so on.

For some languages, the LSP experience is excellent. TypeScript, Rust, and Go have mature language servers that provide fast, accurate completions, diagnostics, and refactorings. For JVM languages, the gap might be more noticeable. The Eclipse-based Java language server is capable, but it won't match IntelliJ's depth for things like:

• Spring and Jakarta EE annotation processing
• Complex refactorings (extract interface, pull members up, change signature with all callers)
• Framework-aware inspections
• Automatic import optimization with custom ordering rules

How to adapt:

• Use Alt+Enter for available code actions—the list will vary by language server
• For Java, ensure jdtls is properly configured with your JDK path in settings

No Project Model

IntelliJ manages projects through .idea folders containing XML configuration files, .iml module definitions, SDK assignments, and run configurations. This model enables IntelliJ to understand multi-module projects, manage dependencies automatically, and persist complex run/debug setups.

Zed has no project model. A project is a folder. There's no wizard, no SDK selection screen, no module configuration.

This means:

• Build commands are manual. Zed doesn't detect Maven or Gradle projects.
• Run configurations don't exist. You define tasks or use the terminal.
• SDK management is external. Your language server uses whatever JDK is on your PATH.
• There are no module boundaries. Zed sees folders, not project structure.

How to adapt:

• Create a .zed/settings.json in your project root for project-specific settings
• Define common commands in tasks.json (open via Command Palette: zed: open tasks):

[
  {
    "label": "build",
    "command": "./gradlew build"
  },
  {
    "label": "run",
    "command": "./gradlew bootRun"
  },
  {
    "label": "test current file",
    "command": "./gradlew test --tests $ZED_STEM"
  }
]

• Use Ctrl+Alt+R to run tasks quickly
• Lean on your terminal (Alt+F12) for anything tasks don't cover
• For multi-module projects, you can open each module as a separate Zed window, or open the root and navigate via file finder

No Framework Integration

IntelliJ's value for enterprise Java development comes largely from its framework integration. Spring beans are understood and navigable. JPA entities get special treatment. Endpoints are indexed and searchable. Jakarta EE annotations modify how the IDE analyzes your code.

Zed has none of this. The language server sees Java code as Java code, so it doesn't understand that @Autowired means something special or that this class is a REST controller.

Similarly for other stacks: no Rails integration, no Django awareness, no Angular/React-specific tooling beyond what the TypeScript language server provides.

How to adapt:

• Use grep and file search liberally. Cmd+Shift+F with a regex can find endpoint definitions, bean names, or annotation usages.
• Rely on your language server's "find references" (Alt+F7) for navigation—it works, just without framework context
• For Spring Boot, keep the Actuator endpoints or a separate tool for understanding bean wiring
• Consider using framework-specific CLI tools (Spring CLI, Rails generators) from Zed's terminal

Tip: For database work, pick up a dedicated tool like DataGrip, DBeaver, or TablePlus. Many developers who switch to Zed keep DataGrip around specifically for SQL—it integrates well with your existing JetBrains license.

If your daily work depends heavily on framework-aware navigation and refactoring, you'll feel the gap. Zed works best when you're comfortable navigating code through search rather than specialized tooling, or when your language has strong LSP support that covers most of what you need.

Tool Windows vs. Docks

IntelliJ organizes auxiliary views into numbered tool windows (Project = 1, Git = 9, Terminal = Alt+F12, etc.). Zed uses a similar concept called "docks":

Zed has three dock positions: left, bottom, and right. Panels can be moved between docks by dragging or through settings.

Tip: IntelliJ has an "Override IDE shortcuts" setting that lets terminal shortcuts like Ctrl+Left/Right work normally. In Zed, terminal keybindings are separate—check your keymap if familiar shortcuts aren't working in the terminal panel.

Debugging

Both IntelliJ and Zed offer integrated debugging, but the experience differs:

• Zed's debugger uses the Debug Adapter Protocol (DAP), supporting multiple languages
• Set breakpoints with Ctrl+F8
• Start debugging with Alt+Shift+F9
• Step through code with F7 (step into), F8 (step over), Shift+F8 (step out)
• Continue execution with F9

The Debug Panel (Cmd+5) shows variables, call stack, and breakpoints—similar to IntelliJ's Debug tool window.

Extensions vs. Plugins

IntelliJ has a large plugin catalog covering everything from language support to database tools to deployment integrations.

Zed's extension catalog is smaller and more focused:

• Language support and syntax highlighting
• Themes
• Slash commands for AI
• Context servers

Several features that require plugins in other editors are built into Zed:

• Real-time collaboration with voice chat
• AI coding assistance
• Built-in terminal
• Task runner
• LSP-based code intelligence

You won't find one-to-one replacements for every IntelliJ plugin, especially for framework-specific tools, database clients, or application server integrations. For those workflows, you may need to use external tools alongside Zed.

Collaboration in Zed vs. IntelliJ

IntelliJ offers Code With Me as a separate plugin for collaboration. Zed has collaboration built into the core experience.

• Open the Collab Panel in the left dock
• Create a channel and invite your collaborators to join
• Share your screen or your codebase directly

Once connected, you'll see each other's cursors, selections, and edits in real time. Voice chat is included. There's no need for separate tools or third-party logins.

Using AI in Zed

If you're used to AI assistants in IntelliJ (like GitHub Copilot or JetBrains AI), Zed offers similar capabilities with more flexibility.

Configuring GitHub Copilot

1. Open Settings with Cmd+, (macOS) or Ctrl+, (Linux/Windows)
2. Navigate to AI → Edit Predictions
3. Click Configure next to "Configure Providers"
4. Under GitHub Copilot, click Sign in to GitHub

Once signed in, just start typing. Zed will offer suggestions inline for you to accept.

Additional AI Options

To use other AI models in Zed, you have several options:

• Use Zed's hosted models, with higher rate limits. Requires authentication and subscription to Zed Pro.
• Bring your own API keys, no authentication needed
• Use external agents like Claude Agent

Advanced Config and Productivity Tweaks

Zed exposes advanced settings for power users who want to fine-tune their environment.

Here are a few useful tweaks:

Format on Save:

"format_on_save": "on"

Enable direnv support:

"load_direnv": "shell_hook"

Configure language servers (requires manual JSON editing): For Java development, you may want to configure the Java language server in your settings:

{
  "lsp": {
    "jdtls": {
      "settings": {
        "java_home": "/path/to/jdk"
      }
    }
  }
}

Next Steps

Now that you're set up, here are some resources to help you get the most out of Zed:

• All Settings — Customize settings, themes, and editor behavior
• Key Bindings — Learn how to customize and extend your keymap
• Tasks — Set up build and run commands for your projects
• AI Features — Explore Zed's AI capabilities beyond code completion
• Collaboration — Share your projects and code together in real time
• Languages — Language-specific setup guides, including Java and Kotlin