What is a .editorconfig file?

A plain-text config file, placed in a project, that tells supporting editors and IDEs which indent style, indent size, line ending, charset, and whitespace rules to apply per file pattern. Most modern editors read it natively or via a plugin.

Where do I put the generated file?

Save it as .editorconfig (no filename before the dot) in your project root. EditorConfig-aware editors look for it there and in parent directories unless a section has root = true.

What does root = true do?

It tells EditorConfig to stop searching parent folders once it finds this file. Without it, an editor may also merge in rules from an .editorconfig higher up the directory tree.

What if I leave a field on "Not set"?

That property is omitted from the section entirely, so the editor falls back to its own default or to a matching rule from a less specific pattern.

Does this tool send my settings anywhere?

No. Everything runs in your browser; the file is generated and downloaded locally with no server involved.

EditorConfig Generator

Name: EditorConfig Generator
Availability: InStock
Author: Nham Vu

Pick indent, line ending, and whitespace rules per file glob and get a ready-to-use .editorconfig file.

root = true (stop searching parent folders)

.editorconfig

Summary

Pick indent, line ending, and whitespace rules per file glob and get a ready-to-use .editorconfig file.

How it works

Toggle "root = true" if this file should stop EditorConfig from searching parent directories.
Edit the default sections or add a new one with "Add Section".
Set a glob pattern for each section, such as * or *.py or {package.json,.travis.yml}.
Choose indent style, indent size, end of line, charset, and whitespace options for that pattern.
Copy the generated text or download it as a .editorconfig file.
Place the file in your project root (or any subfolder it should apply to).

Use cases

Standardize indentation across a team using mixed editors (VS Code, JetBrains, Vim).
Force LF line endings for a repo shared between Windows and Unix contributors.
Keep tabs for Makefiles or Go files while using spaces everywhere else.
Strip trailing whitespace on most files but keep it for Markdown line breaks.
Bootstrap a new repository with sane default formatting rules.
Document per-language formatting choices in one readable file.

Frequently Asked Questions

Last updated: 2026-07-23 · Reviewed by Nham Vu