1# How to Migrate from WebStorm to Zed
2
3This guide covers how to set up Zed if you're coming from WebStorm, including keybindings, settings, and the differences you should expect as a JavaScript/TypeScript developer.
4
5## Install Zed
6
7Zed is available on macOS, Windows, and Linux.
8
9For macOS, you can download it from zed.dev/download, or install via Homebrew:
10
11```sh
12brew install --cask zed
13```
14
15For Windows, download the installer from zed.dev/download, or install via winget:
16
17```sh
18winget install Zed.Zed
19```
20
21For most Linux users, the easiest way to install Zed is through our installation script:
22
23```sh
24curl -f https://zed.dev/install.sh | sh
25```
26
27After installation, you can launch Zed from your Applications folder (macOS), Start menu (Windows), or directly from the terminal using:
28`zed .`
29This opens the current directory in Zed.
30
31## Set Up the JetBrains Keymap
32
33If you're coming from WebStorm, 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:
34
351. Open Settings with `Cmd+,` (macOS) or `Ctrl+,` (Linux/Windows)
362. Search for `Base Keymap`
373. Select `JetBrains`
38
39Or add this directly to your `settings.json`:
40
41```json
42{
43 "base_keymap": "JetBrains"
44}
45```
46
47This maps familiar shortcuts like `Shift Shift` for Search Everywhere, `Cmd+O` for Go to Class, and `Cmd+Shift+A` for Find Action.
48
49## Set Up Editor Preferences
50
51You can configure settings manually in the Settings Editor.
52
53To edit your settings:
54
551. `Cmd+,` to open the Settings Editor.
562. Run `zed: open settings` in the Command Palette.
57
58Settings WebStorm users typically configure first:
59
60| Zed Setting | What it does |
61| ----------------------- | ------------------------------------------------------------------------------- |
62| `format_on_save` | Auto-format when saving. Set to `"on"` to enable. |
63| `soft_wrap` | Wrap long lines. Options: `"none"`, `"editor_width"`, `"preferred_line_length"` |
64| `preferred_line_length` | Column width for wrapping and rulers. Default is 80. |
65| `inlay_hints` | Show parameter names and type hints inline, like WebStorm's hints. |
66| `relative_line_numbers` | Useful if you're coming from IdeaVim. |
67
68Zed 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 WebStorm.
69
70> **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.
71
72## Open or Create a Project
73
74After setup, press `Cmd+Shift+O` (with JetBrains keymap) to open a folder. This becomes your workspace in Zed. Unlike WebStorm, there's no project configuration wizard, no framework selection dialog, and no project structure setup required.
75
76To 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. For new projects, you'd typically run `npm init`, `pnpm create`, or your framework's CLI tool first, then open the resulting folder in Zed.
77
78You can also launch Zed from the terminal inside any folder with:
79`zed .`
80
81Once inside a project:
82
83- Use `Cmd+Shift+O` or `Cmd+E` to jump between files quickly (like WebStorm's "Recent Files")
84- Use `Cmd+Shift+A` or `Shift Shift` to open the Command Palette (like WebStorm's "Search Everywhere")
85- Use `Cmd+O` to search for symbols (like WebStorm's "Go to Symbol")
86
87Open buffers appear as tabs across the top. The sidebar shows your file tree and Git status. Toggle it with `Cmd+1` (just like WebStorm's Project tool window).
88
89## Differences in Keybindings
90
91If 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 WebStorm.
92
93### Common Shared Keybindings
94
95| Action | Shortcut |
96| ----------------------------- | ----------------------- |
97| Search Everywhere | `Shift Shift` |
98| Find Action / Command Palette | `Cmd + Shift + A` |
99| Go to File | `Cmd + Shift + O` |
100| Go to Symbol | `Cmd + O` |
101| Recent Files | `Cmd + E` |
102| Go to Definition | `Cmd + B` |
103| Find Usages | `Alt + F7` |
104| Rename Symbol | `Shift + F6` |
105| Reformat Code | `Cmd + Alt + L` |
106| Toggle Project Panel | `Cmd + 1` |
107| Toggle Terminal | `Alt + F12` |
108| Duplicate Line | `Cmd + D` |
109| Delete Line | `Cmd + Backspace` |
110| Move Line Up/Down | `Shift + Alt + Up/Down` |
111| Expand/Shrink Selection | `Alt + Up/Down` |
112| Comment Line | `Cmd + /` |
113| Go Back / Forward | `Cmd + [` / `Cmd + ]` |
114| Toggle Breakpoint | `Ctrl + F8` |
115
116### Different Keybindings (WebStorm → Zed)
117
118| Action | WebStorm | Zed (JetBrains keymap) |
119| ---------------------- | ----------- | ------------------------ |
120| File Structure | `Cmd + F12` | `Cmd + F12` (outline) |
121| Navigate to Next Error | `F2` | `F2` |
122| Run | `Ctrl + R` | `Ctrl + Alt + R` (tasks) |
123| Debug | `Ctrl + D` | `Alt + Shift + F9` |
124| Stop | `Cmd + F2` | `Ctrl + F2` |
125
126### Unique to Zed
127
128| Action | Shortcut | Notes |
129| ----------------- | -------------------------- | ------------------------------ |
130| Toggle Right Dock | `Cmd + R` | Assistant panel, notifications |
131| Split Panes | `Cmd + K`, then arrow keys | Create splits in any direction |
132
133### How to Customize Keybindings
134
135- Open the Command Palette (`Cmd+Shift+A` or `Shift Shift`)
136- Run `Zed: Open Keymap Editor`
137
138This opens a list of all available bindings. You can override individual shortcuts or remove conflicts.
139
140Zed also supports key sequences (multi-key shortcuts).
141
142## Differences in User Interfaces
143
144### No Indexing
145
146If you've used WebStorm on large projects, you know the wait. Opening a project with many dependencies can mean watching "Indexing..." for anywhere from 30 seconds to several minutes. WebStorm indexes your entire codebase and `node_modules` to power its code intelligence, and re-indexes when dependencies change.
147
148Zed doesn't index. You open a folder and start coding immediately—no progress bars, no "Indexing paused" banners. File search and navigation stay fast regardless of project size or how many `node_modules` dependencies you have.
149
150WebStorm's index enables features like finding all usages across your entire codebase, tracking import hierarchies, and flagging unused exports project-wide. Zed relies on language servers for this analysis, which may not cover as much ground.
151
152**How to adapt:**
153
154- Search symbols across the project with `Cmd+O` (powered by the TypeScript language server)
155- Find files by name with `Cmd+Shift+O`
156- Use `Cmd+Shift+F` for text search—it stays fast even in large monorepos
157- Run `tsc --noEmit` or `eslint .` from the terminal when you need deeper project-wide analysis
158
159### LSP vs. Native Language Intelligence
160
161WebStorm has its own JavaScript and TypeScript analysis engine built by JetBrains. This engine understands your code deeply: it resolves types, tracks data flow, knows about framework-specific patterns, and offers specialized refactorings.
162
163Zed uses the Language Server Protocol (LSP) for code intelligence. For JavaScript and TypeScript, Zed supports:
164
165- **vtsls** (default) — Fast TypeScript language server with excellent performance
166- **typescript-language-server** — The standard TypeScript LSP implementation
167- **ESLint** — Linting integration
168- **Prettier** — Code formatting (built-in)
169
170The TypeScript LSP experience is mature and robust. You get accurate completions, type checking, go-to-definition, and find-references. The experience is comparable to VS Code, which uses the same underlying TypeScript services.
171
172Where you might notice differences:
173
174- Framework-specific intelligence (Angular templates, Vue SFCs) may be less integrated
175- Some complex refactorings (extract component with proper imports) may be less sophisticated
176- Auto-import suggestions depend on what the language server knows about your project
177
178**How to adapt:**
179
180- Use `Alt+Enter` for available code actions—the list will vary by language server
181- Ensure your `tsconfig.json` is properly configured so the language server understands your project structure
182- Use Prettier for consistent formatting (it's enabled by default for JS/TS)
183- For code inspection similar to WebStorm's "Inspect Code," check the Diagnostics panel (`Cmd+6`)—ESLint and TypeScript together catch many of the same issues
184
185### No Project Model
186
187WebStorm manages projects through `.idea` folders containing XML configuration files, framework detection, and run configurations. This model lets WebStorm remember your project settings, manage npm scripts through the UI, and persist run/debug setups.
188
189Zed takes a different approach: a project is just a folder. There's no setup wizard, no framework detection dialog, no project structure to configure.
190
191What this means in practice:
192
193- Run configurations aren't a thing. Define reusable commands in `tasks.json` instead. Note that your existing `.idea/` configurations won't carry over—you'll set up the ones you need fresh.
194- npm scripts live in the terminal. Run `npm run dev`, `pnpm build`, or `yarn test` directly—there's no dedicated npm panel.
195- No framework detection. Zed treats React, Angular, Vue, and vanilla JS/TS the same way.
196
197**How to adapt:**
198
199- Create a `.zed/settings.json` in your project root for project-specific settings
200- Define common commands in `tasks.json` (open via Command Palette: `zed: open tasks`):
201
202```json
203[
204 {
205 "label": "dev",
206 "command": "npm run dev"
207 },
208 {
209 "label": "build",
210 "command": "npm run build"
211 },
212 {
213 "label": "test",
214 "command": "npm test"
215 },
216 {
217 "label": "test current file",
218 "command": "npm test -- $ZED_FILE"
219 }
220]
221```
222
223- Use `Ctrl+Alt+R` to run tasks quickly
224- Lean on your terminal (`Alt+F12`) for anything tasks don't cover
225
226### No Framework Integration
227
228WebStorm's value for web development comes largely from its framework integration. React components get special treatment. Angular has dedicated tooling. Vue single-file components are fully understood. The npm tool window shows all your scripts.
229
230Zed has none of this built-in. The TypeScript language server sees your code as TypeScript—it doesn't understand that a function is a React component or that a file is an Angular service.
231
232**How to adapt:**
233
234- Use grep and file search liberally. `Cmd+Shift+F` with a regex can find component definitions, route configurations, or API endpoints.
235- Rely on your language server's "find references" (`Alt+F7`) for navigation—it works, just without framework context
236- Consider using framework-specific CLI tools (`ng`, `next`, `vite`) from Zed's terminal
237- For React, JSX/TSX syntax and TypeScript types still provide good intelligence
238
239> **Tip:** For projects with complex configurations, keep your framework's documentation handy. Zed's speed comes with less hand-holding for framework-specific features.
240
241### Tool Windows vs. Docks
242
243WebStorm organizes auxiliary views into numbered tool windows (Project = 1, npm = Alt+F11, Terminal = Alt+F12, etc.). Zed uses a similar concept called "docks":
244
245| WebStorm Tool Window | Zed Equivalent | Shortcut (JetBrains keymap) |
246| -------------------- | -------------- | --------------------------- |
247| Project (1) | Project Panel | `Cmd + 1` |
248| Git (9 or Cmd+0) | Git Panel | `Cmd + 0` |
249| Terminal (Alt+F12) | Terminal Panel | `Alt + F12` |
250| Structure (7) | Outline Panel | `Cmd + 7` |
251| Problems (6) | Diagnostics | `Cmd + 6` |
252| Debug (5) | Debug Panel | `Cmd + 5` |
253
254Zed has three dock positions: left, bottom, and right. Panels can be moved between docks by dragging or through settings.
255
256Note that there's no dedicated npm tool window in Zed. Use the terminal or define tasks for your common npm scripts.
257
258### Debugging
259
260Both WebStorm and Zed offer integrated debugging for JavaScript and TypeScript:
261
262- Zed uses `vscode-js-debug` (the same debug adapter that VS Code uses)
263- Set breakpoints with `Ctrl+F8`
264- Start debugging with `Alt+Shift+F9` or press `F4` and select a debug target
265- Step through code with `F7` (step into), `F8` (step over), `Shift+F8` (step out)
266- Continue execution with `F9`
267
268Zed can debug:
269
270- Node.js applications and scripts
271- Chrome/browser JavaScript
272- Jest, Mocha, Vitest, and other test frameworks
273- Next.js (both server and client-side)
274
275For more control, create a `.zed/debug.json` file:
276
277```json
278[
279 {
280 "label": "Debug Current File",
281 "adapter": "JavaScript",
282 "program": "$ZED_FILE",
283 "request": "launch"
284 },
285 {
286 "label": "Debug Node Server",
287 "adapter": "JavaScript",
288 "request": "launch",
289 "program": "${workspaceFolder}/src/server.js"
290 },
291 {
292 "label": "Attach to Chrome",
293 "adapter": "JavaScript",
294 "request": "attach",
295 "port": 9222
296 }
297]
298```
299
300Zed also recognizes `.vscode/launch.json` configurations, so existing VS Code debug setups often work out of the box.
301
302### Running Tests
303
304WebStorm has a dedicated test runner with a visual interface showing pass/fail status for each test. Zed provides test running through:
305
306- **Gutter icons** — Click the play button next to test functions or describe blocks
307- **Tasks** — Define test commands in `tasks.json`
308- **Terminal** — Run `npm test`, `jest`, `vitest`, etc. directly
309
310Zed supports auto-detection for common test frameworks:
311
312- Jest
313- Mocha
314- Vitest
315- Jasmine
316- Bun test
317- Node.js test runner
318
319The test output appears in the terminal panel. For Jest, use `--verbose` for detailed output or `--watch` for continuous testing during development.
320
321### Extensions vs. Plugins
322
323WebStorm has a plugin ecosystem covering additional language support, themes, and tool integrations.
324
325Zed's extension ecosystem is smaller and more focused:
326
327- Language support and syntax highlighting
328- Themes
329- Slash commands for AI
330- Context servers
331
332Several features that require plugins in WebStorm are built into Zed:
333
334- Real-time collaboration with voice chat
335- AI coding assistance
336- Built-in terminal
337- Task runner
338- LSP-based code intelligence
339- Prettier formatting
340- ESLint integration
341
342### What's Not in Zed
343
344To set expectations clearly, here's what WebStorm offers that Zed doesn't have:
345
346- **npm tool window** — Use the terminal or tasks instead
347- **HTTP Client** — Use tools like Postman, Insomnia, or curl
348- **Database tools** — Use DataGrip, DBeaver, or TablePlus
349- **Framework-specific tooling** (Angular schematics, React refactorings) — Use CLI tools
350- **Visual package.json editor** — Edit the file directly
351- **Built-in REST client** — Use external tools or extensions
352- **Profiler integration** — Use Chrome DevTools or Node.js profiling tools
353
354## Collaboration in Zed vs. WebStorm
355
356WebStorm offers Code With Me as a separate feature for collaboration. Zed has collaboration built into the core experience.
357
358- Open the Collab Panel in the left dock
359- Create a channel and [invite your collaborators](https://zed.dev/docs/collaboration#inviting-a-collaborator) to join
360- [Share your screen or your codebase](https://zed.dev/docs/collaboration#share-a-project) directly
361
362Once 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.
363
364## Using AI in Zed
365
366If you're used to AI assistants in WebStorm (like GitHub Copilot, JetBrains AI Assistant, or Junie), Zed offers similar capabilities with more flexibility.
367
368### Configuring GitHub Copilot
369
3701. Open Settings with `Cmd+,` (macOS) or `Ctrl+,` (Linux/Windows)
3712. Navigate to **AI → Edit Predictions**
3723. Click **Configure** next to "Configure Providers"
3734. Under **GitHub Copilot**, click **Sign in to GitHub**
374
375Once signed in, just start typing. Zed will offer suggestions inline for you to accept.
376
377### Additional AI Options
378
379To use other AI models in Zed, you have several options:
380
381- Use Zed's hosted models, with higher rate limits. Requires [authentication](https://zed.dev/docs/accounts.html) and subscription to [Zed Pro](https://zed.dev/docs/ai/subscription.html).
382- Bring your own [API keys](https://zed.dev/docs/ai/llm-providers.html), no authentication needed
383- Use [external agents like Claude Code](https://zed.dev/docs/ai/external-agents.html)
384
385## Advanced Config and Productivity Tweaks
386
387Zed exposes advanced settings for power users who want to fine-tune their environment.
388
389Here are a few useful tweaks for JavaScript/TypeScript developers:
390
391**Format on Save:**
392
393```json
394"format_on_save": "on"
395```
396
397**Configure Prettier as the default formatter:**
398
399```json
400{
401 "formatter": {
402 "external": {
403 "command": "prettier",
404 "arguments": ["--stdin-filepath", "{buffer_path}"]
405 }
406 }
407}
408```
409
410**Enable ESLint code actions:**
411
412```json
413{
414 "lsp": {
415 "eslint": {
416 "settings": {
417 "codeActionOnSave": {
418 "rules": ["import/order"]
419 }
420 }
421 }
422 }
423}
424```
425
426**Configure TypeScript strict mode hints:**
427
428In your `tsconfig.json`, enable strict mode for better type checking:
429
430```json
431{
432 "compilerOptions": {
433 "strict": true,
434 "noUncheckedIndexedAccess": true
435 }
436}
437```
438
439**Enable direnv support (useful for projects using direnv for environment variables):**
440
441```json
442"load_direnv": "shell_hook"
443```
444
445## Next Steps
446
447Now that you're set up, here are some resources to help you get the most out of Zed:
448
449- [All Settings](../reference/all-settings.md) — Customize settings, themes, and editor behavior
450- [Key Bindings](../key-bindings.md) — Learn how to customize and extend your keymap
451- [Tasks](../tasks.md) — Set up build and run commands for your projects
452- [AI Features](../ai/overview.md) — Explore Zed's AI capabilities beyond code completion
453- [Collaboration](../collaboration/overview.md) — Share your projects and code together in real time
454- [JavaScript in Zed](../languages/javascript.md) — JavaScript-specific setup and configuration
455- [TypeScript in Zed](../languages/typescript.md) — TypeScript-specific setup and configuration