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