Boneyard Tools

EditorConfig Generator

Pick your indent style, size, line endings and charset, add per-file overrides, and copy a ready-to-use .editorconfig that keeps formatting consistent across editors.

How to generate a .editorconfig

  1. Choose the global defaults: indent style, indent size, line endings and charset.
  2. Add override sections for file types that need different rules, like Markdown or Makefiles.
  3. Copy the generated .editorconfig into the root of your project.

Examples

Two-space spaces with a Markdown override

indent: space, size 2, plus *.md keeps trailing whitespace
root = true

[*]
indent_style = space
indent_size = 2
end_of_line = lf
charset = utf-8
trim_trailing_whitespace = true
insert_final_newline = true

[*.md]
trim_trailing_whitespace = false

Frequently asked questions

What does root = true do?

It tells EditorConfig to stop looking in parent folders for more config files. Put it only in the .editorconfig at the top of your project.

When should I use a tab indent style?

Use tabs for languages and files that require them, such as Makefiles or Go. Add an override section targeting those files with indent_style set to tab.

How do per-file overrides work?

Each override is a section with a glob like *.md or {*.yml,*.yaml}. Only the properties you set are written, and the rest are inherited from the [*] section.

Which editors support EditorConfig?

Many editors support it natively, including modern JetBrains IDEs and Visual Studio. Others, like VS Code, support it through a widely used plugin.

Is my configuration private?

Yes. The file is built entirely in your browser and nothing is uploaded.

Related tools