Loading page
About this tool
Generate a .editorconfig with indentation, charset, line-ending and whitespace rules, plus per-file-type sections.
This generator builds a valid .editorconfig file — the cross-editor configuration format defined by the EditorConfig specification — from your indentation, charset, line-ending and whitespace choices. It is aimed at teams who want identical formatting behaviour across VS Code, JetBrains IDEs, Vim and every other editor, and it adds convention-correct per-file-type sections such as hard tabs for Makefiles and preserved trailing spaces for Markdown.
Open EditorConfig Generator on AltFTool — it loads instantly in your browser.
Provide your input — an image, text, or data.
Let the tool analyze or generate the result.
Review, refine, and reuse the output wherever you need it.
Property names and values follow the EditorConfig file-format specification, so every compliant editor parses the file.
One-click sections encode real rules: POSIX make requires tabs, Markdown line breaks need trailing spaces, YAML forbids tab indentation.
Indent sizes, line lengths, globs and duplicate sections are checked, so a typo never ships to the whole team.
It stops the upward search for more .editorconfig files. Editors read every .editorconfig from the open file's directory up to the filesystem root and merge them with closer files winning; root = true in the top-most file of your repository marks the boundary so settings from directories above your project are ignored.
Because two trailing spaces at the end of a line are Markdown's hard line-break syntax, so trimming them silently changes the rendered output. The standard fix is a [*.md] section with trim_trailing_whitespace = false, which this generator adds with one click.
No — VS Code needs the official "EditorConfig for VS Code" extension to honour the file. JetBrains IDEs (IntelliJ, WebStorm, PyCharm), Vim 9.1+, Neovim and GitHub's web renderer support EditorConfig natively, which is why one file keeps a mixed-editor team consistent.
indent_size sets how many columns one indentation level occupies, while tab_width sets how wide a tab character displays and defaults to the value of indent_size. You normally set only indent_size; setting indent_size = tab makes indentation follow tab_width instead, which is useful in tab-indented codebases.