.editorconfig Generator

Developer

Generate an .editorconfig file to maintain consistent coding styles across different editors and IDEs. Supported by VS Code, JetBrains, Sublime Text, and many more.

Quick Presets

Global Defaults

File Type Overrides

*.{ts,js,tsx,jsx}
*.{css,scss,less}
*.{html,vue,svelte}
*.{json,yaml,yml}
*.py
*.go
*.{java,kt}
*.md
Makefile

.editorconfig

# https://editorconfig.org root = true [*] indent_style = space indent_size = 2 end_of_line = lf charset = utf-8 trim_trailing_whitespace = true insert_final_newline = true [*.{ts,js,tsx,jsx}] [*.{css,scss,less}] [*.{html,vue,svelte}] [*.{json,yaml,yml}] [*.md] trim_trailing_whitespace = false

About EditorConfig

EditorConfig helps maintain consistent coding styles across different editors and IDEs by defining formatting rules in a simple .editorconfig file at the root of your project.

  • Universal Support - Works with VS Code, JetBrains, Vim, Sublime Text, and 30+ editors
  • Per-file Rules - Different indentation for different file types
  • Team Consistency - Eliminates tabs-vs-spaces debates
  • No Dependencies - No plugins or packages required in most editors

What is This Tool?

An .editorconfig generator creates EditorConfig files that define consistent coding styles across editors and IDEs. Configure indentation style (tabs/spaces), indent size, end-of-line characters, charset, and trim trailing whitespace — enforced automatically by most modern editors.

EditorConfig is supported natively by VS Code, IntelliJ, Visual Studio, Vim, Emacs, and 30+ other editors. It provides a portable, version-controlled way to enforce basic formatting rules without requiring editor-specific setup or a separate formatting tool.

Common Use Cases

Team Consistency

Ensure all team members use the same indentation and line ending settings regardless of their editor or OS.

Multi-Language Projects

Set different formatting rules per file type — 2-space indentation for YAML, 4-space for Python, tabs for Go.

Open Source Projects

Include .editorconfig in repos to help contributors match your formatting without reading style guides.

CI Validation

Use .editorconfig as the source of truth for CI formatting checks with tools like editorconfig-checker.

Frequently Asked Questions

Do I still need Prettier/ESLint?

Yes. EditorConfig handles basic whitespace formatting only. Prettier/ESLint handle code-level formatting (semicolons, quotes, line wrapping).

Which editors support EditorConfig?

VS Code, IntelliJ/WebStorm, Visual Studio, Vim, Emacs, Sublime Text, Atom, and many more — natively or via plugin.

Does it override editor settings?

Yes. EditorConfig settings override editor defaults for files within the project. The root=true directive stops search at the project root.