.editorconfig Generator

Build a .editorconfig for your project. Pick global defaults (indent, line endings, charset) and override per-file-type as needed. Download a file ready to commit at the repo root — every editor that supports EditorConfig (most do) will respect it automatically.

Per-file overrides

How to use the .editorconfig Generator

Pick your defaults; toggle the per-file-type overrides you want. Generate produces a complete .editorconfig. Commit it at the repo root; every editor that supports EditorConfig (VS Code, JetBrains, Vim, Emacs, Sublime, etc.) will pick it up automatically.

What .editorconfig does

Open one repository in five different editors with five different default indent settings and you get churn: one person’s tabs become another’s spaces, line endings flip between LF and CRLF, and every save adds whitespace noise to the diff. EditorConfig fixes this at the source — a single file at the repo root that every major editor reads and obeys, so indentation, line endings, and charset stay consistent no matter who is typing or in which tool.

This builds that file from global defaults plus the per-file-type overrides that matter in practice: 2-space JavaScript, tab-indented Makefiles, untrimmed Markdown. EditorConfig handles the low-level basics every editor understands; for deep code reformatting in supported languages pair it with a Prettier config from the .prettierrc generator, and keep build artifacts out of the repo with the .gitignore generator.

Common use cases

  • Team consistency — the same indent and line endings for everyone, regardless of editor.
  • Cross-OS work — pin LF endings so Windows and Unix contributors stop fighting over CRLF.
  • Polyglot repos — give YAML, Makefiles, and Markdown the indentation each one actually needs.
  • Onboarding — new contributors get correct formatting automatically, with no setup.
  • Cleaner diffs — stop whitespace-only changes from cluttering pull requests.

Frequently asked questions

Which editors support EditorConfig?
VS Code, JetBrains IDEs, Vim, Emacs, Sublime, and most others — some natively, some via a small plugin.

Does it replace Prettier or ESLint?
No. EditorConfig sets basic editor behaviour; the .prettierrc generator covers deep reformatting and ESLint catches code issues. They work together.

Where does the file go?
At your repo root as .editorconfig; the root=true line stops editors searching parent directories for more config.

How do per-file overrides work?
Sections with glob patterns like [*.md] apply settings only to matching files, overriding the global [*] block.
Embed this tool on your site

Free to embed, no attribution required (but appreciated). Paste this where you want the tool to appear: