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