Online .editorconfig file generator for teams
Generate an .editorconfig file (indentation, line endings, charset), right in your browser.
Place it at the project root. Recognized by most editors (VS Code, JetBrains…).
🔒 100% client-side — no data sent
Build a ready-to-use .editorconfig file to unify indentation, line endings and charset across your project. Pick your rules, copy the output and drop it at the root of your repository. Everything is generated 100% in your browser, with no data sent to a server.
What is it for?
- ▸ Enforce 2-space or tab indentation across the whole team
- ▸ Force LF line endings to avoid noisy Git diffs on Windows
- ▸ Standardize UTF-8 charset and trailing whitespace trimming
- ▸ Set per-file-type rules for Markdown, YAML or Makefiles
FAQ
What is an .editorconfig file used for?
It defines coding style rules (indentation, line endings, charset) that most editors apply automatically, so every developer on a project writes with the same formatting.
Where should I place the .editorconfig file?
At the root of your repository. Editors walk up the directory tree until they find a file containing root = true, which stops the search.
Does EditorConfig work without a plugin?
Some editors like VS Code, IntelliJ and Visual Studio support it natively. Others, such as Vim or Sublime Text, require a dedicated plugin to be installed.