.editorconfig Generator 🔒 Runs locally in your browser — nothing is uploaded.

Generate an .editorconfig file — indent, charset, per-language overrides.

Global settings [*]

Per-language overrides

About this tool

An .editorconfig file keeps indentation, line endings and charset consistent across every editor and IDE a project's contributors use — VS Code, JetBrains, Vim and more all read it natively, no plugin required for most. Set your global defaults, tick the per-language overrides your project needs (Markdown skips trailing-whitespace trimming since two trailing spaces mean a line break; Makefiles require literal tabs), and copy or download the result.

Everything is generated locally from the options you pick — nothing is uploaded. Drop the file in your repository root next to .git and commit it; editors pick it up automatically for every file below that point.

Frequently asked questions

What does an .editorconfig file actually do?

It tells every editor and IDE that reads it (VS Code, JetBrains, Vim, Sublime and more, natively for most) which indentation, line-ending and charset to use for files in that folder and below — so a project stays consistent no matter which editor a contributor opens it in, without anyone manually configuring their own settings.

Why does Markdown skip trimming trailing whitespace?

In standard Markdown, two or more trailing spaces at the end of a line force a line break in the rendered output — an intentional, if easy-to-miss, piece of syntax. A global trim-trailing-whitespace rule would silently delete that formatting every time someone saves a file, which is why the Markdown override in this generator turns the rule off for .md files specifically.

Do I need a plugin for my editor to read this file?

Usually not. VS Code, JetBrains IDEs (WebStorm, PyCharm, IntelliJ, etc.) and several others support .editorconfig natively out of the box. A handful of older or less common editors do need a small plugin — check your specific editor's documentation if formatting doesn't seem to change after adding the file, but for the mainstream editors most contributors use, it just works.

Is my project configuration uploaded anywhere when I use this?

No. The file is built entirely from the checkboxes and dropdowns you select, right in your browser — there is nothing to upload since no project file is ever read in the first place. Copy the result or download it directly.