Does .editorconfig conflict with Prettier?

They cover different things: .editorconfig tells the editor how to write files, Prettier decides how code is formatted. Prettier reads indent_style, indent_size, max_line_length and end_of_line from .editorconfig by default, so keeping both consistent is enough.

What does root = true mean?

EditorConfig walks up from the file's directory looking for more .editorconfig files; root = true stops the search. The one in your repository root should always have it, or you inherit whatever sits in a parent directory on your machine.

Why keep trailing spaces in Markdown?

Two spaces at the end of a line mean a hard line break in Markdown. An editor that strips them silently joins your lines, so .md turns trim_trailing_whitespace off.

With end_of_line = lf, what else do Windows colleagues need?

Add git config --global core.autocrlf true so files are checked out as CRLF and committed as LF, or pin it in the repository with * text=auto eol=lf in .gitattributes.

⚙️

⚙️.editorconfig Generator - One Indent Style For The Team

Tabs and spaces in the same pull request, CRLF from the one teammate on Windows, a diff that lights up red over trailing whitespace — all of it goes away with a single .editorconfig in the repository root. VS Code, JetBrains, Vim and Sublime all read it, so a new colleague gets the rules by checking out the code. This generator lays the options out as a form and adds the exceptions that must be there: Makefiles need tabs, Markdown needs its trailing spaces.

Free · No sign-up · Runs in your browserLast updated: 2026-10-26

Loading tool...

How to use .editorconfig

1Start from a project preset (front end, Python, Go, Java or a mixed repo)
2Adjust indentation, line endings, charset and line width
3Tick the per file-type exceptions you want
4Copy or download it into the repository root

FAQ

Does .editorconfig conflict with Prettier?: They cover different things: .editorconfig tells the editor how to write files, Prettier decides how code is formatted. Prettier reads indent_style, indent_size, max_line_length and end_of_line from .editorconfig by default, so keeping both consistent is enough.
What does root = true mean?: EditorConfig walks up from the file's directory looking for more .editorconfig files; root = true stops the search. The one in your repository root should always have it, or you inherit whatever sits in a parent directory on your machine.
Why keep trailing spaces in Markdown?: Two spaces at the end of a line mean a hard line break in Markdown. An editor that strips them silently joins your lines, so .md turns trim_trailing_whitespace off.
With end_of_line = lf, what else do Windows colleagues need?: Add git config --global core.autocrlf true so files are checked out as CRLF and committed as LF, or pin it in the repository with * text=auto eol=lf in .gitattributes.