1---
  2title: Language Server and Tree-sitter Config - Zed
  3description: Configure language support in Zed with Tree-sitter for syntax highlighting and LSP for diagnostics, completion, and formatting.
  4---
  5
  6# Configuring Supported Languages
  7
  8Zed's language support is built on two technologies:
  9
 101. **Tree-sitter** handles syntax highlighting and structure-based features like the outline panel.
 112. **Language Server Protocol (LSP)** provides semantic features: code completion, diagnostics, go-to-definition, and refactoring.
 12
 13This page covers language-specific settings, file associations, language server configuration, formatting, linting, and syntax highlighting.
 14
 15For a list of supported languages, see [Supported Languages](./languages.md). To add support for new languages, see [Language Extensions](./extensions/languages.md).
 16
 17## Language-specific Settings
 18
 19Zed allows you to override global settings for individual languages. These custom configurations are defined in your `settings.json` file under the `languages` key.
 20
 21Here's an example of language-specific settings:
 22
 23```json [settings]
 24"languages": {
 25  "Python": {
 26    "tab_size": 4,
 27    "formatter": "language_server",
 28    "format_on_save": "on"
 29  },
 30  "JavaScript": {
 31    "tab_size": 2,
 32    "formatter": {
 33      "external": {
 34        "command": "prettier",
 35        "arguments": ["--stdin-filepath", "{buffer_path}"]
 36      }
 37    }
 38  }
 39}
 40```
 41
 42You can customize a wide range of settings for each language, including:
 43
 44- [`tab_size`](./reference/all-settings.md#tab-size): The number of spaces for each indentation level
 45- [`formatter`](./reference/all-settings.md#formatter): The tool used for code formatting
 46- [`format_on_save`](./reference/all-settings.md#format-on-save): Whether to automatically format code when saving
 47- [`enable_language_server`](./reference/all-settings.md#enable-language-server): Toggle language server support
 48- [`hard_tabs`](./reference/all-settings.md#hard-tabs): Use tabs instead of spaces for indentation
 49- [`preferred_line_length`](./reference/all-settings.md#preferred-line-length): The recommended maximum line length
 50- [`soft_wrap`](./reference/all-settings.md#soft-wrap): How to wrap long lines of code
 51- [`show_completions_on_input`](./reference/all-settings.md#show-completions-on-input): Whether or not to show completions as you type
 52- [`show_completion_documentation`](./reference/all-settings.md#show-completion-documentation): Whether to display inline and alongside documentation for items in the completions menu
 53- [`colorize_brackets`](./reference/all-settings.md#colorize-brackets): Whether to use tree-sitter bracket queries to detect and colorize the brackets in the editor (also known as "rainbow brackets")
 54
 55These settings allow you to maintain specific coding styles across different languages and projects.
 56
 57## File Associations
 58
 59Zed automatically detects file types based on their extensions, but you can customize these associations to fit your workflow.
 60
 61To set up custom file associations, use the [`file_types`](./reference/all-settings.md#file-types) setting in your `settings.json`:
 62
 63```json [settings]
 64"file_types": {
 65  "C++": ["c"],
 66  "TOML": ["MyLockFile"],
 67  "Dockerfile": ["Dockerfile*"]
 68}
 69```
 70
 71This configuration tells Zed to:
 72
 73- Treat `.c` files as C++ instead of C
 74- Recognize files named "MyLockFile" as TOML
 75- Apply Dockerfile syntax to any file starting with "Dockerfile"
 76
 77You can use glob patterns for more flexible matching, allowing you to handle complex naming conventions in your projects.
 78
 79## Working with Language Servers
 80
 81Language servers are a crucial part of Zed's intelligent coding features, providing capabilities like auto-completion, go-to-definition, and real-time error checking.
 82
 83### What are Language Servers?
 84
 85Language servers implement the Language Server Protocol (LSP), which standardizes communication between the editor and language-specific tools. This allows Zed to support advanced features for multiple programming languages without implementing each feature separately.
 86
 87Some key features provided by language servers include:
 88
 89- Code completion
 90- Error checking and diagnostics
 91- Code navigation (go to definition, find references)
 92- Code actions (Rename, extract method)
 93- Hover information
 94- Workspace symbol search
 95
 96### Managing Language Servers
 97
 98Zed simplifies language server management for users:
 99
1001. Automatic Download: When you open a file with a matching file type, Zed automatically downloads the appropriate language server. Zed may prompt you to install an extension for known file types.
101
1022. Storage Location:
103
104   - macOS: `~/Library/Application Support/Zed/languages`
105   - Linux: `$XDG_DATA_HOME/zed/languages`, `$FLATPAK_XDG_DATA_HOME/zed/languages`, or `$HOME/.local/share/zed/languages`
106
1073. Automatic Updates: Zed keeps your language servers up-to-date, ensuring you always have the latest features and improvements.
108
109### Choosing Language Servers
110
111Some languages in Zed offer multiple language server options. You might have multiple extensions installed that bundle language servers targeting the same language, potentially leading to overlapping capabilities. To ensure you get the functionality you prefer, Zed allows you to prioritize which language servers are used and in what order.
112
113You can specify your preference using the `language_servers` setting:
114
115```json [settings]
116  "languages": {
117    "PHP": {
118      "language_servers": ["intelephense", "!phpactor", "!phptools", "..."]
119    }
120  }
121```
122
123In this example:
124
125- `intelephense` is set as the primary language server.
126- `phpactor` and `phptools` are disabled (note the `!` prefix).
127- `"..."` expands to the rest of the language servers registered for PHP that are not already listed.
128
129The `"..."` entry acts as a wildcard that includes any registered language server you haven't explicitly mentioned. Servers you list by name keep their position, and `"..."` fills in the remaining ones at that point in the list. Servers prefixed with `!` are excluded entirely. This means that if a new language server extension is installed or a new server is registered for a language, `"..."` will automatically include it. If you want full control over which servers are enabled, omit `"..."` — only the servers you list by name will be used.
130
131#### Examples
132
133Suppose you're working with Ruby. The default configuration is:
134
135```json [settings]
136{
137  "language_servers": [
138    "solargraph",
139    "!ruby-lsp",
140    "!rubocop",
141    "!sorbet",
142    "!steep",
143    "!kanayago",
144    "..."
145  ]
146}
147```
148
149When you override `language_servers` in your settings, your list **replaces** the default entirely. This means default-disabled servers like `kanayago` will be re-enabled by `"..."` unless you explicitly disable them again.
150
151| Configuration                                     | Result                                                             |
152| ------------------------------------------------- | ------------------------------------------------------------------ |
153| `["..."]`                                         | `solargraph`, `ruby-lsp`, `rubocop`, `sorbet`, `steep`, `kanayago` |
154| `["ruby-lsp", "..."]`                             | `ruby-lsp`, `solargraph`, `rubocop`, `sorbet`, `steep`, `kanayago` |
155| `["ruby-lsp", "!solargraph", "!kanayago", "..."]` | `ruby-lsp`, `rubocop`, `sorbet`, `steep`                           |
156| `["ruby-lsp", "solargraph"]`                      | `ruby-lsp`, `solargraph`                                           |
157
158> Note: In the first example, `"..."` includes `kanayago` even though it is disabled by default. The override replaced the default list, so the `"!kanayago"` entry is no longer present. To keep it disabled, you must include `"!kanayago"` in your configuration.
159
160### Toolchains
161
162Some language servers need to be configured with a current "toolchain", which is an installation of a specific version of a programming language compiler or/and interpreter, which can possibly include a full set of dependencies of a project.
163An example of what Zed considers a toolchain is a virtual environment in Python.
164Not all languages in Zed support toolchain discovery and selection, but for those that do, you can specify the toolchain from a toolchain picker (via {#action toolchain::Select}). To learn more about toolchains in Zed, see [`toolchains`](./toolchains.md).
165
166### Configuring Language Servers
167
168> **Changed in Preview (v0.225).** See [release notes](/releases#0.225).
169
170When configuring language servers in your `settings.json`, autocomplete suggestions include all available LSP adapters recognized by Zed, not only those currently active for loaded languages. This helps you discover and configure language servers before opening files that use them.
171
172Many language servers accept custom configuration options. You can set these in the `lsp` section of your `settings.json`:
173
174```json [settings]
175  "lsp": {
176    "rust-analyzer": {
177      "initialization_options": {
178        "check": {
179          "command": "clippy"
180        }
181      }
182    }
183  }
184```
185
186This example configures the Rust Analyzer to use Clippy for additional linting when saving files.
187
188#### Nested objects
189
190When configuring language server options in Zed, it's important to use nested objects rather than dot-delimited strings. This is particularly relevant when working with more complex configurations. Let's look at a real-world example using the TypeScript language server:
191
192Suppose you want to configure the following settings for TypeScript:
193
194- Enable strict null checks
195- Set the target ECMAScript version to ES2020
196
197Here's how you would structure these settings in Zed's `settings.json`:
198
199```json [settings]
200"lsp": {
201  "typescript-language-server": {
202    "initialization_options": {
203      // These are not supported (VSCode dotted style):
204      // "preferences.strictNullChecks": true,
205      // "preferences.target": "ES2020"
206      //
207      // These is correct (nested notation):
208      "preferences": {
209        "strictNullChecks": true,
210        "target": "ES2020"
211      },
212    }
213  }
214}
215```
216
217#### Possible configuration options
218
219Depending on how a particular language server is implemented, they may depend on different configuration options, both specified in the LSP.
220
221- [initializationOptions](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#version_3_17_0)
222
223Sent once during language server startup, requires server's restart to reapply changes.
224
225For example, rust-analyzer and clangd rely on this way of configuring only.
226
227```json [settings]
228  "lsp": {
229    "rust-analyzer": {
230      "initialization_options": {
231        "checkOnSave": false
232      }
233    }
234  }
235```
236
237- [Configuration Request](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_configuration)
238
239May be queried by the server multiple times.
240Most of the servers would rely on this way of configuring only.
241
242```json [settings]
243"lsp": {
244  "tailwindcss-language-server": {
245    "settings": {
246      "tailwindCSS": {
247        "emmetCompletions": true,
248      },
249    }
250  }
251}
252```
253
254Apart of the LSP-related server configuration options, certain servers in Zed allow configuring the way binary is launched by Zed.
255
256Language servers are automatically downloaded or launched if found in your path, if you wish to specify an explicit alternate binary you can specify that in settings:
257
258```json [settings]
259  "lsp": {
260    "rust-analyzer": {
261      "binary": {
262        // Whether to fetch the binary from the internet, or attempt to find locally.
263        "ignore_system_version": false,
264        "path": "/path/to/langserver/bin",
265        "arguments": ["--option", "value"],
266        "env": {
267          "FOO": "BAR"
268        }
269      }
270    }
271  }
272```
273
274### Enabling or Disabling Language Servers
275
276You can toggle language server support globally or per-language:
277
278```json [settings]
279  "languages": {
280    "Markdown": {
281      "enable_language_server": false
282    }
283  }
284```
285
286This disables the language server for Markdown files, which can be useful for performance in large documentation projects. You can configure this globally in your `~/.config/zed/settings.json` or inside a `.zed/settings.json` in your project directory.
287
288## Formatting and Linting
289
290Zed provides support for code formatting and linting to maintain consistent code style and catch potential issues early.
291
292### Configuring Formatters
293
294Zed supports both built-in and external formatters. See [`formatter`](./reference/all-settings.md#formatter) docs for more. You can configure formatters globally or per-language in your `settings.json`:
295
296```json [settings]
297"languages": {
298  "JavaScript": {
299    "formatter": {
300      "external": {
301        "command": "prettier",
302        "arguments": ["--stdin-filepath", "{buffer_path}"]
303      }
304    },
305    "format_on_save": "on"
306  },
307  "Rust": {
308    "formatter": "language_server",
309    "format_on_save": "on"
310  }
311}
312```
313
314This example uses Prettier for JavaScript and the language server's formatter for Rust, both set to format on save.
315
316To disable formatting for a specific language:
317
318```json [settings]
319"languages": {
320  "Markdown": {
321    "format_on_save": "off"
322  }
323}
324```
325
326### Setting Up Linters
327
328Linting in Zed is typically handled by language servers. Many language servers allow you to configure linting rules:
329
330```json [settings]
331"lsp": {
332  "eslint": {
333    "settings": {
334      "codeActionOnSave": {
335        "rules": ["import/order"]
336      }
337    }
338  }
339}
340```
341
342This configuration sets up ESLint to organize imports on save for JavaScript files.
343
344To run linter fixes automatically on save:
345
346```json [settings]
347"languages": {
348  "JavaScript": {
349    "formatter": {
350      "code_action": "source.fixAll.eslint"
351    }
352  }
353}
354```
355
356### Integrating Formatting and Linting
357
358Zed allows you to run both formatting and linting on save. Here's an example that uses Prettier for formatting and ESLint for linting JavaScript files:
359
360```json [settings]
361"languages": {
362  "JavaScript": {
363    "formatter": [
364      {
365        "code_action": "source.fixAll.eslint"
366      },
367      {
368        "external": {
369          "command": "prettier",
370          "arguments": ["--stdin-filepath", "{buffer_path}"]
371        }
372      }
373    ],
374    "format_on_save": "on"
375  }
376}
377```
378
379### Troubleshooting
380
381If you encounter issues with formatting or linting:
382
3831. Check Zed's log file for error messages (Use the command palette: `zed: open log`)
3842. Ensure external tools (formatters, linters) are correctly installed and in your PATH
3853. Verify configurations in both Zed settings and language-specific config files (e.g., `.eslintrc`, `.prettierrc`)
386
387## Syntax Highlighting and Themes
388
389Zed offers customization options for syntax highlighting and themes, allowing you to tailor the visual appearance of your code.
390
391### Customizing Syntax Highlighting
392
393Zed uses Tree-sitter grammars for syntax highlighting. Override the default highlighting using the `theme_overrides` setting.
394
395This example makes comments italic and changes the color of strings:
396
397```json [settings]
398"theme_overrides": {
399  "One Dark": {
400    "syntax": {
401      "comment": {
402        "font_style": "italic"
403      },
404      "string": {
405        "color": "#00AA00"
406      }
407    }
408  }
409}
410```
411
412### Selecting and Customizing Themes
413
414Change your theme:
415
4161. Use the theme selector ({#kb theme_selector::Toggle})
4172. Or set it in your `settings.json`:
418
419```json [settings]
420"theme": {
421  "mode": "dark",
422  "dark": "One Dark",
423  "light": "GitHub Light"
424}
425```
426
427Create custom themes by creating a JSON file in `~/.config/zed/themes/`. Zed will automatically detect and make available any themes in this directory.
428
429### Using Theme Extensions
430
431Zed supports theme extensions. Browse and install theme extensions from the Extensions panel ({#kb zed::Extensions}).
432
433To create your own theme extension, refer to the [Developing Theme Extensions](./extensions/themes.md) guide.
434
435## Using Language Server Features
436
437### Semantic Tokens
438
439Semantic tokens provide richer syntax highlighting by using type and scope information from language servers. Enable them with the `semantic_tokens` setting:
440
441```json [settings]
442"semantic_tokens": "combined"
443```
444
445- `"off"` — Tree-sitter highlighting only (default)
446- `"combined"` — LSP semantic tokens overlaid on tree-sitter
447- `"full"` — LSP semantic tokens replace tree-sitter entirely
448
449You can customize token colors and styles through `global_lsp_settings.semantic_token_rules` in your settings.
450
451→ [Semantic Tokens documentation](./semantic-tokens.md)
452
453### Inlay Hints
454
455Inlay hints provide additional information inline in your code, such as parameter names or inferred types. Configure inlay hints in your `settings.json`:
456
457```json [settings]
458"inlay_hints": {
459  "enabled": true,
460  "show_type_hints": true,
461  "show_parameter_hints": true,
462  "show_other_hints": true
463}
464```
465
466For language-specific inlay hint settings, refer to the documentation for each language.
467
468### Code Actions
469
470Code actions provide quick fixes and refactoring options. Access code actions using the `editor: Toggle Code Actions` command or by clicking the lightbulb icon that appears next to your cursor when actions are available.
471
472### Go To Definition and References
473
474Use these commands to navigate your codebase:
475
476- `editor: Go to Definition` (<kbd>f12|f12</kbd>)
477- `editor: Go to Type Definition` (<kbd>cmd-f12|ctrl-f12</kbd>)
478- `editor: Find All References` (<kbd>shift-f12|shift-f12</kbd>)
479
480### Rename Symbol
481
482To rename a symbol across your project:
483
4841. Place your cursor on the symbol
4852. Use the `editor: Rename Symbol` command (<kbd>f2|f2</kbd>)
4863. Enter the new name and press Enter
487
488These features depend on the capabilities of the language server for each language.
489
490When renaming a symbol that spans multiple files, Zed will open a preview in a multibuffer. This allows you to review all the changes across your project before applying them. To confirm the rename, simply save the multibuffer. If you decide not to proceed with the rename, you can undo the changes or close the multibuffer without saving.
491
492### Hover Information
493
494Use the `editor: Hover` command to display information about the symbol under the cursor. This often includes type information, documentation, and links to relevant resources.
495
496### Workspace Symbol Search
497
498The {#action project_symbols::Toggle} command allows you to search for symbols (functions, classes, variables) across your entire project. This is useful for quickly navigating large codebases.
499
500### Code Completion
501
502Zed provides intelligent code completion suggestions as you type. You can manually trigger completion with the `editor: Show Completions` command. Use <kbd>tab|tab</kbd> or <kbd>enter|enter</kbd> to accept suggestions.
503
504### Diagnostics
505
506Language servers provide real-time diagnostics (errors, warnings, hints) as you code. View all diagnostics for your project using the {#action diagnostics::Deploy} command.